Budget and checklist
Budget amounts, plan names and checklist choices are processed in this browser tab. This version does not send them to our server, save them in browser storage, or sync them to an account. They remain available as you move between pages in this tab, but refreshing or closing it clears the working data.
Downloads and printing
Budget CSV files and seller-question TXT files are created in your browser when you request them. Seller selections and order types also stay in this tab; notes are not sent to merchants. Printing uses your browser’s print service. Once you save a file, its storage and any sharing are under your control.
Website requests
A website host necessarily processes network information such as an IP address and requested page to deliver the site. We use Cloudflare to deliver the site. We do not use advertising trackers, remote fonts, session replay or tracking cookies. Budget values and plan names are not added to page URLs or website requests.
Usage measurement
We count page views and actions such as starting a budget, displaying a result, requesting a download and opening a merchant link. Our own counters contain only fixed page and source categories, action types, example/test flags and result states. They do not contain budget amounts, plan names, checklist answers, full URLs, IP addresses or user identifiers. Counts are grouped by hour. Our retention target for these aggregate counters is 90 days; older entries are removed during scheduled maintenance. They cannot reconstruct an individual budget.
On the public site, Cloudflare Web Analytics may also measure page visits, referral and browser information, and loading performance. Cloudflare processes the connection information needed to provide this service. See Cloudflare’s analytics explanation. We do not load these measurements when your browser sends Do Not Track or Global Privacy Control, and test visits are separated from our audience counters. No analytics cookies or cross-site user IDs are set by our code.
Optional updates and tool requests
If you choose the optional updates form, we save your email, selected topic, consent and optional tool request in a separate private Cloudflare D1 database. Email and request text are encrypted; an indexed key is used to prevent duplicate registrations. These details never enter our anonymous usage counters. Please leave out medical, payment or other sensitive personal information.
We will identify whether your request was saved and whether a confirmation email could be sent. Until you confirm, no update subscription is activated. Our sending service receives only the address and email content needed for delivery. Email service acceptance does not guarantee inbox delivery. We send at most two requested practical updates a month, when relevant improvements are available; we do not sell your address.
When sending is available, the private management link in your email lets you change your topic, unsubscribe or delete your saved email and request. Unconfirmed requests expire after seven days. Short-lived keyed network counters help limit abuse without retaining raw IP addresses. A non-reversible suppression key and minimal aggregate records may remain after deletion to avoid accidental sending. You may also request removal by contacting the support address below.
When you contact us
Email is different from the private calculator. If you email [email protected], your address and the information you include are received through our email forwarding and mailbox services. The address uses Cloudflare forwarding to the project’s receiving mailbox. We use messages to handle support and corrections. Please do not send health records, payment details or private seller documents that are unnecessary for the issue.
We aim to remove resolved support correspondence within 90 days unless it is needed for an unresolved issue or a record we must retain. To request removal of your support messages, write to the same address.
Merchant websites
Following an external source link takes you to another website with its own data practices. We use ordinary links in the current version. Any future affiliate tracking will be reviewed and described here before it is enabled. This notice was updated on October 7, 2026.