Security at BodhX
How we host BodhX, protect the database and the credentials you connect, and control who on your team sees what.
Where BodhX runs
Our servers run on Amazon Web Services in the Mumbai region (ap-south-1), and our PostgreSQL database is hosted in the same region. Some providers we use, such as the AI and messaging services, process data outside India; the Privacy Policy says which.
The database
Every table has row-level security switched on with no access policies, so it denies all access by default. The database's public API roles have no access; customer traffic reaches it only through our application, which scopes each request to the signed-in workspace.
Credentials you connect
Most access tokens, OAuth tokens and API keys for your channels and connectors are encrypted with AES-256-GCM when they are saved, and are decrypted only on our servers when BodhX needs to use them. We are moving the rest, including older stored credentials, to the same protection.
Who on your team sees what
Each team member signs in with their own account and holds one role. The role decides which pages and actions they can use and which agents they can reach. Only the account owner can invite people, change roles or remove someone, and a removed member loses access everywhere.
Service providers
The companies that process data for us (hosting, database, AI, messaging, payments and the integrations you turn on) are listed in the Privacy Policy under who receives your data.
Report a security issue
If you find a vulnerability, email hello@bodhx.ai with the details. Please do not access other people's data while testing.
