Reference

sydneycuan Privacy Policy for Indonesian Wallet Access

Our Privacy Policy explains how we handle the account details, device signals and payment records connected with DANA, OVO, GoPay and QRIS.

Account recordsWallet referencesDevice choicesCookie controls
sydneycuan sydneycuan Privacy Policy for Indonesian Wallet Access
CONTACT ROUTES

Where to ask about privacy and wallets

A direct privacy question should reach the same support route that helps with account access or a stalled wallet status. Include your account identifier, the affected payment rail and the date shown on your receipt, but never send a password or full wallet credentials. Our team can then separate a DANA, OVO, GoPay or QRIS record from the account details used for verification.

Team online

Privacy contact

Send a request through the privacy contact route shown on our site. Tell us whether your question concerns account data, cookies, device records or a DANA, OVO, GoPay or QRIS transaction reference.

Account access help

If phone verification blocks account access, contact support from the sign-in path and state that your request concerns the Privacy Policy. We will ask for limited details to locate the correct account record.

Wallet status check

For a payment receipt or status question, provide the rail used, such as QRIS or bank transfer, plus the visible reference. We use that narrow trail to investigate without requesting your wallet password.

DATA PRACTICE

How account data stays under your control

We keep the Privacy Policy practical by separating identity, session and payment records wherever the account process allows.

Account details

We use the details entered during account opening and phone verification to create the correct account record, answer access requests and connect your support question with the right sign-in history.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are handled as transaction references and status evidence, helping us reconcile activity without storing your wallet password.

Device signals

A mobile browser or desktop session may create device, browser and timing signals. We use these signals for session protection and account checks, not as a substitute for your phone verification.

Cookie choices

Cookies can keep a session active, remember a selected setting and support security checks. You can adjust cookie behaviour in your browser, although changing it may require another account sign-in.

Retention timing

We retain each record for the period needed for its stated purpose, account security, payment reconciliation or a legal requirement. A privacy request can ask which category applies to your record.

Change requests

To request access, correction or removal, use our privacy contact route and describe the record concerned. We may verify your phone or account step before changing information linked to you.

Privacy Policy answers for your account

These Privacy Policy answers address the records most often connected with an Indonesian account: phone verification, wallet references, cookies, device access and contact requests. If your situation is not covered, send the question through our privacy contact route with only the details needed to locate your record.

It covers account and phone-verification details, device and session signals, cookie settings, support messages, and payment references created through DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps us confirm that an account access request belongs to you and helps prevent an unrelated person from changing account records or requesting details through the privacy contact route.

Yes. The Privacy Policy covers QRIS, DANA, OVO and GoPay references, along with bank transfer and virtual account status details used to reconcile account activity without requesting your wallet password.

A mobile browser or desktop may provide device type, browser details, session timing and security events. We use these signals for session protection and account checks connected with your sign-in.

Yes. Use our privacy contact route, identify the account record or payment reference involved, and request access or correction. We may verify your phone or account step before responding.

Retention varies by record type and purpose. Account security, payment reconciliation and legal requirements can affect timing; our privacy contact route can explain the category linked to your request.

Your location does not change the data categories described here, but account access depends on local law. If access or eligibility is unclear, contact us before sharing extra account or wallet details.