Reference

gapurabola Privacy Policy for Your Account

Speed Blackjack, Aviator and QRIS wallet access all sit behind an account flow where your personal data needs clear handling.

Account dataWallet recordsCookie choicesAccess requests
gapurabola gapurabola Privacy Policy for Your Account
CONTACT ROUTES

Check Your Privacy Questions Through Support

A clear support path helps when your account details, wallet record or access request needs attention. Start from the support link inside your signed-in account and include the email or phone number connected to your profile. For a payment question, attach the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference without sending your password or full authentication code.

Team online

Privacy request

Ask for a copy, correction or deletion of eligible personal data through the account support path. We may request account details to confirm that the request comes from you.

Wallet record

If a payment reference appears incorrectly, send the date, rail name and visible reference number. We use those details to locate the record without asking for your wallet password.

Login concern

For an unfamiliar sign-in or device change, contact support from your account route and change your password. Do not share one-time codes while we check the account trail.

DATA PRACTICES

Browse How gapurabola Handles Personal Data

We keep the Privacy Policy practical by connecting each data use to an account action you recognise.

Account details

We may collect your contact details and verification information when you open an account. These details help us connect you to the correct profile and respond to account requests.

Payment references

DANA, OVO, GoPay and QRIS records can include a reference, amount and status needed to match activity. Bank transfer and virtual account records follow the same account-linked purpose.

Cookies

Cookies can keep sign-in choices and page settings available on your browser. The Privacy Policy explains their purpose and how you can adjust available cookie controls.

Account security

We use sign-in and device signals to help protect your profile. A request about an unfamiliar device may require identity checks before account details are changed.

Data retention

We retain records only for the periods described in the Privacy Policy, including time needed for account administration, payment reconciliation or a legal requirement.

Change requests

You can ask us to correct, access or delete eligible data through support. We explain any limits, verify the requester and reply using the contact route tied to your account.

Find Privacy Policy Answers Before Joining

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep the wording tied to actual steps, from phone verification and mobile sign-in to payment references and requests sent through support. Where a right or access condition varies, the applicable rule depends on local law.

It covers personal data used for account creation, phone verification, sign-in, support, cookies, device access and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account.

Phone verification helps connect account access to the correct person and supports checks when a device or login changes. The Privacy Policy explains how related contact details are used and retained.

Yes. It covers data collected when you sign in from a mobile browser or desktop, including account signals, cookies and device details used to maintain access and identify unusual activity.

We use payment references, status and related account details to match a DANA or QRIS transaction with your wallet activity. The policy describes retention and permitted disclosures for these records.

You can send an access request through the signed-in support route. We may verify your identity before responding, and the scope or timing of the request depends on local law.

Contact support with the account detail that needs correction and the reason it is inaccurate. We may ask for confirming information before updating the profile or explaining why a limit applies.

Use the privacy request path connected to your account and state which data you want removed. We assess the request against retention duties and explain the outcome where local law permits.