What a regulator can and cannot do for you
Gambling regulators have real powers over the businesses they licence and almost none over anything else. A licence held in one country does not, by itself, protect a player in another.
A gambling regulator is a public authority with statutory powers over a defined set of licensed businesses within a defined territory. Both limits are strict. The most common disappointment in player complaints comes from expecting a regulator to act as a debt-collection service, a court, or an authority over businesses it has never licensed.
What a regulator generally can do
Licence and set conditions. It decides who may operate, and on what terms. Conditions frequently include requirements about complaint handling, fund protection and advertising.
Supervise and investigate. It can require information from licensees, audit their compliance, and investigate suspected breaches — using powers a private individual does not have.
Enforce. Depending on the regime, sanctions may include financial penalties, licence conditions, suspension and revocation. These are documented in Licence status changes and what they signal.
Publish. Enforcement decisions, warning lists of unauthorised sites, and register entries are published, which is what makes independent scrutiny possible at all.
Route complaints. Many regulators require licensees to participate in an alternative dispute resolution scheme, and will direct a complainant to it.
What a regulator generally cannot do
Order an operator to pay you. In most regimes the regulator supervises conduct; it does not adjudicate individual contractual disputes or award compensation. A complaint may inform its supervision and may even trigger enforcement — but the money is recovered, if at all, through the operator, an ADR scheme or a court.
Act against a business it does not licence. Its jurisdiction runs to its licensees. An unlicensed site is a matter for enforcement against unauthorised activity — publication on a warning list, blocking measures, referral to prosecutors — none of which returns your balance.
Reach across borders. A regulator cannot generally compel a company established and licensed elsewhere. Cooperation between authorities exists but is a matter of arrangement, not entitlement.
Reverse a payment. Payments sit with financial institutions supervised by other authorities entirely. See Payment intermediaries: the layer between you and the operator.
Act quickly on an individual matter. Supervisory processes run to timescales set by statutory procedure, not by a player's cash-flow.
The jurisdictional trap
This is the point that costs players the most.
A licence authorises an operator to conduct gambling in the jurisdiction that issued it, subject to that jurisdiction's law. Whether the operator may lawfully accept customers from where you live is a separate question governed by your own country's law, and the answer differs across three broad situations:
- You are in a licensed market and used a locally licensed operator. The local regulator supervises the operator and local consumer protections apply. This is the strongest position.
- You are in a licensed market and used an operator licensed only elsewhere. Your local regulator may treat the operator as unauthorised — a status that permits enforcement against it, but rarely produces a remedy for you. The foreign regulator supervises the operator but generally owes no duty to a player its own framework did not contemplate.
- You are in a prohibited or unregulated market. There may be no authority with both the power and the mandate to assist, and in prohibited markets participation may itself carry legal consequences for the player.
A licence is a permission granted by one state to conduct business under its supervision. It is not a warranty extended to the world.
The regime classification for each jurisdiction GambleLABS records, together with the authorities identified in it, is published under jurisdictions.
Choosing the right authority
More than one authority may be relevant, and they are not interchangeable:
- The gambling regulator for licensing, conduct and enforcement questions.
- The financial regulator where the issue lies with a payment institution rather than the gambling business.
- The data protection authority for misuse of identity documents or personal data — a live issue in verification disputes.
- The consumer protection body for unfair contract terms, in jurisdictions where gambling contracts fall within its remit.
- The ADR scheme named in the operator's terms, for adjudication of the contractual dispute itself.
Sending a complaint to the wrong authority does not usually produce a referral. It produces a closure notice, and the time is lost.
Before you contact anyone
Establish the operator's legal identity and licence position first — see How to read a licence register entry — and assemble the record described in The evidence you need before you complain. Regulators act on documented allegations. An undocumented one is filed.
This article describes general structures. Powers, remedies and time limits differ by jurisdiction, and nothing here is legal advice.
Share
The permanent address of this record. Copy it to share the record itself rather than a link that expires with your session.
https://gamblelabs.network/research/what-a-regulator-can-and-cannot-do
Provenance
Sources
Everything this record rests on, numbered in the order it is cited.
Source list
No citations attached
That absence is itself worth noting. A published claim with nothing behind it cannot be checked by a reader, so this panel states the gap rather than hiding it. Sources are attached in the editorial console and appear here the moment they are.
Provenance
Editorial record
How this record was made, reviewed and signed off — and exactly what is attached to it.
- Record type
- Explainer
- Evidence standard
- Not applicable
- Author
- GambleLABS Editorial
- Editor sign-off
- Not recorded
- Published
- Last reviewed
Explanatory or definitional material that makes no factual claim about a named party.
Human review
A human editorial review is recorded for this record. No source relationship is attached, so this page does not claim that it was checked against sources.
Evidence Engine assistance
No Evidence Engine assistance was used in preparing this record. It was researched, written and checked by people.
How the engine works- Sources
- 0
- Timeline events
- 0
- Connected entities
- 0
- Jurisdictions
- 0
- Subject responses
- No response is currently on record.
- Corrections
- None on record
Where a set is empty its section is not shown above, and nothing is attached that is not listed here. “None on record” means nothing has been recorded against this record — it is not a statement about whether anything was sought.
Machine analysis
Evidence Engine findings
Approved findings the Evidence Engine produced against this record, each with the sources it cites, its evidence status, its score, any contradiction the run raised, and the editor who approved it.
No Evidence Engine-supported finding is published here
The Evidence Engine has produced no approved analysis of this record. A finding appears on this record only once a run has completed against registered sources, every claim in it cites one of those sources, and a named editor has approved the run in full. Nothing is written here to fill the space.
Connected work
Related records
Ranked by what they genuinely share with this piece rather than by date.

Discussion
Comments
Public and attributed. Comments are moderated after publication, not before, and nothing is deleted — a withdrawn or removed comment leaves a marker so the replies beneath it still make sense.
No comments yet
Nothing has been posted against this publication. Comments appear here in the order they are written, each under the name of the member who wrote it.
Add a comment
Comments are attributed, so posting one needs an account. Reading the thread does not.