Replai — Privacy Policy

Last updated: 2026-10-25

Replai is operated by Guangzhou Dawnhan Technology Co., Ltd. (广州丹浛科技有限公司), the personal information handler (data controller) that processes your personal information under this Privacy Policy. “We”, “us” and “our” below refer to this company. Contact: hello@replai.email

This Privacy Policy explains how Replai (“the App”) handles your information. Replai is an AI-assisted email client. We designed it to keep as much of your data on your device as possible; some features require sending data to the cloud, as described below.

1. Information We Process

Category	What	Why
Email account credentials	IMAP/SMTP passwords or OAuth tokens for Google/Microsoft accounts you connect	To connect to your mailbox and send/receive email, and to deliver new-mail push notifications while the App is closed. Stored in the device Keychain. To power server-side new-mail detection: for password-based accounts, the app-specific mail password is also stored on our backend encrypted with AES-256-GCM; for Google/Microsoft accounts, the OAuth tokens needed to keep mail-notification subscriptions alive are stored on our backend encrypted with AES-256-GCM: a short-lived access token and, where your Google/Microsoft account grants offline access, a refresh token that lets our server renew the subscription while the App is closed (we never receive your Google/Microsoft account password). Server-side credentials are erased automatically when the last device connected to that mailbox is unlinked, including by removing the account or signing out on that device. Removing it from one device keeps notifications working on your other connected devices. Temporary backend failures can delay cleanup.
Email content	Message text, subjects, recipients, attachments of accounts you connect	Cached locally to display your mail. Relevant content is sent to the AI model provider for manual cloud AI features (reply, summary, cloud translation, compose, form fill), automatic organization within the scope you enable, and cloud risk explanations when available while you view suspicious mail. See Section 2 for the content and conditions for each use.
Subscription identity	A user identifier and, where available, name/email from Sign in with Apple, Google, or WeChat	To identify your subscription/entitlement and track usage across platforms.
Purchase & usage data	Subscription status, credit balance, and usage counts	To provide and meter paid features. Payment card details are handled by Apple; we never receive them.
Device & diagnostic data	Device push token, app version, coarse network reachability, and diagnostic logs	To deliver push notifications and diagnose backend connectivity. Logs may contain account email addresses, mail-change identifiers, and technical information; they are not fully anonymous. Credential redaction is applied to diagnostic logs attached to feedback as described below.
Feedback (optional feature)	Your description, required contact email, basic app/device information, selected photos/videos, and diagnostic logs if enabled	When you submit feedback, our HTTPS service sends it to hello@replai.email through Tencent Enterprise Mail. The contact email is used for follow-up and need not be a connected account. Logs are enabled by default and can be disabled; credentials are redacted, but email addresses and technical information may remain. Review photos/videos for private content before sending. This feature does not use your mailbox to send email.
Contacts (optional)	Contact suggestions you allow	To help address emails and fill forms, and to correct names in dictated drafts. Matching is done on-device; when you use cloud AI compose, the matching contact names/addresses are included in that request (see Section 2). Only granted when you permit.
In-app browser data (optional)	Cookies, remembered usernames, and website passwords you choose to save in Replai’s built-in browser	To keep you signed in to sites you open from your mail. Stored only on your device (Keychain / WebKit storage) and never sent to us; removed when you clear web data or website passwords in Settings, clear web data in Storage Management, or reinstall the App. Independent of your Replai account sign-in state.
Voice input (optional)	Speech you dictate	Converted to text using Apple’s Speech framework (on-device where supported, otherwise Apple’s speech service). We do not store your audio.

2. Cloud AI Processing

Replai sends the content needed for a cloud AI feature directly from the App to the AI model provider over an encrypted connection to generate the feature's result. This can occur in the following situations:

Manual features: when you request a reply, summary, cloud translation, compose assistance, or form fill, the request includes the relevant mail or other content needed for that task.
Automatic mail organization: this is off until you choose to enable it. Once enabled, mail within your selected scope may be processed automatically, including message text and relevant existing knowledge-center context. You can change the scope or turn automatic organization off in its settings; each message does not require a separate action.
Risk explanations for suspicious mail: local rules first evaluate a message when you view its details. If suspicious signals are found and the cloud explanation feature is available, the App may automatically send the subject, detected signal types, and a cleaned and shortened body excerpt to the AI provider for an explanation. The local detection itself does not require that request.

