Reference

wakanda33 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a wakanda33 account, how we use details linked to DANA, OVO, GoPay or QRIS, and how you can…

Account dataWallet recordsCookie choicesPrivacy requests
wakanda33 wakanda33 Privacy Policy for Your Account
PRIVACY HELP PATH

Ask About Account Data Directly

A clear contact path helps when a privacy question sits beside an account or wallet issue. Open the support link shown near the account and cashier areas, then include your registered phone detail and the subject of your request without sending a password or wallet PIN. We use the account reference to locate the right record and keep the conversation focused.

Team online

Account questions

Ask us which account details are held, why phone verification appears in your record, and what step is needed to correct a spelling or contact detail.

Wallet records

For DANA, OVO, GoPay or QRIS questions, send the payment reference and status shown in your account. We can check the record without asking for your wallet PIN.

Privacy requests

Use the privacy contact path to request a copy, correction or removal review. We may ask for account verification before discussing personal data connected with your wakanda33 access.

DATA CONTROL POINTS

How wakanda33 Handles Your Records

We separate account access, payment matching and privacy requests so each question reaches the relevant record.

Collection

We collect details you enter for account opening and phone verification, plus technical signals such as browser type, device path, login time and session events needed for account operation.

Cookies

Cookies help remember session choices and measure whether a login route works correctly. You can manage cookie behaviour in your browser, though some account functions may then need another sign-in.

Account security

Keep your password and phone verification code private. We use account checks when a request concerns personal data, and we do not ask for a DANA, OVO or GoPay PIN.

Payment matching

A payment reference, rail name and status can be linked to your account when you use QRIS, bank transfer or a virtual account. This supports receipt checks without storing wallet secrets.

Retention

We keep account, device and payment records for the operational, security or legal period that applies to the request. When that need ends, records are removed or anonymised.

Change requests

You can ask us to correct personal details, explain a record, provide a copy where available or review removal. We may retain limited evidence where local law permits.

Privacy Policy Questions for Indonesia

These answers cover the searches we hear most often about account records, wallet references, cookies and personal-data requests. If your situation is not listed, use the privacy contact path and include only the details needed to identify your account.

The wakanda33 Privacy Policy covers account details, phone verification, device and cookie signals, payment references, security checks, retention practices and requests to access, correct or remove personal data.

We may store the payment rail, reference, status and matching time for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN for a record check.

Yes. The Privacy Policy applies when you use a mobile browser or desktop browser, including login events, cookie choices and device signals created while moving from account access to the lobby.

Use the privacy contact path beside the account area and request a data copy. Include your registered phone detail or account reference, but never include your password, verification code or wallet PIN.

Yes. Send a correction request through support with the account detail that needs changing and the accurate version. We may verify your account first, then explain whether the requested change can be made.

Retention depends on the operational, security or legal reason for keeping a record. We review account and payment information for that purpose, then remove or anonymise it when the need ends.

Use the privacy contact route linked near account support and provide a short description of the concern. We will direct it to the relevant data-handling team and may request account verification.