Plain version
What this site collects
Written from the code, not from a template. If a sentence here is wrong, the code is the thing to fix, not the sentence.
The short version
- The shift calculator and the contract decoder send nothing anywhere. Every number you type stays in your browser.
- The site counts visits with its own software, on its own machine. Nothing about your visit is sent to another company. One older section, the charting notes, also still loads Google Analytics, and that one does leave our machine.
- Your full IP address is written to the server log and kept 90 days. Every web server does this; ours is not sent anywhere. In the visit counts we build from it, the address is either shortened or replaced by a one-way hash first.
- Nothing you type into a form is stored with your IP address. Shared sheets, question ratings and comments carry a one-way hash, never the address itself. The one thing we keep that identifies you is an email address, and only if you subscribe.
- No ads, no third-party trackers beyond the one named below, nothing sold or shared. There is nobody to sell it to and nothing worth selling.
- No account, anywhere. There is no login, no password and no profile on this site.
What the server writes down
Every website's server keeps a log. Ours records, for each request: the time, the page, the browser's self-description, the referring page if the browser sends one, and the IP address. That is how we count whether anyone reads this.
The log is kept 90 days and then rolls off by itself. It sits on our own machine and is not sent anywhere. When we produce visitor counts from it, the IP is replaced by a one-way hash first. That is enough to tell one reader from another and not enough to identify anybody.
The “your own series” form
If you fill in the form on /series/, what you typed (your description, email, and name and platform if you gave them) is saved in a file on our own machine and emailed to the one person who runs this site, so he can answer. It is not added to any list and not shared. To have a request deleted, write to [email protected].
Note helper
What you type into Note helper goes to OpenAI to write the draft and comes back to your browser. We do not save it; OpenAI may keep it up to 30 days for abuse monitoring and does not train on it. Your entries stay in your browser's local storage and clear after 16 hours.
We count drafts per day, their cost, and a salted hash of a random number your browser makes; we cannot link it to you. To keep it free for everyone, each connection gets a daily limit: for that we keep a one-way code made from the IP address for two days, then delete it. The access log keeps the IP as for any page.
Google Analytics, charting notes only
The charting notes load Google Analytics, so we can tell whether the writing is read. It sets a cookie. It runs on those pages and no others.
The shift calculator, the contract decoder, the schedule builder, the report sheets, the study guides, the practice questions, the episode pages do not load it, and the pages that promise that in their own text still mean it.
What Google does with what it collects is described in How Google uses information from sites that use our services. If you would rather it did not run, an ad blocker or Google's own opt-out add-on both stop it, and nothing on the site breaks.
What stays in your browser
These are saved on your own device and never sent to us:
Your base rate and differentials on the shift calculator, so you do not retype them. The hours you worked are not saved.
The offers you compared in the contract decoder.
The shifts you picked in the schedule builder and its settings.
Your attempts in the practice questions and the study guides: an unfinished run, past scores and the questions you keep missing, so you can repeat only those.
Report-sheet layouts you built, and which gallery layouts you already liked, so one person counts once.
Light or dark, if you pressed the switch.
Clearing your browser data removes all of it. We never see any of it.
What happens when you send us something
Nothing reaches our server unless you press a button to send it. These are all the places where that happens.
Shared report sheets
If you send a layout to the gallery, we keep the layout, the title and the unit name you typed, plus a hash of your IP. Liking a layout in the gallery stores the layout, the day and a hash of your IP, so one person counts once.
Practice questions and study guides
Three buttons send something. “Fair question?” stores which question, your answer (up or down) and a hash of your IP. Asking for a new question set stores the topic you typed and the same kind of hash. A comment under a set stores what you wrote, the name, role and years you chose to add (all optional), and a hash of your IP; it stays on the page. Your answers to the questions themselves are never sent.
Subscribing to the monthly note
If you subscribe, we keep your email address, the page you subscribed from and a hash of your IP. Nothing is sent until you click the link in the confirmation email. Unsubscribing deletes the address; we keep no list of people who left.
“Email it to me”
On the shift calculator and the contract decoder you can mail the numbers to yourself. They are sent once and not kept: we do not store the address or the numbers after the email goes out.
Mail to [email protected] is forwarded by Cloudflare to a personal mailbox and read by one person. Writing to us does not put you on the subscriber list.
Emails we send (the subscription confirmation, the monthly note and “email it to me”) go out through Resend, an email delivery service. It receives the address and the text of that one email in order to deliver it.
Where this runs
On a computer in an apartment, not in a datacentre. Cloudflare sits in front of it, so they see requests on their way through, as they do for a large share of the internet. Fonts, images and scripts are all served from this domain. The only other companies that receive anything are the two named above: Google Analytics on the charting notes, and Resend for emails you asked for.
Our Instagram and YouTube connection
Our own Instagram account is connected to a small app we wrote, and our YouTube channel is read through Google's public API. They read our posts: view counts and other numbers, and the comments people leave under our videos: the comment text, the public username and the time. We use the numbers to see which episodes work, and the comments so we do not miss them: a draft reply is written for each, and we post the reply ourselves, by hand.
Comments are kept on our own machine, the same one that runs this site. They are not sold, not shared, not used for ads and not combined with anything else. The app posts nothing and reads nothing outside our own account.
Deleting your data
If you commented on one of our videos and want that comment removed from what we keep, write to [email protected] with your username. We delete it from our machine and reply to confirm. Deleting the comment on Instagram, TikTok or YouTube itself is done there, by you.
If you want something removed
Write to [email protected]. Be aware that most of what is here cannot be traced back to you even by us: what you send carries a hash, not an address.
When this changes
This page is updated when the code is, not on a schedule. It says 5 October 2026 below because that is when it was last checked against what the site actually does.
The terms for using the site are on a separate page: Terms of use.
Last checked against the code: 5 October 2026.