Reference

mahkota 212 Privacy Policy For Your Account

Our mahkota 212 Privacy Policy explains what we collect when you open an account, enter the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount access choicesCookie controlsContact for changes
mahkota 212 mahkota 212 Privacy Policy For Your Account
CONTACT THE DESK

Where To Ask About Your Privacy Policy

A clear contact path helps you question a data entry without explaining your whole account history. Start from the support route linked to your account area and mention the email or phone detail connected to your mahkota 212 profile. We use the request to locate the relevant record, check identity and reply about access, correction, deletion or policy wording where local law permits.

Team online

Account data request

Ask us to confirm which account details we hold, such as your login identifier, verification status or wallet reference. Include the account step involved so we can find the correct record without asking you to send a password.

Wallet record question

For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and date rather than a wallet PIN. Our support path can compare the payment status with the account record while keeping secret credentials out of the request.

Correction or deletion

Tell us which field needs changing or which request you want considered for removal. We may ask for an account confirmation before acting, and some records can remain when retention is required by local law.

HANDLING DETAILS

What We Do With Data After Access

We keep the Privacy Policy connected to practical account steps: phone verification before account access, wallet status checks and device sessions.

Account details

We may use your name, contact detail, phone verification result and account activity to create access, answer support requests and protect the account. We do not need your password in a support message, so keep that credential private.

Cookies and sessions

Cookies and similar session records can keep your login path working, remember security preferences and help identify unusual device behaviour. Your browser settings can restrict cookies, although some account and Privacy Policy functions may then need another check.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a status update to your account. We use the reference for reconciliation and support, not as a substitute for your private wallet PIN.

Security checks

Phone verification and device-session checks help us distinguish your account access from an unfamiliar sign-in. If a session appears unusual, we may pause the requested account action while identity details are checked through our support route.

Retention period

We retain account, payment and security records for the period needed to operate the requested service, resolve disputes or meet legal duties. When a record no longer serves those purposes, we assess it for removal or de-identification.

Policy changes

If our data practices change, we update this Privacy Policy and show the revised wording on the policy page. Check the page before opening an account or submitting new wallet details so your choices reflect the current text.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening access. We explain the practical route for checking data, changing details and contacting us, while eligibility and access remain where local law permits.

The Privacy Policy covers account details, phone verification, device sessions, cookies, payment references and support requests. It also explains why technical records may be created when you open the lobby, use DANA or QRIS, and move between account pages.

We may receive a selected payment rail, transaction reference, status, amount-related record and confirmation time for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Do not send us a wallet PIN or account password when asking for help.

You can contact our support route and ask which personal account records we hold. Include your account identifier and the data category you want checked. We may verify your identity first, then respond according to the Privacy Policy and local law.

Send a correction request through the account support path, naming the field that is wrong and the replacement detail. We may confirm your phone or account access before changing it, especially when the request affects wallet matching or payment status.

We keep payment and account records for as long as needed for reconciliation, support, security, dispute handling or a legal duty. The exact period can depend on the record and local requirements, and we assess older data for removal or de-identification.

You may ask us to delete or restrict particular data through support. We assess the request against account security, unresolved payment checks and retention duties. Where local law permits, we remove data that no longer has a valid operational or legal purpose.

Yes. The Privacy Policy applies when you use a mobile browser or desktop, including cookies, session records and device security checks. If you use a shared phone in Yogyakarta or Jakarta, sign out and clear saved browser data after account access.