Reference

Privacy Policy For Your api33 Account

api33 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, browse Live Blackjack Grand, or check DANA and QRIS…

Account clarityWallet recordsCookie choicesContact path
api33 Privacy Policy For Your api33 Account
HELP WITH PRIVACY

Get Direct Answers About Your Data

A clear contact route matters when your account or wallet record does not look right.

Account help Use the account support path when your phone verification, login record, or personal details…
Wallet questions For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the payment…
Privacy requests Ask through our support contact for a copy, correction, deletion question, or explanation of…
DATA HANDLING

What We Do With Account And Device Data

Privacy Policy choices should match what happens during a real session. We use account and device signals to recognise sign-in patterns, protect the phone verification step, connect a…

Account records

We collect details you provide when opening an account, including contact data used for phone verification.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account action can create a reference, amount, timestamp, and status record.

Device signals

When you sign in from a mobile browser or desktop, we may process browser type, device signals, session time, and…

Cookies

Cookies can retain a session choice, support security, and show whether a page works after a change.

Retention decisions

We keep data only for the account, security, support, or transaction purpose that requires it, subject to applicable local rules.

Changes and access

You can ask what personal data we hold, request a correction, ask about deletion, or question a processing purpose through…

Privacy Policy Answers For api33

These Privacy Policy answers focus on the requests we expect from an Indonesian account holder. They explain the account step, wallet records, device behaviour, cookie controls, and contact process in plain language. If your situation is different, send the details through support rather than sharing personal data in an open channel. We will apply the policy that fits your request and location.

The api33 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains your options to ask about access, correction, deletion, and retention.

We use your phone number for the verification step before account access and for account-related support. It helps us distinguish your request from another person’s request. We do not need your wallet PIN or password in a support message, and we verify ownership before changing account details.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use those records to match a transaction with your account, check a receipt, and address a status question without requesting private wallet credentials.

Use the api33 support route and state whether you want access to your data or a correction. Include the account contact used for phone verification, but do not send a password or wallet PIN. We confirm identity first, then explain the next step and any local-law restriction.

Cookies can keep a session choice, support account security, and help us see whether pages work on a mobile browser. Your browser settings can remove or restrict them. If you block necessary cookies, you may need to sign in again or some account functions may not load correctly.

We keep personal data for the account, security, support, or transaction purpose that calls for it, subject to applicable local rules. Payment and security records may need to remain after an account request is made. If we cannot delete a record, we explain the reason through support.

You can ask through support about deletion of personal data connected with your account. We verify the request before acting and check whether a payment, security, or legal record must remain. Eligibility and access depend on local law, so we explain which part can be removed and why.