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.

SunupMail 隐私政策

更新于 2026 年 11 月 9 日,适用于 SunupMail 0.8.4。

数据与用途

SunupMail 提供 Gmail 整理、分类、提醒、阅读和写作辅助。Gmail Local 读取页面已显示的邮件元数据,在浏览器中保存按账号隔离的邮箱索引、规则、联系人、笔记、提醒、项目及配置。邮箱索引最多保存 1000 条元数据。

Local 设置同步可复用已验证的 SunupMail 设备登录,或向 Google 请求已验证的邮箱身份。SunupMail 登记邮箱地址并签发该邮箱的同步凭据,在后台加密保存初始化完成时间、确认的联系人归类、重要标记和规则。设置通过 HTTPS 传输,其他设备确认同一邮箱后可恢复。

在 Outlook 网页版中,SunupMail 整理可见的邮件列表,也可在阅读器中显示当前打开的邮件。此功能使用现有的 Outlook 网页会话,邮件与设置在浏览器本机处理。

Advanced 在用户选择并授权后,通过 Gmail API 处理所选功能需要的邮件标题、发件人、收件角色、时间、正文或片段、会话和标签。用户确认 Cloud AI 和自动存储后,后台会加密保存同步邮件、AI 输入及结果、分类、关系和个人配置。后台定时处理使用独立的 Google 离线授权,关闭浏览器后仍可运行,直至停用或删除。

邮箱验证处理邮箱地址、验证码和设备登录凭据;订阅和额度功能保存相应配置及使用计数。阅读、问答和回复辅助仅发送所选功能需要的内容。

后台自动检查默认关闭,每个邮箱须在应用内单独确认开启。开启后,服务器按管理员设置的间隔检查新增或变化邮件,使用现有套餐额度将符合分析条件的内容交给已配置的 AI 服务,关闭浏览器后仍会执行。关闭此功能后停止后续自动轮次,已入库邮件的分析可继续完成,独立启用的每日定时处理继续保留。此功能仍需有效的 Gmail 后台授权、邮件存储同意和 AI 使用同意。

传输与第三方处理

Gmail Local 默认将邮件数据留在本机。用户启用 Cloud AI 后主动选择某封邮件分析时,该请求按已披露的 Cloud AI 方式处理。Advanced 使用 HTTPS。Cloud AI 直连阿里云 Model Studio(千问)、火山方舟或 BytePlus ModelArk(豆包)、OpenAI(GPT)、Google(Gemini)和 Anthropic(Claude)的商用 API。服务商启用前须核实实际商用账号的条款、处理地区与留存安排。账号条款须禁止将 Gmail 原始和衍生数据用于通用模型训练。

启用 Cloud AI 前,应用内同意页显示此邮箱实际启用的服务商、主用和备用模型、处理地区、留存与用途。前一次调用出现允许切换的故障时,同一请求可能发给已披露的备用服务商。披露内容变化后,系统暂停向 AI 服务传输数据,等待用户确认更新后的披露。

Google 浏览器授权通常由 Chrome Identity 管理。执行“断开并删除”时,当前邮箱的浏览器访问令牌可能经 HTTPS 发送至后台,与后台授权令牌一起加密暂存,仅用于向 Google 提交撤销请求,不会发送给模型服务商。

我们不出售 Google 用户数据,不将其用于广告或通用 AI 模型训练。访问和传输限于已披露的用户功能、必要的安全处理及法律义务。Google Workspace 数据的使用遵守 Google API Services User Data Policy,包括 Limited Use 要求。

保存与安全

后台邮件字段、AI 内容和 Google 令牌通过服务端数据保护机制加密保存;本机数据由浏览器扩展存储隔离。同步记录和个人设置用于持续提供用户选择的功能,保留至用户删除;阅读会话缓存最多保留 7 天。退出设备、暂停任务和撤回 AI 使用同意,不等同于完整删除数据。

本机诊断信息仅用于排查连接和运行问题,不包含邮件正文、令牌或验证码,最多保留 7 天、2500 条、2 MB。管理员可按 SunupMail 用户开启诊断日志上传,默认关闭。开启后,Advanced 扩展在浏览器在线时定期将该用户的脱敏元数据上传至 SunupMail 后台,同时保留本机记录;已上传日志仅供管理员查看,最多保留 7 天、每用户 20000 条。关闭上传后停止新增收集,已有上传记录按保留期过期,或随账号删除一起清除。服务器请求日志不记录请求正文、授权头或原始邮件标识,其运维保留安排须与实际部署一致。

后台任务记录包含账号/邮箱标识、邮件及 AI 请求标识、时间、数量、状态和错误码,不包含邮件正文或 Google 令牌。已完成、失败或取消的轮次在结束后保留 30 天;未完成或暂停的轮次保留至解决、取消或删除账号。账号删除同时清理该用户的任务记录、邮件关联和同步内容。

断开授权与删除数据

在 SunupMail“管理 → 系统配置 → 断开授权与删除数据”中,点击“断开并删除 SunupMail 数据”,输入完整账号邮箱并确认。订阅过期仍可操作;登录失效时可通过独立删除验证码验证邮箱,无需重新开启 AI 或重新授权 Gmail。

服务器受理后立即停止该用户的同步、定时任务和 AI 处理,使设备凭据和会话失效,并阻止旧请求写回。删除范围覆盖该 SunupMail 用户的关联邮箱、邮件缓存、会话快照、AI 输入和结果、联系人、分类、规则、笔记、项目、订阅及额度配置等个人数据,本机同步清理对应扩展数据。已使用的兑换码移除用户身份关联并保持不可再次使用。

删除针对 SunupMail 数据副本;Gmail 原始邮件、草稿和标签保持不变。此操作不代表取消第三方付款或自动退款。AI 服务商已接收的数据受其已披露的留存与删除安排约束,不能仅凭 SunupMail 数据库清空宣称已清除服务商全部副本。

界面分别提示未受理、处理中、撤销待重试和完成状态。关闭弹框不会取消已受理请求。为恢复丢失的响应,本机可暂存删除回执及提交请求所需的 SunupMail 设备凭据,服务器确认受理后清除普通登录凭据。Google 撤销失败所需的令牌最多加密保留 7 天用于重试,成功即销毁;超过期限销毁令牌,并提示用户在 Google 账号中手动移除授权。

服务器完成处理后,随机回执、内部账号标识、邮箱摘要和已撤销凭据摘要等必要的删除及防恢复记录保留 30 天,不包含邮件内容或明文 Google 令牌。本机已完成回执在后续启动或查询时清理。其他运行支持删除功能的新版本扩展的设备在此期间连接时会清理缓存;旧版本或长期离线设备需手动清理扩展数据或卸载扩展。

在线删除不等于备份介质上的逐条即时擦除。应用本身不创建数据库备份;若运营环境另行启用备份,运营方必须披露实际保留周期,并在恢复时重新应用删除记录,避免数据恢复为活动状态。

管理与联系

用户也可在 Google 第三方连接管理 撤回权限,但这不会自动删除 SunupMail 已保存的数据。卸载扩展或清理本机存储,也不替代服务器删除。

操作说明见 数据删除帮助。支持联系入口为 SunupMail Issue Tracker,公开问题中请勿提交邮件内容、验证码或凭据。

数据用途发生重大变化时会更新政策,并按适用要求取得确认。Chrome 商店披露、OAuth 授权界面和实际服务配置须与本政策一致。