1. The two roles
You are the controller of the personal data you load into your workspace — your contacts, their messages, their bookings. You decide what to collect and why.
We are the processor. We hold that data on your instructions and do not decide what to do with it.
Separately, we are the controller of your own account data — your name, your email address, your plan and your usage. That is covered by the Privacy Policy, not by this agreement.
If you are an agency with sub-accounts, you are the controller for your clients' workspaces as between you and us, and responsible to your clients for how their data is used.
2. What we process, and why
| Category | Examples | Why |
|---|---|---|
| Contact records | Names, emails, phone numbers, addresses, tags, custom fields, notes | To provide the CRM |
| Message content | Emails, SMS and chat messages sent and received | To deliver and display conversations |
| Appointment data | Bookings, booking-form answers, marketing consent and its wording | To run calendars and booking pages |
| Files | Anything uploaded to Media Storage | To store and serve them |
| Form and survey submissions | Whatever your forms collect | To capture and route them |
| Payment records | Orders, invoices, subscriptions, transactions | To run the commerce features |
We process it only to provide the Service, to keep it secure, and where you instruct us to. We do not sell it, and we do not use your contacts or their messages to train AI models.
3. Duration
For as long as your account is open, and afterwards only as long as section 7 describes.
4. Your instructions
Using the Service is your instruction to process the data in it. If you give us an instruction that we believe breaks data-protection law, we will tell you rather than carry it out.
5. Confidentiality
Everyone with access to your data is bound to keep it confidential.
6. Sub-processors
We use the companies below. This list is what the platform actually calls, and you can check it against the product. A sub-processor list that is wrong is worse than none.
| Sub-processor | Purpose | What reaches them | Where |
|---|---|---|---|
| Anthropic | AI features you enable | Conversation messages and prompts sent to AI features | United States |
| OpenAI | AI features you enable | As above | United States |
| AI features you enable | As above | United States | |
| Amazon Web Services (Amazon SES) | Email delivery | Recipient address, subject and body of each email sent | Singapore |
| Twilio | SMS, voice and phone numbers | Phone numbers, message content, call metadata | United States |
| Your chosen payment gateway | Payments you take | Payment and customer details, handled by them directly | Varies |
| Our own server infrastructure | Hosting | Everything, at rest | Thailand |
Three things worth stating plainly about that list:
- The AI sub-processors apply only if you enable AI features. A workspace that uses none of them sends nothing to any of the three.
- If you configure your own AI provider key, the data goes to your account with that provider under your agreement with them, and that provider is your sub-processor rather than ours.
- The payment gateways are your choice, made per workspace. We do not receive card numbers at any point.
Where you connect an integration yourself — a social account, another CRM, a calendar — that service receives data on your instruction. It is your sub-processor, not ours.
We will give you notice of a new sub-processor before it starts processing your data, so that you can object.
7. Deletion and return
- Deleting a record in the platform marks it deleted and hides it, rather than erasing it immediately. This is what makes an accidental deletion recoverable.
- Erasing something outright, or closing an account or workspace, is done by asking us at [email protected]. There is no self-service button for this yet, and we would rather say so than imply one exists.
- Backups are kept for disaster recovery and overwritten on a rolling basis. Deleted data can therefore persist in a backup for a period after it is gone from the platform. We do not surgically purge backups on request — they age out. If that is not acceptable for your use, tell us before you sign.
- Export. You can export your data from the platform at any time while your account is open.
8. International transfers
Our servers are in Thailand. Several sub-processors in section 6 operate outside it, so enabling those features transfers personal data internationally.
We have not yet put Standard Contractual Clauses in place. If you are in the EU or UK, or your contacts are, this is the section to take to your own adviser before relying on the Service for that data. We would rather you read it here than find out afterwards.
9. Security
As implemented, not as aspiration:
- Passwords are stored only as hashes.
- Provider credentials and API keys are encrypted at rest with AES-256-GCM.
- Workspace isolation is enforced by the database, not only by application code: row-level security policies mean a query that does not name your workspace returns nothing, so one customer's data cannot be reached from another's session even if application code were wrong.
- Access is over HTTPS.
- Role-based permissions control what each member of your workspace can see and do.
We hold no security certification — no ISO 27001, no SOC 2. If your procurement process requires one, we do not meet it today.
10. Breach notification
If we become aware of a personal data breach affecting your data, we will tell you without undue delay and within 72 hours of becoming aware of it, with what we know: what happened, which data, and what we are doing about it.
We will tell you even where we are not sure of the full extent yet. A late complete report is worse than a prompt partial one, because you may have your own notification deadline running.
11. Helping you meet your obligations
We will give you reasonable help with:
- Requests from individuals — access, correction, deletion, export. Most of these you can do yourself in the platform; write to us for the rest.
- Data protection impact assessments, by answering questions about how the Service works.
- Demonstrating compliance, by providing the information in this agreement and answering reasonable questions about it.
12. Audits
We will answer reasonable written questions about our processing. We do not currently offer on-site audits.
13. Liability
Liability under this agreement is subject to the limits in the Terms of Service.