Reference

Inside loterysambad Privacy Policy

Open your account in seconds and we will show you how we handle sign-in details, payment traces and cookies across the site.

UPIPaytmPhonePeCookies

Browse lobby Read FAQ

What This Policy Covers Today

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

We collect the details you enter when you create an account, verify your identity, add a payment route or ask support for help. That can include your name, mobile number, email address, device data, IP address, cookies, wallet traces and the messages you send us. We

1
use that data to run login access, process deposits and withdrawals, check suspicious activity, answer requests and keep the service records required by law. Access stays limited to staff and service partners who need it for those tasks, and they are bound to use it only
2
for that purpose. If local law changes, or if a state rule gives you a different path, we follow the rule that applies in your place of access. We do not keep data forever; retention depends on the reason we collected it and the period the
3
law expects us to keep it.

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

PRIVACY CONTACTS

Where to Send Privacy Requests

If you want to ask about the data we hold, the fastest route is the contact option in your account area.

In-site chat Use chat to ask what account details we hold, why we need them, or how long they stay on file. We route each request to the team that handles privacy queries, not general site messages.

Email request Send a message from the address linked to your account if you want a copy, correction or deletion request handled. Include the mobile number on file so we can verify the right record quickly.

Contact form Use the form for cookies, device data or access questions when chat is not convenient. We log the request, confirm the account, and reply with the next step under the rule that applies to you.

HOW WE KEEP RECORDS

How We Handle Your Records

We keep the policy tied to your account activity, not a public profile. That means the records we collect are used for login checks, payment trace matching, support replies and legal retention…

Data we collect

We keep only the fields needed to open and secure your account: name, mobile number, email, device data, IP address, cookies, and payment trace details that support verification and record-keeping.

Cookies and sessions

Cookies let us remember your sign-in state, language choice and page flow so you do not repeat entries on every visit. You can clear them in your browser, though some settings may reset after that.

Account security

When we spot an unusual login, we may ask you to confirm the account before changing sensitive fields. That extra check protects your data from accidental edits and helps stop access from the wrong device.

Retention

We keep records only for the time needed to run the account, answer a query, settle a dispute or meet a legal duty. Once that period ends, we delete or anonymise the data where the rule allows.

Requests and fixes

You can ask to see what we hold, correct a mistake or raise a deletion request. We may need one more check on the mobile number or email tied to the account before we act.

Sharing

Some service partners handle verification, hosting, messaging or payment tracing. They receive only the data needed for that task, and they must keep it within the purpose we set for them.

Questions About This Policy

These are the questions we hear most when you want to understand how your account data is handled. Each answer stays focused on access, retention, correction, cookies and contact paths, so you can check what happens before you share anything else. If a local rule gives you a different right, that local rule applies to your account.

It covers the account data you share, the device and cookie data we collect, the support messages you send, and the way we store or share those records under the rule that applies where you access the site.

Usually we need your name, mobile number, email, login details and any identity file the account check asks for. We also record device data and IP address so we can protect access and keep the account stable.

Payment records help us match deposits, withdrawals and account balances to the right profile. We keep the trace needed for verification and dispute handling, but we do not use those records for anything outside the policy set out here.

Yes. You can ask to see the data, fix a mistake or request deletion where local law permits. We first confirm the account through the mobile number or email linked to it, then handle the request.

Retention depends on why we collected the record. Some data is needed for account checks or legal duties, so it stays longer; other data is removed once it is no longer needed for service or record-keeping.

Cookies remember session state, language and page flow. Device records help us spot unusual access and keep the login path working. You can clear cookies in your browser, though some settings may reset after that.

Use chat, email or the contact form in your account area. If your request needs a correction or a copy, include the mobile number or email on file so we can match the right record.

Inside loterysambad Privacy Policy

Where to Send Privacy Requests

How We Handle Your Records

Data we collect

Cookies and sessions

Account security

Retention

Requests and fixes

Sharing

Questions About This Policy

01 What does this policy cover?

02 What details do you collect when I open an account?

03 How do you use my payment records?

04 Can I ask for a copy or correction?

05 How long do you keep account data?

06 What about cookies and device records?

07 How do I contact you about a privacy request?

Related Pages