What Solenoid stores about you
This is everything the Solenoid API and this website store or log about you, taken from the code. The agency responsible is Robin Lange, trading as omit, in New Zealand.
| What | Where | How long | Why |
|---|---|---|---|
| Your account ID and plan | Your account's Durable Object | For the life of the account. Keys are never stored: they are derived when needed. | To run your account and apply your plan's allowance |
| Ledger entries: scopes, units, amounts, timestamps, idempotency keys and signatures | Your account's Durable Object | For the life of the account. Nothing deletes them automatically yet. | To enforce your limits and give you signed receipts |
| A salted hash of your network address for each signup and account recovery | Solenoid's own ledger, in the ops account's Durable Object | Indefinitely. Rows written before 11 pm UTC on 30 September 2026 hold an unsalted hash. | To limit how many signups and recoveries come from one network |
| Your recovery email | Your account's Durable Object | Until you replace it. Replacing it also emails the previous address. | So you can get your admin key back by email |
| The 6-digit code emailed when you attach or recover a recovery email: the address, the time and a keyed hash of the code, and a record of each send and each failed attempt | Your account's Durable Object | A code stops working 15 minutes after it is sent. A scheduled job deletes each code and each record within a day of writing it. | To confirm you control the address, and to limit sends and guesses |
| Code, confirmation and change-notice emails, with the address each goes to | Resend, which sends them | Resend's own retention (Resend's privacy policy) | To deliver them |
| Request logs, which can include your IP address and request headers, and logged error text | Cloudflare Workers Logs on the API (Workers Logs docs) | 7 days, on the Workers Paid plan | To find and fix errors and abuse |
| Page visits on this site: the URL with its query string (so a ?ref= tag), the referrer, your browser, device and country | Umami, a privacy-first analytics tool omit hosts itself. It uses no cookies, and this site's script tells it to honour Do Not Track. (Umami on cookies, Umami on Do Not Track) | Until omit deletes them | To count visits and see which links bring people here |
| Billing name, email, card and address; your account ID, as the Checkout client_reference_id and on the subscription | Stripe | Stripe's own retention (Stripe's privacy policy) | To take payment for Pro and match it to your account |
| Your Stripe customer and subscription IDs; the ID, link and expiry of your latest Checkout page; and the ID of any second subscription found while you were already on Pro | Your account's Durable Object | For the life of the account. The Checkout page entry is replaced by the next one. | To manage your plan, report usage to Stripe, reuse an open Checkout page and catch a second subscription |
| If a second subscription is found while you are on Pro: your account ID, its subscription ID and its Checkout page ID | An email to security@solenoid.systems, sent through Resend | Resend's own retention, and in that mailbox until deleted by hand | So a duplicate payment can be refunded by hand |
| Email you send to privacy@solenoid.systems or security@solenoid.systems | Solenoid's mailbox | Until deleted by hand | To answer you |
Your account's Durable Object is placed in one Cloudflare data center when it is created, and it does not move after that (Cloudflare's data location docs). That can be outside New Zealand. Cloudflare, Stripe and Resend process data outside New Zealand under their own terms: see the privacy policies of Cloudflare, Stripe and Resend.
To see, correct or ask us to delete what Solenoid holds about you under the NZ Privacy Act 2020, email privacy@solenoid.systems. We answer within 20 working days (section 44, section 63).