Reference

Your data choices stay clear

Blackjack, Viking Runecraft, Football Strike and wallet actions create account records, and this Privacy Policy explains how l70 collects, uses and protects those records.

Account dataCookie controlsUPI recordsPaytm and PhonePeRequest support
l70 Your data choices stay clear
CONTACT ROUTES

Reach us about privacy quickly

Privacy questions should reach the team that can act on account records, not a general mailbox.

Account privacy email Email our privacy desk for access, correction, deletion or data-use questions. Include your account email and a short description of the request so we can verify you before making any account change.
Live chat escalation Use chat when a privacy issue is linked to a current login, wallet action or payment check. The agent can mark the case for the privacy desk after confirming basic account ownership.
Payment record query For UPI, Paytm, PhonePe or Google Pay privacy questions, send the transaction time and reference shown in your wallet. Mask sensitive details, and we will match the record internally.
DATA CARE

How your privacy is managed

We handle privacy work as part of daily account operations: sign-in checks, wallet checks, cookie settings, support records and payment reconciliation are all kept within controlled systems.

Account details

We collect details you provide during account creation, profile edits and support contact. These records help us identify you, maintain access, respond to disputes and apply region rules where local law permits.

Wallet records

Payment data linked to UPI, Paytm, PhonePe and Google Pay is used to match deposits, withdrawals, refunds and failed attempts. We retain references needed for reconciliation and complaint handling.

Cookies and device data

Cookies help keep you signed in, remember settings and spot unusual access patterns. You can adjust browser settings, though some account and wallet checks may need cookies to work properly.

Security checks

We monitor login times, device signals, IP patterns and wallet activity to reduce account takeover risk. When something looks unusual, we may ask for extra verification before allowing changes.

Retention rules

Some records are kept while your account is active and for a limited period after closure where disputes, payment checks or legal duties require it. Other records are removed sooner.

Your requests

You may ask to access, correct or delete eligible personal data. We verify identity first, then explain what can be changed, what must be retained and the expected response window.

Questions about your data rights

These answers explain common privacy requests connected with your account, wallet records, cookies and support contact. They are written for India readers using the service where local law permits. If your situation involves a live payment or account lock, contact support with masked details so the team can verify the case.

We collect details you submit, such as account contact data, login records, device signals, wallet activity and support messages. Payment references from UPI, Paytm, PhonePe and Google Pay are stored only as needed for account operations.

Payment records help us match deposits, withdrawals, failed transfers, refunds and disputes to your account. We do not ask you to share passwords or one-time codes, and sensitive details should be masked when contacting support.

Yes. Send a request from your registered email or verified chat session and tell us which detail is wrong. We may ask for proof before changing account, contact or payment-related records.

You can ask us to delete eligible personal data. Some records may need to remain for payment checks, dispute handling, security records or legal duties, and we will explain any retained categories.

Cookies support sign-in sessions, preference storage, fraud checks and page performance. You can manage them in your browser, but blocking some cookies may affect account access, wallet checks or security prompts.

Support messages are available only to staff who need them for service, privacy or account-security work. Cases may be escalated to a specialist team, and access is limited according to role.

Use the privacy email or live chat and include your registered contact detail plus the exact request. For payment matters, provide the transaction time and masked reference, never your password or one-time code.