Reference

Open the draja77 Privacy Policy

The draja77 Privacy Policy explains what we collect when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextAccount access choices
draja77 Open the draja77 Privacy Policy
CONTACT THE TEAM

Ask about privacy beside your account

A direct privacy question should not require you to search through the lobby. Use the support path connected to your account area and include the email or phone detail used during registration, without sending a password or one-time code. We can then locate the relevant request, explain a wallet record or device entry, and tell you which verification step is needed. If you are in Bandung or elsewhere in Indonesia, the same account-based route applies where local law permits.

Team online

Privacy request

Send a request through the account support path when you want to ask what personal data we hold or why a particular record appears. Include your registered contact detail and the subject of the request; we use that information to match the enquiry safely.

Wallet records

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, contact us from the account area and identify the date and payment rail. We can check the linked status and explain the record without asking you to disclose a password, PIN or one-time code.

Access assistance

When login or phone verification stalls, use the support route beside your account controls. We may ask for an account detail or device confirmation before discussing private data, because the Privacy Policy requires us to protect the account holder from unauthorised disclosure.

DATA HANDLING

Check how we protect your records

Privacy works best when each account action has a clear reason and a limited data path.

Account details

We use the contact information you provide during account opening to support sign-in, phone verification and privacy requests.

Payment references

A payment rail can leave a reference, status or receipt record connected with your account.

Cookies and devices

Cookies and device signals can help keep a session working between login and the lobby, including when you switch from…

Security checks

We may compare account details, phone verification and device activity when access looks unusual.

Retention choices

We keep records only for the period needed for account operation, security, support handling and applicable legal duties.

Change request

To correct a name, phone detail or other account field, contact support from the registered route and describe the change…

Find answers about this Privacy Policy

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover collection, cookies, wallet records, access requests and account closure without turning the page into a general lobby description. If your question is not listed, use the support route connected to your registered account and ask us to review the specific record.

It covers personal data linked to account opening, sign-in, phone verification, device sessions, support messages and payment references. It also explains cookies, security checks, retention and your request rights. Game activity such as Live Baccarat Turbo matters only where it creates an account or session record.

We use your phone number for account identification, verification and access support. It helps us connect a privacy request to the correct account and reduce unauthorised disclosure. If the number changes, contact us through the registered support path so we can explain the verification step.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references connected to your account, along with bank transfer and virtual account status where used. These records help us match a payment event and investigate a receipt or status question without requesting your wallet PIN.

You can ask us to identify the personal data connected to your account and explain its purpose. Send the request through account support using your registered contact detail. We may verify ownership first, and some security or operational records may remain when retention is required.

Describe the inaccurate field, such as a phone number or account name, through the registered support route. We will check that you control the account before making a change. After assessment, we confirm the correction or explain why another verification step is needed.

Your browser settings can restrict or remove cookies, and you can use the Privacy Policy to understand their purpose. Some cookies support session continuity and security between login and the lobby. Restricting them may interrupt sign-in, verification or the return to an active session.

We stop using the account for ordinary access after closure, but selected records may remain for security, support history, payment matching or applicable legal duties. If you request closure or deletion, we explain which data can be removed and which records need a defined retention period.