Privacy Policy

Last updated: July 20, 2026

This policy explains what personal data Marnie ("we", "us") collects, why we collect it, and what control you have over it. It covers the website marnie.chat, the dashboard at app.marnie.chat, and the bots we host for you (the "Service").

1. Who is responsible

Marnie is the data controller for the personal data described here. For any privacy question or to exercise a right below, contact [email protected].

2. What we collect

Category	Examples	Why
Account data	Name, email address and profile picture from Google Sign-In	To create and secure your account
Bot configuration	Bot name, personality, plan, chosen model, connected channels	To provision and run your bot
Conversation content	Messages you exchange with your bot	Processed on your own bot's machine to generate replies — see below
Bot memory	Notes your bot keeps about you — people, preferences, plans, routines	So your bot remembers context between conversations
Credentials you supply	Messaging bot tokens, your own AI provider API key	To connect your bot to the channels you choose
Usage and technical data	Log data, timestamps, IP address, error diagnostics, AI token usage	Security, troubleshooting, and metering credits
Billing data	Subscription status and transaction identifiers	To give you access to what you paid for

We request only the openid, email and profile scopes from Google. We do not receive your Google password, contacts, calendar or files.

Your bot runs on its own dedicated machine. Every bot is provisioned on a separate virtual machine with its own storage. Bots belonging to different customers are isolated from one another — they share no runtime, no database and no files, and one bot cannot read another's data.

We do not collect your conversations. Messages are processed on your own bot's machine to produce a reply, and are sent to the AI provider for that purpose. They are not gathered into a central store we browse or analyse, and they are not included in backups.

What we do back up is only this: your bot's memory notes, its routines, its persona and its configuration — never your chat transcripts.

Your bot keeps a memory. To stay useful between conversations, it writes notes about what you tell it. You can read, export or delete that memory from the dashboard at any time.

We never receive your full payment card details. Payments are processed by Paddle as merchant of record; we only see the resulting subscription and transaction records.

3. Why we may use it (legal bases)

To perform our contract with you — running your bot, keeping its memory, providing support, managing your subscription.
Legitimate interests — securing the Service, preventing abuse and fraud, diagnosing faults and improving reliability, balanced against your rights.
Legal obligation — keeping records we must keep and responding to lawful requests.
Consent — where we ask for it specifically; you may withdraw it at any time.

We do not sell your personal data, and we do not use your conversations or your bot's memory to train our own models.

4. Who processes your data

Provider	Purpose	Data involved
Anthropic	AI model that generates your bot's replies	Conversation content and relevant memory
Hetzner	Virtual machine hosting your bot	Bot data, memory, logs
Cloudflare (R2)	Encrypted backups	Memory notes, routines, persona and configuration — no chat transcripts
Google	Sign-in	Name, email, profile picture
Paddle	Payments, invoicing and tax (merchant of record)	Billing and payment data
Telegram / WhatsApp	Message delivery on the channel you connect	Messages sent through that channel
Vercel	Website and dashboard hosting	Technical and log data

Each provider's own privacy policy governs its handling of that data. We share data with them only as needed to run the Service, and otherwise disclose personal data only where required by law or to protect our rights, our users, or the Service.

5. Where your data is stored

Your bot runs on a virtual machine in the European Union, and memory backups are stored in Cloudflare R2 under an EU jurisdiction restriction, meaning those backups remain within the EU. Some providers above may process data outside your country, including in the United States; where that involves a transfer out of the European Economic Area, it relies on appropriate safeguards such as the European Commission's standard contractual clauses.

6. How long we keep it

Account data — while your account exists, and a short period afterwards.
Bot memory, routines, persona and configuration — while the bot exists. When you delete a bot, these are kept in backup form so you can restore them into a future bot, until you delete that memory from the dashboard.
Conversations — held only on your own bot's machine for it to function, and destroyed with that machine when the bot is deleted. We do not retain copies.
Backups — kept for a maximum of 30 days, and no more than the 10 most recent copies of a bot's memory are retained at any time. Older copies are deleted from our backup storage.
Billing records — as long as tax and accounting law requires.
Logs — a limited period, for security and troubleshooting.

Deleting your account removes your bots and schedules deletion of the associated data.

Data from a deleted bot is erased after 90 days. When you delete a bot we keep its memory, routines, persona and configuration in backup storage so you can restore them into a new bot. If you do not restore them, and do not delete them yourself from the dashboard, we permanently delete them from our backup storage (Cloudflare R2) 90 days after the bot was deleted. You can delete them sooner at any time from Settings → Memories.

7. Your rights

Depending on where you live you have rights over your personal data. If you are in the European Economic Area or the United Kingdom, these include the right to:

access a copy of your data;
correct inaccurate data;
delete your data;
export it in a portable format — you can download your bot's memory from the dashboard at any time;
restrict or object to certain processing, including processing based on legitimate interests;
withdraw consent where processing relies on it;
complain to your local data protection authority.

To exercise any of these, email [email protected]. We respond within the period applicable law requires (usually one month), free of charge for reasonable requests.

8. Security

Isolation is the core of the design: each bot gets its own dedicated virtual machine and storage, so customers never share a runtime or a database and a fault or compromise in one bot cannot reach another. Infrastructure access is restricted and key-based, backups are encrypted, and traffic is encrypted in transit. No system is perfectly secure and we cannot guarantee absolute security, but we take technical and organisational measures appropriate to the risk, and will notify you and any relevant authority of a personal data breach where the law requires.

9. What you should not send your bot

Please avoid sharing passwords, payment card numbers, government identifiers, or other people's sensitive personal data with your bot. Your bot is instructed not to store secrets, but you are responsible for what you choose to send it.

10. Children

The Service is intended for users aged 18 and over and is not directed at children. We do not knowingly collect personal data from children; if you believe a child has provided us data, contact us and we will delete it.

11. Cookies

We use cookies and similar technologies that are strictly necessary to sign you in and keep your session secure, plus limited analytics to understand how the site is used. You can block cookies in your browser, but sign-in will not work without the essential ones.

12. Changes

We may update this policy. Changes are posted here with a new date, and we will give notice of material changes by email or in the dashboard.

13. Contact

Privacy questions or requests:
Email: [email protected]