07 / security
your data, at rest.
We treat every conversation like it's our own. Here's the exact list of how we protect it.
◆ summary
HTTPS for all traffic, channel credentials encrypted in the database, workspace isolation and files only your team can see. heysteff doesn't use your conversations to train its own models. Reports & questions: [email protected].
Encryption
- In transit: the dashboard, the API and the webhooks are served only over HTTPS (TLS).
- Channel credentials: WhatsApp, Instagram, Messenger, Gmail and Shopify tokens are stored encrypted with AES-256-GCM.
- Platform secrets: never in code or in the repository; they live in the server configuration.
Data and models
- heysteff does not use your conversations to train its own models or share them across workspaces.
- Conversations are isolated per workspace: every table with customer data has row-level security (RLS) in Postgres, so one workspace can't read another's data.
- To draft each reply, the agent sends the conversation context to an AI model provider that heysteff chooses and manages. Each provider handles that data under its own policy.
- You can request deletion of a contact's data or of your workspace.
Infrastructure
- The platform runs in a single production region; you can't choose where your data is hosted today.
- Photos, audio and documents from your conversations are shown only to signed-in users of your workspace; WhatsApp and Meta receive them through signed links that expire.
Compliance
- Chilean Law 19.628 (personal data protection).
- GDPR best practices for EU customers.
- Aligned with WhatsApp Business & Meta Platforms official policies.
Responsible disclosure
Found a security issue? Email [email protected]. Tell us what you found and how to reproduce it, and we'll look into it.