Privacy Policy
Happy Bot is an open-source desktop app and DeepSeek Harness plugin (source code). It runs on your own computer. This policy explains what Happy Bot does with your data, including data from services you connect, such as Google.
Where your data lives
Your team, chats, memories, settings and secrets are stored in Happy Bot's data folder on your computer. Happy Bot does not operate servers that receive this data.
Model providers you choose
To answer you, a Bot sends the conversation, including tool results, to the model provider you configured (for example DeepSeek). That provider's own terms and privacy policy apply. Happy Bot sends nothing to a model provider you have not configured.
Connectors and messaging apps
When you connect a service (for example GitHub, Notion or a mailbox), Happy Bot stores the access token, refresh token or app password in its secret store on your computer. Tokens go only to the service they belong to. They are kept out of chat records and model requests, and by default no Bot's shell can read them. A Bot reads data from a connected service only when it uses that service's tools in a conversation.
When you connect a messaging app (for example Telegram or Feishu), Happy Bot stores the bot credentials on your computer and only processes messages from accounts you have paired.
Disconnecting a service deletes its stored tokens from your computer. You can also revoke Happy Bot's access from the service's own account settings.
Google user data
If you sign in with Google to connect Gmail, Happy Bot requests the gmail.modify scope and your email address (userinfo.email). The sections below state exactly what Google data Happy Bot accesses, how it uses it, who receives it, and how it is protected.
Google data Happy Bot accesses
- Your Google account email address, used to name the connected mailbox in settings.
- Gmail message metadata and content — subjects, senders, recipients, bodies and attachments — when a Bot searches or reads your mail at your request.
- The write access
gmail.modifygrants: creating drafts, sending messages, marking messages read or unread, starring, applying and removing labels, and moving messages between mailboxes including to Trash. Happy Bot never permanently deletes email. - OAuth access and refresh tokens, stored in Happy Bot's secret store on your computer.
How Happy Bot uses Google data
- Only to perform the email actions you or your Bots request inside Happy Bot, and for nothing else.
- Message content a Bot reads is shown in your conversation and sent to the model provider you configured, as described above, so the Bot can work with it.
- No email is sent until you confirm it on a card that shows the recipients and content.
Who receives Google data
- The only third party that can receive Google user data is the model provider you configured yourself, and only the content included in the conversations you direct.
- Happy Bot does not send Google user data to Happy Bot's developers or to any server they run, does not sell it, does not share it with anyone else, and does not use it for advertising or to train models.
- No person reads your Google user data, unless you ask for help and share it yourself.
How Google data is protected
- All processing happens on your computer; Happy Bot operates no servers that receive your Google data.
- OAuth tokens stay in the local secret store. They are kept out of chat records and model requests, by default no Bot's shell can read them, and they are sent only to Google over HTTPS.
- Disconnecting the mailbox deletes the stored tokens. Mail content exists only in the chat records on your computer and is deleted with the conversation.
- You can revoke Happy Bot's access at any time in your Google account settings.
Happy Bot's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Happy Bot complies with the Google APIs Terms of Service and does not use Google APIs for AI-generated Non-Consensual Intimate Imagery (AI NCII).
This website
This site is served as static files. It loads no third-party scripts and sets no cookies of its own.
Changes and contact
We will update this page when Happy Bot's handling of data changes. Questions: open an issue on GitHub. Security reports: use GitHub's private vulnerability reporting for the repository.
隐私政策
Happy Bot 是开源的桌面应用和 DeepSeek Harness 插件(源代码),运行在你自己的电脑上。本页说明 Happy Bot 怎样处理你的数据,包括你连接的服务(例如 Google)的数据。
数据存在哪里
团队、聊天、记忆、设置和密钥都存在你电脑上 Happy Bot 的数据目录里。Happy Bot 不运营接收这些数据的服务器。
你选择的模型服务
为了回答你,Bot 会把对话(包括工具结果)发给你配置的模型服务(例如 DeepSeek),适用该服务自己的条款和隐私政策。你没有配置的模型服务,Happy Bot 不发任何内容。
连接器与聊天软件
连接一个服务(例如 GitHub、Notion 或邮箱)后,Happy Bot 把访问令牌、刷新令牌或授权码存在你电脑上的密钥库里。令牌只发给它所属的服务,不进聊天记录和模型请求,默认任何 Bot 的终端都读不到。只有 Bot 在对话中使用这个服务的工具时,才会读取它的数据。
接入聊天软件(例如 Telegram 或飞书)时同理,机器人凭据存在你电脑上,只处理已配对账号发来的消息。
断开连接会删除电脑上存的令牌。你也可以在该服务自己的账号设置里撤销 Happy Bot 的权限。
Google 用户数据
如果你用 Google 登录来连接 Gmail,Happy Bot 会请求 gmail.modify 权限和你的邮箱地址(userinfo.email)。下面逐条说明 Happy Bot 访问哪些 Google 数据、怎样使用、给谁、以及怎样保护。
Happy Bot 访问的 Google 数据
- 你的 Google 账号邮箱地址,用来在设置里给连接的邮箱命名。
- Gmail 邮件的元数据和内容——主题、发件人、收件人、正文和附件——当 Bot 按你的要求搜索或阅读邮件时。
gmail.modify授予的写入能力:创建草稿、发送邮件、标记已读或未读、加星标、应用和移除标签、在文件夹之间移动邮件(包括移入垃圾箱)。Happy Bot 永不永久删除邮件。- OAuth 访问令牌和刷新令牌,存在你电脑上 Happy Bot 的密钥库里。
Happy Bot 怎样使用 Google 数据
- 只用来完成你或你的 Bot 在 Happy Bot 里要求的邮件操作,没有其他用途。
- Bot 读到的邮件内容会显示在对话里,并按上文发给你配置的模型服务,供 Bot 处理。
- 每封邮件都要你在显示收件人和内容的卡片上确认后才会发出。
Google 数据给谁
- 唯一可能收到 Google 用户数据的第三方是你自己配置的模型服务,且只限你指示的对话里包含的内容。
- Happy Bot 不把 Google 用户数据发给 Happy Bot 的开发者或他们运营的任何服务器,不出售,不分享给任何其他人,不用于广告或训练模型。
- 除非你求助时自己提供,没有人会查看你的 Google 用户数据。
Google 数据怎样被保护
- 全部处理都在你的电脑上完成;Happy Bot 不运营接收你 Google 数据的服务器。
- OAuth 令牌只存在本机密钥库,不进聊天记录和模型请求,默认任何 Bot 的终端都读不到,只通过 HTTPS 发给 Google。
- 断开邮箱连接会删除已存的令牌。邮件内容只存在于你电脑上的聊天记录里,随对话一起删除。
- 你可以随时在 Google 账号设置里撤销 Happy Bot 的访问权限。
Happy Bot 对从 Google API 获得的信息的使用和向其他应用的传输,将遵守 Google API Services User Data Policy,包括其中的 Limited Use 要求。
Happy Bot 遵守 Google API 服务条款,不将 Google API 用于生成非自愿私密图像(AI NCII)。
本网站
本站以静态文件形式提供,不加载第三方脚本,本身不设置 Cookie。
变更与联系
Happy Bot 处理数据的方式变化时,我们会更新本页。有问题请在 GitHub 提 Issue;安全问题请用仓库的私密漏洞报告。