1. About this policy
This policy applies to BChat for Android, BChat Web and this BChat information website. “BChat,” “we” and “us” refer to the team operating the BChat app. Our privacy contact is info@arabbg.com.
This policy describes the app’s data handling, including optional features when you use them. It does not make a feature available if that feature or its server support is disabled in your version.
2. Information we handle
| Information | What it includes and why |
|---|---|
| Account and sign-in | A Firebase user identifier and, when phone sign-in is used, your phone number and verification information. Guest access, where available, also creates an account identifier. Authentication and anti-abuse services process technical verification information. |
| Profile and presence | The name, profile photo, status, country, city, area, school, university and work details you choose to provide, plus online or last-seen information. Public profile information is available to other signed-in users for discovery and communication. |
| Messages and media | Message text, photos, video, voice messages, files, sender and recipient identifiers, timestamps and delivery/read status. Internet messages and their attachments are stored using Firebase to deliver conversations and display history. |
| Optional features | Location information for maps and nearby discovery; business or group details you submit; reports, block relationships and related message identifiers or evidence. Public business listings may include a contact number, address and map position. |
| Technical information | Push-notification registration tokens, app and device information, network information such as IP address, and security or operational events processed by the services that authenticate accounts, deliver content, display maps and protect the app. |
BChat Web
BChat Web uses Firebase phone-number verification to sign into the same account as the Android app. Google reCAPTCHA helps prevent abuse. The browser keeps sign-in information for the browser session by default. If you select “Keep me signed in,” Firebase stores sign-in information on that device until you sign out or clear browser data. Loaded profiles and messages are held in memory; BChat does not enable persistent browser chat storage. Sign out on shared devices. Messages you send on the web are stored in the same Firebase conversations. Phone-only Bluetooth history, contact links and local tools do not automatically sync to the web. Reading messages on the web does not currently mark them as seen. Web Nearby can use your browser location, only when you request it and allow permission, to sort people by approximate distance. This location stays in browser memory and does not enable cloud location sharing. The web world map displays already-shared approximate areas. Newer map records use approximately 500-metre display circles; older nearby-sharing records show a broader area and are labeled accordingly. Web map tiles are served by OpenStreetMap, whose servers receive network and requested-map-area information when you open or move the map. See OpenStreetMap Foundation privacy information. Shops and Help include registered listings and the published directories used by the Android app. Selecting a listing’s map, source or telephone link opens the external service you choose.
Information kept on your phone
Contact-name links use the Android contacts you select; BChat does not upload your address book through this feature. Personal expense and company cash/sales ledgers are stored in local app databases. If you export or share a statement, the information goes to the destination you choose.
On-device message translation uses downloaded ML Kit models. Its translation input is processed on your device; ML Kit may send SDK performance and usage metrics to Google. Optional read-aloud features may use your device’s configured text-to-speech service, whose processing depends on that service and your settings.
If you enroll your own voice for personal message readings, the reference recording is stored in the app’s private, account-scoped storage on your phone. Generated message readings are uploaded as audio and shared with the intended recipient. Deleting the saved reference voice stops future use on that phone; it does not remove audio already sent to others.
3. Location and map sharing
You can view the worldwide people map without enabling sharing. If you enable Appear and grant location permission, BChat reads your device location locally and uploads a coarse area-cell identifier. The map uses the cell’s centre to display an approximate area of about 500 metres. This is an approximate-area display, not a guarantee of anonymity or a minimum distance between the pin and your actual position.
Your area pin, profile name and photo can be visible to other signed-in users worldwide, subject to blocking controls. The current map feature refreshes location while its map screen is open; it does not request background-location permission. Turn Appear off to request removal of the shared map record.
Pins stop appearing after approximately five minutes without a fresh captured location. Expiry hides a pin and restricts access; it does not itself delete the stored record. If your removal request cannot reach the server, removal may wait for connectivity.
The separate approximate-area sharing feature, where available, shares more broadly rounded area cells and stops treating a location as current after 24 hours. Shop discovery and map selection may also use your current position locally. If you publish a business address or map position, that listing can be public; the people-map privacy area does not apply to business listings.
4. How information is used
- Create and protect accounts, verify sign-in and prevent abuse.
- Deliver messages, attachments, notifications and requested voice readings; maintain chat history and delivery status.
- Show profiles, nearby or worldwide map areas and business or group information you choose to share.
- Operate block and report features, investigate misuse and respond to support or privacy requests.
- Provide the optional local tools and device integrations you select.
6. Permissions and your controls
- Location: optional for map sharing and local discovery functions. You can deny or revoke it in Android settings.
- Camera and microphone: used when you take photos or videos, record voice messages, or enroll a reference voice.
- Photos and files: the items you choose can be read and uploaded when you send or publish them.
- Contacts: optional access for linking existing contacts or creating a contact you request.
- Bluetooth/nearby devices: used to discover, connect and exchange supported messages with nearby Bluetooth devices.
- Notifications: used to notify you about incoming activity if you allow them.
You can edit your profile, disable sharing, block users and use available deletion controls. Denying a permission can limit its associated feature. Turning off a permission does not automatically erase information already stored in the cloud or held by another person.
7. Storage and retention
Account records, profiles, cloud messages and uploaded files can remain stored while the account and content are maintained. They are not automatically erased merely because you close the app, sign out or uninstall it. They remain until removed through available controls or an account/content-deletion request is fulfilled, subject to the exceptions below.
Local settings, contact links, voice reference files and ledgers remain in the app’s device storage until you remove them through available controls or Android removes that app data. Files exported outside the app and copies held by recipients are separate.
Clear chat and account deletion are different. A clear-chat or hide-history action may affect only the view on your phone. It does not necessarily remove cloud messages, attachments or the other participant’s copy. For cloud-account deletion, use the request process below.
Some information may need to be retained to comply with law, handle disputes, prevent fraud or investigate safety reports. When responding to a verified deletion request, we will explain any applicable retained categories and reasons. Provider backups and security records may follow their own retention schedules.
8. Request account or data deletion
You can request deletion of your BChat account and associated data by emailing info@arabbg.com with the subject BChat account deletion request. This request route is available without signing into BChat or this webpage.
- Identify the BChat account: provide its account/user ID or the phone number used for sign-in, and the profile name if helpful. If you use a guest account, contact us before uninstalling or clearing app data so ownership can still be verified.
- Tell us whether you want to delete the whole account or particular data.
- We will verify ownership before acting, assess the request, and explain its handling and any information that must be retained.
Account-deletion requests cover the account/authentication record and associated profile, shared map records, messages and uploads under BChat’s control, subject to verification and legitimate legal or security retention. We cannot remove screenshots, downloads, forwarded content or other independent copies held by recipients. Never send your password, SMS verification code or payment details in a request.
Privacy and deletion contact
info@arabbg.com
This opens your email app. A request is sent only when you choose to send it; this webpage does not submit or delete anything automatically.
9. Security
BChat uses service authentication, access controls and encrypted network connections for its cloud services. These controls do not make every message end-to-end encrypted. Internet chat content is stored in Firebase, and this policy does not promise end-to-end encryption. No method of transmission or storage is completely secure.
The homepage and privacy-information pages do not include tracking scripts, an advertising SDK or analytics. BChat Web includes the Firebase sign-in form, Firebase SDKs and Google reCAPTCHA needed for authentication and chat. The hosting platform may process request and security logs, including IP addresses, to serve and protect the webpage.
10. Children and guardians
Public profiles, messaging and optional location sharing can reveal personal information to other users. Parents or guardians who believe a child’s information has been provided or shared inappropriately can contact info@arabbg.com to request review and removal. Do not include a child’s sensitive information in a public profile or business listing.
11. Privacy requests and policy changes
Contact info@arabbg.com with questions or requests to access, correct or delete information, or exercise privacy rights available under applicable law. We may need to verify the account to protect it against unauthorized requests.
We will update this webpage when the policy changes and revise the date above. Where applicable law or a material change requires additional notice or consent, we will provide it through an appropriate channel.