Privacy
1. The short version
Every draw happens in your browser, and the lists you save are stored on your own device. They are never uploaded, and no server here ever sees a name.
There is no account, no sign-up, no upload button and no server that receives what you type. Every draw, every shuffle and every saved list happens inside your own browser. If you want to verify that rather than believe it: open your browser's developer tools, switch to the network tab, type a list, and spin the wheel. Nothing goes out.
2. What is stored, and where
Your lists and each tool's working state are kept in your browser's local storage, which is a per-site box on your own device. It is not sent anywhere and no server here can read it. The cookies page lists every key by name and explains why local storage is not a cookie.
That is a trade rather than a free win, and the cost belongs here rather than buried: your lists do not follow you to another device, clearing your browsing data removes them with nothing to restore from, and a browser short of space can discard them on its own. There is no copy, because a copy would need a server.
3. Share links
A share link carries the list inside the part of the address after the #. That part is
never sent to a server — it is not in the request, not in the referrer, and not in
any access log. It is why sharing a list works without an upload.
⚠️ It does mean the names are visible to anyone who has the link, and to anything that stores the link — a chat history, a browser's address bar, a bookmark. Treat a share link as being as public as the place you paste it.
4. What the web server sees
Fetching a page is still a request to a computer somewhere, and that is true of every site. The server that sends you these pages necessarily sees your IP address, the page you asked for, the time, and what your browser tells it about itself. That is how the web works rather than something this site chose, but it is not nothing, so it is stated instead of glossed over.
These files are served by Cloudflare Pages, a product of Cloudflare, Inc. Your request reaches one of their servers rather than a machine belonging to this site, so the details above — your IP address, the page, the time — are seen by them in the course of delivering it. Their handling of that is governed by their own privacy terms, not by this page.
5. Advertising
This site is funded by ads. When ads are switched on, Google and its partners may set cookies and collect data under the consent you give — that is disclosed in full on the privacy and cookie pages.
At the time of writing, no advertising code is loaded at all. That is checked on every single build rather than promised: the build fails if any ad or analytics code appears in the files that get published. When that changes, this page and the cookies page change in the same release — they are not allowed to lag behind the switch.
6. Analytics
There are none today. No analytics script of any kind is loaded, and the same build check that covers advertising code covers analytics code.
7. Children
These are ordinary utilities and a classroom is one of the places they are meant to be used. The site asks for no personal information from anybody, of any age, so there is nothing collected from a child any more than from an adult — which is the only guarantee worth making here, and it is made by the design rather than by a policy.
8. Your data, and why this section is short
Most privacy policies explain how to request a copy of your data or ask for it to be deleted. There is nothing here to request or delete. No account exists, no server holds anything of yours, and every list you have typed is already in your own hands — clearing your browser's site data for this site removes all of it, immediately and completely, without asking anybody.
If advertising is switched on later, the data Google collects under your consent is held by Google rather than by this site, and their own controls apply to it. That will be spelled out on the cookies page in the same release that switches it on.
9. Changes
Any change that alters what is stored or what is sent will be recorded on the changelog with its date. This document carries the date it was published at the top.