BeeChat
Delete accountCreate account

Current Android code review · July 19, 2026

Data Safety Disclosure

A public summary of the data practices reflected in the current BeeChat master branch and production architecture.

Overview

  • Data is encrypted in transit using HTTPS or secure WebSocket connections.
  • 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.
  • The current app contains no advertising, behavioral-analytics, crash-reporting, or FCM remote-push SDK.
  • Users can request permanent account deletion in the app or on the public web deletion page.

Data categories

CategoryExamplesMain purpose
Personal infoEmail, username, profile and account identifiersAccount, security, support
MessagesEnd-to-end encrypted payloads and delivery metadataMessaging and synchronization
Photos, videos and filesUser-selected encrypted media, attachments and BeeDrive filesUser-requested sharing and storage
Contacts and social graphFriend requests, friends, blocked contacts and group membershipSocial and safety features
App activityConversation, notification, read, delivery and settings eventsCore functionality and service integrity
Device or other IDsClient instance, device registration, session and public-key identifiersAuthentication, multi-device delivery and security
Diagnostics and securityIP address, user agent, request and security eventsFraud prevention, troubleshooting and security

Not collected by the current Android build

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.

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.

Sharing and processing

BeeChat uses infrastructure and email processors to provide the service: Tencent-hosted VPS and PostgreSQL, Cloudflare R2, and Resend. 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; infrastructure-provider processing is described publicly here regardless of the console classification.

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.