Privacy policy

Last updated 11 November 2026

calcsheet is operated by Dataraft (calc@struct.work). This page says what the site collects, why, and who else handles it.

Without an account

Using a calculation needs no account, and neither does this browser's first report of a free calculation; after that, downloading a report needs a free account, described below. Opening a calculation's page sets a cookie, calcsheet_used, which holds only the value 1 and lasts a year; the server reads whether it is there, to tell the tallies described below that this browser has used a calculation, and for nothing else. Downloading that first report sets a second cookie, calcsheet_sample, which also holds only the value 1 and lasts a year; the server reads whether it is there, so that the next report asks you to sign in, and for nothing else. The server logs each request: your IP address, the page asked for (including any values carried in its address), and the time. When a calculation refuses its inputs or fails, the values entered are logged too; they are engineering inputs rather than personal data. When you download a report, the calculation's inputs and its short hash are kept, with no link to you, so that the address printed on the report keeps working; the project fields you type into a report are not kept. Logs are used to keep the service running, to find faults and to enforce rate limits. Your IP address is also held briefly in memory to rate-limit requests.

The site loads one analytics script, Umami, from a server we run ourselves. It sets no cookie. Each time you open a page it sends that page's path and title, any campaign tags in the address you arrived by (but none of the values you enter), the path of the page on this site that linked you to it or the address of the outside site that did, your screen size and your browser's language. It also records whether you are signed out, signed in, or signed in with Pro, and nothing else about your account.

It also sends the name of a few things you do, each with the calculation's short name (the one in its address) where there is one: calc-run when a calculation recomputes, with whether its checks pass and its highest demand-to-capacity ratio as a band (0.5 or less, then up to 0.8, 0.95 or 1.0, or above 1.0), which is worked out from the values you enter but is not them; calc-error when it refuses a value, and input-change the first time you change a field, each with the field's name (for a refusal that no single field explains, calc-error carries instead the name of the calculation step that could not be computed, never a value); calc-export when you create its PDF, print it or copy its link, with which of those; paywall-hit when you ask for a report that needs Pro, and upsell-click when you follow the link to buy it; seen-figures, seen-checks, seen-results, seen-derivation, seen-faq, seen-history and seen-related when that part of the page comes into view (seen-derivation-locked for a derivation that needs Pro); engaged once a page has been in front of you for 30 seconds; feedback-yes, feedback-no and feedback-reason when you answer the question at the foot of a calculation, with the reason you picked; solve-click when you press Find the smallest size that passes, and save-click when you press Save this case, with whether that calculation is free, has a Pro report or is Pro; door-signup when you send the form in the panel either button opens, with which button opened it; index-search when you search the list of calculations, with the words you typed (cut to 40 characters), how many calculations matched, and the words again when none did; index-click and calc-link when you follow a link to a calculation or out of one, with where the link sat and whether you had searched; sections-link when you follow a link from the section properties page to a calculation, with that calculation and the section's family; outbound-click when you follow a link to another site, with its address less anything after a question mark; page-404 when a page is not found, with the path asked for when it is under /calc/; sign-in-start when you follow a link to sign in, with where that link sat; signup and login when you create an account or sign in; checkout-start and checkout-complete when you open or finish a checkout, and checkout-close, checkout-error and payment-failed when you close it, it fails or a payment is declined, each with the plan chosen; and found-us when you answer the question on the page after a checkout, with the answer you picked from its list. The signup, login, checkout-start, checkout-complete and paywall-hit events also carry where this visit came from: the campaign tags of the first page you opened in this tab and the name of the outside site that linked to it, where there was one. That, and a link you follow until the next page sends it, are noted in this tab's session storage, which ends when the tab closes. When you open a checkout, those tags and that site name go to Paddle with it, so that a payment can be credited to where you came from. When a payment completes, our server sends one more, payment, with the amount before tax, the currency, whether it bought a report or a subscription, and those tags and that site name. None of them carries the values you enter, your project fields, your name, your email or anything that identifies your account. From the request, the analytics server works out your browser, operating system, device type and rough location (country and, where it can tell, region and city). Umami does not store your IP address; it uses it, with your browser's user agent and a salt that changes every month, to compute a hash that tells one visitor's pages from another's. The site loads no advertising scripts and no third-party fonts or libraries. The one exception is the subscribe page, which loads Paddle's checkout script from Paddle so that you can pay; it runs on that page and nowhere else.

