Overview
This Data Security Policy sits beside the Bandhu Privacy Policy. It explains, in consumer language, how Bandhu is designed to protect your information. It does not claim a certification, named encryption standard, or audit that has not been completed.
Prepared on 1 September 2026. Effective for the product at founding-batch launch.
Security chain
Bandhu’s protection is designed as a sequence: your companion, your account identity, your personalized cloud, encrypted communication, your permissions, Master Voice, a secure passphrase where required, then the authorized action.
We keep that explanation conceptual. Publishing internals would not make you safer.
Identity
Bandhu establishes a protected relationship between the registered user identity and the authorized Bandhu device. Cryptographic processing combines those identities to derive unique credentials for your environment.
Your email address and a device hardware address are not used as a raw encryption key.
Personalized cloud
Each Bandhu user is associated with a personalized cloud environment. Bandhu establishes a protected relationship between the registered user identity and the authorized Bandhu device. Cryptographic processing combines the account identity and device identity to derive unique security credentials used to protect the user's personalized environment.
Storage and infrastructure run on Google Cloud. Communication with Bandhu’s servers is designed to be encrypted in transit.
Master Voice
Master Voice verifies the authorized user. A secure passphrase, generated for selected sensitive actions and shown only in the Bandhu mobile application, confirms authorization for that action.
See the Privacy Policy’s Master Voice Security section for the full description.
Incidents
If a security incident affects your personal information, we will work to contain it and notify you as the law requires. We do not publish a fake response-time promise.
Contact
Questions about security belong on the Support page, or with a Grievance Officer once one is named on the Privacy Policy.