Subprocessors
Some parts of CalculatorLib are run for us by other companies. This page lists every one of them that can see data from your visit, what it processes and why. It is written from the code that actually runs the site, not from a template.
Last reviewed: November 7, 2026.
Where your data is kept
Everything the service stores for you — your account, your saved calculations and your support tickets — sits on our own machines in three places: the main copy in Germany and a live copy in France, both inside the European Union, and another live copy in the United States, on a server we rent from DigitalOcean in New York. Backups of that data are kept with Cloudflare R2 (encrypted) and, until that copy is retired in November 2026, also with Backblaze B2 — see their rows above. There is no other option: we cannot move an account to a different region on request, and we cannot keep it inside the European Union only. The companies in the table above process data elsewhere wherever their row says so.
One exception to the machines above: the files you attach to a support ticket, and the encrypted backups of everything described here, are stored in Cloudflare R2 in its Asia-Pacific region, which is outside the European Union. That transfer relies on Cloudflare's data processing agreement, which includes the Standard Contractual Clauses.
| Processor | What it processes | Why | Where it processes |
|---|---|---|---|
| Cloudflare | What it processesEvery request to the site passes through Cloudflare: your IP address, the page you asked for and your browser headers. It also runs the anti-abuse check on our sign-in, sign-up and support forms, the image service, the on-site assistant, PDF export, and Cloudflare R2, our main file storage: the site's media files, uploaded files and our encrypted daily database backup. | WhyDelivering the site quickly worldwide, keeping automated abuse off the forms, and storing our files and backups. | Where it processesGlobal edge network, wherever you connect from. Files stored in Cloudflare R2 (media, support-ticket attachments, encrypted backups): Asia-Pacific region, outside the European Union. |
| Server hosting (OVH) | What it processesOur application server, our main database and our search index run on a machine we rent from OVH in Germany. A second OVH machine, in France, keeps a full live copy of the database and holds the sign-in sessions. Everything the service stores — your account, saved calculations, support tickets — sits on them. | WhyThe service has to run somewhere. We administer these machines; the provider supplies and physically secures them. | Where it processesGermany and France (European Union) — our own machines in OVH data centres. |
| DigitalOcean | What it processesA third machine, a server we rent from DigitalOcean in its New York region, keeps another full live copy of our database — including your account, saved calculations and support tickets — and a copy of the sign-in sessions. | WhyKeeping the service running and the data intact if one of our other machines fails. We administer this server; DigitalOcean supplies and physically secures it. | Where it processesUnited States (New York region) — our own server in a DigitalOcean data centre. |
| What it processesGoogle Analytics receives page views with your approximate location and device type. Google AdSense receives ad requests on pages that show ads. If you choose Sign in with Google, Google confirms your email address to us. | WhyUnderstanding which tools people use, funding free access with advertising, and offering a sign-in that needs no new password. | Where it processesUnited States, on infrastructure spread across several countries. | |
| Sentry | What it processesWhen something breaks, an error report is sent: the page URL, your browser and the technical details of the fault. It is not loaded until you interact with the page. | WhySeeing faults and fixing them, instead of waiting for somebody to report a broken page. | Where it processesUnited States. |
| Email delivery (Cloudflare Email Service) | What it processesYour email address and the content of the message whenever we send you one: verification, sign-in, security alerts and billing notices. | WhyDelivering account and billing email reliably. We send it through Cloudflare Email Service rather than from our own servers; Cloudflare is the same company listed above. | Where it processesUnited States, on infrastructure spread across several countries. |
| Stripe | What it processesOnly if you buy a paid plan: your name, email, billing details and card data, which you enter on Stripe pages. Card numbers never reach our servers. | WhyTaking payment and managing subscriptions. | Where it processesUnited States, with its Irish company as the contracting party for Europe. |
| Backblaze B2 | What it processesA second copy of our daily database backup, which includes account data, and older copies of the site's media files. Our main storage and backups are on Cloudflare R2. Backblaze receives this second backup copy only during a short transition; after that it stops, and the copies held there will be deleted. | WhyA secondary backup copy during a short transition, before it is stopped and deleted. | Where it processesUnited States. |
| Anthropic (Claude) | What it processesCalculator content and descriptions, which Claude helps us write and check. Search phrases — both those that bring people to us from Google Search and those typed into our own search box — pooled together with every digit replaced before they are sent, so none of them is tied to a visitor or an account. Messages sent through our support and feedback forms, after email addresses, phone numbers and other personal details have been removed. While helping us fix a fault, Claude Code, the AI assistant our engineers use, may also see logs and stored data. The on-site assistant does not use Anthropic. | WhyWriting and checking calculator content, finding out which tools people look for but cannot find, sorting support requests and feedback, and fixing faults faster. What we send through Anthropic’s API is covered by its commercial terms, which do not allow Anthropic to train its models on it. | Where it processesUnited States, on infrastructure spread across several countries. |
| On-site assistant (Cloudflare Workers AI, Fireworks AI, TypeSafe via OpenRouter) | What it processesWhatever you type into the chat assistant is sent for an answer, along with the page you are on. Do not put personal details in it. | WhyAnswering questions about the calculators. The assistant runs on Cloudflare Workers and passes your question to a language-model provider and, to choose the right calculator, to a decision-model provider (TypeSafe, via OpenRouter). | Where it processesUnited States, on infrastructure spread across several countries. |
| Browser notifications (web push) | What it processesOnly if you turn on browser notifications: the push address your browser gives us, each alert, encrypted on our server before it leaves so the push service cannot read it, and the time it is sent. | WhyDelivering the alerts you asked for. Your browser decides which push service carries them: Google for Chrome and Android, Apple for Safari, Microsoft for Edge, Mozilla for Firefox. We send from our own server, with no other company in between. | Where it processesUnited States, on infrastructure spread across several countries. |
| Have I Been Pwned (Pwned Passwords) | What it processesOnly when you choose or change a password: the first five characters of the password's SHA-1 hash, so we can check it against passwords already exposed in data breaches. Your password, its full hash and your email address are never sent. | WhyRefusing passwords that criminals already have. | Where it processesGlobal — its edge network, wherever you connect from. |
Scroll the table sideways to read every column.
The last column says where each one processes. Where we cannot show it from our own configuration or a contract, the cell says so instead of guessing.
What runs on our own machines
Our database, search index and cache run on our own servers — the rented machines described under “Server hosting” and “DigitalOcean” above — inside a private network, and the calculation itself is done there. No calculator input is sent to any company on this list to be computed, and none of them is part of how the feature works.
One thing to be clear about, because it is easy to miss. Your inputs still travel to us over the network, so Cloudflare, which every request to the site passes through, carries them. And after you press Calculate they are written into the page address, so the result can be bookmarked and shared: from that moment they are part of the URL, and the services above that see page addresses see them too — analytics on any visit to that link, and an error report if the page then fails. The on-site assistant is a separate surface, described in its own row above.