The server also keeps anonymous tallies of page views, recomputes, report downloads, sign-ins and checkouts, one row per event with the calculation's name and the time, so we can see which calculations are used; a sign-in's row names instead where it was started (a report, the page header, the subscribe page or the account pages) or how it failed. Requests whose browser names a known crawler are left out, by reading its user agent at the time and keeping nothing; a page fetched by an AI assistant on a reader's behalf (ChatGPT, Claude or Perplexity) is counted under the assistant's name instead of as a page view. A step towards a report, the subscribe page or a sign-in is counted apart, as unverified, when the request carries neither the calcsheet_used cookie nor a signed-in session. They hold no address, cookie value or account, and are kept beside the account data.

With an account

Signing in uses Google. Google tells us an account identifier, your email address and whether Google has verified it, and offers your name and profile picture, which we do not use or keep. We keep you signed in with one cookie, calcsheet_session, which holds that identifier and is signed so it cannot be altered. A second cookie, calcsheet_oauth, exists only for the few minutes a sign-in takes. A third, calcsheet_event, is set for one minute after you sign in and holds only the word signup or login, so that the page you land on can send that event to analytics when analytics is on; the server never reads it. None of the three is used for advertising.

The first time you sign in we create an account record on our server. It holds the account identifier, your email address and the date you first signed in, and the cases you export: their inputs and title-block fields, so that Your reports can list them and hand the report back. The email address is updated if it has changed when you next sign in. It also notes whether the address has been verified. The identifier recognises you when you return; the email address lets us find your account if you write to us about it. Signing out deletes the cookie; it does not delete the account record. A Pro subscriber may also upload one firm logo, a PNG or an SVG of at most 200 KB; an SVG is converted to PDF when it is uploaded and only that copy is kept. The logo is stored with the account record and printed at the top of every report the subscriber downloads, and used for nothing else; it can be replaced or deleted at any time on the account page and is kept until then. Deleting your account, which you can ask for as Keeping and deleting says, deletes the logo too.

Payments

Payments are handled by Paddle.com as Merchant of Record. We never see or store your card details. When you subscribe, Paddle tells us about the subscription, and we keep with your account record its Paddle customer and subscription identifiers, its status and the end of its current billing period, which is what decides whether Pro is unlocked. When you buy a single report, we keep its Paddle transaction identifier, the calculation it is for and when you paid, which is what unlocks that report for a day. Paddle's privacy policy covers what it holds.

Monthly email

The form on the section properties page and on each calculation sends the address you type straight to listmonk, a mailing list server we run ourselves at list.struct.work; calcsheet's own server never receives or stores it. listmonk keeps your email address, the date you subscribed and whether you have confirmed. It first sends one email asking you to confirm (double opt-in), and sends nothing else until you follow its link. Every email it sends names Dataraft, gives our mailing address and carries an unsubscribe link; unsubscribing takes effect without anything further from you, and you can also unsubscribe by writing to newsletter@struct.work. Your address is used for nothing but this email. It is kept while you are subscribed; an address that is never confirmed is deleted, and after you unsubscribe it is kept marked as unsubscribed, so that you are not mailed again.

Who else handles data

  • Cloudflare, which carries traffic to the site.
  • Google, for sign-in.
  • Paddle, for payments.
  • listmonk, at list.struct.work, our own mailing list server, for the monthly email.

We do not sell personal data or share it for advertising.

Keeping and deleting

Server logs are kept for 30 days. Account data is kept while you have an account. To see, correct or delete what we hold about you, write to calc@struct.work. An email subscriber's address is kept in listmonk as the Monthly email section says.