BeeChat
Delete account注销账号Create account注册账号

Current Android code review · July 24, 2026当前 Android 代码审查 · 2026 年 7 月 24 日

Data Safety Disclosure数据安全说明

A public summary of the data practices reflected in the current BeeChat master branch and production architecture.依据当前 BeeChat master 分支及生产架构整理的公开数据实践摘要。

Overview概览

  • Data is encrypted in transit using HTTPS or secure WebSocket connections.数据通过 HTTPS 或安全 WebSocket 连接进行传输加密。
  • Supported message and file content is encrypted on the user’s device before upload.受支持的消息与文件内容会在用户设备上完成加密后再上传。
  • BeeOrbit does not sell user data or use it for advertising.BeeOrbit 不出售用户数据，也不将其用于广告。
  • The current app contains no advertising, behavioral-analytics, or crash-reporting SDK. Google Play-capable Android builds include Firebase Core and FCM only for opaque data-only wake hints; FCM auto-initialization is disabled unless that build capability is explicitly enabled.当前应用不包含广告、行为分析或崩溃上报 SDK。支持 Google Play 的 Android 构建仅使用 Firebase Core 与 FCM 接收不透明的纯数据唤醒提示；除非构建时明确启用，否则 FCM 自动初始化保持关闭。
  • Users can request permanent account deletion in the app or on the public web deletion page.用户可以在应用内或公开网页中申请永久注销账号。

Data categories数据类别

Category类别Examples示例Main purpose主要用途
Personal info个人信息Email, username, profile and account identifiers邮箱、用户名、个人资料与账号标识Account, security, support账号、安全与支持
Messages消息End-to-end encrypted payloads and delivery metadata端到端加密载荷与投递元数据Messaging and synchronization消息与同步
Photos, videos and files照片、视频与文件User-selected encrypted media, attachments and BeeDrive files用户选择的加密媒体、附件与 BeeDrive 文件User-requested sharing and storage用户请求的分享与存储
Reports and moderation evidence举报与治理证据Report categories, descriptions, review records, and plaintext or files a reporter explicitly chooses to attach举报分类、说明、审核记录，以及举报人明确选择附加的明文或文件Safety, abuse prevention, enforcement, and appeals安全、滥用防范、规则执行与申诉
Contacts and social graph联系人与社交关系Friend requests, friends, blocked contacts and group membership好友申请、好友、黑名单与群组成员关系Social and safety features社交与安全功能
App activity应用活动Conversation, notification, read, delivery and settings events会话、通知、已读、投递及设置事件Core functionality and service integrity核心功能与服务完整性
Device or other IDs设备或其他标识符Client instance, device registration, session and public-key identifiers; FCM-enabled builds also use a Firebase registration token客户端实例、设备注册、会话及公钥标识；启用 FCM 的构建还会使用 Firebase registration tokenAuthentication, multi-device delivery, security, and message wake-up认证、多设备投递、安全与消息唤醒
Diagnostics and security诊断与安全IP address, user agent, request and security eventsIP 地址、User-Agent、请求及安全事件Fraud prevention, troubleshooting and security防欺诈、故障排查与安全

Not collected by the current Android build当前 Android 版本不收集的类别

The current manifest does not request location, microphone, phone, SMS, call-log, calendar, or address-book permissions. The reviewed dependency set contains no advertising ID, ad network, behavioral analytics, or crash-reporting SDK. BeeChat does not process financial, health, fitness, or web-browsing data as part of its current core features.当前 Android 清单未申请定位、麦克风、电话、短信、通话记录、日历或系统通讯录权限；已审查的依赖中不包含广告 ID、广告网络、行为分析或崩溃上报 SDK。BeeChat 当前核心功能不处理金融、健康、健身或网页浏览数据。

Optional and required data可选与必需数据

Account credentials, basic identifiers, security records, and delivery metadata are required to provide the service. Profile text, avatar, friend relationships, messages, media, BeeDrive files, local backup export, camera-based QR scanning, and notifications depend on features the user chooses to use. Camera, file access, notifications, and foreground real-time service controls are presented at the point of use or in Android settings.账号凭据、基本标识、安全记录与投递元数据是提供服务所必需的。个人资料文本、头像、好友关系、消息、媒体、BeeDrive 文件、本地备份导出、相机扫码及通知取决于用户选择使用的功能。相机、文件访问、通知和前台实时服务控制会在实际使用时或 Android 设置中提供。

Sharing and processing共享与处理

BeeChat uses infrastructure and email processors to provide the service: Tencent-hosted VPS and PostgreSQL, Cloudflare R2, Resend, and Google Firebase Cloud Messaging for enabled Google Play builds. FCM receives the app-instance registration token and configuration needed for delivery; BeeChat sends only an opaque schema and wake ID, not message content or conversation identifiers. Data is not sold. The Play Console answer for ‘data shared’ must remain consistent with the developer’s contracts and Google Play’s service-provider exception; provider processing is described publicly here regardless of the console classification.BeeChat 使用基础设施与邮件处理服务来提供产品，包括腾讯云 VPS 与 PostgreSQL、Cloudflare R2、Resend，以及在启用的 Google Play 构建中使用 Google Firebase Cloud Messaging。FCM 会接收投递所需的应用实例 registration token 与配置；BeeChat 只发送不透明的 schema 和 wake ID，不发送消息内容或会话标识。数据不会被出售。Play Console 中“是否共享数据”的选择必须与开发者合同及 Google Play 对服务提供商的例外规则保持一致；无论控制台最终如何分类，我们都会在此公开说明服务提供商的处理活动。

Deletion and retention删除与保留

See the account deletion section of the Privacy Policy for the exact categories deleted, retained, and left on other users’ devices. The current default server delivery-cache periods are also listed there.账号注销时删除、保留以及仍存在于其他用户设备上的具体数据类别，请参阅隐私政策的账号删除部分；当前服务端默认投递缓存期限也在该政策中列明。

Accuracy notice准确性说明

This disclosure is tied to the reviewed source and must be reviewed again before each Play release whenever permissions, SDKs, providers, authentication, messaging, moderation, storage, or deletion behavior changes.本说明与已审查的源代码对应。每次 Google Play 发布前，如权限、SDK、服务提供商、认证、消息、内容治理、存储或删除行为发生变化，均必须重新审查并更新。