Privacy

Who is responsible

Controller under Article 4(7) GDPR for the processing described here is Finn Jung, Rotlintstraße 79, 60389 Frankfurt am Main, Germany.

The website

No cookies, no analytics, no tracking pixels, no third-party scripts, no third-party fonts. Everything the page needs is served from this domain, so loading it tells nobody but us that you were here. Standard web-server logs record IP address, time, path and user agent, and are kept for seven days for abuse defence.

The service

What is stored

• Message history of the linked account: text, sender, timestamps, chat and contact names, and metadata about media. Media files are downloaded only when a tool explicitly requests one.
• Device credentials from the QR link, which keep the session alive the same way WhatsApp Web does.
• Account record: an identifier, your bearer token, your store path, whether sending is enabled, and a contact address if you gave one.
• Operational logs: that a request happened, which account, which tool, how long it took. Not the content of messages or tool results.

Where it is stored

On a single server in Nuremberg, Germany, inside the European Union, in a per-account directory. No cloud message database, no replication to other providers.

Encryption at rest is being introduced per account. Until the page says otherwise, treat the store as unencrypted on disk and protected by access control alone. We would rather say that plainly than claim a safeguard we have not finished building.

Sub-processors

Three companies touch this service, and none of them for the content of your messages beyond what hosting inherently implies:

• Hetzner Online GmbH, Gunzenhausen, Germany — the server the store lives on.
• Cloudflare, Inc. — DNS and the tunnel that publishes the site. Traffic is terminated by Cloudflare, so it sees request metadata; tool results pass through encrypted in transit.
• 1337 Services GmbH (Njalla) — the domain and the mail forwarding behind the addresses on this page. Mail you send us passes through it.

We add none without changing this list first.

Who can access it

You, through your token. The operator, through the machine — technically unavoidable for any hosted service, and used only for debugging a problem you reported or for the legal reasons below. Nobody else.

Be clear about what that means: a hosted service that can search your messages for you can, by construction, read them. Nobody can honestly promise otherwise about this kind of product. If that trade is not one you want to make, run it yourself — the code is the same and it is free.

What we never do

• Train models on your messages, or let anyone else do it.
• Sell, rent or share your data, or run ads.
• Send message content to analytics or error-tracking services.
• Read your chats out of curiosity, or scan them for content.

Where the data goes when you use it

When you connect an MCP client, the messages a tool returns travel to that client and, in an assistant, to that assistant's model provider. That transfer is caused by your prompt and governed by the client's own privacy policy — we are not a party to it. Pick your client accordingly.

Retention

• Messages: kept while the account is linked. On the Free plan a chat with no activity for 30 days is pruned along with its messages; active chats are kept whole. On Pro nothing is pruned.
• After you unlink or ask for deletion: the store and the account record are removed within 30 days, backups included.
• Inactive accounts: on the Free plan, 14 days without a single request and the store is deleted. On Pro the store stays as long as the subscription runs.
• Logs: 7 days for web logs, 30 days for service logs.

Your rights

Under the GDPR you may request access, correction, erasure, restriction, portability, and object to processing. Mail [email protected]; identity is verified through the linked account. You can also complain to your national data protection authority.

Legal basis: performing the contract you asked for (Art. 6(1)(b)) for running the service, and legitimate interest (Art. 6(1)(f)) for abuse defence and operational logs.

The other people in your chats

A conversation has two sides, and the other side did not sign up here. Storing your own copy of your own conversations is ordinarily yours to do — the same copy your phone and WhatsApp Web hold. If you use this in a business context, that copy is a processing activity you are responsible for, and you may owe your contacts an explanation. Our data processing agreement covers that case; accepting it takes a click, not a signature.

Disclosure

We disclose data only when legally compelled by a competent authority, and will tell you unless we are forbidden to. We have never received such a request.

Changes

Material changes are announced to the contact address on the account at least 14 days before they take effect. The date at the top marks the current version.