LEGAL REFERENCE

Privacy Policy for Your Account

rajatoto2 keeps live casino tables, slot rooms and sportsbook markets under one account flow for Indonesia, and this Privacy Policy shows how the data behind that flow is...

Policy-first account flowIndonesia data contextQRIS and e-wallet contextClear contact paths
Explore Games Read FAQ
rajatoto2 Privacy Policy for Your Account

How We Handle Account Data

This Privacy Policy explains how we collect, use, store and protect personal data connected with your rajatoto2 account, lobby access, identity checks, device sessions and wallet references. We use the data you provide to operate your account, confirm access where local law permits, reduce misuse, answer your privacy requests and keep transaction records aligned with supported regions. DANA, OVO, GoPay and QRIS

names may appear in account records only as context for wallet activity, confirmation checks or service support. We do not treat this policy as permission to sell your personal data. We share limited data only with service partners who help us run secure account, verification, hosting, analytics or support processes under controlled terms.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

24/7 SUPPORT

Privacy Contact Paths for You

Send privacy questions through the path that matches your account issue. We keep the wording direct, ask only for needed details and route each request to the team handling data access, correction or retention.

Team online

Privacy inbox

Use the privacy inbox when you want to ask how your account data is collected, stored or shared. Include your account name, contact email and a clear request so we can trace it safely.

Account support desk

Contact account support when your privacy question is linked to login records, wallet references or profile details. We may ask verification questions before discussing any data tied to your account.

Policy change queries

If a policy update affects how you understand your data, send us the section name and your question. We will explain the change without asking for unrelated account details.

TRUST MARKERS

Policy Signals You Can Check

Our privacy page is written so you can see who controls the data flow and why each data category matters. These signals help you assess the policy before...

Named data controller

We identify rajatoto2 as the brand responsible for account privacy decisions on this page, so you know where to send...

Plain privacy wording

We avoid legal fog where possible and explain data collection in direct account terms. That helps you understand what happens...

Local market context

The policy reflects Indonesia access and supported regions, including references to DANA, OVO, GoPay and QRIS when those names appear...

Purpose limits

Each data category is linked to a purpose, such as account access, support, verification, security checks or legal record keeping...

Retention controls

We keep account data only as long as needed for the purposes described, unless legal duties require longer storage. When...

Internal policy checks

Our team checks privacy wording against current account flows, support scripts and wallet-reference handling. If the flow changes, we update...

Consistency Across Related Policy Pages

Your privacy expectations should not change from one legal page to another. We keep this Privacy Policy aligned with related pages so account data, cookies, contact paths and...

Account terms alignment
Our account terms describe access rules, while this Privacy Policy explains the data used to support those rules. We check both pages so privacy wording does not conflict with account handling.
Cookie page alignment
Cookie wording supports this policy by explaining device signals, session tools and analytics tags. We keep cookie purposes tied to account safety, page function and measurement, not vague tracking language.
Promotion terms alignment
When a campaign collects account details, the related terms must match this Privacy Policy. We keep promo form fields, contact choices and retention wording consistent with privacy commitments.
Verification wording alignment
Identity and access checks may require extra data. Our related pages use the same privacy language, so you understand why verification is requested and how those records are controlled.
Wallet reference alignment
DANA, OVO, GoPay and QRIS references are described as account context, not broad financial profiling. Related pages should use the same narrow wording when wallet activity is mentioned.
Support flow alignment
Support scripts follow this Privacy Policy when handling data questions. We ask only what is needed to confirm your account and answer the privacy issue you raised.
Change date alignment
When this policy changes, related pages are checked for matching dates and wording. That way you do not see one privacy statement here and a different promise elsewhere.
PLATFORM SNAPSHOT

Privacy Layout You Can Scan

This page is built to help you read the policy fast before opening an account. The layout highlights data purposes, contact routes, change markers and Indonesia context without pushing you away from the policy.

01
Policy summary band The summary band explains the policy purpose in plain account language before the legal detail starts. It helps you decide which data areas matter most to your account decision.
02
Data category cards Cards group personal data into clear buckets such as account details, device signals, verification records and support messages. This makes it easier to see why each category is collected.
03
Context chips Short chips such as DANA, OVO, GoPay and QRIS show where local wallet references may appear in privacy records. They are context markers, not a separate privacy promise.
04
Contact rail The contact rail keeps privacy help close to the policy text. You can raise access, correction, deletion or retention questions without searching through unrelated account pages.
05
Update marker A clear update marker shows when the policy was last changed. If wording is revised, we keep the date visible so you can compare it with earlier account decisions.
06
FAQ block The FAQ block answers practical privacy questions in direct language. It focuses on account data, sharing, retention and your request paths instead of repeating broad brand messages.

Privacy Policy Questions Before You Join

We collect account details you submit, login records, device signals, verification data, support messages and transaction context. We use these records to run your account, protect access and answer privacy requests.

We need account data to create and maintain your account, confirm access where local law permits, protect sessions, respond to support issues and keep records required for supported regions.

Those names may appear in transaction or support records as wallet-reference context. We use them to confirm account activity, investigate issues and maintain records, not to create unrelated personal profiles.

We share limited data with service partners that help with hosting, security, analytics, verification or support. They must handle the data for our stated purposes and under controlled processing terms.

We keep data for as long as needed to manage your account, meet legal duties, resolve disputes and protect access. After that, we delete it or reduce its link to you.

Contact us through the privacy inbox or account support path. Tell us what you want to access, correct or delete, and we will verify your account before handling the request.

When we change this policy, we update the page date and adjust related wording where needed. If the change is important, we may add an account notice or direct support response.