LEGAL REFERENCE

How mantap21 Handles Your Privacy

This is our privacy policy page, where we set out how mantap21 collects, stores and uses the data tied to your account. We've written it for Indonesia readers...

Data we storeWhy we store itYour rightsRetention windowsContact paths
mantap21 How mantap21 Handles Your Privacy

Our Privacy Posture and Jurisdiction Notes

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

PLAYER SUPPORT

Privacy Contact Paths

Privacy Inbox Email our privacy desk for access requests, corrections...
In-Account Ticket Open a ticket from inside your account when...
Live Chat Desk Use the chat bubble for quick clarifications about...
WHY THIS PLATFORM

How We Keep This Policy Honest

Editorial Owner

Our in-house compliance lead owns this document and signs off every revision. Nothing on this page is auto-generated marketing copy...

Review Cadence

We revisit the policy on a fixed quarterly cadence and whenever a processor changes. Each revision gets a dated entry...

Processor Register

We keep a current register of every third party touching your data, from KYC vendors to payment routers handling DANA...

Data Minimisation

We collect only the fields the lobby and payment rails actually need. Optional profile entries stay optional, and we flag...

Breach Protocol

If a security event affects your records, we notify you directly through your registered channel and lodge the matter with...

Independent Audit

An external auditor reviews our handling controls each year and tests the deletion pipeline end-to-end. Findings feed straight back into...

Consistency Across Our Policy Pages

ScopeThis page focuses on personal data. Our terms page covers account conduct and our cookie note covers tracking — three documents, one consistent voice, no contradictions between them.
DefinitionsTerms like account data, verification data and device signals carry the same meaning across every legal page we publish, so you don't have to re-learn vocabulary moving between them.
JurisdictionEvery policy page references the same supported-regions clause for Indonesia, so the access conditions you read here match what the terms page tells you about lobby eligibility.
RetentionRetention windows quoted here align with the financial-record windows on the terms page. If one document updates, the other updates in the same release cycle.
ContactThe privacy inbox, ticket category and chat path on this page are the same routes referenced on the support page, so you never get bounced between desks.
Change LogMaterial updates appear in a shared change log at the foot of each legal document, dated and summarised, so you can audit history without filing a request.
LanguageAll policy pages are written in the same en-ID register for Indonesia readers — plain, declarative sentences, no boilerplate dumps copied from elsewhere.

What This Policy Page Gives You

Plain-English Body

We've stripped the legalese where we can. The clauses you actually need — what we hold, why, and for how long — sit near the top and read like normal English, not a contract template.

Dated Change Log

Every revision is dated and summarised. You can see at a glance which clauses moved in the last release and whether any change affects how your account data is handled.

Quick Anchors

Section anchors let you jump straight to retention, processors or your rights without scrolling the whole document. Useful when you only need to confirm one specific point.

Rights Summary

Your access, correction, deletion and objection rights sit in a single block near the contact section, so the route from reading about a right to exercising it is short.

Processor Notes

Where a clause depends on a third party, we name the category and point to the register. No vague references to unspecified partners handling your mantap21 records.

Mobile Layout

The page is built for phone reading first. Headings stay tight, paragraphs stay short, and the contact chips remain reachable at the bottom of the viewport on small screens.

Privacy Questions We Hear Often

We store the account identifiers you submit at signup, the verification documents required by Indonesia regulation, your linked e-wallet references, and session signals from the device you use to reach the lobby. Nothing beyond that is retained by default.

Financial and verification records sit in archive for the window Indonesia statute requires, typically several years. Marketing-related fields are removed sooner. Specific retention durations are listed inside the policy body above this FAQ block.

Yes. File an access request through the privacy inbox or open a ticket from inside your account. We confirm identity first, then return a structured export within the statutory window for Indonesia data subjects.

Only the minimum needed to route a transaction. When you top up via DANA, OVO, GoPay or QRIS, the provider receives the reference and amount required to settle. They do not receive your full mantap21 profile.

Yes, most fields are editable from your account settings directly. For locked fields tied to verification, raise a correction request through the privacy ticket category and our team will action it once supporting evidence is supplied.

We notify you through your registered contact channel, describe the scope in plain terms, and report the event to the Indonesia authority within the timeframe statute sets. Remediation steps are communicated alongside the initial notice.

Material revisions trigger an in-account notice before they take effect, plus an entry in the dated change log at the foot of this page. Minor wording fixes are logged but won't prompt a separate alert.