Security and data handling
The access controls, sessions and encryption Sell Whisper AI gives your team, and how the data you store is used. The privacy policy is the binding statement.
Security features
Role-Based Access Control (RBAC)
Five roles (Owner, Admin, Member, Support, Viewer) with distinct permission sets. Enforced at the API level — not just the UI.
- Permissions enforced on every API request, not just in the dashboard
- Workspace-scoped roles: a user can have different roles in different workspaces
- Role changes take effect on the next authenticated request
Two-factor authentication (2FA)
Enable 2FA for your own account to require a one-time code in addition to your password on every login.
- Supports authenticator apps (Google Authenticator, Authy, 1Password)
- Recovery codes generated at setup — store them securely
- Each person opts in from Settings → Security; there is no account-wide 2FA enforcement switch yet
Sessions
See the devices and browsers signed in to your account, and sign a session out remotely when you no longer trust it.
- Active sessions listed in Settings → Security
- Sign out an individual session without changing your password
- Revoke all other sessions keeps your current browser signed in and ends the rest
API key management
Create, rotate, and revoke Public API keys for your account. Keys are stored hashed; only a short prefix is kept for identification.
- Generate multiple keys — one per integration or environment
- Rotate a key with zero downtime: create a new key, update your integration, then revoke the old one
- Revoke a compromised key — further requests with that key are rejected
- View the last-used time for each key
Data encryption
Traffic is encrypted in transit. Integration credentials are encrypted at the field level before they are stored.
- TLS 1.3 for all data in transit
- Integration OAuth tokens and similar secrets encrypted at the field level
- Public API keys stored as irreversible hashes, never in plaintext
- Account export lets Owners download their account data from Settings
How your data is used
Processing
Conversation and knowledge base content is processed to generate your agents' replies, through the AI provider you choose for each agent. We also analyse usage patterns to generate insights and improve our AI models, as the privacy policy describes.
Service providers and location
Hosting, payment, analytics and AI providers process data on our behalf under contract. Your data may be processed outside your country of residence, with safeguards such as standard contractual clauses.
Retention
We keep your data while your account is active or as needed to provide the service. You can delete conversations, leads and knowledge base content from the dashboard; there is no separate chat-retention control in account settings today.
Your data rights
You decide what conversation, lead and knowledge base data you keep in Sell Whisper AI, and you can act on it as follows.
Enterprise and SSO
SAML SSO, enforced SSO, a tenant-facing audit-log screen, scoped API keys and configurable chat retention are not available in the product today. If your organisation needs those controls, contact sales so we can scope what is already shipped (roles, 2FA, sessions, account export) against what you still need.
Do not treat marketing or older docs that mention SAML, enforced SSO or 12-month audit-log retention as a current capability. This page is the source of truth for what ships.
Responsible disclosure
If you discover a security vulnerability in Sell Whisper AI, please report it responsibly. We take all security reports seriously and will respond within 48 hours.
Report vulnerabilities to security@sellwhisperai.com with a detailed description. Please do not publicly disclose the issue until we have had time to investigate and remediate.