Let Agents In

Privacy

Krystian Gwizdała, a private individual in Poland, is the controller of the data described here. Write to hello@letagentsin.com about anything on this page, including deletion. There is no registered company behind this yet. If one is formed and becomes the controller, this page will say so and everyone whose address we hold will be told.

What we store

  • Scan results. Requests to public pages of a domain, and what they answered. These describe companies rather than people, and they are published: every scan has a permanent link and the curated set is downloadable at /corpus.json.
  • An email address, when you give one: to send a scan result, to confirm a domain you asked us to watch, or to deliver something you bought. A watch record holds an identifier for the watch itself, the address you gave us, the domain you asked us to watch, when it was created, when you confirmed it, which measurement the last alert was compared against, the score at that measurement, how many points were measurable then, when we last checked, when you stopped it, kept so we cannot undo your unsubscribe, whether it is a trial or paid, the subscription identifier, when there is one, which category to read the domain against, when it is not one we publish, the brand name to search for beside the domain, when you gave one. That list is generated from the record itself rather than written here, so it cannot fall behind it. Nothing is bought from anybody, nothing is joined to anything, and no third party receives it.
  • A page counter. A date, a path, and whether the request looked like a browser, an unnamed client, or one of a short list of search and AI crawlers we watch for by name so we can tell which indexes read us. The crawler name is the only thing kept from the user-agent, and it names a company's robot rather than a visitor. No IP address, no user-agent string stored, no identifier that could be joined to a person.

What we do not do

No cookies. No analytics script, no advertising pixel, no session recording, no third-party tag of any kind. We sell vendors the argument that a page should be readable without running a bundle, so a tracker that needs JavaScript would sit badly next to it and would miss the visitor we care about anyway. We do not sell or share personal data, and we do not use it to train anything.

Who processes it for us

Heroku (hosting, EU region), MongoDB Atlas (storage), and Resend (email delivery). Each of them sees only what is needed to do that job. A payment provider is added here the day payments go live, and it will be named before anybody is asked for a card.

How long

Scan results are kept as long as they are published, because a permanent link that stops working is worse than one that ages. An address given for monitoring is kept until you stop it: every email we send carries a stop link, and using it ends the mail immediately. An address given for a one-off delivery is kept for as long as we owe you a receipt or a rescan.

Your rights

Access, correction, deletion, portability and objection, under the GDPR. One email to hello@letagentsin.com is enough, and there is no account to close first. You can also complain to your data protection authority.

Scanning somebody else

Anyone can scan any domain here, which is the point: a vendor is measured the way an agent would measure them, from the outside, using only what they publish. If your domain is in our corpus and you would rather it were not, write and it comes out. If a verdict about you is wrong, write and we rescan; corrections are published beside the row rather than quietly applied.