LEGAL REFERENCE

How domtoto Handles Your Account Data

This is the privacy policy for your domtoto account. We explain what we collect when you open the lobby, why we keep it, and how long it stays...

Account dataSession logsCookie controlsIndonesia scopePlain wording
domtoto How domtoto Handles Your Account Data

Our Privacy Posture and Your Rights

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

24/7 SUPPORT

Reach Us About Your Privacy Record

Team online

Privacy Inbox

Email our data desk to request an export, a correction or a deletion of your domtoto account record. We confirm receipt the same day and resolve inside the window your jurisdiction defines.

Live Chat Desk

Open the chat bubble inside the lobby and ask for the privacy queue. The agent routes your case to the data team and shares a ticket reference you can quote in any follow-up message.

Account Settings

Inside your domtoto profile you'll find toggles for marketing contact, session cookies and saved device list. Changes apply immediately and a confirmation lands in your registered inbox for your records.

WHY VISITORS TRUST US

How This Policy Is Reviewed

Policy Owner

Our data protection lead signs off every revision before it appears on this page. Nothing ships without their review, and the version date at the foot of the policy is updated each time wording shifts.

Legal Sign-off

External counsel familiar with Indonesia data rules reads each draft. They flag anything that conflicts with local statutes and we adjust the wording before the policy reaches your screen.

Security Review

Our security engineers map every clause to a real control — encryption at rest, access logging, vendor scoping. If a clause cannot be backed by a live control, we rewrite it until it can.

Vendor Audit

Processors that touch your data sit on a register we audit twice a year. Contracts carry data-processing addenda and breach-notice clauses that match the obligations you read in this policy.

Change Log

Material changes are summarised at the head of the page and emailed to your registered address. Minor edits are dated quietly so you can compare wording across revisions whenever you need to.

User Feedback

When you write in with a privacy question that exposes unclear wording, we treat it as a bug. The next revision usually carries the clarification and we credit your input in the change log.

SIDE BY SIDE

Consistency Across Our Policy Pages

01

Terms of Service

Definitions used here — account, session, processor, retention — match the Terms exactly so you never read two versions of the same word.

02

Cookie Notice

The cookie categories described in section four mirror the toggles inside the Cookie Notice, including the analytics and preference buckets you can switch off.

03

AML Statement

Identity-check data referenced in our AML page is the same record this policy governs, with retention windows that line up clause for clause.

04

Complaints Page

The escalation route in our complaints page picks up where this policy ends, so a privacy ticket can become a formal complaint without restarting from zero.

05

Account Closure

Closure timing here matches the closure flow page: data minimisation kicks in the day your wallet zeroes and your final session expires.

06

Marketing Preferences

Opt-in language on this page is repeated verbatim on the marketing preferences screen so the consent you give is the consent we record.

07

Vendor Register

The processor list summarised here is published in full on our vendor register, refreshed alongside every material policy update.

QUICK SIGNAL

What Defines Our Policy Layout

Plain Wording Every clause is written for a reader, not a lawyer...
Section Anchors Each heading carries a deep link so you can share...
Version Date The foot of the page shows the day this wording...
Inline Examples Where a clause talks about data we collect, a short...
Quick Index A short table of contents sits at the top of...
Contact Block Every page closes with the same contact block — privacy...

Privacy Questions We Hear Most

We record your name, date of birth, contact details, the device you sign up on and the payment reference linked to your first top-up. Anything beyond that is collected only when a specific feature needs it.

Yes. Send the request from your registered email and we'll confirm receipt the same day. Where local law permits, we erase your record once outstanding obligations — financial, regulatory — have cleared on your account.

Login and session records sit on file for the period our jurisdiction sets for fraud and dispute handling. After that window they are aged out automatically and cannot be restored, even by our internal teams.

Only with processors we have contracted — payment partners, identity-check vendors, analytics. Each is scoped to the task they perform and audited against our register. We never sell your record to advertisers.

Open your profile, head to the marketing screen and switch the channels you want off. The change applies immediately and a confirmation message lands in your inbox so you have a written record of it.

Your record sits with regional processors in supported regions, with encryption at rest and access logging on every read. Cross-border transfers happen only where local law permits and under contracted safeguards.

Material changes are summarised at the head of the page and emailed to your registered address before they take effect. Minor edits are dated in the change log so you can compare any two revisions.