Privacy Policy
Effective 8 September 2026. Ultrabench · ultrabench.dev
Short version: the only personal data we ask you for is an email address, we do not sell anything to anyone, there are no cookies and no analytics, and one email to support@ultrabench.dev deletes you.
What we collect
- Your email address, plus the date and which form you used, when you subscribe to the newsletter or ask for the pre-order link. Nothing else — we do not ask for your name.
- Your ballot, if you vote on what gets benchmarked first: the address and the option you picked, so that one address counts once. Voting does not subscribe you to anything unless you tick the box that says so, and the published tally is counts only.
- Ordinary server logs. This site runs on Cloudflare, which records request metadata (IP address, user agent, URL, timestamp) to serve and protect it. We do not join those logs to your email address and we do not build profiles from them.
- Order records for anything you buy: what you bought, when, and the processor's order reference. Card numbers never reach us — Lemon Squeezy or Stripe handles payment and holds the billing data under its own privacy policy.
- Files and configurations you submit for a benchmark run or batch job, and the results we produce from them. Retention and handling are in the acceptable use policy: deleted within 30 days of delivery unless you ask sooner.
- Mail you send us, kept as sent so we can answer it and keep a support history.
No cookies are set by this site. There is no advertising network, no session tracking, no analytics script, and no social embed. If that ever changes, this page changes first.
Why, and on what basis
We use your address to send what you asked for, and we use order and support records to deliver purchases, handle refunds and meet tax and accounting obligations. Under the GDPR and UK GDPR, that is consent for the newsletter (withdrawable at any time), contractual necessity for purchases, and legal obligation for the records tax law requires us to keep.
Who else sees it
Only processors doing work we cannot do ourselves: Cloudflare (hosting, email delivery, storage), Lemon Squeezy (consumer checkout, as merchant of record), Stripe (invoiced business payments), and Anthropic, whose Claude models draft and answer our mail and generate this site — mail you send us is processed by them for that purpose, under their terms. We do not sell personal data, we do not share it for cross-context behavioural advertising, and we have never received a government request for it. Data may be processed in the United States.
How long we keep it
Subscriber addresses until you unsubscribe or ask for deletion, then removed on the next working day. Job inputs and outputs: 30 days. Order and tax records: as long as tax law requires, currently seven years. Support mail: three years.
Your rights
Whatever your jurisdiction, one route works: mail support@ultrabench.dev and ask. You can get a copy of what we hold, have it corrected, have it deleted, or object to a use. We answer within 30 days and we do not charge for it, and we will not make you use a form or a portal. EU/UK residents may also complain to their supervisory authority; California residents have the CCPA rights to know, delete, correct and opt out of sale or sharing, and we do not sell or share. We will never discriminate against you for exercising a right.
Email specifics
Every newsletter carries one-click unsubscribe and, from the first send, our postal address. We do not use open- or click-tracking pixels. A business mailing address is being established and will be published here and in every newsletter footer before any bulk email is sent. Until then, the postal address of the responsible party is available on request from support@ultrabench.dev.
Children
This is not a service for children. We do not knowingly collect data from anyone under 16; if we learn we have, we delete it.
Security, and its limits
Addresses live in a Cloudflare database reachable only by our own code; credentials live in an OS keychain, not in this repository; the machine that does the work makes outbound connections only and accepts no inbound traffic. This is a one-person, one-machine operation, so treat it accordingly: do not send us secrets, credentials or regulated personal data (see acceptable use). If we ever have a breach affecting your data, we will email you and post it here.
Changes
New version, new effective date, and an email to subscribers for anything material. Previous versions are in the operator's public repository history.