Entrants and eligibility
Choosing duplicate-entry controls for a giveaway
Understand browser, account, and IP checks, and decide how to review entries moved to jail.
Start with the entry policy
Decide whether the giveaway allows one entry per account, browser, or public IP address. Those rules are not equivalent. People in one household or workplace may share an IP, while one person may use several browsers or networks. Publish the rule in terms entrants can understand.
A browser identifier usually stays within one browser profile. It should not be treated as proof that Chrome and Brave on the same device belong to the same person. Account checks work only for signed-in entrants, and IP checks depend on the public address observed when an entry is submitted.
Review jailed entries
When a duplicate rule is triggered, the new entry can be moved to jail for review. In the Jail section, creators can also choose to move matching original active entries to jail. This extra action is off by default, so the original stays active unless the creator enables it.
Review the reason and the entry details before releasing or removing anyone. An IP match alone can be a shared network, not deliberate abuse.
Keep a record of decisions
Set the controls before opening the entry link and avoid changing policy without telling entrants. If you release a jailed entry or remove one, record why and use the same standard for similar cases.
No anonymous device check can guarantee one human per entry across browsers and networks. Clear rules, a review process, and a saved list are more useful than treating one signal as certainty.
Put this into practice
Start with a sample wheel, then replace the entries with your own list.
Review giveaway controls