Terms Page
The terms page sets the contract; this privacy policy explains the data side. Definitions stay aligned so a word like account or session means the same thing on both.
This page sets out how unsurtoto login collects, stores and uses the information tied to your account. We wrote it for you — the person opening a lobby...
Our privacy policy applies wherever local law permits access to unsurtoto login, with Indonesia as our primary supported region. We collect only what your account flow needs: identifiers you submit at sign-up, session signals that keep the lobby stable, and transaction references when you use e-wallets like DANA, OVO, GoPay or QRIS. We do not sell your personal data. Where supported regions
impose stricter rules on consent, retention or cross-border handling, those rules override the defaults written here. You can ask us to correct or erase your record at any time, and we will respond within a reasonable window tied to the request type.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We rewrote this policy without legal padding so the meaning stays obvious. If a clause affects your account, we say so directly rather than burying it under defined terms or cross-references that send you elsewhere.
The policy is reviewed on a fixed cadence and after any change to how we handle account data. The footer carries the last-reviewed date so you always know which version applies to you.
Each revision is signed off by a named reviewer on our side. That keeps accountability inside the brand instead of pointing you at a generic mailbox when you raise a privacy concern.
Wording is tuned for Indonesia where we operate, and we flag clauses that shift when other supported regions apply stricter rules on consent, retention or transfer of your record.
We keep a short change log of material edits to this policy. You can scan it to see what moved between versions without rereading the whole document end to end.
If a clause reads unclear, tell us through the privacy inbox. We treat that feedback as input for the next review and credit the change in the log when wording is updated.
The terms page sets the contract; this privacy policy explains the data side. Definitions stay aligned so a word like account or session means the same thing on both.
Cookies and similar identifiers are covered in their own notice. This policy points there for browser-level signals and keeps the focus on account-tied records you create with us.
Our security notes describe the controls protecting your record. This policy describes what is collected and why; the two read as companions rather than duplicates.
DANA, OVO, GoPay and QRIS references on the payments page line up with the transaction fields named here, so you can trace which data point belongs to which step.
Contact routes here mirror the ones on the main support page, with privacy queries flagged so the right reviewer picks them up instead of a general agent.
Identity checks have their own notice covering documents and retention. This page references that flow without repeating its detail, keeping each document focused on its own job.
Whatever you can change in account settings is mirrored here in writing. If the screen offers an action, this policy explains the data effect of using it.
One canonical page carries the full privacy text. Other surfaces link back to it rather than restating clauses, so you only ever read one version of the rule that affects your record.
Each clause has a stable anchor link. Share or bookmark the part that matters to you and the link will keep landing on the same section even after future edits.
Clauses are ordered by what you are likely to ask first: what we collect, why, how long we hold it, and how you reach us. Legal scaffolding sits lower on the page.
A visible last-reviewed date sits at the top of the policy block. You never have to guess whether the version on screen is current or a cached older draft.
Headings describe the clause in plain words instead of legal labels. Scanning the page tells you what it covers without forcing you to read every paragraph.
Contact paths sit inline next to the clauses they relate to, so a question about erasure or export is answered with the right route on the same line.