Field guide · Privacy
What happens to your list when you use Random 42
Each Random 42 tool appears on the same page as its instructions. Browser-side code reads the names, list files, and settings you provide, then produces the result for the active task. Page delivery and Google Analytics 4 handle separate technical and page-visit data.
In one minute
The short version
Names, choices, rules, imported file contents, and results are processed in browser memory. They are not placed in the page URL or sent as custom analytics events. Refreshing, leaving, or closing the page clears the current task, but the site still processes ordinary delivery and page-visit data.
- The instructions and interactive controls share one Random 42 page; there is no separate app or embedded tool frame.
- Names, rules, imported file contents, and results are processed in browser memory for the current task.
- Google Analytics 4 measures page visits, not the contents of your list or result as custom events.
- Refreshing, navigating away, or closing the page clears the active task state.
On this page
Guide section
1. The instructions and tool share one page
A Random 42 tool page includes the title, guidance, input controls, random operation, result, and available copy, print, or download actions. You do not move to another domain or load an embedded app to complete the task.
When you generate a result, browser-side code works with the current page state. The random operation does not require uploading the active list or imported file to a Random 42 account or workspace.
| Area | What it handles | What it means for you |
|---|---|---|
| Tool workspace | Pasted entries, imported file contents, settings, and results | Browser code uses them for the current task |
| Page analytics | Page visits and related device or request information | Google Analytics does not receive list or result contents as custom events |
| Hosting and CDN | Ordinary request and security information needed to serve the page | This technical data is separate from the entries used by the tool |
Guide section
2. What happens to a list during a session
A name pasted into a tool becomes an active entry in browser memory. Depending on the tool, the page may trim whitespace, remove blank rows, identify duplicate display names, read an imported file, or keep current-session history while it builds a result.
Refreshing, navigating away, or closing the page clears that task state. Random 42 does not create an account, cloud roster, permanent result page, or cross-device record from the entries you use. Copying, printing, or downloading a result creates an output that you control outside the active task.
Input
Names, options, imported files, and rules enter the active page state.
Compute
The tool prepares inputs and calculates results during the active session.
Result
Groups, choices, orders, or draws remain in memory until copied or downloaded.
Clear
Refresh, leave, or close the page to clear the current task state.
Guide section
3. What page delivery and analytics still process
A browser tool still has to be delivered over the internet. The hosting and CDN layer can process ordinary request information such as IP address, browser headers, requested URL, and security signals. Random 42 also loads Google Analytics 4 to measure page visits; it may process page, device, and request information for that purpose.
The current analytics setup does not send names, imported list contents, tool settings, generated results, or free-text errors as custom events. A recorded page visit shows that a page loaded; it does not establish which entries were used or whether a result was generated.
Guide section
4. Minimize what you paste even when the tool does not save it
Keeping an active list in browser memory reduces exposure, but it does not make every input appropriate. Use display names or other minimal identifiers. Avoid addresses, email addresses, phone numbers, health details, student records, compensation, performance notes, and other sensitive information that the task does not need.
On a shared computer, leave or refresh the page after the task and close any copied or downloaded result you no longer need. Present mode can expose a result to people in the room, so review it before sharing the screen.
Guide section
5. Check the current disclosure before sharing a list
Before using a real roster, confirm that the page asks only for the information the task needs. Review the generated result before you present, copy, print, or download it.
The Privacy and Cookie pages describe the current website analytics, cookies, technical request data, and browser controls. Use those notices when you need the full policy rather than treating this guide as a substitute.
Try the workflow
Related live tools
Use a simple name workflow without a cloud roster.
Open tool 02 · Ready to useClassroom Group GeneratorCreate student groups without saving the roster.
Open tool 03 · Ready to useWork Team GeneratorPrepare work fields in the tool and export only the needed result.
Open toolKeep reading