Reference

api33 Privacy Policy for Your Account

The api33 Privacy Policy explains what we collect when you open an account, sign in, check DANA or QRIS status, and contact our support route.

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How Wallet Records Fit This Policy

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

Our Privacy Policy covers details you provide during account creation, including your contact details and phone verification step, plus technical records created when you sign in from a mobile browser. It also explains how we handle payment references from DANA, OVO, GoPay, QRIS, bank transfer and

1
virtual account activity. A receipt or status check can be connected to your account so we can respond to a wallet query. We use data only for stated account, security, support and legal purposes, and access to api33 depends on local law. Where local law permits,
2
you can ask us to explain, correct or remove eligible personal details through the support path.

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

CONTACT ROUTES

Get Privacy Help Near Wallet Support

A clear contact path matters when a Privacy Policy question concerns a login, phone verification or wallet record.

DATA PRACTICES

Account Security Across QRIS Access

We keep this Privacy Policy practical by linking each data practice to an account action you recognise.

Data we receive

We may receive account contact details, phone verification results, sign-in records, device signals and payment references. A game choice such as Live Baccarat or Bingo may also appear as activity linked to your account.

Cookies and devices

Cookies and similar device records help retain a sign-in session and identify unusual access. On a mobile browser, these records support the path from account entry to the lobby without revealing your password to support.

Account protection

Phone verification and account checks help us distinguish an authorised request from an unknown contact. Never place a password, wallet PIN or full security code in a support message.

Storage period

We retain account, security and payment-reference records only for the period needed for stated service, dispute, safety or legal purposes. When a record is no longer needed, our handling follows the applicable retention process.

Your changes

You can ask us to correct eligible contact details or request a copy of personal data through account support. We verify ownership first, then explain what can be changed under local requirements.

Policy updates

If this Privacy Policy changes, we will place the updated wording on this page and show the relevant date. Check it before opening the lobby, especially after changing your phone or wallet details.

Privacy Policy Answers for api33

These Privacy Policy answers address the searches we expect before account access: what data is collected, how wallet records are used, how cookies work and how to request a change. If your question involves a specific receipt, phone number or sign-in, use the account support route so we can check the relevant record.

It covers account details, phone verification, device and cookie records, payment references, support messages, security handling, retention and requests to access or correct eligible personal data.

Yes. The policy includes references connected to DANA, QRIS and other listed wallet or bank methods when those records are needed for account support, status checks, security or dispute handling.

Phone verification helps confirm account ownership before access or a privacy request is handled. It also helps us identify unusual sign-in activity without asking you to share a password.

Use the support route linked to your account and ask for a personal data access request. Include your account contact detail, then complete the ownership check before we respond.

You can request correction of eligible account details through support. State which detail is wrong, provide the account contact used at sign-in and complete any ownership check we require.

Cookies can retain a sign-in session and support security checks on your mobile browser. You can manage browser cookie settings, although changing them may affect account access or session continuity.

Yes, access depends on local law. Where local law permits, we handle eligible requests about account data, cookies, wallet references and corrections through the stated support path.

api33 Privacy Policy for Your Account

Get Privacy Help Near Wallet Support

Account Security Across QRIS Access

Data we receive

Cookies and devices

Account protection

Storage period

Your changes

Policy updates

Privacy Policy Answers for api33

01 What does the api33 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS records?

03 Why does api33 need phone verification data?

04 How can I request my personal data?

05 Can I ask api33 to correct account details?

06 How are cookies handled on a mobile browser?

07 Does access under this Privacy Policy depend on location?

Related Pages