SunupMail Privacy Policy
Updated November 9, 2026. Applies to SunupMail 0.8.4.
Data and purposes
SunupMail provides Gmail organization, classification, reminders, reading and writing assistance. Gmail Local reads metadata already displayed in Gmail and stores account-scoped mailbox indexes, rules, contacts, notes, reminders, projects and preferences in the browser. The local index holds up to 1,000 metadata records.
Local settings sync uses a verified SunupMail device login or requests the verified email identity from Google. SunupMail registers the email address and issues a credential for this mailbox. It encrypts the setup completion time, confirmed contact categories, stars, and rules on its server. The settings travel over HTTPS and can be restored after confirming the same mailbox on another device.
In Outlook on the web, SunupMail organizes the visible mail list and can display the currently opened message in its reader. The integration uses the existing Outlook web session and processes Outlook mail and settings on the device.
After users choose and authorize Advanced, the Gmail API processes subjects, senders, recipient roles, dates, bodies or snippets, conversations and labels needed for selected features. With Cloud AI and automatic storage consent, the server encrypts synchronized mail, AI inputs and results, classifications, relationships and personal settings. Scheduled processing uses separate Google offline authorization and can continue after the browser closes until disabled or deleted.
Email verification processes addresses, codes and device credentials. Subscription and quota features retain corresponding settings and usage counters. Reading, questions and reply assistance send only information needed for the selected feature.
Automatic background checks are off by default and require a separate in-app confirmation for each mailbox. If enabled, the server checks new or changed mail at an administrator-configured interval and sends eligible content to the configured AI services using the existing plan allowance, even when the browser is closed. Turning this feature off stops future automatic rounds; analysis of already stored mail can finish, and a separately enabled daily schedule remains in effect. Gmail authorization, storage consent and AI consent are still required.
Transfers and processors
Gmail Local keeps mail on the device by default. If users enable Cloud AI and select a message for analysis, that request uses the disclosed Cloud AI processing. Advanced uses HTTPS. Cloud AI connects directly to the commercial APIs of Alibaba Cloud Model Studio (Qwen), Volcengine Ark or BytePlus ModelArk (Doubao), OpenAI (GPT), Google (Gemini), and Anthropic (Claude). The server enables a provider after its commercial account terms, processing region and retention have been verified. Eligible accounts must prohibit general-purpose model training on Gmail data and data derived from it.
Before enabling Cloud AI, the in-app confirmation shows which of these providers are active for the mailbox, their primary or fallback models, processing regions, retention and purposes. A request can go to a disclosed fallback when an earlier attempt fails. Changes to the disclosed processing facts pause AI transfers until the user confirms the updated disclosure.
Chrome Identity normally manages browser Google authorization. During Disconnect & delete, the current mailbox's browser access token may be sent over HTTPS and temporarily encrypted with server tokens solely to submit Google revocation requests. Tokens are not sent to model providers.
We do not sell Google user data, use it for advertising, or train general-purpose AI models with it. Access and transfers are limited to disclosed user-facing features, necessary security handling and legal obligations. Our use of Google Workspace data adheres to the Google API Services User Data Policy, including Limited Use requirements.
Retention and security
Server mail fields, AI content and Google tokens are encrypted using server data protection. Browser extension storage isolates local data. Synchronized records and personal settings support selected ongoing features and remain until deleted. Reader conversation caches expire after at most seven days. Signing out of a device, pausing jobs and withdrawing AI consent are distinct from complete account data deletion.
Local diagnostics support connection troubleshooting without mail bodies, tokens or verification codes, and are limited to seven days, 2,500 entries and 2 MB. Administrators can enable diagnostic uploads for an individual SunupMail user; this is off by default. While enabled and the browser is online, Advanced periodically uploads that user's redacted metadata to the SunupMail backend in addition to retaining it locally. Uploaded diagnostics are available only to administrators and are limited to seven days and 20,000 entries per user. Disabling uploads stops new server collection; existing uploads expire with retention or are removed with account deletion. Server request logs exclude request bodies, authorization headers and raw mail identifiers; operational retention must match the actual deployment.
Background task records contain account/mailbox identifiers, message and AI request identifiers, timing, counts, statuses and error codes, without mail bodies or Google tokens. Completed, failed and cancelled rounds are retained for 30 days after completion; unfinished or paused rounds remain until resolved, cancelled or the account is deleted. Account deletion removes the user's task records and message associations as well as the synchronized content.
Disconnecting and deleting data
Open SunupMail Manage → System configuration → Disconnect access and delete data. Choose Disconnect & delete SunupMail data, type the full account email, and confirm. No active subscription is required. If signed out, a separate deletion code verifies the mailbox without enabling AI or renewing Gmail authorization.
Once accepted, the server stops the user's synchronization, schedules and AI processing, invalidates sessions and credentials, and fences older writes. Deletion covers the SunupMail user's linked mailboxes, cached mail, conversation snapshots, AI inputs and results, contacts, categories, rules, notes, projects, subscription and quota settings, and personal account data. Corresponding browser extension data is cleared. Used redemption codes lose user identity associations and remain unusable.
Deletion affects SunupMail copies. Original Gmail messages, drafts and labels remain. It does not cancel third-party payments or automatically issue refunds. Data already sent to AI processors remains subject to their disclosed retention and deletion arrangements; clearing SunupMail's database does not by itself confirm erasure of every processor copy.
The interface distinguishes unconfirmed submission, processing, pending revocation and completion. Closing a dialog does not cancel an accepted request. To recover lost responses, the browser may retain a deletion receipt and the SunupMail credential needed to submit the request until acceptance is confirmed; ordinary sign-in credentials are then removed. Tokens needed for failed Google revocations are encrypted and retried for up to seven days, then destroyed. Successful revocation destroys them immediately. Unconfirmed revocations after the deadline are reported with instructions for manual removal in Google account settings.
After processing completes, minimal deletion and restoration-prevention records remain for 30 days, including random receipts, internal account identifiers, email digests and revoked-credential digests. They contain no mail content or plaintext Google tokens. Completed local receipts are cleared on subsequent startup or checks. Other devices running an updated extension that supports deletion clear caches if they connect during this period; manually clear extension data or uninstall on older versions and devices that remain offline longer.
Online deletion does not imply immediate per-record erasure from backup media. The application does not itself create database backups. If operators separately enable infrastructure backups, they must disclose actual retention and reapply deletion records during restoration so deleted data does not become active again.
Controls and contact
Users can remove access in Google third-party connections, but this does not delete data already held by SunupMail. Uninstalling or clearing local extension storage is also not a substitute for server deletion.
See data deletion help. Contact support through the SunupMail Issue Tracker; do not put mail content, verification codes or credentials in public issues.
Material changes to purposes require policy updates and user confirmation where applicable. Chrome Web Store disclosures, OAuth consent and actual service configuration must match this policy.