Reference

Privacy Policy for Your keris34d Account

keris34d Privacy Policy explains what we collect when you open an account, use the lobby and connect DANA, OVO, GoPay or QRIS.

Clear data purposesWallet status checksAccount access controlsRequest path included
Browse The Lobby Read FAQ
keris34d Privacy Policy for Your keris34d Account
HELP WITH DATA

Get Privacy Help Beside Account Support

A privacy question should have a clear route, especially when it concerns a phone number, wallet reference or sign-in record. Contact our support desk from the account help path and state that your request concerns the Privacy Policy. Include the email or phone detail linked to your account, but do not send a password or full wallet credentials. We can use your account step, payment reference or device path to locate the relevant record and explain what action is available.

Team online

Privacy request

Ask us to explain how a particular account detail is used under this Privacy Policy. We may ask you to confirm the account email or phone number before discussing records, so another person cannot obtain private account details.

Wallet record

If a DANA, OVO, GoPay or QRIS reference looks incorrect, send the transaction reference through account support. We check the payment status against the account record and separate wallet matching details from unrelated profile data.

Access concern

When a new phone or browser changes your sign-in path, contact support before sharing more personal data. We can review the account security event, confirm the phone verification step and help protect access where local law permits.

DATA CONTROL

What We Do With Account Data

We keep this policy practical: each data type has a reason connected to account access, payment matching, security or support.

Account details

We use the contact details you submit to create and protect your account, complete the phone verification step and respond to Privacy Policy requests. Keep these details current so we can distinguish your request from an unrelated account enquiry.

Payment references

A wallet name such as DANA or QRIS, together with a reference and status, can help us match an account action. We do not need your wallet password for that check, and you should never include it in a support message.

Cookies

Our browser cookies can support a continuing session and help connect your login to the correct account. You can clear or restrict them in your device browser; after that, you may need to complete login and phone checks again.

Security events

We may retain records of sign-in attempts, device changes and verification actions to investigate suspicious access. These records help us respond when your account opens on a different phone or desktop and are handled for account protection.

Retention period

We retain personal data while it supports your account, a payment reconciliation, a security investigation or a legal obligation. When the applicable purpose ends, we review the record for deletion, anonymisation or continued retention required by local law.

Your requests

You can ask what personal data we hold, request correction of inaccurate account details or ask about deletion where the law allows. Send the request through account support with enough detail for us to find the record without exposing your password.

Privacy Policy Answers for keris34d

These Privacy Policy answers focus on the account questions you are most likely to have before opening access. They explain the records connected with login, local wallets, cookies, security and contact requests without turning the policy into a general lobby description. If your situation is not covered, use the account support path and identify the request as a privacy matter.

It covers account details, phone verification, device and login records, cookie activity, payment references and support requests. The Privacy Policy explains why we use each category, how it helps protect account access and when retention may continue for security, reconciliation or legal needs.

Phone verification helps connect an account to the person completing the access step and helps us respond to unusual sign-ins. We use the result for account security and support checks, not as a public profile detail. Access remains where local law permits.

Yes. It covers the payment references and status details linked to an account action through DANA, OVO, GoPay or QRIS. We use those records to match an account step and investigate a receipt or status issue, without asking for your wallet password.

You can contact account support and ask about access to personal data or correction of inaccurate details. Include the account email or phone number and describe the record you mean. We may verify your identity first, then handle the request under applicable law.

Cookies can keep a browser session connected to the right account and remember settings during access. You can clear or restrict them in your phone or desktop browser. If cookies are disabled, login may require additional steps and some account functions may not continue.

Retention depends on the purpose: account operation, payment reconciliation, security investigation or a legal requirement. We review records when that purpose ends and may delete or anonymise them when permitted. Some records can remain longer where local law requires it.

Use the account support path and label your message as a Privacy Policy request. Tell us whether it concerns account details, a device event, cookies or a DANA, OVO, GoPay or QRIS reference. Do not send passwords, wallet credentials or full security codes.

Related Pages

keris34d Indonesia FAQ Register Super Sic Bo About Us