RandomLast updated: 12 October 2026
The short version
- There are no accounts, so there is nothing to sign up for and nothing to sign in to.
- Every generator runs in your browser. The names, lists and questions you type are never sent to us.
- We run two scripts from Google: Google Analytics, which counts page visits and sets one cookie if you allow it, and Google AdSense, which shows the adverts and is told not to use advertising cookies. Neither ever sees what you type into a generator.
- Your saved lists and recent results are stored by your own browser, on your own device, and you can erase them from this page.
- Our server keeps ordinary web access logs for a short time, the way every web server does.
1. Who we are
Random Toolkit ("we", "us") operates the website at randomtoolkit.com and the Random Toolkit mobile app. You can reach us at [email protected].
2. What we do not collect
We want to be specific rather than reassuring, because the specifics are unusually simple here. We do not collect:
- anything you type into a generator — names, lists, questions, custom characters;
- any result any generator produced for you;
- any password or passphrase the password generator produced;
- your name, email address, phone number or any other identifier, unless you email us;
- advertising identifiers, or anything about you from other sites.
This is not a policy decision we could quietly reverse. The generators have no way to send us what you type: there is no API endpoint, no form submission and no database on the other end. The page you are reading is a flat file, and everything it does, it does on your device.
3. What your browser stores, on your device
So that a generator is still set up the way you left it, some pages save a small amount of data in your browser's localStorage. This is storage that belongs to your browser, on your machine. It is never transmitted anywhere, and we cannot read it.
| What | Why |
|---|---|
| Your entries | So the wheel, the picker, the list randomizer and the team generator still hold your list tomorrow. |
| Saved lists | The lists you name and keep, so they are ready in any generator that takes one. |
| Recent results | The last dozen results of a generator, so you can check what it just said — and the last sixty across all of them, which is what the History page shows. |
| A few settings | The coin's running tally and the sides you named it; the question you last asked. |
Two things are deliberately never stored: anything the password generator produces, and anything from a page you have not used. A password written to browser storage would outlive the tab it was made in, so it is not written at all.
Erase it yourself, right now. This removes every list, result and setting this site has stored in this browser. It cannot be undone, and it does not need our permission or involvement.
You can also clear it through your browser's own "site data" or "cookies and site data" settings, which removes exactly the same thing.
4. Cookies
This site sets one cookie, and only if you have said it may. It belongs to Google Analytics and holds a randomly generated number, so that two page views can be counted as one visit. It carries no name, no email address and nothing you have typed. The adverts are requested with advertising cookies switched off — see section 6 — so no cookie here is used to build an advertising profile of you.
You are asked before any of it happens, and until you answer Google Analytics is not fetched at all — not the script, not a cookieless ping, nothing. Say no and it stays that way. You can change your answer at any time, right here, and blocking cookies for this domain or browsing privately stops it too. Every generator works exactly the same either way: nothing on this site is behind a cookie wall.
5. Server logs
Like every web server, ours records a line for each request it serves: the time, the address requested, the response status, how long it took, the browser's user-agent string, and the IP address the request came from. We use these to keep the site up and to notice when a page is broken.
They are not linked to any identity, are not used to build a profile of you, and are not shared with advertisers. They are kept for a short operational period and then discarded. Note that these logs record which page was requested and never what you typed into it, because what you type never reaches the server in the first place.
6. Third parties
Two scripts on this site come from somewhere else, both from Google: Google Analytics, and Google AdSense, which shows the adverts. Everything else — the typefaces, the images, the code every generator runs — is served from our own domain.
The adverts are chosen and served by Google AdSense. To show one, Google receives what any browser sends when it fetches something: your IP address, the browser's user-agent string and the address of the page the advert appears on. Google processes this under its own privacy policy. This site tells Google, through Consent Mode, that advertising cookies are not allowed, so the adverts are not personalised from a profile of you. In the EU and the UK, Google may ask for your consent itself before it shows an advert. The adverts sit beside the generators, never inside them, and they cannot see what you type, because that never leaves your device.
What it receives is the ordinary page-level picture: which page was opened and when, roughly which country the request came from, the language and screen size of the browser, and the page that linked here. Google processes this for us, and may do so outside your own country. It never receives what you type into a generator, because that never leaves your device.
Our hosting provider processes traffic on our behalf as any host does, and we may run a server-side error-reporting service that receives crash details from our own application code — technical diagnostics, not page content. None of them receives anything you type into a generator.
7. The mobile app
The app can also report which screens are opened and which generators are used, through Firebase Analytics, together with what Firebase records for itself about the install: a randomly generated app instance identifier, the device model, the operating system version and the country the request came from. It is off until you say otherwise — the app asks once, on the way in, with the switch already off, and skipping the question leaves it off. It never sends anything you type into a generator, any result it produced, any saved list or any password, and you can turn it off again at any time in the app's own settings, under Behaviour.
The Random Toolkit app runs every draw on your own device: what you type into a generator, and what it gives back, never leave the phone. Your saved lists and history live in the app's own storage, are cleared from its settings at any time, and are gone completely when you uninstall it. There is no account. On Android it asks for no permissions beyond internet access; on iOS it asks for your photo library only at the moment you choose a picture for the wheel or the coin.
8. Children
The site is suitable for all ages and is widely used in classrooms. We do not knowingly collect personal information from anybody, of any age, because we do not collect personal information at all.
9. Your rights
Rights of access, correction, deletion and portability all attach to personal data a service holds about you. We hold none, so in practice there is nothing to request — and the one store of your data that does exist, in your own browser, is under your control and erasable from section 3 above.
If you have emailed us, we hold that email and our reply. Write to [email protected] and we will delete the correspondence on request.
10. Changes
If this policy changes, the date at the top of the page changes with it. Substantive changes will be noted on the page rather than slipped in.
11. Contact
Questions about any of the above: [email protected].