Reference

Legal terms for your account

This page explains how we handle access, data use, account records and changes to these terms before you open an account.

Local law firstData handlingCookies and recordsSupport contact

Explore Lobby Read FAQ

How access and policy apply

casinoscore Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Our legal position is simple: the terms on this page apply to your account, your device data and the way we store support records. If a rule changes by state, territory or another local rule set, the stricter local requirement applies for that place. We do

1
not treat this page as a substitute for local legal advice, and we do not add promises that cannot be checked. Where you ask for access, we look at the law that applies to your location at the time. If your account details, device data or
2
transaction records need to be kept for a lawful reason, we keep them for that reason and remove them when that reason ends, unless another rule says otherwise. For context, the payment rails you may see in India are UPI, Paytm, PhonePe and Google Pay.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

Where to send legal requests

Use the route that matches your request. For policy questions, data copies, deletion requests or correction calls, send a clear message from your registered account path so we can match it to…

In-account form Use the form in your account for policy questions, data requests and record corrections. It helps us match your details quickly and keep the conversation tied to the right account.

Email route If you prefer email, send the same request from your registered address and mention the subject clearly. We use that route for access questions, written clarifications and follow-up on completed actions.

Help desk For time-sensitive legal points, the help desk can point you to the right team and log the issue for you. Keep your message short, factual and easy to verify.

DATA CARE

How we handle records and access

We keep policy handling tied to the account itself. That means we store the details needed to run access checks, answer questions, and keep a record of changes you ask for.

Data use

We use account and device data only for access checks, support, risk control and record keeping. We do not ask for extra details unless the request needs them or a rule says we must keep them.

Cookies

Cookies help us remember your session, language and display settings, and they help us spot repeated login attempts. You can clear them in your browser, but some page functions may then ask you to sign in again.

Security

Protect your login details with a password you do not reuse elsewhere. If you share a device, sign out after use. We may ask for verification before changing policy-sensitive account settings or sending stored records.

Retention

We keep records only for the period needed to answer queries, meet legal duties or settle account history. When that period ends, we remove or anonymise the data unless another rule requires us to keep it longer.

Changes

If you spot a mistake in your profile or contact details, ask us to correct it in writing. We will check the request against the account record and confirm the change once it is validated.

Contact

For access, correction or deletion questions, use the same route shown in your account and state what you want changed. Clear requests help us respond faster and avoid back-and-forth.

Questions about legal access

These questions cover the practical side of account law, data handling and contact paths. If a point depends on where you are, we apply the law that governs your account or request at that time. Keep your request specific, use your registered details, and include any reference number from earlier messages so we can trace it without delay.

Yes. If local law changes, we apply the rule that governs your account or request at that time. If the change affects access or record handling, we may pause the action until the requirement is clear and documented.

We keep the details needed to run account access, answer support messages, verify changes and meet legal duties. That can include contact data, login records and message history tied to your request.

Yes. Send the correction from your registered route and state the exact field that needs updating. If the change affects identity or payment records, we may ask for proof before we edit it.

Cookies help us remember your session, language and basic site settings. If you clear them, some pages may sign you out, and you may need to confirm your session again.

You can ask us to remove data that is no longer needed, but we may keep records that a law, tax rule or fraud check requires us to retain. We will explain what stays and why.

Use the contact form in your account or the email route shown there. Include your registered details, a short subject line and any reference number so we can route it correctly.

We keep records only as long as needed for access checks, dispute handling, legal duties or internal audits. After that period, we delete or anonymise them unless another rule requires retention.

Legal terms for your account

Where to send legal requests

How we handle records and access

Data use

Cookies

Security

Retention

Changes

Contact

Questions about legal access

01 Does local law affect my account?

02 What data do you keep?

03 Can I correct my account details?

04 How do cookies affect access?

05 Can I ask for deletion?

06 How should I contact you?

07 How long do you keep records?

Related Pages