# A careful guide to account limits and self-exclusion

Account limits and self-exclusion tools can help readers make deliberate choices about online gaming access. Before signing in or changing an account setting, it is useful to understand what each option is intended to do, which settings are available, and how changes are confirmed.

# What to check before signing in

Readers can begin by checking that they are using the correct website and a secure connection. They should avoid links received through unexpected messages and instead use a verified access route. Check the spelling of the site address, look for secure browser indicators, and avoid entering passwords or recovery codes on pages that appear unusual.

A login page should also be treated as an access point, not as proof that any account setting has been applied. Readers can review the available account, safer-play, and support sections after signing in, while keeping passwords, one-time codes, and recovery details private.

# Comparing limits with self-exclusion

Limits and self-exclusion are different types of control. A limit may help a reader manage a selected aspect of account activity, while self-exclusion is a stronger request to restrict access. The exact choices, scope, and effect should be checked in the current official information before making a selection.

Consider these questions:

• Which account activity can be controlled?
• Is the setting temporary, ongoing, or subject to a stated review process?
• Does the choice apply to one account or to a wider service?
• What confirmation should appear after the request is submitted?
• Which verified support channel should be used if the setting is unclear?

Do not assume that closing a browser tab, deleting an app, or signing out creates self-exclusion. Readers should look for a clear confirmation and keep a private record of the request details without storing sensitive login information in an unsafe place.

# If help or verification is needed

If a setting cannot be found or its effect is uncertain, consult the current official requirements and use a verified submission channel. Never send card images, CVV or CVC details, PINs, one-time passwords, passwords, or recovery codes in a support request, KYC file, screenshot, email, or chat. Normal entry into a verified payment form is separate from sending payment credentials through an unverified channel.

For a focused checklist, readers can review the account limits and self-exclusion guide and then confirm each setting through the current official account interface.