Privacy
Your messages stay yours.
Bharat Connect (BC) is an officer-approved communications app for iPhone, iPad, and Android. It is an independent product — not an official app of the Indian Army, Ministry of Defence, or any government. We do not sell personal data, we do not show ads, and we do not use an advertising ID.
Message text is end-to-end encrypted. Plaintext and conversation keys stay on your device. The unit server cannot read your chats.
Encrypted message copies and account records are held by the unit Core so delivery works when someone is offline. This is not a fully server-less messenger.
When you start mesh, approved handsets nearby discover each other over Bluetooth and the local network. That hop is device-to-device.
How chat works
BC uses the unit Core as a ciphertext relay. You send an encrypted blob; the other person decrypts it on their handset. We never store readable chat text, and we cannot decrypt it.
Encrypted messages, delivery metadata (conversation id, timestamps, sender id), and chat files are stored so a message still arrives if the other person is offline or on another approved device. Voice calls use encrypted media between handsets; call setup goes through Core. Unit broadcasts from command are stored so they can be delivered to the roster.
We do not claim that “no data is stored on any server.” Account data and encrypted chat copies are stored. What we do claim: operators cannot read your private chat contents.
Data we process
Enrollment
- Service members: full name, service number, and a hash of identity last-4 digits. We never collect a full Aadhaar or other complete identity number.
- General users: full name and a mobile number, stored as an enrollment handle. General users cannot browse the contact directory.
Device
A device identifier, platform (iOS or Android), and coarse last-known location used only to confirm the authorized-territory geo-fence and to show last-seen to unit admins. Location is not used for advertising and is not collected in the background.
Messages and files
Ciphertext and metadata as described above. Filenames for chat files are stored as ciphertext. Files are held so recipients can download them; view them in the app.
Admin audit
Command-console actions (approve, revoke, lock, wipe) are logged for the unit that operates this deployment.
Permissions (iPhone, iPad, and Android)
BC asks only for what a feature needs. You can refuse optional permissions; some features then stay off. System wording differs slightly by platform.
- Location (while using the app): confirms you are within authorized Indian territory. Not used for ads. Not collected in the background.
- Bluetooth and local network: asked when you start offline mesh, to discover nearby approved devices.
- Microphone: only when you place or accept a voice call or record a voice note.
- Camera: only when you capture a photo for chat or your profile. BC does not provide video calling.
- Photos and files: the system picker on iOS and Android. BC does not request full photo-library or all-files access.
- Notifications: optional alerts for messages and unit broadcasts.
- Face ID, Touch ID, or other biometrics: optional unlock. PIN always works. Biometric data never leaves the device.
Contact directory
Service members can search approved contacts to start chats, including with general users. General users cannot list or search the unit directory. Once a service member opens a thread, both sides can chat.
Who can see data
- Unit officers who operate the command console, for enrollment and device control.
- Infrastructure that hosts this deployment (database and file storage for Core).
- We do not sell data. We do not share it with advertisers. We do not use an advertising ID.
Push services (Apple Push Notification service or the equivalent on Android) may receive a device token and a generic wake-up. Push payloads do not include message plaintext.
Retention
Enrollment and device records last for as long as you remain on the unit roster, or until you or an officer delete the account. Encrypted chat copies and files are kept so history can be delivered, subject to disappearing-message settings and unit policy. Audit logs are kept for command accountability.
BC is intended for authorized adults in a unit. It is not directed at children.
Account deletion
In the app: Settings → Delete account. That removes your enrollment and personal records from the unit server and erases local keys. Officers can also delete a directory entry. Step-by-step instructions: Delete your account.
Contact
Privacy questions: Support. The operator of this deployment is the unit that hosts Bharat Connect.