No — the names you paste into a random name picker wheel are not uploaded anywhere, sent to a server, logged, or saved outside your browser tab. The Random Name Picker Wheel runs as client-side JavaScript, meaning every step — reading your typed list, picking a winner, displaying the result — happens locally on your device using the browser engine. Your browser's cryptographic random generator, accessed through crypto.getRandomValues, supplies the entropy for the spin, and the chosen name is highlighted directly below the wheel. There is no form submission, no API call carrying your roster, no analytics payload with student or employee names attached, and no database write. The page does not require an account, does not ask for an email, and does not set a tracking cookie tied to your list. When you close the tab, the JavaScript variables holding your names are released by the browser's memory manager and the input field is gone. Nothing persists on a server because nothing was ever sent to one. That is the privacy contract: type, spin, see the winner, close — and your list was never anywhere except on your screen.
What "Uploaded" Actually Means for a Random Name Picker
When people ask whether the names they enter are uploaded, they are usually worried about three concrete things: that the list will be sent to a remote server, that it will be stored in a database the operator can read later, or that it will be quietly packaged into analytics that get aggregated or sold. All three are legitimate concerns, and they describe the default behavior of most web tools. A typical online form takes your input, submits it to a backend, writes a row to a database, returns a response, and may also fire tracking events to a third-party analytics provider along the way. The names pass through several systems owned by other people before you see a result, and that is the realistic baseline to measure against.
A random name picker wheel is a different shape of tool. The job it does — drawing one entry from a list — is small enough to fit entirely in the page. There is no reason for the names to round-trip to a server, and a well-built picker does not make that round trip. That distinction is the whole answer to the privacy question, but it is worth naming what is actually happening under the hood so you can recognize the difference yourself.
How the Random Name Picker Wheel Keeps Your List Local
The Random Name Picker Wheel is built so the only code that touches your list runs in your own browser tab. When you type or paste names into the box, the browser stores those values in the page's Document Object Model — a tree of in-memory objects that exists only while the tab is open. The wheel animation, the spin logic, and the winner highlight all read from that local tree. The draw itself does not use the usual Math.random function that many scripts rely on. Instead it calls crypto.getRandomValues, the same Web Crypto API that secure login flows use to generate tokens, and applies a technique called rejection sampling to remove modulo bias — the subtle skew that happens when a range does not divide evenly into the size of your list. In plain terms, with N names on the wheel, every name ends up with an exactly equal 1-in-N chance. The distribution has been checked across tens of thousands of simulated spins to confirm it stays statistically flat, with no hidden weighting and no house edge.
Because the randomness comes from your own device and the result is rendered locally, there is no round trip to draw. Nothing on the page calls fetch or XMLHttpRequest to send your roster over the public internet. There is no signup form, no email capture, and no watermark tying the result back to a user account you never created. The browser's Network tab, which records every request a page makes, stays empty for the spin itself. That is the most direct evidence you have that the names never leave the tab.
How to Spin a Winner Without Sending Names Anywhere
- Open the Random Name Picker Wheel in your browser. The page loads once and then sits there; you do not need to install anything or create an account.
- Type or paste your names into the input box, one name per line. Blank lines are ignored automatically, so stray empty rows from a spreadsheet paste will not skew the draw. Duplicate names are kept if you want to give someone extra chances.
- Click the "Spin the wheel" button. The wheel animates and decelerates until it stops on a single random winner, which appears highlighted directly below the wheel.
- If you want to draw several winners without repeats — for example a running order or a ranked prize list — tick the "Remove winner after each pick" checkbox before the next spin. Each winner drops off the wheel automatically, so subsequent spins can never land on the same name twice.
- Keep spinning as long as you need. When you are done, close the tab. The browser releases the memory holding your list and there is nothing left to clear, log out of, or delete.
Privacy Signals to Look for in Any Random Picker
If you are evaluating a different name picker and want to know whether it uploads your list, the practical checklist is short. The Random Name Picker Wheel is built to satisfy every item on it.
| Privacy signal | What this picker does |
|---|---|
| Where the spin runs | Inside the browser tab using client-side JavaScript |
| Network requests during a spin | None — the page does not call any server to pick a winner |
| Account or sign-up | Not required, not requested, not implied |
| Storage of your list after the tab closes | None — closing the tab releases the in-memory list |
| Random source | Browser's Web Crypto API (crypto.getRandomValues) |
| Bias handling | Rejection sampling applied to remove modulo bias |
| Watermark tying output to you | None |
| Limit on number of names or spins | None — works for a handful of names or several hundred |
A tool that fails any one of those checks is sending or keeping more than it needs to. A picker that asks you to log in before showing the wheel, that reloads after each spin, that places a tracked sharing link on the result, or that warns you that "your wheels are saved to the cloud" is doing some form of upload or remote storage even if it never names a server out loud. The opposite pattern — instant load, no login, no reload, empty network log — is what a genuinely client-side picker looks like.
When the Privacy Guarantee Matters Most
The privacy of a name picker is not an abstract preference. For certain lists, uploading them to a third-party server is a real problem, and the consequence ranges from awkward to actionable.
- Student rosters. Teachers running cold-call draws, presentation order, or "who is the line leader today" are working with minors. Schools have formal policies about where student names can be transmitted, and pasting a class list into a tool that quietly sends it to a backend creates a paper trail that did not exist before.
- Employee names. HR-led draws for holiday gifts, parking spots, or "lunch on the company" decisions involve internal personnel data. Treating a vendor's random draw tool as a system of record — even briefly — raises questions that legal teams do not enjoy being asked.
- Giveaway and raffle entrants. Contest lists often contain real people who did not consent to having their names processed by an unrelated third party. A tool that runs locally means the names never touch a system outside the organizer's own machine.
- Sensitive team picks. Choosing who presents first, who answers a hard client question, or who covers an unpopular shift is exactly the moment a list should not leak. Keeping it local keeps the awkwardness off the network.
For all of these situations, the operational rule is the same: if the tool's privacy posture is unclear, do not paste real names into it. Use a picker whose contract is "everything happens on your device" and you do not have to investigate further.
Fairness You Can Verify, Not Just Trust
Privacy is half of the trust story. The other half is whether the winner is genuinely random, because a tool that quietly favors the first name on your list is doing something worse than uploading — it is producing a rigged result in private. The Random Name Picker Wheel addresses this directly. The draw uses your browser's cryptographic random number generator, which is the same class of source used to generate session tokens and encryption keys. To remove the small but real skew that appears when a list size does not divide evenly into the output range, the picker applies rejection sampling: values that would cause a bias are discarded and a new draw is taken. With that step, every name on the wheel gets exactly the same 1-in-N probability of winning, regardless of its position or its neighbours. The distribution has been simulated across tens of thousands of spins to confirm it stays flat, so the fairness claim is not just asserted — it has been measured.
Put together, the two properties work as a pair. A draw that is private but biased is still not fair, and a draw that is fair but uploads your class list is still not safe. The wheel combines both: client-side execution, cryptographic randomness, bias correction, and no network round trip. You get a winner you can show on a projector, post in a chat, or read out loud, without ever having shared the underlying list with anyone but the people already in the room.