Reference

sga505 Privacy Policy for Indonesia

sga505 Privacy Policy explains how we handle the details you provide when you open an account, sign in from a phone, or check wallet activity through DANA, OVO…

Account clarityWallet recordsCookie choicesRequest support
sga505 sga505 Privacy Policy for Indonesia
REQUEST ROUTES

Privacy Policy Help From Your Account Path

A clear contact route matters when you want to ask about Privacy Policy handling rather than a lobby feature. We can direct a request to the account path that matches your sign-in details, wallet status or cookie question. Include the phone number connected to your account and a short description of the request, but do not send a password or one-time verification code. When your question concerns a DANA, OVO, GoPay or QRIS receipt, keep the reference visible so we can check the correct record. For account safety, we may ask you to complete a verification step before discussing personal data.

Team online

Account privacy request

Use the account support path to ask what personal details are connected to your sign-in. We may confirm your phone verification before discussing the record, helping us avoid sending account data to the wrong person.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt needs clarification, share its reference through the support path beside the cashier area. We use that reference to locate the relevant transaction status without requesting your password.

Cookie choice support

Ask us how browser cookies affect your session on a phone or desktop. We can explain the cookie category involved and record a request to change optional settings where that control is available.

HANDLING DETAILS

What Our Privacy Policy Explains

The practical value of this Privacy Policy is that it connects each data use to an account action you recognise.

Account data

We may handle the account details you submit, including contact details used for phone verification. This supports sign-in, account recovery and requests about your own record. We do not need your password in a support message, and you should keep it private.

Payment references

A DANA, OVO, GoPay or QRIS transaction can produce a reference, amount status or timestamp connected with your account activity. We use those fields to check a receipt or status question, while the relevant wallet provider may apply its own data terms.

Cookies and sessions

Cookies and similar browser storage can remember session details so your phone or desktop browser can keep the correct account path. We distinguish necessary session functions from optional measurement settings and explain how to ask about a cookie connected with your visit.

Security checks

Phone verification and sign-in checks help us reduce mistaken access to an account. We may review device or session signals when a login appears unusual, then ask for an account step before releasing personal details. Never share a one-time code with support.

Retention period

We retain account and transaction records only for the operational, legal or dispute-handling period that applies to the record. A request to remove data may be limited when a record is needed for a payment status check, account safety or a legal duty.

Changes and contact

You can contact us through the account support route to request access, correction, clarification or a change to optional cookie settings. Tell us which record you mean, such as a phone detail or QRIS receipt, so we can assess the request accurately.

Privacy Policy Answers for sga505

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. They cover what we collect, why a verification step can appear, how cookies work on mobile, and how to contact us about a personal record. The policy applies where local law permits, and access depends on local law.

The sga505 Privacy Policy covers account details, phone verification, sign-in and device sessions, cookies, wallet references, security checks, retention and requests about your personal record. It explains why we handle each category and how to contact us when you need access, correction or clarification.

We collect the details needed for the account path, including contact data used for phone verification and records created by sign-in or account activity. If you use DANA, OVO, GoPay or QRIS, a payment reference or status may also connect to your account.

Phone verification helps us confirm that the person requesting account access or account data has the correct contact detail. It can also support recovery and security checks. We will not ask you to place a password or one-time code in a support message.

Our Privacy Policy treats DANA and QRIS references as transaction-related records used to match a receipt, status question or account activity. We may use a reference and timestamp for that check. DANA and QRIS may separately apply their own privacy terms to data they handle.

Yes, contact us through the account support path and identify the record you want to access or correct, such as a phone detail or wallet reference. We may complete an account verification step first, then assess the request under applicable local requirements.

Necessary cookies can keep your sign-in and account path connected as you move between pages on a phone or desktop browser. Optional cookies may support measurement or preferences. Ask support which category applies to your session and request a change where available.

We keep records for the period needed for account operation, security, payment status checks, disputes or applicable legal duties. The period can differ by record type. If you request removal, we assess whether a remaining retention requirement prevents immediate deletion.