隐私政策
更新日期：2026年10月21日
适用范围与联系
本政策说明 Ailyre 网站、账号、AI 速递订阅、Design MCP 和留言功能如何处理个人信息。Ailyre 由 Neo / Isshin 运营。隐私、账号和安全问题可联系 [email protected]。
Google 登录
你选择 Google 登录后，我们从 Google 获取用于登录的基础身份资料，例如稳定的账号标识、名称、邮箱、邮箱验证状态及组织域（如有）。这些信息用于识别账号、验证邮箱和关联已有 Ailyre 账号。Google 登录资料不用于广告定向或训练通用 AI 模型。我们不获取你的 Google 密码，也不通过登录权限读取 Gmail 邮件或 Google Drive 文件。用于校验身份的 Google 访问令牌不会作为长期 Google 访问凭据保存。
GitHub 登录
你选择 GitHub 登录后，我们获取用于登录的基础公开资料，例如稳定的账号标识、用户名、名称，以及你已验证的邮箱地址。这些信息用于识别账号、关联已有 Ailyre 账号和订阅；无法验证邮箱时，你仍可通过邮箱验证码完成验证。我们不获取你的 GitHub 密码，也不申请代码仓库读取或修改权限。用于校验身份的 GitHub 访问令牌不会作为长期 GitHub 访问凭据保存。GitHub 登录资料不用于广告定向或训练通用 AI 模型。
账号与服务数据
邮箱验证码登录会处理邮箱、验证码校验记录和登录会话。Linux DO 登录会处理其账号标识和必要公开资料。按你实际使用的功能，我们还会处理订阅偏好与投递记录、MCP Key 的哈希与调用用量记录，以及你主动提交的留言或服务请求。验证码、会话凭据和 Key 用于身份校验与服务访问，不应公开分享。
用途与服务提供方
信息用于登录和账号管理、你选择的服务、邮件投递、故障排查及防止滥用。Google 和 GitHub 分别处理其自身的登录认证；托管及 Cloudflare 等网络服务处理必要请求信息；邮件服务商（包括 Brevo 中继）处理收件地址和完成投递所需的邮件内容。MCP 会处理你主动提交的请求。我们不出售 Google 或 GitHub 登录资料；仅为提供上述功能和处理必要的安全问题使用这些资料。第三方服务也适用其自身的隐私政策。
Cookie、本地存储与日志
网站使用 Cookie 保存登录会话和授权流程状态，并可在浏览器本地保存语言、声音等偏好。服务器和网络服务可能记录 IP 地址、请求时间、路径、状态码等安全及运行日志。关闭必要 Cookie 可能影响登录。
保存与删除
账号、订阅及相关记录会按提供服务、处理投递和安全审计所需保存。你可以联系上述邮箱申请访问、更正或删除自己的资料；我们会先核对身份，并说明可删除的范围及需要保留的必要记录。退订、防止重复投递和安全审计可能需要保留最小记录；备份也可能影响删除完成的时间。
你的选择
登录本身不会自动订阅 AI 速递。你可在订阅管理页调整偏好或退订，在账号页撤销 MCP Key，并在 Google 或 GitHub 账号设置中撤销 Ailyre 的相应授权。撤销第三方登录授权不会自动删除 Ailyre 账号或取消独立邮件订阅；如需进一步处理，请联系我们。
更新
当功能或数据处理方式变化时，我们会更新本页；涉及新的数据用途或额外第三方登录权限时，会提供相应说明和授权流程。
Privacy Policy
Updated: 21 October 2026
Scope and contact
This policy describes how the Ailyre website, accounts, AI briefing subscriptions, Design MCP and guestbook handle personal information. Ailyre is operated by Neo / Isshin. Contact [email protected] about privacy, accounts or security.
Sign in with Google
When you choose Google sign-in, we obtain basic identity information such as a stable account identifier, name, email address, verification status and hosted domain, where provided. We use it to identify your account, verify your email and link an existing Ailyre account. Google sign-in data is not used for targeted advertising or to train general-purpose AI models. We do not receive your Google password or use sign-in permissions to read Gmail messages or Google Drive files. Google access tokens used to verify identity are not retained as long-term Google access credentials.
Sign in with GitHub
When you choose GitHub sign-in, we obtain basic public profile information such as a stable account identifier, username and name, along with your verified email addresses. We use it to identify your account and link an existing Ailyre account and subscription. If an email cannot be verified through GitHub, you can verify it with an email code. We do not receive your GitHub password or request permission to read or modify repositories. GitHub access tokens used to verify identity are not retained as long-term GitHub access credentials. GitHub sign-in data is not used for targeted advertising or to train general-purpose AI models.
Account and service data
Email-code sign-in processes your email address, verification records and login sessions. Linux DO sign-in processes its account identifier and necessary public profile information. Depending on the features you use, we also process subscription preferences and delivery records, MCP key hashes and usage records, and messages or service requests you submit. Verification codes, session credentials and keys support authentication and access; do not share them publicly.
Purposes and service providers
We use information for sign-in, account management, services you select, email delivery, troubleshooting and abuse prevention. Google and GitHub each handle their own authentication. Hosting and network providers, including Cloudflare, process necessary requests. Email providers, including the Brevo relay, process recipient addresses and message contents needed for delivery. MCP processes requests you choose to submit. We do not sell Google or GitHub sign-in data; we use it to provide these functions and address necessary security issues. Third-party services have their own privacy policies.
Cookies, local storage and logs
Cookies support login sessions and authorization state. Browser storage may retain language, sound and other preferences. Servers and network services may log IP addresses, request times, paths and status codes for security and operation. Blocking essential cookies may prevent sign-in.
Retention and deletion
Account, subscription and related records are retained as needed to provide services, handle delivery and support security audits. You may contact us to request access, correction or deletion of your information. We first verify ownership and explain what can be deleted and which necessary records must remain. Unsubscribe handling, duplicate-delivery prevention and security auditing may require minimal records; backups may also affect when deletion is complete.
Your choices
Signing in does not automatically subscribe you to the AI briefing. You can change preferences or unsubscribe through subscription management, revoke MCP keys in your account, and remove Ailyre authorization in your Google or GitHub account settings. Revoking third-party sign-in authorization does not automatically delete your Ailyre account or cancel an independent email subscription. Contact us for further assistance.
Updates
We update this page when features or data practices change. New uses of data or additional third-party sign-in permissions will have corresponding notices and authorization flows.
ailyre