Legal
Privacy policy
Last updated: Draft
This is a pre-launch draft. It is published so you can see the shape of our terms while we finalise them with counsel, and it is not yet the agreement between us. If you need final documents before you can build — a DPA, a signed agreement, a security review — email hello@mapier.ai and we will get them to you directly.
Who controls what
Mapier has two different relationships with data and they carry different obligations. Keeping them apart is the most important thing in this document.
For this website, Mapier Labs Inc. is the controller. We decide what we collect from visitors and why.
For the messaging service, you are the controller and Mapier is your processor. The messages your agent sends and receives, and the phone numbers it sends them to, are your end users' data. We process it on your instructions to deliver the service, and for nothing else.
What we handle for you
To deliver messages and prove they arrived, the service handles:
- Message content and attachments your agent sends and receives
- Phone numbers and platform handles for the people your agent talks to
- Conversation and group metadata: participants, names, timestamps
- Delivery evidence: which channel carried a message and what happened to it
- Operational logs and audit records of the commands your keys issued
We do not train on your message content
Customer message content is not used to train models — ours or anyone else's. It is processed to deliver and prove delivery of the message, and that is all.
What we collect on this website
Separately from the service: if you submit the contact form we receive the work email, name, company and other details you type, so we can reply. That form does not write to a database — it forwards to our email and to an internal channel.
Sub-processors
We use a small number of vendors to run the service. The current list, with what each one processes and where, is available on request and will be published here before launch. Enterprise agreements include notice of changes to it.
Retention and deletion
Retention windows depend on your plan and are stated in your agreement. You can delete a conversation's stored content through the API at any time, and we delete customer data on termination.
Where data goes
The service runs across cloud infrastructure and a fleet of hosts, which may sit in different jurisdictions from you or from the people your agent messages. The regions in use and the transfer mechanism that covers them will be named here before launch, and are available on request now.
Your rights, and your end users'
If you are a visitor to this site, contact us to access, correct or delete what we hold about you. If you are one of your customers' end users, your relationship is with them — they are the controller, and we will route your request to them.
We do not sell or share personal information as those terms are used in the CCPA.
Contact
Privacy questions go to hello@mapier.ai.
