How We Handle Your Account Data
This is the mamibet88 privacy policy, written in plain language for our Indonesia account holders. We explain what we collect when you open an account, why we hold...
Our Privacy Posture and Your Rights
We collect the details you give us at sign-up — name, contact, payment reference — plus session data your device shares when you browse our lobby. We hold it where local law permits and only for the purposes you'd expect: verifying your account, processing your DANA, OVO, GoPay or QRIS transactions, and keeping the site stable. We don't sell your data. You
can request a copy, ask us to correct it, or close your account at any time, and we'll act on that request inside the timelines our supported regions require. If our policy changes, we'll flag it on this page before the new wording takes effect.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Why You Can Rely on This Policy
Here's how we keep this document honest and current.
Reviewed quarterly
Our legal and product teams sit down every quarter to check this policy against what the lobby actually does. If...
Written by humans
No boilerplate copied from elsewhere. The wording you're reading was drafted by the same team that runs our Indonesia operations...
Versioned openly
Every revision carries a date and a short note on what changed. You can ask support for prior versions if...
Encrypted in transit
Anything you submit through our forms — sign-up, payment reference, support ticket — moves over encrypted connections. We treat your...
Minimal collection
We ask for what we need to run your account and nothing more. If a field isn't required for verification...
Clear escalation
If our first reply doesn't resolve your concern, you can escalate to our data lead. The path is published here...
Consistency Across Our Policy Pages
Our policy documents share the same backbone so nothing contradicts.
| Terms of Service | Account rules and platform conduct live there; data handling lives here. Where the two touch — verification, account closure — the wording matches on both pages. |
|---|---|
| Cookie Notice | Browser storage and tracking pixels are detailed separately. This privacy policy points to it for session specifics rather than duplicating the same paragraphs. |
| KYC Policy | Identity checks get their own page with document lists and timelines. We reference it here when explaining why we hold verification data. |
| Payments Policy | DANA, OVO, GoPay and QRIS handling rules sit in our payments document. This policy explains the data side; that one explains the money side. |
| Promotions Terms | Campaign-specific data collection is described where the campaign runs. This page covers the baseline that applies whether you opt into promos or not. |
| Complaints Procedure | If a privacy reply doesn't satisfy you, the complaints page sets out next steps. The contact path here feeds directly into that procedure. |
| Account Closure | How to close, what we keep afterwards, and for how long — covered in closure documentation and mirrored in the retention section of this policy. |
What This Policy Page Covers
Here's the shape of the document so you can skim to what you need.
Data we collect
Account fields you fill in, verification documents you upload, and the technical signals your device sends while you browse our lobby. Each category is listed with the reason we need it.
How we use it
Running your account, processing transactions through supported wallets, keeping the site secure, and meeting obligations in supported regions. Nothing beyond those purposes without asking you first.
Who sees it
Our own staff on a need-to-know basis, plus the payment and verification partners we have to share specific fields with. We name the categories so there are no surprises.
How long we keep it
Retention windows match the legal periods our supported regions require. Once a window closes, the record is removed or anonymised on a scheduled cycle.
Your controls
Export, correction, deletion, and the right to object to certain uses. The steps to exercise each are listed with the team that handles them.
Policy updates
How we tell you when wording changes, how much notice you get, and where to find prior versions if you want to check what shifted between revisions.