What we collect
The static editorial pages do not run analytics, set their own cookies, offer accounts or collect form submissions. If you email the editors, the message and your return address are received through email, outside those pages. Owner reviews are written in a separate application under /owners/, described below.
Calculators
Calculator inputs are processed in your browser and are never sent to a server, placed in a web address, stored on your device or written to any log. Closing the page discards them. There is no “save” function; if one is added later it will be opt-in and will say plainly that another person using the same device could read what you saved.
Third parties
The static editorial pages serve their assets, including fonts, from this site. Owner review pages can load Cloudflare Turnstile to check sign-ins and review submissions.
Hosting
The static editorial pages are hosted as files by Vercel. The host processes ordinary request information, which can include an IP address, requested URL and browser details, to deliver and secure the site. The site operator may have access to limited hosting logs. Do not put personal or calculator information in a page URL.
Owner reviews
Owner reviews and detailed records are written in the owner reviews section of this site (/owners/), which runs as a separate application with its own sign-in. A short review needs no email sign-in: sending it creates an anonymous account and uses session cookies to keep your access in that browser. A detailed record needs an email sign-in. Those cookies can accompany other requests to this site. The owner-review application stores what you enter; the static editorial pages do not collect it.
- What is stored. Your email address if you give one (it is optional for a short review), the name you give, your country, whether you are a household or business, and what you write about your machine. A detailed record can also hold dates, costs, serial or order numbers and documents you upload.
- What can become public. Only what you agree to: for a short review, your words exactly as written (a moderator never edits them); for a detailed record, a summary you approve word for word. Your country and the name you choose to sign with can appear. Your email, documents, serial and order numbers, prices and private messages never do.
- Who reads it. The editors listed on the About page, as moderators. Moderator sign-in needs a second factor.
- Your email address. If you sign in, it identifies your account. If you give it with a review, an editor may use it to ask about that review or record if you choose follow-up contact. The account and email services process it. We do not publish it, sell it, give it to makers or add it to a mailing list. A short review sent without one may not be accepted, because the editors cannot check anything with you.
- Withdrawal and erasure. You can withdraw a published review at any time on that site, and it disappears from the owner reports pages at once. Copies already made by others, such as search engine caches or archives, are outside our control. To ask for deletion of your account and what you sent, sign in to the owner reviews application and use Delete your account. To ask about deleting one review or record, or if you cannot sign in, contact the editors.
- Deletion on request. A deletion request starts the documented erasure process; it is not the completed deletion. The editors remove the account, records, files and history, keeping one dated line that a deletion took place.
- Services involved. Supabase stores the records and handles sign-in; Vercel hosts the site; Cloudflare Turnstile checks that a person, not a script, is signing in or sending a review, and receives your IP address to do so. The site has no analytics. Public review filters can appear in a web address. Private review text, contact details, original documents and calculator inputs stay out of those addresses.
Correction, October 19, 2026: Earlier wording applied the static editorial pages’ privacy limits across the site. It also omitted the in-app deletion request and did not distinguish that request from the editors’ erasure procedure.