Local translation and on-device speech do not send content to an AI model provider. Knowledge-center records and cached AI results are stored on your device, but generating or updating them through cloud AI involves the processing described above.

Google account and Gmail data

Mail features on your device: when you connect Gmail, Replai uses your Google authorization to read and display messages and attachments, search mail, send messages, and update mail organization such as labels, read state, and stars. These functions process the relevant message contents, addresses, and mailbox metadata.
New-mail notifications: our backend creates and renews Gmail notification subscriptions (watch), receives mailbox-change notifications through Google Cloud Pub/Sub, and uses change identifiers to find new messages. For notification previews, it requests Gmail message metadata with the From and Subject headers and sends the sender/subject through Apple's push service to your registered devices. This notification flow does not retrieve Gmail message bodies or attachments.
Offline authorization: Google OAuth credentials are kept in your device Keychain. The access token and, when you grant offline access, refresh token needed for background notifications are also stored on our backend encrypted with AES-256-GCM. This allows notification subscriptions to be renewed while the App is closed. We do not receive your Google account password. The multi-device retention and removal rules in Sections 1, 5, and 6 apply.
AI features: Gmail content may be sent from the App to the AI model provider under the manual and automatic processing conditions in Section 2. This is separate from the backend notification flow described above.

3. Where Data Is Stored

On your device: email cache, drafts, extracted “memory” entities, subscription/credit state, and settings are stored locally (including Keychain for credentials).
Our backend (Firebase / Google Cloud): push registration tokens, configuration delivery, and the credentials needed for new-mail push described in Section 1 (app-specific mail passwords and Google/Microsoft OAuth access/refresh tokens encrypted with AES-256-GCM; encryption keys kept in a separate secret store). To detect new mail our server reads only message envelopes (sender, subject, date, read state) and relays sender/subject in the notification; we do not store your email content on our backend. Feedback that you separately choose to submit is processed in transit; only submission status, digests, and rate-limit metadata are stored as described in Section 5.

4. How We Share Information

We share information only as needed to run the App:

AI model provider — the mail and other content needed for the manual and automatic cloud AI processing described in Section 2, to generate results.
Tencent Enterprise Mail — the feedback you choose to submit, delivered to our support mailbox for follow-up.
Apple — for in-app purchases, subscriptions, and push notifications.
Google / Microsoft — for email account authentication (OAuth), mailbox access and mail operations, and server-side notification subscriptions when you connect those accounts.
Google Firebase / Cloud — for our backend (push, remote configuration, and processing feedback submissions).
Tencent (WeChat) — only if you choose “Sign in with WeChat”: the WeChat app returns a one-time authorization code, which our backend exchanges for your WeChat user identifier and, if you permit it, your nickname and avatar. We never receive your WeChat password, contacts, or chat history.

We do not sell your personal information or use your email content for advertising.

Third-party SDKs

SDK	Provider & purpose	Data it may access
WeChat Open SDK	Shenzhen Tencent Computer Systems Co., Ltd. — used only to start WeChat sign-in and receive the authorization result. It is not initialized unless WeChat sign-in is configured in the build.	Device identifiers, network status, and whether WeChat is installed. See open.weixin.qq.com for Tencent’s developer terms and privacy documentation.

5. Data Retention

Locally stored data remains until you delete it, remove the account, or uninstall the App. Content sent for cloud AI processing is used to generate your result and is not retained by us for other purposes. Push tokens and configuration data are retained while your installation is active. Server-side mail credentials (Section 1) are retained only while the account is connected on at least one of your devices, and are erased automatically when its last connected device is unlinked. Temporary backend failures can delay cleanup.

Feedback content is processed in transit by our backend and retained in our support mailbox through Tencent Enterprise Mail as needed to handle your request. Our backend keeps only submission digests/status and hashed rate-limit records, with submission records scheduled for deletion after 30 days and rate-limit records after their one-hour window. Automatic deletion may take additional time after expiry. To request deletion of feedback content, contact hello@replai.email. Unsent feedback forms are not saved to disk or retained as feedback drafts after you leave the page.

6. Your Choices & Rights

