Reference

Privacy Policy for your rajaluck account

Your account, device, cookie and payment privacy choices sit at the centre of this Privacy Policy, including records linked to UPI, Paytm, PhonePe and Google Pay.

Account dataCookie choicesUPI contextAccess requests

Explore the Lobby Read FAQ

How we handle India account data

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

This Privacy Policy applies when you create or use an account with rajaluck, contact our team, visit rajaluck.asia, adjust cookie choices or make payment-related requests through UPI, Paytm, PhonePe or Google Pay. We collect only the data needed to run your account, verify access, process wallet

1
activity, keep records, meet legal duties and answer your privacy requests. Some data comes from you directly, such as name, mobile number, email address and identity checks. Other data is created through use, such as login time, device type, IP address, cookie settings and transaction references.
2
Access and eligibility depend on local law and are available where local law permits. If a rule requires us to keep a record, we retain it for that purpose and limit access to staff or service partners who need it.

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

CONTACT PATHS

Privacy help for UPI and Paytm

Privacy requests need a clear route, especially when they involve payment references or account access.

Email privacy desk Send privacy requests to [email protected] with your registered mobile number, email address and a short description of the change you want. We reply after matching the request to your account records.

Chat privacy queue Open chat from your account menu when you need a quick privacy status check. The team can confirm receipt, explain pending identity checks and point you to the next safe step.

Account request form Use the privacy request form for copies, corrections or deletion requests where allowed by law. Add payment reference IDs only when the request involves UPI, Paytm, PhonePe or Google Pay activity.

HANDLING CARE

Cookies, security and data changes

We treat privacy work as an account operation, not a slogan. Each request is logged, checked against account ownership and handled by staff with limited access.

Data we collect

We collect account details, contact data, device signals, login records, cookie choices and wallet references. Game titles such as Speed Baccarat or Aviator may create session records used for account history and dispute checks.

Payment privacy

UPI, Paytm, PhonePe and Google Pay entries may include transaction IDs, timestamps and status messages. We use these records to match wallet activity, answer payment privacy requests and meet record-keeping duties.

Cookie controls

Cookies help keep your session active, remember language choices and flag unusual access patterns. You can adjust browser settings, but some account functions may ask you to log in again after changes.

Account security

We use password checks, session controls and device signals to reduce unauthorised access. If a privacy request touches sensitive data, we may ask for an identity step before acting on it.

Retention periods

Some records are kept while your account stays active, while payment and legal records may remain longer. When a record is no longer needed, we remove it or make it harder to link back to you.

Change requests

You can ask us to correct account details, provide a copy, restrict certain processing or delete data where the law allows. We explain any refusal in plain language with the reason.

Your Privacy Policy questions answered

These answers explain the practical parts of the Privacy Policy in plain language. They cover what data is collected, how payment records are treated, how cookies work, and how you can contact us. If your request needs account matching, we will ask only for details needed to confirm ownership.

It covers account details, contact records, login history, device signals, cookie settings, wallet activity and privacy request messages. It also covers records created when you use lobby areas such as Speed Baccarat, John Hunter or Football Strike.

We share payment-related data only with service partners who help process or check transactions, or where a legal duty requires it. UPI, Paytm, PhonePe and Google Pay references are used for wallet matching and privacy requests.

Cookies remember your session, help keep access secure and support basic site functions. If you block or delete them, you may need to log in again, and some account settings may not load as expected.

Yes, you can ask us to correct account details that are incomplete or wrong. We may request a short identity check first, especially when the change involves mobile number, email address or payment records.

We keep records for as long as they are needed for account operation, transaction matching, legal duties or dispute handling. When those reasons end, we delete the record or reduce its link to you.

We match the request to your account before sharing or changing data. Sensitive requests may need extra confirmation, such as a registered email reply or another account check, so data is not sent to the wrong person.

Access and eligibility depend on local law and are available where local law permits. If a privacy request is affected by a legal rule, we explain what we can do and what record must remain.

Privacy Policy for your rajaluck account

Privacy help for UPI and Paytm

Cookies, security and data changes

Data we collect

Payment privacy

Cookie controls

Account security

Retention periods

Change requests

Your Privacy Policy questions answered

01 What data does this Privacy Policy cover?

02 Does rajaluck share my payment details?

03 How do cookies affect my account?

04 Can I ask for my data to be corrected?

05 How long do you keep account records?

06 How is my account protected during privacy requests?

07 What if local law affects access?

Related Pages