Bcall for Android

Privacy policy

Effective: 14 September 2026 · Operator: BCALL US LTD

Bcall lets people call you through your personal link. This policy explains the information used by the Android app (us.bcall.android) and its account and calling services. Contact support@bcall.us for privacy questions or data requests.

Your account and preferences

Firebase Authentication handles sign-in with Google or email and password. Bcall uses your Firebase account identifier, email and profile information to associate your personal link, display name and preferences with your account. Google sign-in provides an identity credential; Bcall does not receive your Google password. Availability, working hours, time zone and Do Not Disturb settings control how calls are routed.

Device registration and notifications

When you enable incoming calls, we associate an installation/receiver identifier, a Firebase Cloud Messaging token, app version and platform with your account. These identify the device that should receive a call. Notifications can contain a caller label, call and device identifiers, expiry and a temporary scoped authorization token. Notification details may appear on your lock screen, depending on Android settings.

Calls and history

We process live microphone audio to connect you with the caller. If you enable video, we process live camera video too. The camera stops when the app enters the background; audio continues for the active call. Ending the call stops capture. Media can travel directly between participants or through a relay server. Participants may have their own ability to capture information they receive.

We store call metadata such as caller-provided labels or reasons, call times, duration, outcome, participating receivers, and technical connection events. Connection diagnostics include transport and candidate types used to establish a call. These records support call history, missed-call notifications and troubleshooting; they are separate from live audio and video.

Network information and permissions

Our servers and service providers process IP addresses and connection metadata to route traffic, prevent abuse and operate the service. The browser calling service can receive a country code derived from the caller's network location. The Android app does not request precise location, contacts or SMS access. Microphone and notification access support calls; camera access is requested for video, and Bluetooth access is optional for compatible audio accessories.

Service providers and other Bcall products

Google Firebase provides authentication, installation identifiers and push delivery. We use MongoDB Atlas for server data, Cloudflare for web/network delivery and security, and hosting and relay infrastructure to operate Bcall. Google Cloud Storage is also used by shared legacy Bcall services. Providers process information needed for their respective services; processing can occur outside your country.

The Android app has no advertising placements and does not include Firebase Analytics or Crashlytics. Related Bcall websites and older clients can use additional services, including Google Analytics and Mixpanel for visits and usage, and speech/recording services for legacy features. This policy does not imply those products have the same data flows as Android. These static privacy and deletion pages do not load analytics or advertising scripts.

Your public profile is visible to visitors, and call information and media are delivered to the people you communicate with. We may also disclose information when required by law or necessary to protect the service and its users.

Storage and deletion

Account, profile, preferences and enabled receiver records are retained to operate your account until they are removed or the account is deleted. Modern call-session history is configured to expire approximately 90 days after the call ends; database expiry runs asynchronously. Legacy call records from other Bcall products do not necessarily use this same period.

Server logs, support correspondence and backup copies are separate from the automatic call-history expiry. The automated account-deletion process does not erase every such copy immediately. Privacy requests concerning retained information are handled through support, including any retention needed for security, resolving disputes or legal obligations. Provider-controlled records also follow the relevant provider's retention and deletion practices; see Firebase privacy information.

To request deletion in the app, end any active call and go to Settings → Account → Delete account. Verify ownership with Google or your password. You can also request deletion without installing the app. The server removes the shared Bcall account/profile, receiver registrations and associated call records and requests removal of the Firebase identity. Temporary failures can require retries. Deleting a shared account also affects other Bcall clients using that account.

Your choices and age

You can change availability, disable receiving on this device, sign out, and manage Android microphone, camera, notification and Bluetooth permissions. Bcall for Android is intended for a general audience aged 13 and over and is not designed for children under 13. Where parental permission is required by local law, it must be obtained before using the service. If you believe a child under 13 has provided personal information, contact us.

Depending on applicable law, you may request access, correction, deletion or a copy of your information, or object to or restrict certain processing. Send requests to support@bcall.us; we may need to verify account ownership. Do not send passwords. We update this page when our practices change.