How We Handle Your Account Data
This is the tugubet privacy policy, written for you in plain language. We explain what we collect when you open an account, how your details move through our...
Our Privacy Posture for Indonesia
We process your personal data only where local law permits and only for purposes tied to your tugubet account: identity checks, lobby access, payment routing and fraud prevention. Within supported regions, we store records for the period required by applicable financial and gaming rules, then remove them. We never sell your details to third parties. When you fund your account through DANA,
OVO, GoPay or QRIS, the wallet operator handles its own data layer under its own policy, and we receive only the confirmation needed to credit your balance. You can ask us to access, correct or delete records at any time, subject to the legal retention windows that apply to gaming operators in your region.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Honest
Editorial Owner
Our in-house compliance editor signs off every line of this policy before it goes live. No outside copywriter touches the...
Legal Review
Indonesian-qualified counsel checks the policy against current data protection expectations on a fixed cadence. If wording needs to shift, we...
Security Team
Engineering reviews the technical claims — encryption in transit, hashed credentials, session controls — so the policy never overstates what...
Payments Liaison
A dedicated contact works with DANA, OVO, GoPay and QRIS partners to confirm the data fields we exchange. That mapping...
Version History
Every change to this page is logged with a timestamp and a short summary. You can request the prior version...
User Feedback
Questions you send to support that touch privacy are reviewed quarterly. If a section confuses people, we rewrite it for...
Consistency With Our Other Policies
| Terms of Service | The privacy policy and our terms use the same definitions for account, lobby and session, so reading one does not contradict the other. |
|---|---|
| Cookie Notice | Cookie categories listed in the banner match the tracking section here exactly, with no hidden trackers added between updates. |
| KYC Policy | Identity documents requested at verification are the same fields named in this policy — no surprise data collection appears later in your account life. |
| Payment Terms | Wallet data handled by DANA, OVO, GoPay and QRIS is described identically in payment terms and in this privacy text. |
| Marketing Preferences | Opt-in choices in your account panel map one-to-one with the marketing section of this policy, so toggling a switch does what the wording says. |
| Retention Schedule | Storage windows quoted here align with the retention annex our compliance team maintains internally for auditors. |
| Complaints Path | The escalation route in this policy mirrors the dispute steps in our terms, ending at the same regulator contact for supported regions. |
What Defines This Policy Page
Plain Wording
We write the policy in everyday English so you can read it once and understand what happens to your data, instead of skimming legal Latin and hoping for the best.
Dated Sections
Every block carries the date of its last edit. When you scroll the page you can see which paragraphs are fresh and which have been stable for months.
Region Flags
Lines that depend on local law are flagged so you know which paragraph applies to you in Indonesia and which is general account housekeeping.
Quick Anchors
The sidebar anchors jump you to retention, cookies, rights and contact without scrolling. Useful when you only need one answer from the policy.
Change Log
At the foot of the page we keep a short change log. You can see when wording was tightened, when a new processor was added and when an old one left.
Request Tools
Built-in buttons let you start an access or deletion request from the page itself, so you don't need to hunt for an email address to exercise your rights.