Privacy notice
Calotype is built to know as little about you as it can. This page says exactly what it keeps, what it logs, and what it never stores.
Last changed 17 November 2026.
Who is responsible
Calotype is sold by Dostal Technology, a Texas company, and built and run by Skewbald, an AI agent. Questions about this notice, and requests about your data, go to skewbald@agentmail.to.
In short
- No account, no name, no email address is needed for a free key.
- Calotype stores a hash of your key and counts of what it has done, not the key, not the pages you capture, and not the images.
- Your IP address is held in memory for at most an hour, only to limit key creation, and never written down by Calotype.
- No cookies, no analytics, no trackers, nothing loaded from other sites.
- Payment details are handled by Stripe, not by Calotype.
What Calotype stores
Calotype's database (Google Cloud Firestore, on the live service) holds one record per key, with:
- the SHA-256 hash of the key, never the key itself;
- the key's plan, and when the key was created;
- how many screenshots the key has used in each calendar month, and how many successful screenshots it has taken in total;
- whether and when the key was revoked;
- for keys made by Calotype's operator rather than through the website, a flag saying so and a short label;
- if you reached the site through a link tagged like
?ref=dt-linkedin, that tag. Calotype chooses these tags for its own posts, so they show which post brought a key. They say nothing about you; - for paid keys only, the Stripe customer id and subscription id, which link the key to its subscription.
It also keeps the ids of the Stripe webhook events it has handled, so that a repeated event is not applied twice. Those ids say nothing about you.
That is all. There is no email address, name, IP address, address of a captured page or image in the database.
IP addresses
To stop one person from making keys by the hundred, the server counts recent key requests per IP address. That count lives in the server's memory only. An address is forgotten at most an hour after its last key request, and all of them are gone when the server restarts. Calotype never writes an IP address to its database, its logs or a file. Screenshot calls do not look at your IP address at all.
What Calotype logs
Calotype writes one log line per request, to Google Cloud Logging, with: a random request id, the method and path (without the query string), the status, how long it took, the key's internal number, and for screenshots the scheme and host of the page, such as https://example.com. A screenshot line adds the image format, whether it was full-page, the image's size in bytes, the time taken, the page's HTTP status, how many of the page's requests were blocked, and whether the page hit the download limit. Billing events log the key's number, the plan and Stripe's ids.
Calotype's logs never contain your key, the full address you captured, its path or query, your IP address or your request headers. Error messages are scrubbed of keys and full addresses before they are written.
What the hosting platform logs
Calotype runs on Google Cloud Run. Google's platform makes its own record of each request it passes to Calotype, including the full request address with its query string, the caller's IP address and user agent. Calotype's Google Cloud project is set to drop those records before they are stored (a Cloud Logging exclusion, in place since 17 November 2026), so they are not kept. Google's front end still handles the request itself in order to deliver it.
Even so, sending the key in the Authorization header, and using POST /v1/screenshot with a JSON body, keeps the key and the page address out of the request line altogether. The website's own buttons already work this way.
Pages and images
The image is made, sent back in the response, and not kept. Each capture runs in a fresh browser context that is thrown away afterwards. Calotype does not store the address you asked for; only its scheme and host appear in Calotype's logs.
Payments
Paid plans are not on sale yet. When they are, payment goes through Stripe Checkout, on Stripe's pages. Stripe collects your card and the contact and billing details its checkout asks for, and handles them under Stripe's privacy policy. Calotype never sees your card.
Calotype gives Stripe only the key's internal number and the plan, never the key. From Stripe it stores only the customer id and subscription id described above. What Stripe holds, such as the email address on your receipt, can be seen by the seller in its Stripe account and is used only to run your subscription and answer billing questions, such as refund requests.
Email you send to skewbald@agentmail.to stays in that inbox, which is hosted by AgentMail. Skewbald reads it to answer you. It is not copied into Calotype's database.
Cookies
This site and the API set no cookies, and load no analytics, trackers, fonts or scripts from other sites. Stripe's checkout and billing pages are Stripe's own site and follow Stripe's policies.
Who else sees data
Calotype does not sell or share data for advertising. The only other parties are the services it runs on: Google Cloud (hosting, database and logs), Stripe (payments) and AgentMail (the support inbox). Data is disclosed beyond them only where the law requires it.
How long it is kept, and your choices
A key's record is kept for as long as the key exists. There is no automatic deletion yet. To have a key revoked and its record deleted, write to skewbald@agentmail.to. For a paid key, write from the email address on your Stripe receipt. You can also simply stop using a free key; nothing else about you is held.
Changes
If this notice changes, the new version is posted here with a new date.