Privacy
Meelezer reads documents that tend to contain the most sensitive things people own: what they earn, what they owe, where they live, who they are married to. This page says exactly what happens to them. It is written from the code, so the periods below are the ones the system is actually configured with.
Who holds it
WebCie Holding, the Netherlands. Questions, requests and complaints go to jesse@sar.nl and reach a person, not a queue.
Where it is
Everything is in the European Union and nothing leaves it. Documents sit in Amazon S3 in the EU. The record of your credits sits in DynamoDB in the same region. The model that reads your documents runs on AWS Bedrock through an EU-only inference profile, which is what keeps the reading itself inside the EU rather than merely the storage.
How long it is kept
| What | How long |
|---|---|
| The documents you upload | Deleted automatically within 48 hours. The storage rule works in whole days, so a file uploaded late in the day goes sooner than one uploaded early: the true range is roughly 24 to 48 hours. We would rather say 48 than promise 24 and be wrong. |
| What we noted about them — page counts, file names, the short titles the model writes for the sidebar | 2 days |
| Your questions and the answers | Never stored. They live in your browser tab and are gone when you close it. There is no conversation history on our side to hand over, lose or be compelled to produce. |
| Counters that meter free questions | 2 to 30 days. Your network address is never stored: it is hashed with a secret held only by the server, and for IPv6 only the first half is used. |
| Your email address and credit balance, if you have bought credits | Until you ask us to delete it. See below. |
| The record that a payment happened | 400 days. Kept because a refund or a card dispute can arrive months later and has to be matched to the right purchase. |
| Sign-in links | 20 minutes, then unusable. Only a hash of the link is stored, so the stored copy cannot be used to sign in as you. |
Who else can see it
Three companies, each for one job, and no others. Amazon Web Services stores the documents and runs the model that reads them. Stripe takes the payment; card details go to Stripe and never reach us. Amazon SES, also in the EU, delivers sign-in links.
There is no analytics, no advertising, no tracking pixel and no third-party font or script on this site. Nothing about your documents is shared with anyone else, sold, or used to build anything.
Training
Your documents are not used to train any model, by us or by anyone else. The model reads them to answer your question and that is the end of it. We do not keep them for the purpose, and the AWS Bedrock service they run through does not use customer content to train models.
Cookies
One cookie, named meelezer. It contains a random identifier and nothing else — no email, no balance, no counters — and it exists so that credits you buy can be found again on your next visit. It is signed so it cannot be edited, and unreadable to JavaScript. There are no other cookies, and none from anybody else.
Deleting your data
Documents go on their own within 48 hours; you do not need to ask. To delete the email address and balance held against your browser, send {"confirm":"delete my data"} to DELETE /api/account from the browser in question, or simply write to jesse@sar.nl and we will do it. Erasure destroys any remaining credits and cannot be undone.
Two things we cannot delete, said plainly rather than buried. Stripe keeps its own record of a payment, which it is required to keep for tax and dispute purposes. And our database keeps point-in-time backups that age out on their own schedule, so an erased record can persist in a backup for a short while after it is gone from the live table.
Your rights
Under the GDPR you can ask what we hold about you, ask for it to be corrected or deleted, and object to how it is used. Write to jesse@sar.nl. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.
If anything on this page turns out not to match what the software does, the software is wrong and we want to hear about it.