Reference

Privacy Policy for Your meritking Account

Your privacy choices sit next to the account flow: before you open an account, we tell you which details we collect for login, wallet checks, cookies, and support…

Account data useCookie choicesDANA recordsOVO, GoPay, QRISSupport privacy requests
meritking Privacy Policy for Your meritking Account
CONTACT PATHS

Three Ways to Ask About Privacy

Privacy questions need a clear route, not a generic inbox. Use live chat for urgent account access, email for data requests that need attachments, and the in-account ticket path when you want us to match the request to your logged-in profile. Our team works 09:00-01:00 WIB, and we may ask for an OTP check before discussing private records.

Team online

Live chat privacy queue

Open live chat from the lobby footer and choose Privacy Request. We answer during 09:00-01:00 WIB, confirm your account phone by OTP, then send sensitive follow-up by email when records need checking.

Email for data rights

Write to [email protected] from the email linked to your profile. Include your account ID, the privacy right you want to use, and whether DANA, OVO, GoPay, or QRIS records are involved.

Logged-in privacy ticket

After login, head to Account > Help > Privacy Ticket. That path carries your account ID automatically, so we can compare device logs and respond without asking you to paste private wallet references in chat.

ACCOUNT CONTROLS

Six Controls Around Your Account Data

We handle this policy as an operating checklist, not a wall of legal wording. Each control below maps to something you can see or request: cookie settings, device sessions, payment references, game-category…

Data kept limited

We ask for the details needed to create your profile, verify access, and process wallet events. Extra documents are requested only when account safety, payment matching, or local record duties make them necessary.

Cookie settings

Cookies keep your session active, remember language choice, and help us spot repeated failed logins. You can clear them in Chrome at Settings > Privacy and security > Clear browsing data before returning to the lobby.

Device sessions

Open Account > Security > Devices to see recent phones and browsers connected to your profile. If a device looks wrong, remove it, change your password, and contact chat so we can mark the session.

Payment references

Wallet records include transaction time, rail name, amount, status, and reference code for DANA, OVO, GoPay, or QRIS. We keep payment proof separate from chat text so request handling stays limited.

Access and correction

Ask for a copy or correction by email or Privacy Ticket. We check the account ID, confirm OTP where needed, and respond with the data categories we hold or the change result.

Retention handling

Some records stay longer because payment disputes, security logs, or local rules require a trace. When that reason ends, we delete, mask, or aggregate data so it no longer points directly to you.

Privacy Questions Before You Open an Account

These answers cover the privacy tasks you are most likely to check before opening or using an account. They focus on access, correction, cookies, payment records, and contact timing, so you know what happens before you send DANA, OVO, GoPay, or QRIS details through the wallet. For anything unique, contact us and we will handle it through the same verification steps.

We collect your name, phone or email, login credentials, device signals, IP records, cookie choices, and wallet references. We use them for access, support, payment matching, security checks, and legal record duties where service is allowed.

Yes. We record the rail name, reference code, transaction time, amount, and status so the wallet can match your request. We do not store your full app login details for DANA, OVO, GoPay, or QRIS.

Yes. Email [email protected] or use Account > Help > Privacy Ticket. We verify your account ID and may request OTP confirmation before sending a summary of the data categories linked to your profile.

Cookies keep your session active, remember language choice, and help detect repeated failed logins. On Android Chrome, use Settings > Privacy and security > Clear browsing data if you want to remove stored browser data.

You can request a correction through the Privacy Ticket path. We compare your request with login records and wallet references, then update details that are not locked by payment evidence or local record duties.

Retention depends on the record type and local law. Login logs, payment references, support tickets, and security alerts may have different timelines; once the reason ends, we delete, mask, or aggregate the data.

Access is limited to staff and service partners who need the record for support, payment matching, security checks, hosting, or legal duties. Internal access is logged so sensitive account records are not opened without a work reason.