localhost6767

The rules

Last updated 11 October 2026. These rules are enforced by the software, not by trust. Where a rule is enforced in the database or by cryptography, it says so.

What this is

A free community wheel for referral codes. Contributors add a referral code or link for an app. Visitors spin once per app and get one contributor's code at random. There is no prize from us, no money, no ads, and nothing to buy. Any bonus comes from the app's own referral program, on the app's own terms.

Fairness rules

  1. One active referral per app per account. Enforced by a database constraint. You can edit or delete yours and add a new one, but never hold two at once for the same app.
  2. One spin per app per person. You do not need an account to spin: without one, it is one spin per app per browser. When you create a passkey or sign in from that browser, its spins move to your account and the browser stays tied to the account, so creating an account or signing out never grants a second spin. Enforced by a database primary key. An empty slice uses the spin too. Your result is saved and you can reopen it.
  3. Equal odds for every contributor. With up to twelve codes, every code gets exactly one slice of the same size; the remaining slices are empty while the wheel fills. Above twelve, the twelve slices become anonymous, no slice is empty, and the pick is a uniform position in the full list of active codes. Nobody can buy, boost, or pin a slice.
  4. Provably fair picks. Before you spin, the server commits to a secret seed by showing you its SHA-256 hash. Your browser adds its own random seed. The slice is sha256(serverSeed + ":" + clientSeed), first eight hex characters, modulo the number of slices. After the spin the server reveals its seed. Your browser checks that the revealed seed matches the commitment and that the slice matches the formula, and shows the result under "Verify this spin" in the result window. Neither the operator nor you can steer the outcome after the commitment.
  5. Duplicate codes are rejected. The same code or link cannot be active twice for one app.
  6. Reports come only from real spins. Only the account whose spin landed on a code can mark it "worked" or "didn't work", one current report per account, and contributors cannot report on their own code. Editing a code clears its reports.
  7. Misleading or offensive entries get hidden by the community. The same spinners can report an entry as misleading or offensive. Three reports from different accounts hide it from the wheel automatically; its owner can only delete it. Benefit notes are also filtered on submission: no links, email addresses, phone numbers, chat handles, money promises, or offensive words.
  8. Dead codes leave on their own. A contributor can give a code an expiry date; when it passes, the code drops off the wheel and the owner can set a new date. A code that at least three spinners mark "didn't work", with those reports outnumbering "worked" two to one, retires from the wheel until its owner updates it; updating clears the old reports.
  9. Adding a code needs a passkey account. No email, no password. A passkey is a real device with Face ID, Touch ID, fingerprint, or a PIN, which makes throwaway accounts expensive. The server stores only a public key. A private window gives a browser another guest spin; we accept that, because the scarce thing is a slot on the wheel, not a spin.
  10. Delete means delete. Deleting a referral removes it and its reports immediately. Deleting your account removes your passkeys, referrals, spins, and reports.

Is the operator cheating?

The operator is one person with one passkey account, bound by the same limits above: one code per app, one spin per app. The operator cannot steer which slice you land on because of the commitment scheme in rule 4; you can verify every spin yourself. The operator can remove codes that look fraudulent, break an app's program terms, or are reported broken repeatedly. The operator does not reorder, boost, or hide codes for any other reason.

How do I know a code is from a real person?

Every code is tied to a passkey account on a real device, and each account can hold one code per app. Contributors are shown only by their account number (for example "Member 76201E"); nobody chooses a name, so nobody can pose as someone else. The result window shows that number, when the code was added, and how many spinners reported it worked or did not. We do not verify identities and we do not collect names or emails; the signal you get is device-backed accounts plus community reports, not a background check. If a code is a scam, report it to the email on the About page and it will be removed.

What gets removed

See the Terms for what you agree to and the Privacy policy for what is stored.