Reference

suaka999 Privacy Policy Explained Clearly

Our Privacy Policy shows how we collect, use and protect the details connected with your suaka999 account, including phone verification, device access and DANA or QRIS references.

Account dataWallet referencesDevice choicesContact requests
suaka999 suaka999 Privacy Policy Explained Clearly
HELP ROUTES

Browse Privacy Help From Your Account

A clear contact route matters when a privacy question sits beside a login or wallet record.

Data access request Use the account support path to ask which personal details are linked to your…
Wallet record query For a DANA, OVO, GoPay or QRIS reference, send the receipt number and date…
Correction request If your phone, email or account detail needs correction, tell us through the signed-in…
DATA PRACTICE

Switch On Clear Data Controls

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We may hold the phone number and other details you submit for account creation, phone verification and support replies. We use them for the stated account purpose rather than treating every field as open-ended data.

Device signals

Your browser, device type and connection details can appear in security records when you sign in. These signals help us compare a new session with normal account activity without exposing your wallet password.

Cookie choices

Cookies can keep sign-in continuity and remember policy-related settings on your browser. You can clear browser data, although doing so may require another account check when you return to the lobby.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account reference can be retained to match a receipt with an account action. We use the reference for checking, not as a wallet credential.

Retention checks

We retain records for the period needed for the original account, security or transaction purpose, subject to legal requirements. When a record is no longer needed, our handling follows the applicable removal process.

Your request path

Ask for access, correction or removal through the signed-in support route. We may verify account ownership first, then explain what can be changed and whether a legal or security reason requires continued retention.

Check Privacy Policy Answers Before Access

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the records connected with suaka999, wallet references, browser behaviour, account checks and requests for changes. If your situation is not listed, use the account support route and describe the specific record you want us to locate.

It covers how we handle account details, phone verification, device and browser signals, cookies, payment references and support requests connected with your suaka999 account in Indonesia.

Yes. The Privacy Policy explains that DANA, QRIS, OVO, GoPay, bank transfer and virtual account references may be used to match a receipt or account action.

Device type, browser and connection details help us compare sign-in activity, investigate an unfamiliar session and protect account access. They are handled as security signals, not wallet passwords.

Use the signed-in support route and ask for a data access request. We may verify account ownership before explaining which personal details are linked to your phone and account record.

You can request correction of an account detail such as a phone or email record through support. We check the request against account information before applying an approved change.

Retention depends on the purpose of the record, account activity and applicable legal requirements. We keep information only for the period needed for account, security or transaction handling.

You may request removal through the account support path where local law permits. We first verify the request and explain if a security or legal requirement means some record must remain.