Reference

32zk Privacy Policy for Your Account Data

The 32zk Privacy Policy gives you a direct view of the data we collect, why we use it and how you can ask for changes.

Account dataWallet recordsCookie choicesRequest support

How Our Policy Covers Wallet Records

32zk Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy explains the account data needed to create and secure your profile, including contact details, phone verification results and sign-in activity. It also describes records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps, such as a reference, amount and status

1
supplied during a payment action. We use these records to match your account activity, investigate a stalled receipt and protect the cashier path from misuse. A mobile browser may store session and cookie data differently from a desktop browser, so we describe both access paths in
2
our policy. You can ask us about a particular record through the support route in your account. Account availability and any related processing depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP DIRECTLY

Get Help With Privacy Requests

A clear contact path matters when you want to see, correct or question account data. Start from the support link connected to your account and tell us whether your request concerns phone…

Account privacy route Use the support path attached to your account when you want to ask about phone verification, sign-in records or a correction. We check ownership before sharing account-specific details.

Wallet record request Mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account when a payment record is part of your question. This helps us locate the relevant reference and status.

Cookie assistance If a mobile browser or desktop browser keeps a session longer than expected, contact us through your account support route. We can explain the cookie setting connected with that access.

CONTROL YOUR RECORDS

Security Choices Behind Your Account

We keep this policy practical by separating account security, payment tracing and cookie behaviour. Phone verification helps us confirm the account step before access, while sign-in and device signals help identify unusual…

Collection purpose

We collect account and device data for stated reasons such as phone verification, sign-in protection, payment receipt matching and support replies. The Privacy Policy connects each record type with its purpose.

Cookie controls

Cookies can keep a signed-in session and remember browser choices. Our policy explains their role on mobile and desktop paths, so you can decide which browser settings suit your access.

Account security

Phone verification and sign-in checks help us protect your account from unauthorised access. If a device behaves unexpectedly, use the account support route before changing profile details.

Wallet matching

A DANA, OVO, GoPay or QRIS reference may be connected with your account record to resolve a receipt or status question. Bank transfer and virtual account records follow the same stated purpose.

Retention period

We keep personal records for the time needed to provide the stated account service, protect the account or meet a legal requirement. Ask support which retention rule applies to your request.

Change requests

You can ask us to correct account data or clarify how it is used through the support path in your account. Include the relevant account step so we can respond accurately.

Privacy Policy Answers Before Account Access

These Privacy Policy answers focus on the questions we expect before you open an account or connect a local wallet. They cover collection, access, correction, cookies, retention and contact steps without turning the page into a general lobby description. If your question involves eligibility or access, the answer remains subject to local law.

The 32zk Privacy Policy covers account details, phone verification, sign-in activity, device and cookie records, wallet references, support requests and retention. It also explains how to ask about or correct a record.

Phone verification helps us confirm that an account request belongs to you and supports account security. We record the verification result for that purpose, subject to the Privacy Policy and local law.

Yes. The Privacy Policy includes payment references and status records connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account steps when those records reach your account.

Use the support link connected to your account and request a data access explanation. Include the account step or wallet reference involved; we may confirm ownership before discussing account-specific records.

You can ask for a correction through the account support route. Tell us which detail is inaccurate and provide the relevant verification context, so we can check the record before making a change.

Cookies may keep your session active and remember browser choices. The Privacy Policy explains their purpose on mobile and desktop paths; your browser controls can manage or remove them.

We retain records for the stated account, security, support or legal purpose, then handle them under the applicable retention rule. Ask through support if you need the rule for a specific record.

32zk Privacy Policy for Your Account Data

Get Help With Privacy Requests

Security Choices Behind Your Account

Collection purpose

Cookie controls

Account security

Wallet matching

Retention period

Change requests

Privacy Policy Answers Before Account Access

01 What does the 32zk Privacy Policy cover?

02 Why does 32zk need phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 How can I ask what data 32zk holds?

05 Can I request a correction to my account data?

06 How do cookies work on a mobile browser?

07 How long does 32zk keep personal records?

Related Pages