Bcall

BCALL US LTD

Privacy policy

Effective: 1 October 2026

BCALL US LTD develops and operates Bcall. This policy covers our website, shared account and calling services, and Bcall for iPhone, including development versions. The Android privacy policy gives additional platform-specific details. Contact support@bcall.us with privacy questions or requests.

Your personal link and chosen public profile are visible to visitors. Calls need access to your microphone; video needs camera permission. You can read this policy and contact support without signing in. These static information pages do not load analytics scripts.

Account deletion and data requests

Account and public profile

When you sign up or sign in, Firebase Authentication processes your email, authentication credentials and account identifier. Google sign-in provides identity and profile information; Bcall does not receive your Google password. In supported iPhone versions, Sign in with Apple provides an account identifier and the name and email you choose to share. If you choose Hide My Email, Apple provides a private relay address instead of your personal email. Bcall does not receive your Apple password. Linking Apple to an existing Bcall account requires your consent and keeps that account’s personal link and data. We use your account identifier, email, chosen link, display name, profile information and preferences to provide the service. Public profile information, including a profile image or headline if configured, is shown to visitors to your link.

Availability, working hours, time zone and Do Not Disturb preferences control when calls reach you. We use account and authentication information to protect access, respond to account requests and prevent misuse.

Calls and device information

We transmit live microphone audio to connect participants. In clients supporting video, camera video is transmitted when you turn it on. Bcall for iPhone does not offer call recording; its camera stops when the app enters the background, while an active audio call can continue. Media may travel directly between participants or through relay infrastructure. The other participant may independently capture information received during the conversation.

We store call metadata, including caller-provided names or reasons, call times, duration, outcome, participating receiver identifiers and technical connection events. This supports call history, missed-call notifications, operation of calls and troubleshooting. The calling website can send the referring site's hostname and a country code derived from network location, and collect browser or device information. These records are separate from live call media.

To deliver calls to a receiving device, we process an installation or receiver identifier, platform, app version and push-notification tokens. Bcall for iPhone uses Apple's push services and CallKit; incoming and missed-call notifications can include a caller label and call identifiers. Notification details can appear on your lock screen according to your device settings.

Servers, hosting providers and network services process IP addresses and connection information to deliver traffic, diagnose failures and prevent abuse. The iPhone app does not request your address book or precise location. Microphone and camera permissions control capture. Your device settings control notifications and related permissions.

Website analytics and local storage

The interactive Bcall website uses Google Analytics and Mixpanel to understand visits and feature usage, and Microsoft Clarity for interaction analytics. Information can include page and referring-site information, browser and device details, approximate network location, language, interaction events and identifiers stored in cookies or browser storage. On personal calling pages, Mixpanel associates events with the public Bcall link name. These services are not included in the native iPhone app.

The website also uses browser storage for language preferences, authentication and temporary call state. The iPhone app uses Firebase and the device Keychain for sign-in, and local preferences for its installation identifier, language and receiving settings. Clearing browser storage removes locally saved choices; it does not delete your server account. You can manage or block cookies and website storage in your browser. Blocking required storage or scripts may prevent sign-in or calling.

Support and older Bcall features

When you contact us, we receive your email address, message and any information or attachments you choose to provide. We use them to answer your request and investigate the issue.

Older Bcall clients and account features can hold recording, voicemail or transcription data when those features are used. These are separate from the current iPhone app, which does not offer recording or voicemail. Such files may be stored by shared services, including Google Cloud Storage, and are included where applicable in the account-deletion process.

Who receives information

Information is shared with the people you communicate with as described above and with providers needed to operate Bcall: Google Firebase for authentication, Apple for Sign in with Apple, private email relay and iPhone push delivery, MongoDB Atlas for server data, Cloudflare for delivery and security, hosting and relay providers for calls, and the website analytics providers listed above. Android uses Firebase Cloud Messaging for push delivery; see its separate policy. Processing and storage can take place outside your country.

We require service providers handling personal information on our behalf to protect it consistently with this policy and applicable requirements, and to use it for the services they provide. Their own privacy notices describe their services: Firebase, Google, Apple, MongoDB, Cloudflare, Mixpanel and Microsoft.

We may also disclose information when required by law or when necessary to protect the service, investigate abuse or protect people's rights and safety.

Retention and deletion

Account, profile, preferences and receiver records are kept to operate your account until removed or the account is deleted. Modern call-session history is configured to expire approximately 90 days after a call ends; database expiry is asynchronous. Older call records do not necessarily have the same retention period.

Account deletion removes the shared Bcall account and profile, personal-link configuration, receiver registrations and associated call records, and requests deletion of the Firebase identity. Associated legacy recording or voicemail files, if present, are included in the server deletion process. Temporary failures can require retries.

Operational logs, support correspondence, backups and records controlled by service providers are separate from automated account deletion and may remain afterwards. Retention may be needed for security, legal obligations or resolving disputes. Support can handle requests about retained information and explain any applicable limitation. Deletion cannot remove information another participant has independently kept.

Your choices and requests

Depending on applicable law, you may also have rights to object to or restrict processing and to complain to your local data-protection authority. Withdrawing consent does not affect processing that occurred before withdrawal. Some information is necessary to provide your account or calls. See account deletion for more detail.

Children and changes

Bcall is intended for a general audience aged 13 and over and is not designed for children under 13. Where local law requires parental permission, it must be obtained before use. Contact us if you believe a child under 13 has provided personal information.

We update this policy when our practices change and display the effective date above. For questions about this policy or the organization responsible for your data, contact BCALL US LTD at support@bcall.us.