LEGAL REFERENCE

Privacy built for your account

dapa toto keeps your account data, lobby activity and contact choices in one clear privacy flow for Indonesia. Open your account in seconds and we will show you...

Clear collectionAccount privacyIndonesia focusSupport ready

Browse the Lobby Read FAQ

How we handle your privacy

This Privacy Policy explains how we collect, use, store, share and protect personal data when you create an account, access our lobby, contact support or use account features where local law permits. We collect details you provide directly, technical data from your device, account security records and transaction references linked to supported regions. DANA, OVO, GoPay and QRIS may appear as context

within your account flow, but we do not turn this policy into a payment instruction page. We use your data to operate your account, secure access, respond to your requests, meet compliance duties and improve the way privacy controls are presented. We aim to keep the wording practical, so you can understand what happens before you join, while you browse, and when

you ask us to update or remove eligible records.

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

HELP CHANNELS

Privacy help when you need it

If you have a privacy question, we want the route to feel simple. Use the contact path that matches your request, include...

REVIEW SIGNALS

How this policy stays accurate

We treat this page as a live privacy document, not a filler legal page. Our team checks wording against the account journey, support scripts and local access requirements...

Policy owner

A named internal function maintains the privacy text and checks that updates reflect how account data is collected, used and...

Change review

When account screens, verification steps or contact flows change, we compare them with this policy and update wording that no...

Plain wording

We avoid hiding privacy terms behind heavy legal phrasing. You should be able to understand what data we ask for...

Access awareness

Where local law permits access, we explain data handling in a way that fits the supported regions we serve, including...

Support alignment

Our support team uses the same privacy posture shown here, so requests about correction, account access or contact preferences are...

Record discipline

We keep privacy records only for relevant operational, security and compliance reasons, then review retention needs so old data is...

Consistent policy language across pages

Privacy works better when related pages do not contradict each other. We keep this page aligned with account terms, cookie wording and contact instructions, while still making this...

Account terms

Our account terms explain access rules, while this Privacy Policy explains what happens to your data during that access. The two pages are checked together when account handling changes.

Cookie wording

Cookie language covers browser storage and similar tools. This page connects those tools to privacy purposes, including security, session continuity and preference handling across your device.

Contact page

Our contact page may show the fastest route to reach us, but this policy explains what we need from you before discussing private account records.

Promo messages

Promotional content may invite you to see what is running this week, while this page explains how contact preferences and message records are handled privately.

Security steps

Security prompts protect your account access, and this policy explains why certain checks, device signals or login records may be stored for account protection.

Regional access

Pages that mention supported regions use the same privacy posture: access is described where local law permits, and personal data is handled with that context in mind.

Data requests

If you ask to access, correct or remove eligible data, support follows this policy first, then checks any related page only when it affects the request.

Policy layout you can scan

We designed this privacy page to help you decide before opening an account. The layout separates collection, use, retention, contact choices and support routes, so you...

Short privacy badges

The opening badges show the main privacy themes immediately, so you can see that the page is about account data, Indonesia context and support access before reading deeper.

Clear data purpose

Each paragraph links data collection to a practical account reason, such as security, support, access, preference handling or compliance, instead of leaving the purpose vague.

Readable sections

Section titles stay short and direct, helping you scan the privacy flow on mobile before deciding whether to join, browse further or contact us with a question.

Contact routes

Support cards separate privacy, security and marketing preference questions, so you can send the right request without exposing more personal data than the case requires.

Consistency checks

The comparison section explains how this policy stays aligned with account terms, cookies and contact pages, reducing mixed messages about how your data is handled.

FAQ closure

The final questions answer privacy points you are likely to check before creating an account, including retention, updates, device data and contact preference handling.

Privacy questions before you join

We collect the details you submit, account identifiers, contact records, device signals and security logs needed to operate your account. We avoid asking for extra data unless it supports access, verification or support.

We use your data to create and maintain your account, protect login access, answer support requests, manage contact preferences and meet compliance duties. We do not use this policy to expand beyond those privacy purposes.

They may appear as account context in supported regions, but this page focuses on personal data handling. Transaction references may be stored for security, account support and compliance where local law permits.

Yes. Contact support with enough detail to identify your account, and we will review eligible corrections. We may verify you first to protect your private records from unauthorised changes.

We keep data for account operation, security, legal and compliance needs, then review whether continued storage is still required. Some records may stay longer when disputes or legal duties apply.

We check that the request comes from the right account holder before sharing, changing or removing private records. This helps prevent another person from using support to access your data.

Yes. Tell us which channel you want adjusted, and we will apply the preference where our systems and regional rules allow. Service or security messages may still be sent when needed.