Home > Trust and Security
Trust & Security
Last updated: November 20, 2026. We try to say only what is true today. Plans are marked as planned.
The short, honest version
- Saved conversations are locked. What we keep in the inbox (names, summaries, items, notes) is encrypted with a key that only your access code can open.
- Live messages are not hidden from the system. When a customer writes, our server reads the message in memory and sends it to our AI provider so the assistant can answer. After WhatsApp is connected, Meta also carries the message. Because of this, we do not claim that nobody can ever read your messages.
- Our rule: we do not read your customers' conversations, we do not put message text or phone numbers in our logs, and we do not sell your data or use it to train AI models. Access to our systems is limited to the founder, and our AI work assistants are instructed never to touch production secrets or customer conversations. These are our rules and commitments; the numbers below show what is actually in place.
- You stay in control. In your dashboard (Account tab) you can download your data, cancel, and delete your account and all data yourself.
Who handles your data
| Who | What for | What they get |
|---|---|---|
| STEEVY BOT AI (the founder) | Runs the service as your processor | Your business information and, while answering, the live messages |
| Groq | AI text, photo understanding and speech-to-text | The message, photo or voice note being answered, in real time |
| OpenAI (only if we turn it on) | Photos and voice transcription | The photo or voice note being understood |
| Supabase | Database | Encrypted saved conversations, business profile, usage counts |
| Render and Cloudflare | Hosting and network protection | Traffic to the site |
| Meta / WhatsApp (when connected) | Delivering WhatsApp messages | The messages, under Meta's own terms |
| Stripe (planned) | Card payments | Payment details, never stored by us |
What is in place today, and what is still being built
| Protection | Status |
|---|---|
| Saved conversations encrypted (key opened only by your access code) | In place |
| Access codes stored only as hashes; recovery code; login lockout after repeated failures; automatic logout after 30 minutes idle | In place |
| HTTPS, security headers, rate limits, abuse filters, protection layer in front of the site | In place |
| Database closed to the public internet; each business only sees its own records | In place |
| AI safety rules: says it is an AI, refuses unsafe requests, hands tricky cases to you, does not take payments or ask for card numbers or passwords | In place |
| Download, cancel and delete from your dashboard | In place |
| Two-step login for our admin tool | Available, being made mandatory |
| Signature checks and a security review of the WhatsApp connection | Planned, before WhatsApp goes live |
| Zero data retention with our AI provider | Being confirmed; we will not claim it until we have confirmed it |
| Tested backups and restore | Planned |
| Uptime and security alerts | Partly in place, being expanded |
| Review of our legal texts by a lawyer | Planned |
If something goes wrong
- If a security incident affects your data, we tell you without undue delay, and within 72 hours of becoming aware where possible, with what happened, what data was involved and what to do.
- If you find a problem, email us at support@steevyai.com. We read security reports and thank people who report in good faith.
- If the AI says something wrong, tell us; you can also take over any conversation yourself.
What we ask of you
Keep your access code and recovery code in two safe places. Tell your customers that an AI answers them. Do not send card numbers, passwords, one-time codes, ID numbers or health data in chats. Use WhatsApp only with customers who contacted you or agreed to be contacted.
No system is perfectly secure. This page is not a guarantee. For the legal terms, read the Privacy Policy and the Terms.