Reference

gps303 Privacy Policy For Your Account

Clear account records, wallet details and device choices are explained in the gps303 Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet recordsCookie choicesPrivacy requests
gps303 gps303 Privacy Policy For Your Account
PRIVACY HELP

Where To Send A Privacy Request

A direct request helps us locate the right account record without exposing private details in a public message. Contact our support route from the account area when you need to ask about stored data, a cookie choice, a phone verification record or a wallet transaction reference. Include the email or phone detail attached to your account, but never send a password or full payment credentials. We may ask for an account step to confirm that the request comes from you.

Team online

Account data request

Use the support path inside your account to ask what personal details we hold. We may confirm your phone verification step before discussing account data, so a private request is connected to the correct gps303 record.

Wallet record question

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference and date through support. We use that detail to locate the payment event without asking you to share a wallet password or complete card credentials.

Cookie or access issue

If a browser setting affects privacy choices or account access, tell us your device type and browser path. We can explain which cookie setting or login step is involved while keeping the request focused on your data.

DATA PRACTICE

How We Handle Account Privacy

Privacy controls work best when each record has a clear purpose. We separate account access details from payment references where our operating systems allow, restrict internal access to people who need it…

Account details

We use contact details and phone verification to create, protect and maintain your account. A clear account path helps us match a privacy request with your record, while the lobby choice, such as Live Baccarat or Super Bingo, is handled as account activity.

Payment references

DANA, OVO, GoPay and QRIS may provide a reference, amount and status connected with an account transaction. We use those details to reconcile receipts and investigate a wallet issue, rather than storing your wallet password or private wallet login.

Device signals

Your browser, operating system, language setting and login time can help us recognise a familiar device and investigate an access problem. We do not need your phone camera or contact list for the ordinary mobile path from login to the lobby.

Cookies

Cookies can retain a selected language, session state or privacy preference on your browser. You can clear them through browser settings, although removing session cookies may require you to complete phone verification again before account access.

Retention period

We retain account, support and transaction records for as long as they serve account operation, dispute handling, fraud checks or legal needs. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers.

Changes and questions

You can ask us to correct inaccurate contact details, explain a stored record or consider a deletion request through support. We assess the request against account protection and legal duties, then reply using the contact detail already attached to your account.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account, device and payment questions you may have before opening an account. We keep each answer tied to the actual data path: phone verification, wallet references, cookies, support requests and access from Indonesia. If your question concerns a specific record, use the support path while signed in so we can check the correct account.

The gps303 Privacy Policy explains that we may hold contact details, phone verification results, login events, device signals, cookie choices, support messages and transaction references. We use them to provide account access, investigate issues and meet operational or legal needs.

No. We may receive a transaction reference, status and related account details for DANA, OVO, GoPay or QRIS, but you should never send a wallet password through support. The payment provider manages its own account credentials and privacy practices.

Phone verification helps us connect an account request with the person seeking access. It can also help us handle a correction, data access or wallet-status question without exposing account details to someone using an unrelated phone number.

We may record browser type, operating system, language setting, login time and related device signals. These details help investigate unusual access and explain a mobile login problem. They do not require access to your phone camera or contact list.

Yes. Send a signed-in support request asking for access to a record or correction of inaccurate details. Include the account email or phone reference, and we may complete an identity check before discussing or changing private information.

We keep these records while they support account operation, receipt matching, dispute handling, fraud checks or legal duties. After the purpose ends, we remove or anonymise them where practical. A specific retention question can be sent through the account support path.

The policy is written for account and data activity connected with the Indonesia service path. Access or eligibility depends on local law, and the service is available where local law permits. Payment providers may apply additional privacy terms to their own records.