Reference

rtp800 Privacy Policy for Your Account

rtp800 Privacy Policy explains how we collect, use and protect the details connected with your account, device and payment activity.

Account clarityCookie choicesPayment recordsChange requests
Explore Our Lobby Read FAQ
rtp800 rtp800 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Help Without Guesswork

A clear contact path helps when you want to ask about a stored detail, correct an account record or question a payment reference. Start from the support route connected to your rtp800 account and include the phone number or account identifier used during verification; do not include a wallet PIN. We can then match your request with the relevant sign-in, cashier or cookie record. If you are in Yogyakarta, the same process applies when access is available where local law permits.

Team online

Account request

Use the account support path for a copy, correction or deletion request. Include your verified phone detail and the subject of the Privacy Policy question so we can locate the correct record without asking for your DANA, OVO, GoPay or QRIS PIN.

Payment query

For a receipt or wallet-status question, send the transaction reference rather than card or wallet credentials. Our support team can connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference to the relevant account record.

Security concern

If a sign-in, phone-verification or device event looks unfamiliar, contact us through the account support route promptly. We may ask you to confirm account ownership, but we will not ask for your wallet PIN or sign-in password in that request.

HANDLING YOUR DATA

How We Apply This Privacy Policy

We apply this Privacy Policy to practical account events rather than treating every visit alike.

Account details

We use your phone and account details to create the requested account, complete phone verification and help restore access. Keeping these details accurate lets us connect a support request to the right account without exposing another person’s records.

Device signals

When you sign in from a phone, tablet or desktop browser, we may record device, browser and security signals. These help us recognise unusual access and protect the account; they are not a request for your device passcode.

Cookies

Cookies and similar storage can keep a session working, remember selected settings and help us understand which page was requested. You can manage browser cookie controls, although switching them off may interrupt sign-in or the route back to the lobby.

Payment records

For DANA, OVO, GoPay and QRIS, we handle the account-linked reference and status needed to match a transaction. Bank transfer and virtual account records serve the same purpose; we do not need your wallet PIN to check a receipt.

Security controls

Phone verification, sign-in checks and restricted support handling help protect account data. If you switch from mobile to desktop, these checks may appear again when the device or session differs from the earlier account path.

Retention requests

We retain account, security and transaction records only for service needs, dispute handling or legal duties that apply to the request. Ask us to correct, export or remove eligible data through support, and we will explain any lawful reason a record must remain.

Privacy Policy Answers for rtp800

These Privacy Policy answers address the account and device questions most often raised before phone verification or a wallet transaction. We keep the wording practical so you know what to send, what we may retain and how local access affects a request. If your case involves a specific record, use the account support route with the relevant reference.

The rtp800 Privacy Policy covers account and phone-verification details, sign-in and device signals, cookie storage, support messages and payment references. It also explains why we use those records, how long they may remain and how you can request a copy, correction or eligible removal.

No. Our Privacy Policy distinguishes a transaction reference or status from a wallet secret. When you use DANA, OVO, GoPay or QRIS, send only the reference needed for a receipt or status question. Never place a wallet PIN in a support message.

Use the account support path linked to your verified account and ask for a data copy under the Privacy Policy. Include the phone detail or account identifier used during verification. We may confirm ownership before responding so another person cannot obtain your account records.

Yes. Send a correction request through account support and identify the exact field that is wrong. We may ask for a verification step before changing phone or account details. Payment references remain tied to the transaction record so status checks remain accurate.

On a mobile browser, cookies or similar storage can keep your session and selected settings available between pages. You can adjust browser controls, but disabling required storage may interrupt phone verification, sign-in or the return path from a payment page.

We keep payment, account and security records for as long as needed to operate the requested service, handle disputes or meet applicable legal duties. The exact period can depend on the record and jurisdiction. You can ask support why a particular record remains.

The Privacy Policy applies to the services we make available, but account access and eligibility depends on local law. Where local law permits, you can use the account path and contact support about your data. We will explain if a local rule changes the response.

Related Pages

rtp800 Indonesia Account information Flores Fortune Megaways About Us Liga 1 Handicap Odds