LEGAL REFERENCE

Privacy Policy at eurototo

This is the eurototo privacy policy — the document that tells you exactly what we collect, why we keep it, and how long it sits on our servers...

Plain-English PolicyIndonesia-FocusedData MinimisedConsent-LedUpdated Regularly
See the Lobby Read FAQ
eurototo Privacy Policy at eurototo

How We Handle Your Account Data

Our privacy posture follows Indonesian data-protection norms and applies where local law permits. We collect the minimum needed to open and protect your eurototo account: identity details, device fingerprints, session logs, and the wallet reference you nominate. Payment rail names like DANA, OVO, GoPay and QRIS appear in your transaction history because the lobby has to route deposits and withdrawals correctly. We

never sell your personal data. Internal teams handling fraud checks and policy reviews see only what their role requires. You can ask us to export, correct or erase data tied to your profile at any time, subject to retention rules tied to anti-fraud obligations in supported regions.

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

SUPPORT

Privacy Contact Paths

If something in this policy needs explaining or you want to exercise a data right, here's how to reach the team that actually handles it. We route privacy requests separately from general...

Privacy Inbox Email our data team directly with your account reference and the request type — access, correction, or erasure. We acknowledge inside one business day and aim to resolve within thirty.
In-Lobby Chat Open the chat icon while signed in and pick the privacy topic from the dropdown. The agent will escalate straight to our compliance desk rather than handing it back to standard support.
Postal Request For formal data requests you can post a signed letter to our registered office. Include your account email so we can match the request to the correct eurototo profile without delay.
EDITORIAL CLARITY

How This Policy Gets Reviewed

We treat the privacy page as a living document rather than a one-time legal sign-off. Here's who touches it and why you can take it at face value.

Compliance Sign-Off

Every policy edit passes through our compliance lead before it goes live. They check Indonesia-specific clauses and confirm retention windows...

Legal Counsel

External counsel reviews material changes annually. They flag drafting that could be ambiguous for Indonesian readers and rewrite anything that...

Security Team

Our security engineers map every data category in this policy to an actual store, so what you read here matches...

Editorial Pass

A plain-language editor rewrites legalese before publication. If a clause cannot be explained in two sentences, we split it rather...

Version History

Each revision carries a date stamp and a short note explaining what changed. Older versions stay accessible so you can...

User Feedback

Questions raised through the privacy inbox feed back into the next revision. If many of you ask the same thing...

Consistency Across Our Policy Pages

Our privacy, terms, cookie and KYC pages are written as a set. Here is how this document lines up against its siblings so nothing contradicts.

Privacy vs Terms
The terms cover your account contract; this privacy page covers data. Where they overlap — like account closure — both pages point to the same retention window so you never see conflicting numbers.
Privacy vs Cookies
Cookie behaviour has its own page with the granular toggles. This document references it but does not duplicate it, keeping each policy focused on a single subject for easier scanning.
Privacy vs KYC
Identity-verification data sits under KYC procedure with stricter retention. This page links out rather than restating, so the legal basis for each data class stays unambiguous.
Privacy vs Marketing
Consent for promotional messages is logged separately from account data. You can withdraw marketing consent without affecting the data we must keep for fraud and audit reasons.
Privacy vs Payments
Wallet identifiers tied to DANA, OVO, GoPay or QRIS are referenced here, but the payments policy holds the full processing detail. Both pages cite the same retention clock.
Privacy vs Security
The security page describes controls; this page describes data. Together they answer both what is held and how it is protected, without overlapping wording that could drift apart over time.
Privacy vs Complaints
Privacy complaints follow the same escalation ladder as account complaints, but reach our compliance desk one step earlier. The complaints page documents the shared timelines openly.
PLATFORM SNAPSHOT

What This Policy Page Shows You

To make the document usable rather than ornamental, we built the page around six visible elements. Each one helps you find the clause you actually need.

Section Anchors A sticky sidebar lists every clause heading. Tap one and...
Plain-Language Summary Every clause opens with a one-line summary in everyday English...
Last-Updated Stamp A clear date sits at the top of the page...
Data-Category Table A compact table maps each data category to its purpose...
Rights Checklist Your data rights are listed as a checklist with the...
Change Log At the foot of the page, a log records every...

Privacy Policy Questions

We store your registration details, verification documents, session logs and transaction references. Wallet identifiers tied to DANA, OVO, GoPay or QRIS appear so deposits can be reconciled. Anything outside that scope is not collected.

Account records sit on our servers for the retention period required by anti-fraud and tax obligations in supported regions. Once that clock runs out, the profile is deleted or anonymised, except for aggregated audit data.

Yes. Email the privacy inbox from your registered address and we will compile an export. The package usually arrives within fifteen business days and covers every clause listed on this policy page.

We share only with processors needed to run the service — payment routers, verification partners and infrastructure providers. They are contractually bound to our privacy standards and never receive more than the specific fields their function requires.

Most fields can be edited from your account settings. Identity-verified fields like full name or date of birth need a quick message to compliance with supporting documents, and we update them once the document check clears.

Material changes are notified by email and through an in-lobby banner before they take effect. The change log at the foot of the page records what shifted, so you can compare against the version you originally agreed to.

Use the privacy inbox or open in-lobby chat and pick the privacy topic. Both routes reach the compliance desk directly rather than general support, which keeps response times tight and the answer accurate.