Privacy

What you type into a tool

It stays on your device. Every tool currently on this site does its work in the page, so there is no request that could carry your input anywhere. Turn off your network and the tools keep working.

This is enforced rather than promised: the build fails if a tool page makes an unexpected network request, or if text typed into a tool appears in any request. How we build tools explains the mechanism and how to verify it yourself.

Share links carry their state in the part of the URL after the #, which browsers never send to a server. So a shared palette or configuration reaches the person you sent it to without ever reaching us.

What is stored on your device

Some tools can remember things between visits, such as a class list or a set of previously used campaign names. Where that exists:

• it is off until you switch it on;
• the control says in plain words what is being kept;
• one button clears it;
• it is stored in your browser only and is never transmitted.

Clearing your browser's site data removes it. We have no copy, so we cannot restore it and cannot look at it.

Server logs

This site is hosted on Vercel. Like any web host, their servers record requests for the pages and files you load, including your IP address, the time, the page requested and your browser's user-agent string. That is a normal consequence of loading a web page from any server anywhere, and it is how the site gets to your browser at all.

We do not add anything to those logs, do not join them to anything, and do not use them to build a profile. Note the distinction the rest of this page rests on: the host can see that you requested a page. Nobody, including us, can see what you typed into the tool on it.

Analytics

There is none installed today. No analytics vendor's script loads on any page of this site, no request is made to any analytics service, and no page-view is reported to anyone. You can check this the same way we do: open your browser's network panel and watch what a page requests. Every request goes to this domain.

One precision, because the sentence above used to be wider than the truth and a reader could catch it. The site ships its own small analytics module, and you will see a file with Analytics in its name load. It is the switch, not the tag: while no vendor is configured it contacts nothing and reports nothing. What we promise is that no third party receives anything, not that no file with that word in it exists.

The product that will be installed is Google Analytics 4. The property was created on 22 August 2026 and has received nothing since, because creating a property and installing a tag are two different acts and only the first has happened. There is no tag on this site, so there is no data in it. Consent will be offered by Google Funding Choices before any analytics cookie is set.

The install itself has no date, and we are not going to publish one we do not have. It ships when the engineering ahead of it is finished, and a date here that slipped would simply become another false sentence on this page. Until a dated entry in the changelog records that the tag is live, the paragraphs above are the whole current truth and nothing in the rest of this section is collecting. From the date of that changelog entry, the rest of this section describes what runs.

Google Analytics 4 is not cookieless. That is the entire reason a consent mechanism is required for it, and why Funding Choices ships with it rather than after. When the tag is live, GA4 will set cookies for measurement once you have been offered a choice and have accepted; declining will be as easy as accepting. Event data retention will be set to 14 months. Google signals will be off: that is a deliberate choice against cross-device advertising identity, not a default we left alone.

When the tag is live, pages will contact these hosts for analytics and consent, and no others for that purpose:

• https://www.googletagmanager.com
• https://www.google-analytics.com
• https://fundingchoicesmessages.google.com

Today none of those hosts are contacted. The network allowlist the build enforces is empty, so any page that reached one of them would fail the gate. When the tag ships, those three origins are added to that allowlist in the same commit as the tag, and this page's list is updated in that commit if it changes. The gate continues to refuse anything not on the allowlist.

The tool promise is untouched by Google Analytics 4. What you type into a tool stays in the page. When a tool does put state in the address, which happens when you use a share or copy-link control rather than automatically as you type, it goes in the part after the hash mark, and browsers never put that fragment into an HTTP request to our servers. When GA4 is configured, the page_location value sent to Google is stripped of both the hash and the query string at config time, so tool state is not in what leaves for analytics. That is what we send, not a claim about what the script can read in your tab: a script running on the page can see the full address in JavaScript. Nothing you type leaves your browser for us, for Google, or for anyone else.

On the build check, precisely, because the earlier wording here claimed more than the code does. The release is checked with analytics forced on against pages carrying tool state in the address, and it fails if any request carries that state onward. That check currently exercises the analytics path this site actually has configured, which is not GA4. A GA4-specific version of that check ships with the tag, before it, not after, and until then this paragraph is describing a test of a different vendor's path. We would rather say that than let the sentence borrow credit.

Advertising

There are no ads on the site today. No advertising code loads on any page and no ad request is made.

An application to Google AdSense was submitted on August 19, 2026. That is why the site now serves an ads.txt file naming Google as an authorized seller, and why every page carries a site ownership tag in its source. Both are how a publisher proves it owns a domain. Neither shows you an ad, and neither contacts anyone when you load a page. If the application is approved, the paragraph below starts applying, and this page will be rewritten before a single ad runs.

Stated plainly, because this is the part that genuinely changes: an advertising network is a third party, and when ads are running it will be able to see that your browser loaded a page on this site, and may use cookies or similar technology depending on your consent choices. Visitors in the EEA and the UK will get a consent choice before any of that happens, and declining will be as easy as accepting.

What will not change is the tool itself. Your input still never leaves your browser, with ads or without them. Those are two separate questions and it would be dishonest to let a strong answer to the first one imply an answer to the second.

Cookies

The site sets none today. When Google Analytics 4 and Funding Choices are live, Funding Choices will set a cookie to remember your consent choice, and GA4 will set measurement cookies only after that choice has been offered and accepted. The consent cookie is the one that is hard to avoid without asking you again on every page; the measurement cookies are optional and follow your choice.

Children

Some tools here are built for classroom use and will be used by teachers with students present. They collect nothing, require no account, and store nothing on a server, which is the design that makes them safe to project. We do not knowingly collect personal information from anyone, of any age.

Your rights

Data protection law gives you rights to access, correct and delete personal data held about you. We hold none, so there is nothing to access, correct or delete. If you believe that is wrong, write to us and we will look into it.

Changes

When this page changes materially, the date at the bottom moves and the change is noted in the changelog. Adding analytics or advertising counts as material and will be recorded that way.

A note on this document

This is written in plain English by the person who built the site, and it describes the site accurately. It has not been reviewed by a lawyer. If you need a formal data processing agreement or a compliance attestation for your organization, get in touch and say so.

Last updated August 23, 2026. Only changed when something material changed, which is why some of these dates are old.