Your customers trust you. You can trust us with their data.
An overview of how Inboxbee protects your workspace. We keep this page factual and update it as we add controls.
Workspace isolation
Every row of customer data belongs to one workspace. The database enforces this with row-level security, so one workspace can never read another’s conversations, even if application code makes a mistake. The application connects with a least-privilege database role.
Encryption
Channel credentials, such as messaging tokens, and two-factor secrets are encrypted with AES-256-GCM before they are stored, and each sealed value is bound to its own record. Traffic between your browser, our apps and our servers uses HTTPS.
Passwords and sign-in
Passwords are hashed with argon2id. Every account can turn on two-factor codes, passkeys and trusted devices, with one-time recovery codes. Sensitive actions ask you to confirm your password or passkey again.
Access control
Teammates get roles that limit what they can see and change. Pro adds custom roles, single sign-on and an audit log of important actions.
Developer access
API keys are separate for live and sandbox use and can be revoked at any time. Outgoing webhooks are signed with HMAC-SHA256 and a timestamp, so you can verify they came from us. Outbound requests to customer URLs go through a guard that blocks internal network addresses.
AI and your data
The AI agent answers from the knowledge you give it and the tools you allow. Prices and order details come from your connected store, not from the model. You can set a monthly AI budget and turn the agent off per channel.
Data deletion
You can delete contacts and conversations from your workspace. Data deletion requests from connected messaging platforms are processed automatically.
Report a vulnerability
Please email [email protected] with the details and steps to reproduce. Please give us reasonable time to fix the issue before sharing it publicly.
Start answering today
Free for up to three teammates. Add more when you’re ready.