Privacy

Material you give us. The pages, documents and corrections a business adds so the assistant can answer from them, and the passages we derive from that material in order to search it.

Conversations. What a customer asked, what the assistant answered, and where a person took over. A customer talking to a widget is not asked to make an account, and we do not try to identify them beyond what they type.

Account and workspace. The name and email of the people who sign in, the business's own details, and a record of what was done in the workspace and by whom.

Usage. Counts — requests, questions answered, storage used — so a business can see what it is using and be billed correctly. Our operational logs are tagged with the workspace but the content of prompts and answers is removed before it reaches them.

Connecting Google is optional. Nothing below happens unless a business explicitly connects its Google account, and it can disconnect at any time.

Google Calendar — calendar.events. We read the times a business is already busy so the assistant can offer times that are actually free, and we create, change or cancel the appointments its customers book. We use this for nothing else. We do not read anything about the Google account beyond its calendar events.

A spreadsheet you choose — drive.file. If a business points the assistant at a spreadsheet, it picks that file through Google's own file picker and we can read only that file. This scope gives us no access to anything else in the Drive, and we cannot browse or list it.

We do not request access to Gmail, to contacts, or to Drive as a whole, and the assistant cannot read a business's email.

Google data is used only to answer the question in front of the assistant and to carry out the action a customer asked for. It is never sold, never used for advertising, and never used to train any model. Where answering a question requires it, the relevant detail is sent to our model provider to produce that one answer.

Mara's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting. A business can disconnect Google in its Mara settings, or revoke access directly at myaccount.google.com/permissions. Either way we stop being able to reach the calendar immediately, and we delete the stored authorisation. Any appointments already in the calendar stay there — they belong to the business, not to us.

The authorisation belongs to the workspace rather than to the person who granted it, so a colleague leaving the business does not take the connection with them.

In our database and file storage in the European Union (Ireland). Answering a question also sends the relevant passages and the customer's question to our model provider, which processes them in the United States.

We do not offer data residency anywhere else today. If a regulator requires it, we cannot serve that business yet.

Material and corrections are kept until the business removes them. Customer conversations are kept for as long as the business chooses — 30 days, 90 days, six months, a year, or indefinitely — and older conversations are then removed automatically.

A Google authorisation is kept until it is disconnected, revoked at Google, or the workspace is deleted.

A business can take a complete copy of everything in its workspace at any time, without asking us, and can delete conversations or the whole workspace itself. A deletion removes the rows and the stored files; we count what remains afterwards and show that count, so the deletion is verified rather than promised.

Each workspace's material, conversations and connections are separated in the database, and a request is resolved to one workspace before any data is touched. A workspace can have an owner, an administrator and a support member, and those permissions are enforced in the database rather than in the screens.

Our own staff do not read a business's conversations as a matter of course. Where we need to look at something to fix a fault, that access is recorded.

Our hosting and database provider, our model provider, our email provider, and — where a business uses it — WhatsApp for messages that travel over WhatsApp. The current list, and what each one does, is on the security page.

Most of it does not need us: export and deletion are in the product. For anything else — a question about this policy, a request about personal data, or a complaint — write to privacy@mara.support and a person will answer.

If a business's customer wants their conversation removed, the business can delete it from its own desk, or ask us.

If this policy changes in a way that affects what we do with a business's data, we will say so in the product rather than quietly reposting the page.