Home > Privacy Policy
Privacy Policy
Last updated: November 20, 2026
STEEVY BOT AI ("we", "us") operates STEEVY AI, an AI customer-service assistant for WhatsApp Business. This policy explains, in plain words, what information we handle, why, who sees it and what your rights are.
1. Two roles: who is responsible for which data
- Visitors of this website and the demo. For this data, we decide how it is used. We are the "controller" (GDPR) or the "business" (CCPA).
- Customers of a business that uses STEEVY AI (WhatsApp conversations). The business decides why and how its customers' data is used. We act only as its processor (GDPR) / service provider (CCPA) and handle that data only on the business's instructions to provide the service. If you are a customer of such a business, please contact that business first about your data.
2. What we collect and why
| Information | From whom | Why we use it | Basis (GDPR) | How long we keep it | Shared with |
|---|---|---|---|---|---|
| Messages typed in the demo, voice recordings and photos you choose to send | Visitors | To generate the demo reply or transcript | Your request / consent by using the demo | Not stored. Sent in real time to our AI provider. Photos are resized and stripped of hidden metadata (such as location) first | Groq |
| Your IP address, sent to Google when your browser loads the site's fonts (Google Fonts) | Visitors | Display the site's typefaces | Legitimate interest | Kept by Google under its own policy; we do not receive it | |
| Anonymous visitor code (one-way hash of your IP address) | Visitors | Daily limits and abuse prevention | Legitimate interest (security) | Memory only, lost when the server restarts, never written to disk | Nobody |
| IP address and security events (blocked requests, attack patterns) | Visitors | Protect the service from attacks and abuse | Legitimate interest (security) | Short term, in memory (recent events only) | Render, Cloudflare (as network providers) |
| Page views and visits | Visitors | Understand how many people visit the site | Legitimate interest | Per our analytics provider's settings. No cookies, no advertising profiles. Not active on admin and business dashboard pages | Umami |
| Visitor reviews: first name or nickname you type, star rating, review text, date | Visitors who choose to leave a review | Show the review on the website once our team approves it | Your consent (you tick a box) | Stored in a file on our server until you ask us to delete it or our team deletes it. There is no automatic deletion; we keep at most the 300 most recent reviews. Only approved reviews are public. To delete yours, contact us (section 9) | Nobody (approved reviews are visible to everyone who visits the site) |
| Demo tickets (short summary, items, first name given) | Visitors | Show how a hand-off or order request works | Legitimate interest | Deleted automatically after 30 days | Nobody |
| Business account: business name, plan, usage counts, the business information entered, access code (stored only as a hash), encryption keys (the private key is locked with the access code) | Business clients | Provide, secure and limit the service; contract | Contract | While the account is active. Erased from our database when the account is deleted | Supabase, Render |
| Customer conversations handled for a business: message content, first name, order details, summary, notes (and a phone number once WhatsApp is connected) | Customers of business clients | Generate replies and keep the business's inbox | The business's instructions | Saved ticket content (name, summary, items, notes) is stored encrypted (see 3b). Kept until the business deletes it or closes its account; we do not delete business tickets on a timer today. Erased from our database when the business is deleted or its access code is reset. The live message itself is not stored in full, but it is processed unencrypted in server memory while we answer | Groq (to write the reply; OpenAI only if we enable it, see section 4), Supabase (storage), Meta (WhatsApp delivery) |
| Appointment bookings (planned feature, Plus and Pro plans): the customer's first name, phone number and appointment time | Customers of business clients who book | Show the owner the booking and send appointment reminders | The business's instructions | The phone number is stored readable by our server (not locked like ticket content) so reminders can be sent, and it is cleared 7 days after the appointment. Not available yet | Supabase, Render, Meta |
| Messages you send to our own WhatsApp number (waitlist or support) | Visitors | Answer you | Legitimate interest / your request | As long as needed to help you | Meta |
We do not collect more than this, and we do not require visitors to create an account.
3. What we never do
- We do not sell or share personal information (including "sharing" for cross-context advertising), and we do not use it for advertising or profiling. We do not knowingly sell or share the data of anyone under 16.
- We do not use a business's conversations or information for ourselves, for another client, to compete with that business, or to build products for others. Each business's data is kept separate and is visible only in that business's own dashboard.
- We do not read customer conversations as a rule. STEEVY staff do not open them, our admin page cannot display stored tickets, and technical access is limited. But we do not claim it is impossible: our system processes messages automatically to reply (see 3b).
- We do not use your content to train AI models, and we do not turn on any training option with our AI provider. What the provider does with data it receives is set by its own terms and privacy policy. We have not yet confirmed a "zero data retention" setting with Groq. We plan to ask for it. Until we confirm it, please assume the provider may keep requests for a short time under its own rules.
- We do not store demo voice recordings or photos.
3b. What we can see, what is encrypted, and why
Short answer: saved tickets are locked. Live messages are not locked from our server while we answer. This is not end-to-end encryption.
1. While the AI answers (live). A customer message, photo or voice note reaches our server through WhatsApp (delivered by Meta). Our server reads it in memory, and sends it to our AI provider (Groq today; OpenAI only if we turn it on for photos or voice, and then we will list it here). Photos are resized and stripped of location data first. At this moment the message is not encrypted from our server or from the AI provider. The system does this automatically. STEEVY staff do not read messages as a rule. We do not store the full chat.
2. Saved tickets (encrypted at rest). When the AI hands a case to a human or records an order request, we save a ticket. Its name, summary, items and notes are encrypted with the business's public key. They can only be opened with that business's access code or recovery code. Our database provider (Supabase) holds only the locked version.
3. Not encrypted. Ticket type, status, dates and times, the business ID, usage counts, plan, the access code hash (not the code) and account details such as the business name. We need these to run, limit and secure the service. Settings the business enters (its business information) are also stored so the AI can use them.
Appointments and extra providers (planned). For the planned appointment reminders (Plus and Pro), the customer's phone number is stored readable by our server so it can send reminders. It is cleared 7 days after the appointment. Photos and voice notes may be sent to OpenAI, if we turn that option on for them.
Why we encrypt. If our database were ever leaked, the saved ticket content would be unreadable. That limits the harm, and it helps us meet security and data-minimisation duties (for example GDPR Article 32 and the "reasonable security" duty in California law). We say "help meet". Encryption alone does not guarantee legal compliance.
What this means for you. Business owner: only you can open saved tickets, and if you lose both codes we cannot recover them. Customer: your message is handled by software to get a reply, and a short summary may be saved locked, so please do not send passwords, card numbers or ID numbers. One more honest limit: the first access code and recovery code are made by our admin tool and shown once at setup, so we ask each business to change both codes at its first login.
4. Who processes data for us (sub-processors)
| Provider | Purpose | Data |
|---|---|---|
| Render | Hosting of the website and app | Everything the app handles, in transit and in memory |
| Supabase | Database | Business accounts, usage counts, customer conversations for business clients |
| Groq | AI model, photo understanding and speech-to-text | The message, voice or photo being answered, in real time. Retention is set by Groq's terms. We have not yet confirmed zero data retention |
| OpenAI (only if we enable it) | Optional photo understanding or voice transcription | Same as Groq. Not used today. We will update this list before use |
| Stripe (planned) | Card payments for paid plans | Billing details. Not active yet. Card data goes to Stripe, not to us |
| Cloudflare | Network protection, DNS and speed | Web traffic (IP addresses), in transit |
| Meta (WhatsApp Business Platform) | Delivering WhatsApp messages, once a business is connected | WhatsApp messages and phone numbers |
| Umami | Visit statistics | Anonymous page views |
| Google (Google Fonts) | Website typefaces | Your IP address and browser details, sent by your browser when it loads the fonts |
Each provider has its own terms and privacy policy. They are bound to protect data and to use it only to provide their service. We will update this list before adding a provider that handles client conversations.
5. Your rights
You can ask us to access, correct or delete the information we hold about you, to restrict or object to its use, to receive a copy of it, and to withdraw consent. Email us at support@steevyai.com. We will answer within 30 days (45 days where the law allows). We may need to confirm who you are first, and an authorized agent may ask on your behalf. We will not treat you differently for using your rights. If you are a customer of a business client, we will pass your request to that business.
California residents (CCPA/CPRA). In the last 12 months we handled these categories: identifiers (a hashed IP address, a first name you give), internet activity (visits to this site), audio and images (only processed in real time in the demo, not stored), and commercial information (plans and usage of business clients). We got them from you or from your device. We use them only for the purposes in the table above. We do not sell or share personal information and we do not use or disclose sensitive personal information beyond what is needed to provide the service. You may ask to know, delete or correct your information.
European Economic Area, UK and Switzerland (GDPR). Our legal bases are listed in the table above. Our servers and providers are mainly in the United States. Your data may be processed outside your country. When data is moved from the EEA, UK or Switzerland we plan to rely on safeguards such as the standard contractual clauses in our providers' data-processing terms. You can complain to your local data-protection authority.
Haiti and other countries. If you are elsewhere, the same rights described here are open to you. We will handle your request in good faith, even where no local law requires it.
How to use your rights. Business owners can download their data, cancel the subscription and delete the account and all its data themselves in the dashboard (Account tab). For anything else, email us at support@steevyai.com and say what you want: a copy (access), a fix (correct) or deletion. Tell us the business name if you are a customer of a business. We may ask you to prove who you are. A business owner can also delete tickets in the dashboard. We delete on request from our database. Copies at providers or backups expire on their normal schedule.
Retention. Demo tickets are deleted automatically after 30 days. Tickets of a business are kept until the business deletes them or closes its account. Live messages are not stored in full.
6. For businesses that use STEEVY AI
You are responsible for having a legal basis and any required consent to message your customers, for telling them that an AI assistant replies (our assistant states this in its first message of each conversation), and for following the WhatsApp Business messaging policies. Our processing terms are in section 14 of the Terms of Service. Saved tickets are stored encrypted and appear in your dashboard only after you sign in with your access code. If you lose both your access code and your recovery code, we cannot recover your stored conversations (see section 7 of the Terms), because we have no copy of your key. You can change your code in the dashboard without losing them. If an administrator resets a code, that business's stored conversations are erased, so a reset can never be used to read old conversations. While a message is being answered it is processed, not encrypted, in our server's memory and by our AI provider, and short summaries are then saved encrypted (see 3b).
7. Security, retention and breaches
We use HTTPS, encryption of stored ticket content, access codes stored as hashes, databases that are closed to the public internet (only our server can reach them), separation between businesses enforced by our application (each dashboard only asks for its own business's records), rate limits, abuse filters and automatic deletion of demo tickets. No system is perfectly secure. If a security incident affects personal information we handle for a business, we will tell that business without undue delay, and within 72 hours of becoming aware where possible, so it can meet its own duties. See also the Trust & Security page for who has access, what is done and what is still being built.
8. Children
The service is not for children under 13 (under 16 where the law sets that age). We do not knowingly collect their information. If you think we have, contact us and we will delete it.
9. Changes and contact
We may update this policy. The date at the top shows the latest version, and we will tell business clients about important changes. Contact, and to report a security problem: email us at support@steevyai.com.