Do Not Assume BetStop Reaches Every Casino Account

Map every account and service

List each operator, hostname, username, registered email and phone. Mark whether the service is an Australian licensed wagering provider, an offshore casino, an app-only account or an unknown mirror. Check the current BetStop scope rather than assuming that similar gambling products share the same exclusion system.

For any account not clearly covered, submit a direct permanent closure or self-exclusion request through the signed-in support channel. State the requested scope: login disabled, deposits rejected, promotional contact stopped and duplicate-account creation prevented where the operator offers that control.

• Account ID
• Operator and domain
• BetStop coverage result
• Direct request ID

Preserve closure evidence

Save the request timestamp, transcript, confirmation email and the date access should end. Test only the non-gambling control needed to confirm closure, such as whether the account reports disabled status; do not deposit to test an exclusion. Record marketing messages received after the effective time and unsubscribe or complaint references.

If the operator asks for identity evidence, use its authenticated upload path and provide only what is necessary to locate and close the account. A closure request should not require payment, remote access or disclosure of one-time codes.

Add device and payment barriers

Register-level and operator-level exclusion can be reinforced with bank gambling blocks, app restrictions, content filters and support from a trusted person or counselling service. These layers address accounts beyond one register and reduce the chance that a new hostname bypasses a single control.

Questions players ask