Remove a connected email account at any time in Settings to stop processing that mailbox on that device. Its server-side push credentials are erased when the last connected device is unlinked.
For Gmail, the last-device cleanup also attempts to stop the Gmail notification subscription and revoke the backend's offline authorization. These external steps can fail temporarily. You can independently remove Replai's access to your Google Account on Google's third-party connections page; see Google's instructions for removing account access. Removing access prevents further access under that authorization, but does not by itself erase data previously downloaded or saved by Replai. Remove the mailbox in the App and contact us for other deletion requests.
Sign out of your subscription identity in the App.
You can turn automatic mail organization off and avoid requesting manual cloud AI features. This does not disable the separate cloud risk-explanation behavior described in Section 2.
Uninstalling the App removes locally stored data.
Depending on your region, you may have rights to access, correct, or delete personal data — contact us to request.

7. Security

Credentials are stored in the device Keychain; network traffic uses TLS. Mail credentials stored on our backend for push delivery are encrypted at rest with AES-256-GCM, with encryption keys held in a separate secret store; plaintext exists only transiently in memory to establish mailbox connections and is never written to logs. Configuration delivered by our backend is signed. No method of transmission or storage is 100% secure, but we take reasonable measures to protect your data.

8. Children

Replai is not directed to children under 13 (or the minimum age in your jurisdiction). We do not knowingly collect data from children.

9. International Transfers

Your data may be processed in countries other than your own (including where our AI provider and cloud infrastructure operate). We rely on encryption and appropriate safeguards for such transfers.

10. Changes

We may update this Policy; material changes are reflected in the “Last updated” date.

11. Contact

Privacy questions or requests: hello@replai.email

Replai — 隐私政策

最后更新:2026-10-25

Replai 由广州丹浛科技有限公司(Guangzhou Dawnhan Technology Co., Ltd.)运营,该公司是按本隐私政策处理你个人信息的个人信息处理者;下文中的“我们”均指该公司。联系邮箱:hello@replai.email

本隐私政策说明 Replai(“本应用”)如何处理你的信息。Replai 是一款 AI 辅助邮件客户端,我们尽量将数据保留在你的设备本地;部分功能需将数据发送至云端,详见下文。

1. 我们处理的信息

类别	内容	用途
邮箱账号凭证	你连接的账号的 IMAP/SMTP 密码,或 Google/Microsoft 的 OAuth 令牌	用于连接你的邮箱、收发邮件,并在应用未运行时投递新邮件推送。凭证存储于设备钥匙串(Keychain)。为实现服务端新邮件检测:口令类邮箱的专用密码会以 AES-256-GCM 加密后存储于我们的后端;Google/Microsoft 账号则将维持邮件通知订阅所需的 OAuth 令牌以 AES-256-GCM 加密后存储于我们的后端:短期有效的访问令牌,以及在你的 Google/Microsoft 账号授予离线访问权限时用于在应用未运行期间续订通知的刷新令牌(我们不会收到你的 Google/Microsoft 账号密码)。当该邮箱最后一台关联设备解绑时(包括在该设备移除账号或登出),服务端凭证将自动抹除。仅从一台设备移除时,其他关联设备仍可接收通知。后端临时故障可能使清理延后。
邮件内容	你连接账号的邮件正文、主题、收件人、附件	本地缓存用于显示邮件。手动云端 AI 功能(回复、总结、云端翻译、撰写、表单填充)、你开启的范围内的自动整理，以及查看可疑邮件时可用的云端风险解释，会将所需内容发送给 AI 模型方。各类处理的内容与条件见第 2 节。
订阅身份	来自 Apple、Google 或微信登录的用户标识,以及(如有)姓名/邮箱	用于识别你的订阅/权益并跨平台统计用量。
购买与用量数据	订阅状态、credit 余额、使用次数	用于提供并计量付费功能。支付卡信息由 Apple 处理,我们不会接触。
设备与诊断数据	推送令牌、App 版本、粗粒度网络可达性、诊断日志	用于推送通知与后端连通性诊断。日志可能包含账号邮箱地址、邮件变更标识和技术信息，并非完全匿名。反馈所附诊断日志会进行凭据脱敏，详见下文。
反馈(可选功能)	问题描述、必填的联系邮箱、基本 App/设备信息、所选图片/视频，以及开启时附加的诊断日志	你主动提交后，由我们的 HTTPS 服务通过腾讯企业邮投递至 hello@replai.email。联系邮箱用于后续沟通，无需是已绑定账号。诊断日志默认开启、可关闭；凭据会脱敏，仍可能保留邮箱地址和技术信息。发送前请检查图片/视频中的私人内容。此功能不使用你的邮箱发件。
通讯录(可选)	你授权的联系人建议	用于填写收件人和表单,以及纠正语音口述稿中的人名。匹配在设备本地完成;使用云端 AI 撰写时,匹配到的联系人姓名/地址会随该次请求一并发送(见第 2 节)。仅在你授权时启用。
内置浏览器数据(可选)	你在 Replai 内置浏览器中选择保存的 Cookie、登录账号与网页密码	用于保持你在从邮件打开的网站上的登录状态。仅存于你的设备(钥匙串 / WebKit 存储),不会发送给我们;在设置中清除网页数据或网页密码、在存储管理中清理网页数据、或卸载重装 App 时删除,与 Replai 账号的登录状态无关。
语音输入(可选)	你口述的语音	通过 Apple 语音框架转为文字(支持时在设备本地,否则使用 Apple 的语音服务)。我们不存储你的音频。

