State access control

Three decisions, not one

Whether somebody in a given state may register, may play, and may redeem are three separate settings. They are not stages of one funnel and they do not have to agree with each other.

Three settings, not three steps. Any combination is valid and several are common: open to play and closed to redemption while a position is being reviewed, open to registration ahead of a launch date, closed to everything the day a state moves. A platform that treats them as one switch cannot express what an operator actually needs.

Who determines where a player is

You determine where a player is. We act on what you tell us. That boundary is worth stating precisely, because the word geolocation implies a technology and we do not supply one. There is no IP lookup, no device fingerprint, no GPS check and no specialist vendor on our side of the line. You decide how to establish a player's state — and the methods vary a great deal in cost and defensibility — and the state arrives with the request.

So a wrong determination produces a rule correctly applied to the wrong jurisdiction. That is worth sitting with: the settings will do exactly what you configured, the record will show what was decided and when, and none of it will help if the state we were given was not the state the player was in. The exposure is yours, and the quality of your location method is the part of this that nobody else can improve for you.

What happens when a state moves

Configuration, not code, and the decision is yours. A change to a state's position is a setting, not a release. Nothing has to be deployed, and the change takes effect without your engineering team scheduling anything. What is not automatic is the decision: we do not close a state for you, because whether a development applies to your structure is a question for your counsel and not for a supplier's reading of a press release.

Whatever you decide, write down why. A setting that changed on a date you can evidence is worth considerably more than one that is simply correct today, and the difference only ever matters at the moment somebody asks. What has changed, and when, is tracked on the state reference.

Registration, play and redemption are separate

Worth saying twice, because it is the part most often built wrongly. A platform that collapses the three into one switch cannot express a state that is closed to redemption and open to play — which is not a hypothetical arrangement but a common one, and the shape a cautious position usually takes while counsel reads something.

The setting that matters most is the narrowest one. Redemption is where value leaves, it is the gate several states restrict on its own, and it is the one where being wrong costs money rather than a signup.

Who enforces this on each route

Which is the same shape as redemption and payments on this site: the policy values live with us on both routes, and what differs is what acts on them. The full capability table sets out the rest.

Not legal advice

What a state's position is, and whether it applies to your structure, is a question for your counsel. This page describes the mechanism, not the conclusion — a setting is only as good as the decision behind it.