Last updated: November 18, 2026

Privacy policy

How Watch OTP handles Gmail data.

Purpose and access

Watch OTP is operated by the Watch operator for accounts the operator controls. Its sole use of Gmail messages is to retrieve one-time authentication codes and complete the associated account login. Each configured mailbox requires the operator’s Google OAuth authorization.

The integration requests the gmail.readonly permission. This permission permits reading mailbox data; application filters narrow which messages are used for code extraction. The integration does not send, change, delete, forward, or mark emails as read.

Data read and processed

The reader searches messages from the previous day, optionally using subject hints, and fetches up to ten matching messages per search, including message identifiers, sender and subject headers, receipt times, and text or HTML content. It then applies configured sender rules and a login-time cutoff, with a 60-second tolerance, before extracting a code. Messages can be fetched before these application filters are applied.

Mailbox verification also reads Gmail profile metadata, including the mailbox address and message and thread totals. Stored mailbox metadata uses a masked email address.

Storage and retention

OAuth access and refresh tokens are kept in permission-restricted files on the operator’s server and refreshed as needed. They are separate from the mailbox metadata database. The database stores mailbox configuration and status, a masked address, and OTP attempt records such as attempt and mailbox identifiers, timestamps, outcome, diagnostic reasons, message identifier, and message count.

The Gmail reader processes email content and extracted codes in memory. It does not deliberately archive message bodies or store extracted codes in its OTP audit records. Those records may contain diagnostic error text. There is no automatic expiry configured for mailbox metadata or OTP attempt records; they remain until the operator removes them. Token files remain until replaced or removed by the operator.

The authentication system separately stores account secrets and resulting browser session state in an encrypted server-side vault. Browser profiles and authentication diagnostics are managed by that system; they have a separate lifecycle from the OTP reader.

Use and disclosure

Gmail API requests are sent to Google. An extracted code is supplied to the corresponding account’s authentication flow, including the service issuing that code. The Gmail integration has no advertising, marketing, sale-of-data, or model-training function. Access is intended for the operator and the operator-controlled authentication system.

Control, revocation, and deletion

The mailbox owner can revoke Watch OTP access in Google Account connections. Revocation prevents further authorized Gmail access; it does not automatically erase files or records already stored on the operator’s server. The operator can remove the relevant OAuth token files and mailbox or attempt records. Contact the operator through your existing support channel to request deletion or ask about this policy.

This public website

These static information pages do not use cookies, analytics scripts, forms, or a Google sign-in button. Serving a page necessarily processes connection details such as your IP address. The website does not enable HTTP access logging; server operational and error logs may still be recorded.