Everybody claims it. Almost nobody shows the working. This page is the working: where your data physically sits, every company that touches it, and each obligation matched to the thing we actually built for it.
Three companies, one of which is the messenger you already chose. No others. No data broker, no ad network, no training set.
Telegram carries it, encrypted in transit, the same as every other chat on your phone.
Hetzner, Falkenstein. Your messages and notes are stored here, in your own folder, so your operator can remember context.
The context needed for that one reply goes to Claude under an agreement with EU transfer safeguards. Never used for training.
The reply comes back and is stored with the rest of your operator's memory. No third destination exists.
Row by row: the obligation, what we do about it in plain language, and whether it is working today or still honestly outstanding. Open any row to see the thing itself.
The disclosure, as it actually arrives — word for word from the product.
Said up front, before anything is created — not buried in a policy.
export my data and your operator replies with a zip of everything it holds about you — the same plain files it reads itself.A real export, produced on 2026-08-29 during testing.
delete my operator. You get told exactly what disappears, then confirm. The files are erased from disk, not flagged as hidden.Two steps on purpose: nothing irreversible happens on one tap.
The record written the moment you agree.
The whole list. If a fourth ever appears, this page changes first.
Two different clocks, on purpose.
What the sandbox can and cannot see, every single reply.
The one row we would love to change, and have not earned yet.
The part most companies leave off the compliance page.
Run by Scandinavian Communication AB (Sweden). Servers in Germany. Last reviewed 2026-08-29 · Privacy notice · Terms of use · Questions: hello@skogstrom.se
Nine everyday practices we see in nearly every company, each one a breach of a row above. Walk through them, and open any card to see how the operator handles the same row.
It is the most common breach in Europe right now. No processor agreement, unknown hosting region, and the vendor may train on it. The company is the controller, so the company owns the breach.
Three companies touch your words, all under agreements: Telegram carries the message, Hetzner stores it in Germany, Anthropic writes the reply in the US under EU transfer safeguards. Neither may train on your data. The whole list is on this page.
Evidence: Every company involved, in the map above.
A human name, a stock photo, and never a word about being an AI. Since 2026-08-02 that silence is a breach of the AI Act, not a design choice.
Your operator says it is an AI before it is created and again in its first message. The line is written into every operator's instructions, so it still holds months later.
Evidence: The disclosure, word for word, in the map above.
"In the cloud" is the usual answer. Article 13 requires telling people what is stored and where, at the time of collection, not after a subject access request.
Your messages, notes, Telegram user ID and first name. Stored on our server in Falkenstein, Germany. Said before anything is created, and again in the privacy notice.
Evidence: The up-front notice in the map above.
A deleted flag in the database, backups untouched, AI memory still holding the details. The person was promised erasure and got a checkbox.
Send "delete my operator". You are told exactly what disappears, you confirm, and the files are erased from disk. The erasure is recorded with a timestamp.
Evidence: The two-step delete transcript in the map above.
Portability means a machine-readable copy of what is held, including what the AI remembers. Most tools have no export at all, or one that leaves the AI's memory out.
Send "export my data" and your operator replies with a zip of everything it holds about you, the same plain files it reads itself. No proprietary format.
Evidence: A real export from testing, in the map above.
When asked to prove consent, the company produces a screenshot of today's form. The terms have changed three times since. That is not proof of anything.
Your agreement is recorded with the exact version of the terms you accepted and a fingerprint of the wording, so nobody can quietly rewrite them afterwards.
Evidence: The consent ledger line in the map above.
No retention period, no deletion job, no distinction between what the company needs and what belongs to the user. Storage limitation is a rule, not a preference.
Operational logs are deleted automatically after 90 days. Your own notes and memory stay until you delete them, because those are yours, not ours.
Evidence: The two retention clocks in the map above.
No way to tell who entered what, and every customer's data sits in one context the next colleague can scroll through. Add a hard-coded API key in a shared script and it is a breach waiting for a date.
Every reply runs in its own sandbox that can see one operator's folder and nothing else. Credentials are encrypted on disk and invisible to it. An automated check against the live server tries to break out and must fail.
Evidence: The sandbox diagram in the map above.
Procurement asks for the certificate and gets a slide instead. A false compliance claim is worse than an honest gap, and buyers know it.
Not certified, and we will not pretend otherwise. We follow the practices the standards describe. If your procurement needs the certificate, say so and we will talk about the timeline.
Evidence: The "honest no" row in the map above.
Ask it directly. If the honest answer is "not yet", that is the answer you will get.