Data and account access
Privacy, with a narrow purpose.
The application is intended to use one operator’s authorized Google account only to verify the sender and send an approved company-news digest.
Google information and permissions
- Basic identity: the account’s verified email address, stable Google account identifier, issuer and relevant identity-verification claims. Requested scopes:
openidandemail. - Outgoing email: the recipient address, subject, HTML and plain-text digest content, message identifiers and delivery results. Requested permission:
gmail.send. - Authorization credentials: temporary access tokens and an offline refresh token, plus application client credentials, to support authorized unattended delivery.
No mailbox-read, mailbox-search, message-modification or deletion permission is planned. Google’s send permission allows account-level sending; the application’s own approval checks narrow who receives a digest.
Purpose and proposed Limited Use commitment
Google account information would be used to verify the authorized sender, deliver approved messages, diagnose delivery failures and prevent duplicate sends. Company research uses public sources; Google account identifiers, credentials and mailbox data must not be supplied to research models.
Planned Limited Use commitment: Company Watchlist’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data will not be sold, used for advertising or used to train general-purpose AI models. The live integration has not been verified.
Storage and service providers
The planned hosted job runs on Trigger.dev. Google refresh/client credentials and the verified account binding would be held in its server-side secret storage. The setup helper is designed to handle those values through a private local pipe; no live setup has been qualified.
The planned design would store private research, saved digest editions, recipient and message identifiers, and delivery/audit history in Supabase. Google would process outgoing email for delivery.
Proposed human-access restriction: An operator or administrator role alone would not authorize reading Google-derived data. Human review would require the user’s prior affirmative agreement to the reviewer viewing the specific messages, files or other data involved. The only exceptions proposed here are access necessary for security purposes or to comply with applicable law, within Google’s Limited Use requirements. Routine operation, review or support is not a separate exception. These restrictions must be implemented and qualified before live use.
This disclosure site is designed for static hosting on Cloudflare Pages. These pages have no forms, scripts, application cookies, analytics or advertising. The hosting provider may process routine connection/request information under its own practices.
Retention and deletion limits
No automatic deletion schedule or self-service deletion feature is implemented. Research, editions and delivery/audit history are retained until an authorized administrative deletion. Credential and account-binding removal requires separate host administration.
Before live Gmail operation, retention choices must be set and a controlled deletion procedure verified. Provider logs, backups and copies already delivered to a recipient are subject to their respective retention and controls; immediate or complete erasure is not guaranteed.
Disconnecting Google access
The account owner can remove the application’s permission through Google Account connections. Revoking access does not automatically erase saved digests or delivery history.
The operator’s planned shutdown procedure is to disable jobs and sending, revoke active application approvals, remove stored Google credentials and account binding, revoke the Google grant, and separately review and delete stored Google-related data through an approved administrative procedure. That deletion path remains a pre-activation qualification requirement.
Operator and privacy requests
- Operator
- Gavin Blanusa
- Privacy contact
- gavinblanusa@gmail.com
Contact the operator for privacy requests or support. No request deadline or legal compliance guarantee is made by this notice.