Privacy Policy

1. Information we process

• Discord account and server information: When you sign in through Discord, we process your account ID, username or display name, avatar, server memberships, and permissions to identify you and determine which servers you may manage. We also process server IDs, names, icons, and configuration needed to provide the service.
• Monitoring configuration: Service names, monitored bot IDs, website or API addresses, game server addresses, repository integration settings, and notification destinations that you configure.
• Monitoring results: Service status, timestamps, response times, errors, and status history, depending on the type of monitor.
• Integration and authentication information: Discord OAuth access tokens, API credentials, webhook destinations, and integration tokens used for features you enable. Do not post these values in public support channels.
• Operational information: Application errors and service events used to operate and troubleshoot Watcher. Requests also expose connection information, such as an IP address, to the servers handling them.
• Support information: Information you choose to provide when contacting us.

2. Discord presence monitoring

Watcher uses Discord's Guild Presences intent to observe the reported online/offline presence of other bot accounts configured as monitored services in servers shared with Watcher. This supports status displays, timestamped status history, and outage/recovery notifications.

The presence event handler forwards the server ID, account ID, presence status, and event timestamp to Watcher's backend. The backend checks whether the account is configured as a monitored service before storing a status transition. Because filtering currently occurs in the backend, presence events for accounts that are not monitored, including human accounts, may also be transmitted to that backend for this check.

Stored presence-monitoring records contain the monitored account ID, associated server IDs, and timestamped online/offline transitions. Online, idle, and Do Not Disturb are treated as online. The presence handler does not forward activity names, custom statuses, device/client presence details, or message content.

Reported Discord presence is not a complete application-health check: an account appearing online does not guarantee that its commands or external services are functioning.

3. How information is used

Watcher processes information to authenticate dashboard users, check server-management permissions, operate configured monitors and integrations, display service status and history, deliver notifications, and diagnose service problems. Discord message content is not needed to determine a monitored bot's presence status.

4. Where information is processed and shared

Monitoring configuration and results, including stored presence transitions, are processed outside Discord in Watcher's backend and database. Infrastructure providers handling those systems may process the information needed to deliver their services.

Configured service status and history are made available through Watcher's dashboard and service interfaces. Notifications and enabled integrations send relevant information to the Discord channels, webhooks, or other destinations configured for those features. The people who can view those destinations may see the information sent there.

Discord and any external services you connect have their own privacy policies. For Discord's practices, see the Discord Privacy Policy.

5. Login and cookies

The dashboard uses cookies for Discord OAuth state verification and your login session, including your Discord account ID and OAuth access token. The OAuth state cookie is configured to expire after 15 minutes, and login cookies after 24 hours. Logging out clears the login cookies in your browser.

You can block or clear cookies using your browser settings, but authentication and dashboard features may stop working. You do not need to sign in or accept a login cookie to read this policy.

6. Retention and deletion

Monitoring records are stored to provide service configuration and historical status information. Stored bot presence history does not currently have a fixed automatic expiration period; records may remain until removed through service cleanup or a deletion request. Do not assume that removing a monitor immediately erases all historical records.

Server-removal cleanup attempts to remove that server's configuration and references from shared monitoring records. A monitored service may remain in the database if it is still associated with another server. Information already delivered to Discord channels or external notification destinations is subject to those destinations' own controls and retention practices.

To request deletion of information associated with your account, server, or bot, contact us using the support link below. Include the relevant Discord IDs and describe the records concerned. We may need to verify that you own or are authorized to manage the account, server, or bot before acting on a request.

7. Your choices and requests

• Server administrators can change or remove configured monitors and notification destinations, and can remove Watcher from their server.
• You can log out of the dashboard and revoke Watcher's authorization in Discord's Authorized Apps settings.
• Bot operators and users can contact support with questions or requests concerning access, correction, deletion, or an objection to presence processing. Removing a monitor is not a global opt-out if another server still monitors the same account, and does not prevent all incoming presence events from being processed.

Depending on your location, you may have additional rights under applicable data protection law. Please contact us to discuss a request.

8. Contact and policy changes

Contact the Watcher team through our Discord support server for privacy questions and data requests. Ask how to submit sensitive details privately rather than posting credentials or personal information in public channels.

We may update this policy as the service or its data practices change. The latest version will be available on this page with an updated revision date.