2. 云端 AI 处理

Replai 会将云端 AI 功能所需的内容，通过加密连接从 App 直接发送给 AI 模型方，以生成该功能的结果。这可能发生在以下场景:

手动功能:当你请求回复、总结、云端翻译、辅助撰写或表单填充时，请求会包含完成该任务所需的邮件或其他相关内容。
自动整理邮件:此功能默认关闭，需由你选择开启。开启后，所选范围内的邮件可能自动处理，包括邮件正文及知识中心已有的相关上下文。你可以在自动整理设置中调整范围或关闭功能；每封邮件无需单独操作。
可疑邮件风险解释:查看邮件详情时，先由本地规则评估邮件。若发现可疑信号且云端解释功能可用，App 可能自动将主题、命中的信号类型，以及经过清洗和截断的正文片段发送给 AI 模型方生成解释。本地检测本身不需要这次请求。

本地翻译和设备端语音不会向 AI 模型方发送内容。知识中心记录和 AI 结果缓存保存在你的设备上，但通过云端 AI 生成或更新这些内容时，仍会发生上述处理。

Google 账号与 Gmail 数据

设备上的邮件功能:连接 Gmail 后，Replai 使用你的 Google 授权读取和显示邮件及附件、搜索邮件、发送邮件，以及更新标签、已读状态、星标等邮件整理信息。这些功能会处理相关邮件内容、地址和邮箱元数据。
新邮件通知:我们的后端创建并续订 Gmail 通知订阅(watch)，通过 Google Cloud Pub/Sub 接收邮箱变更通知，并利用变更标识查找新邮件。为生成通知预览，后端请求包含 From 和 Subject 邮件头的 Gmail 元数据，再通过 Apple 推送服务向你的已注册设备发送发件人/主题。此通知流程不读取 Gmail 邮件正文或附件。
离线授权:Google OAuth 凭证保存在设备钥匙串中。后台通知所需的访问令牌，以及你授予离线访问时提供的刷新令牌，还会以 AES-256-GCM 加密保存在我们的后端，用于在 App 关闭时续订通知。我们不会获取你的 Google 账号密码。多设备留存与移除规则见第 1、5、6 节。
AI 功能:在第 2 节所述手动和自动处理条件下，Gmail 内容可能由 App 发送给 AI 模型方。这与上述后端通知流程是不同的数据处理路径。

3. 数据存储位置

你的设备本地:邮件缓存、草稿、提取的“记忆”实体、订阅/credit 状态与设置(凭证存于钥匙串)。
我们的后端(Firebase / Google Cloud):推送注册令牌、配置下发,以及第 1 节所述用于新邮件推送的凭证(专用密码以及 Google/Microsoft 的 OAuth 访问/刷新令牌以 AES-256-GCM 加密存储,密钥保存在独立的密钥管理服务中)。为检测新邮件,我们的服务器仅读取邮件信封信息(发件人、主题、日期、已读状态)并在通知中转发发件人/主题;我们不在后端存储你的邮件内容。你另行选择提交的反馈经后端中转，后端仅保存第 5 节所述的提交状态、摘要和限流元数据。

