Reference

Privacy Policy For Your piket88 Account

Your piket88 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsMobile accessPolicy requests
piket88 Privacy Policy For Your piket88 Account
REQUEST HELP

Three Ways To Ask About Privacy

A clear contact route helps you question a record without guessing which account step caused it.

Account privacy request Use the account support path when you want to ask what personal details are…
Wallet record question For a DANA, OVO, GoPay or QRIS record, tell us the payment rail, reference…
Device access concern If a mobile browser session looks unfamiliar, contact our support route with the device…
SIX DATA PROMISES

What We Handle Behind The Policy

The Privacy Policy is useful when it matches the way an account actually works. We separate account identity, wallet references, device signals and support messages so a request can be checked against…

Account details

We may hold the phone number and login details you enter when creating or using an account. Phone verification can connect an access request to that account. Keep your login details private, and ask us to explain any account field whose purpose is unclear under this Privacy Policy.

Payment references

DANA, OVO, GoPay and QRIS can create transaction references, while bank transfer and virtual account steps can create matching records. We use those references to check status and account ownership; do not send a wallet PIN, card secret or password in a support message.

Cookies and sessions

Cookies and similar browser storage can keep a mobile session working and remember basic access choices. If you clear them, you may need to sign in and complete the account step again. Your browser settings can control some cookies, although certain sign-in functions may then change.

Account security

We use sign-in events, device signals and phone verification to help identify unusual account access. If you switch from a phone to a desktop browser, the new session may create a separate access record. Contact support promptly if the time or device shown does not match you.

Retention choices

We keep account, support and payment-reference records only for the period needed for account operation, security checks, dispute handling or legal duties. The exact period can depend on the record and local requirements. Our support route can explain which retention rule applies to your request.

Changes and contact

You can ask about a correction, access request or deletion question through the privacy support path. Include the account identifier and a precise request so we can check ownership before acting. We may need phone verification, and any response depends on local law and required records.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often from people in Indonesia. They cover what is collected, how a request is checked, what happens on a mobile browser, and how to contact us about a DANA, OVO, GoPay or QRIS record. Where a request concerns eligibility or access, the answer depends on local law.

The piket88 Privacy Policy covers account details, phone verification, login events, cookies, device signals, support messages and payment references. It explains how these records support account access, security and status checks for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use the phone number you provide to create or identify your account and to complete the clear phone verification step before account access. It can also help us check ownership when you ask about a record or request a correction under the Privacy Policy.

Yes. The Privacy Policy covers references connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account status checks. We use the reference and account details needed to trace an event, but you should never send a wallet PIN or password.

A mobile browser or desktop session may produce access time, browser and device signals used for session continuity and security checks. These details can help us spot an unfamiliar sign-in. Clearing cookies may require you to sign in and complete phone verification again.

Use our privacy support path and state whether you want access to a record or a correction. Include your account identifier, the relevant date and the precise field or event. We may confirm ownership through phone verification before responding, where local law permits.

Retention depends on the record, such as account details, a support message, a device event or a payment reference. We keep it for account operation, security, dispute handling or legal duties, then apply the relevant retention rule. Support can explain the category linked to your request.

Yes. Tell support whether the record concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, then provide its date and displayed status. We can check the matching account event without asking for your wallet credential, and any action depends on local law.