Reference

Privacy Policy for your 6lack account

Your 6lack account connects live tables, slots, sportsbook markets and local rails such as UPI, Paytm, PhonePe and Google Pay; this Privacy Policy explains what data sits behind…

Account dataCookie choicesUPI recordsIndia privacy contact
Explore the Lobby Read FAQ
6lack Privacy Policy for your 6lack account
PRIVACY CONTACT

Three privacy contact paths

Privacy requests need a clear path, not a generic queue. Use the channel that matches your request so we can check your account, confirm identity and respond without exposing data to the…

Privacy email Write to our privacy desk with your registered email, account name and the request you want handled. Do not include full card details, passwords or screenshots that show private codes.
Account support Use in-account support when you can still access your profile. We can connect your request to recent logins, payment records and support chats without asking you to repeat sensitive details.
Security report Contact us quickly if you see an unknown login, changed phone number or payment activity you did not start. We can pause risky actions while privacy checks are completed.
DATA HANDLING

Six ways we handle data

We treat privacy as part of daily account operations, not a separate page that sits aside from the lobby.

Account records

We collect the details needed to create and maintain your account, such as name, contact details, login data and verification…

Payment traces

UPI, Paytm, PhonePe and Google Pay activity may create transaction references, timestamps and status logs.

Cookie controls

Cookies help keep you signed in, remember display choices and measure how privacy tools work.

Security logs

We record device type, IP address, session timing and risk signals when your account is accessed.

Retention periods

We keep data only for account operations, legal duties, dispute handling and security needs.

Request handling

You can ask to access, correct, restrict or delete eligible account data.

Privacy questions before you join

These answers explain common privacy points before you open an account or continue using the lobby. They focus on account data, payment records, cookies, device logs, access requests and how we respond when you contact us. If a privacy issue is linked to local eligibility, access depends on local law and is available where local law permits.

We collect the details needed to create your account, keep it secure and meet legal duties. This may include your name, contact details, login records, verification status, device data and support messages.

Payment records help us match wallet actions to your account, trace failed transfers and verify withdrawal requests. We keep transaction references, timing and status details only for payment handling, dispute checks and legal needs.

Yes. Send a request through privacy email or in-account support. We will verify your identity first, then share eligible account data in a format we can provide without exposing another person’s data.

Cookies support sign-in sessions, language choices and basic site measurement. You can adjust browser settings, but blocking every cookie may affect account access, security checks or parts of the lobby that require a session.

Access is limited to teams that need data for account support, payment checks, security work, legal duties or privacy requests. We use access controls and internal logging to reduce unnecessary viewing.

Contact support from your account or write to the privacy desk with the detail that needs correction. We may ask for proof before updating records that affect access, payments or identity checks.

You can request deletion of eligible data. Some records may need to stay for legal, security, payment dispute or account integrity reasons, and we will explain what remains and why.

Related Pages

6lack App FAQ About Us Ice Joker