Six things that protect your data
These are architectural decisions, not policy promises — they are how the software is actually put together.
Tenant isolation
Every record — conversation, contact, template, automation — is scoped to your organisation and filtered by it on every single query. There is no shared pool of contacts and no path by which one business can read another's data.
Encrypted credentials
Store API keys and access tokens are encrypted before they are written to the database, and are only ever decrypted to talk to your own store. Disconnecting removes them and the webhooks we created.
Role-based access
Your team members get roles with specific permissions. An agent can reply to conversations without being able to export your contact list, change billing or delete data.
Scoped API keys
Developer keys carry only the scopes you grant — messaging, contacts or phonebooks — can be revoked individually, and every call is logged against the key that made it.
Verified webhooks
Every inbound webhook, from Meta or from your store, is signature-verified before it is processed. Unsigned or tampered requests are rejected, and repeated events are recognised and skipped.
No lock-in
Export your contacts whenever you want. Your WhatsApp number and approved templates belong to your own Business Account, so if you leave, they go with you.
The commitments that matter
A privacy policy is a legal document. This is the plain-English version of the parts you actually care about.
- We do not sell, rent or share your contact list with anyone
- We do not pool your customers with other businesses' customers
- We do not message your customers on our own behalf, ever
- We do not use your conversations to train AI models
- We do not add a margin to Meta's conversation charges
- We do not require you to keep your data with us to keep your number
AI and your data
When your AI agent answers a message, the conversation context and any documents it needs are sent to the AI model provider to generate that reply. That is how the feature works — there is no way to produce an answer without the model seeing the question.
What we can tell you plainly: we do not use your conversations to train models, the data is sent only to generate that specific reply, and if you never enable an AI block, nothing is ever sent to a model provider at all.
Your customers' rights
If one of your customers asks you to delete their data, you can do it yourself: delete the contact and their conversation history goes with it, or clear an individual chat while keeping the contact. You do not need to raise a ticket with us to honour a request from your own customer.
What we are not claiming
We are a small, independent product. We have not completed a SOC 2 audit, we do not hold an ISO 27001 certificate, and we are not a HIPAA business associate. If your procurement process requires any of those, we are not the right vendor today and we would rather say so on our own website than in month three of an evaluation.
What we do offer is a straightforward architecture, honest answers to specific questions, and no incentive to make your data hard to remove. If you have a security questionnaire, send it — support@aptoair.com — and we will answer it accurately, including the questions where the answer is no.