Your data, your control
How Klantr protects your data: in plain language, honestly, and only what we actually do.
What this is (and isn't)
This is an honest, plain-language explanation of how Klantr handles your data — not a final legal statement. The formal privacy statement and our Dutch Chamber of Commerce (KVK) number follow at launch. We promise nothing here the product can't keep, and we claim no certifications.
What we store from you
From you we keep your name, your agency name and your email address — nothing more. Per client you record: company name, a contact person's first name, a business email, the retainer amount (euros per month), hours per month, the short line you type yourself, the deliverables that result, a 'last contact' timestamp, and whether this month's update has been sent. Data minimisation is the rule: we only ask for what the tool genuinely needs.
The silence clock: only the timestamp
The silence clock runs on one thing: the timestamp of your last update per client. Every time you send an update through Klantr, that refreshes the timestamp for that client. Klantr does not connect to your mailbox and never reads, receives or processes your emails, subjects or attachments — we store only that timestamp, so we can flag which retainer client has gone quiet and how many euros are at stake. (Automatically counting messages you bcc to Klantr is on the roadmap.)
Where your data lives
Your data sits in a Postgres database at Supabase. Where the provider offers it, we run on EU-region infrastructure, and we keep the setup deliberately modest. We don't give an absolute, unconditional guarantee here, but the default is European hosting wherever that's available.
Encryption in transit and at rest
All traffic runs over HTTPS, so data is encrypted in transit between your browser and the server. At the database provider your data is also encrypted at rest — stored in encrypted form, not as plain text. So neither on the wire nor on disk is there a readable copy without the right keys.
Each account sees only its own rows
We use row-level security: at the database level, every query is limited to the rows of your own account. No other account can ever see or change your client data, and you can't see theirs. This is enforced in the database itself, not just in the application code — so even if a bug ever crept into the app, the separation holds.
Passwordless login
You log in with a magic link: you enter your email, receive a one-time sign-in link, and you're in. We store no passwords — so there's no password to leak, guess or reuse. Authentication runs through Supabase Auth.
The AI: no training on your data
The text is generated via Anthropic's API. Under their commercial API terms, your inputs and the generated outputs are not used to train their models. The AI only describes factually what was done and how many hours remain — it is never advice, and certainly not medical, financial or legal advice.
You approve every update
Nothing goes to your client automatically. You read every monthly update, can edit every line, and decide yourself whether and when it gets sent. The AI delivers a draft; you keep control over what your client ultimately sees. Outbound email is sent via Resend.
Our sub-processors
We work with a small set of fixed providers: Supabase (database and authentication), Anthropic (AI text generation via API), Resend (outbound email), and later Paddle as merchant-of-record for payments — that one is not connected yet, billing starts later. With each of them a data-processing agreement (DPA) is or will be in place. We add no hidden parties.
Export, retention and deletion
Your data is kept as long as you have an account. You can export it anytime as CSV or JSON. If you delete your account, your data is erased within 30 days, except where a legal retention duty requires us to keep something a little longer. Under the GDPR you have the right to access, rectification, erasure, data portability and objection; we respond within 30 days — the statutory month.
If something does go wrong
If, despite everything, a data breach occurs, we follow the breach-notification duty under the GDPR: we assess the breach, report it to the Dutch Data Protection Authority where required, and inform you if your data is involved. We don't hide incidents.
You always reach a human
Klantr is built and run by one person, and that person is reachable. A question about your data, a deletion request or a privacy concern doesn't disappear into a faceless ticket system — you get an answer from someone who is genuinely accountable for it.
Contact
Questions about your data? Email support@klantr.nl.