Reference

Open the suria33 Privacy Policy

The suria33 Privacy Policy shows what we collect when you open an account, sign in from a mobile device, or connect DANA, OVO, GoPay and QRIS.

Account recordsWallet referencesCookie choicesAccess requests
suria33 Open the suria33 Privacy Policy
HELP WITH RECORDS

Browse Your Privacy Support Path

A clear support route helps when your account record, cookie choice or wallet reference does not look right. Start from the signed-in account support panel so we can connect your request to the correct account step. If access is unavailable, use the support route shown on our brand home and include only the details needed to locate the issue. We handle policy questions about Indonesia access where local law permits.

Team online

Account support panel

Use the signed-in support panel for a copy request, correction request or question about the account data connected to your phone verification. We may ask you to confirm account details before discussing records, so another person cannot obtain your private account information.

Wallet status check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction date, amount and visible reference through the account support path. Do not send a wallet password or full banking login; we use the supplied reference to trace the status.

Access assistance

When you cannot reach the account panel, tell us the device type, sign-in step and message shown on screen. We use those details to separate a device cookie issue from an account verification issue before discussing any personal record.

DATA CONTROL ROOM

Switch Through suria33 Data Controls

We keep the Privacy Policy practical by linking each data practice to an account action you can recognise.

Account creation

When you open an account, we collect the details needed for account setup and phone verification. The verification step helps us match a request to the right account before we provide, correct or remove personal records under the Privacy Policy.

Device behaviour

Your mobile browser can send session, language, device and security signals when you move from login to the lobby. We use these signals to maintain access and investigate unusual sign-ins, not to request the private password for DANA, OVO or GoPay.

Cookie settings

Cookies can keep your session active and remember settings between account pages. You can manage browser permissions from your device settings, although turning some cookies off may interrupt sign-in or require you to confirm the account step again.

Payment references

For QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity, we retain the reference and status needed to reconcile your account record. We do not describe a wallet password as part of the payment reference handled by our support team.

Retention choices

We retain account, security and transaction records for as long as an operational or legal purpose requires. After that point, we remove, anonymise or restrict them through our retention process, subject to requests that depend on local law.

Change requests

You can ask for access, correction or deletion by using account support and stating the exact record involved. We may verify your phone or account details first, then explain what we can change and why a legal retention duty may prevent removal.

Ask About suria33 Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the account step, local wallet references, mobile access, cookies and requests for personal records without turning the policy into a general lobby description. If your situation is not covered, contact us through the account support path where local law permits.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support records and payment references. It explains why we use each category, how retention works and how you can request access, correction or deletion where local law permits.

Our policy concerns transaction references and status details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We do not ask you to send a wallet password through support. Share only the reference and account details needed to trace a payment record.

Open the signed-in account support panel and request access to your personal record. We may ask you to confirm the phone or account step linked to the request. After checking the request, we explain the available record and any restriction required by local law.

Yes. Use the account support path and identify the field that is wrong, such as a contact detail or verification status. We may confirm your account before making a change, then tell you whether the correction is completed or requires further checking.

Cookies can preserve your sign-in session and remember settings as you move from a mobile login to the lobby. You can manage them in your browser or device settings. If essential cookies are blocked, we may ask you to repeat verification before access continues.

We keep payment references and account records only while an operational, security or legal purpose requires them. This can include reconciling QRIS or bank transfer activity and resolving a support request. We then remove, anonymise or restrict the record under our retention process.

Use the signed-in account support panel whenever you can access it. If login stalls, follow the support route on our brand home and provide the device, account step and policy question. We handle requests according to applicable Indonesian requirements where local law permits.