Reference

Privacy Policy For Your satria66 Account

Our Privacy Policy explains what satria66 collects when you open an account, verify your phone, browse the lobby, or use DANA and QRIS.

Clear data purposesWallet record detailsDirect privacy requestsIndonesia access context
satria66 Privacy Policy For Your satria66 Account
CONTACT ROUTES

How To Ask About Privacy

A clear contact route helps you resolve a privacy question without repeating your account story. Start from the account help path and include the email or phone detail linked to your profile, plus the subject of your request. We use those details to locate the right record without asking you to send a wallet password or a full payment credential. If a wallet status stalls, separate the payment reference from your privacy request so both matters can be handled safely.

Team online

Account help path

Open the account help path when you need to ask what data we hold or why a phone verification record appears. Include your linked contact detail and request type; we may ask for an account check before discussing private records.

Wallet record query

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the transaction reference rather than wallet credentials. We can use the reference to locate a status entry and explain which payment data is retained.

Access or change request

Ask us to access, correct, or remove eligible personal data through the same account contact route. We verify that the request comes from you, explain any lawful restriction, and confirm the action taken on the relevant record.

DATA PRACTICE

How We Handle Your Account Data

Privacy work is tied to practical account controls, not a vague promise. We separate identity details from payment references where the process allows, limit internal access to the records needed for a…

Account data

We may collect your name or contact detail supplied during account creation, your phone verification result, sign-in events, and support correspondence. These records help us connect a request to the correct profile and prevent another person from receiving account data.

Payment references

A DANA, OVO, GoPay, or QRIS transaction can create a reference, amount status, and time record linked to your account. Bank transfer and virtual account entries may be kept for reconciliation, while wallet passwords and access codes should never be sent to us.

Cookies and devices

Cookies can keep a session active and remember selected settings, while device and browser signals help us detect unusual sign-in behaviour. You can clear or restrict cookies in your browser, although some account steps may then need to be repeated.

Account security

We use phone verification and account checks before exposing private details or processing a sensitive request. Keep your sign-in details private, sign out on shared devices, and contact account help if a device path or session looks unfamiliar.

Retention periods

We retain each category only for as long as its account, security, dispute, or legal purpose requires. Payment status records may remain after a session closes so an interrupted DANA, QRIS, or bank transfer question can be checked accurately.

Your requests

You can ask what personal data we hold, request a correction, or ask whether deletion is available. Send the request through account help with your linked contact detail; where local law permits, we explain the response and any reason a record must remain.

Privacy Policy Answers For Indonesia

These answers address the questions we expect you to ask before opening or using a satria66 account. They focus on account records, wallet references, cookies, device access, correction requests, and the local-law limits that can affect a response. If your situation is not covered, use the account help path and describe the specific record you want us to check.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references. It explains why we use each category, how we protect it, how long records may remain, and how you can ask about access or correction.

Phone verification helps connect account access to the contact detail you supplied and supports checks before private information is disclosed. We record the verification result rather than asking you to place a wallet password in a support message or privacy request.

Yes. The Privacy Policy covers transaction references and status details created when you use DANA or QRIS, along with OVO, GoPay, bank transfer, and virtual account records. These entries help us trace an interrupted status without requesting your wallet credentials.

You can ask for access to eligible personal data through the account help path. Include your linked email or phone detail and a clear request. We verify the requester first, then explain the records available and any restriction that depends on local law.

Send a correction request through account help and identify the specific field, such as a contact detail or account record. We may request an account check before changing it, then confirm the result or explain why a record cannot be altered.

We keep payment status and reference data for the period needed for account operation, security, dispute handling, or applicable requirements. A DANA, QRIS, or bank transfer entry may remain after the session closes so its history can be reconciled.

You may request deletion of eligible personal data through the account contact route. We assess the request against the record's purpose and applicable requirements. Where local law permits, we remove or limit eligible data and explain any information that must remain.