4. 信息共享

我们仅在运行应用所必需时共享信息:

AI 模型方——第 2 节所述手动和自动云端 AI 处理所需的邮件及其他内容，用于生成结果。
腾讯企业邮——你主动提交的反馈内容，用于投递至支持邮箱并跟进处理。
Apple——用于应用内购买、订阅与推送通知。
Google / Microsoft——当你连接相应账号时，用于邮箱认证(OAuth)、邮箱访问与邮件操作，以及服务端通知订阅。
Google Firebase / Cloud——用于我们的后端(推送、远程配置、反馈提交中转)。
腾讯(微信)——仅当你选择“微信登录”时:微信客户端返回一次性授权码,由我们的后端换取你的微信用户标识,以及(在你授权的前提下)昵称与头像。我们不会获取你的微信密码、通讯录或聊天记录。

我们不会出售你的个人信息,也不会将你的邮件内容用于广告。

第三方 SDK 清单

SDK 名称	提供方与用途	可能获取的信息
微信开放平台 SDK(WeChat Open SDK)	深圳市腾讯计算机系统有限公司——仅用于发起微信登录并接收授权结果;未配置微信登录的构建不会初始化该 SDK。	设备标识信息、网络状态、是否安装微信。腾讯的开发者条款与隐私说明见 open.weixin.qq.com。

5. 数据留存

本地存储的数据在你删除、移除账号或卸载应用前一直保留。发送给云端 AI 处理的内容仅用于生成结果,我们不为其他目的留存。推送令牌与配置数据在你的安装有效期内保留。服务端邮箱凭证(见第 1 节)仅在该账号仍连接于你的至少一台设备期间保留,当最后一台关联设备解绑时自动抹除;后端临时故障可能使清理延后。

反馈内容经我们的后端中转，并由腾讯企业邮支持邮箱按处理请求所需保留。后端仅保留提交摘要/状态和限流哈希记录，提交状态在 30 天后、限流记录在一小时窗口结束后进入自动删除流程，到期后实际删除可能有所延迟。可联系 hello@replai.email 请求删除反馈内容。未发送的反馈表单不保存到磁盘，离开页面后不会保存为反馈草稿。

6. 你的选择与权利

随时在设置中移除已连接的邮箱账号,以停止在该设备处理该邮箱;最后一台关联设备解绑后,其服务端推送凭证会自动抹除。
对于 Gmail，最后一台设备解绑后的清理还会尝试停止 Gmail 通知订阅并撤销后端离线授权；这些外部操作可能暂时失败。你也可以独立前往 Google 的第三方关联页面移除 Replai 对 Google 账号的访问权限，操作方法见Google 移除账号访问权限说明。移除权限后，Replai 无法继续通过该授权访问 Google 账号，但这不会直接删除 Replai 此前已下载或保存的数据。请同时在 App 中移除邮箱，其他删除请求可联系我们。
在应用内登出订阅身份。
你可以关闭自动整理邮件，并不主动请求手动云端 AI 功能；这些操作不会关闭第 2 节所述的独立云端风险解释行为。
卸载应用即删除本地存储的数据。
依你所在地区,你可能有权访问、更正或删除个人数据——可联系我们请求。

7. 安全

凭证存储于设备钥匙串;网络传输使用 TLS。为推送而存储于后端的邮箱凭证以 AES-256-GCM 静态加密,密钥保存在独立的密钥管理服务中;明文仅在建立邮箱连接时短暂存在于内存,绝不写入日志。后端下发的配置经过签名。没有任何传输或存储方式是 100% 安全的,但我们采取合理措施保护你的数据。

8. 儿童

Replai 不面向 13 岁以下(或你所在司法辖区的最低年龄)儿童。我们不会有意收集儿童数据。

9. 跨境传输

你的数据可能在你所在地以外的国家/地区处理(包括我们的 AI 提供方与云基础设施所在地)。我们对此类传输采用加密及适当保障措施。

10. 变更

我们可能更新本政策;重大变更将体现在“最后更新”日期。

11. 联系方式

隐私相关问题或请求:hello@replai.email