Reference

sonic88 Privacy Policy for Your Account Data

Our sonic88 Privacy Policy shows what we collect, why we use it, and how you can ask about your records before opening an account.

Clear data purposesWallet record contextCookie choicesAccount contact path

Explore Our Lobby Read FAQ

How Our Privacy Policy Applies Locally

sonic88 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details you provide when opening an account, completing phone verification, signing in, contacting support, or checking a wallet status. It also covers technical records created when your phone, tablet, or desktop browser reaches our pages, such as device type, session activity, and

1
cookie preferences. We use these details to maintain account access, investigate payment status, protect the account from unauthorised activity, and respond to policy requests. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references may appear in account records when you choose those routes. Access and
2
eligibility depends on local law, and this policy applies where local law permits. We may update the wording when our data practices change and will keep the current version available through the account area.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where to Ask About Privacy Policy

A clear contact route helps you act on the Privacy Policy instead of searching through unrelated account pages.

Policy questions Use the support link beside your account controls to ask how we collect, use, store, or disclose a particular data field. Include the page section or request type so our team can route the question without asking you to repeat unrelated account details.

Account access If phone verification or login prevents you from reaching the Privacy Policy, tell us the account phone detail and device path you used, such as mobile browser or desktop browser. Never send your password, one-time code, or wallet PIN in the request.

Wallet records For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record, use the cashier support path and provide the transaction reference only. We can separate a payment-status check from a request to correct or remove personal data.

SECURITY PRACTICE

What We Do With Your Account Records

Privacy depends on clear handling after the account is opened, not only on a page you read once.

Account data

We use registration details and phone verification records to create and maintain your account access. We do not ask you to place a password, one-time code, or wallet PIN into a support message when you contact us about this policy.

Cookie controls

Cookies and similar browser records can help us keep a session working and understand basic page use. Your device may show cookie controls through its browser settings, while the policy explains the purpose connected to each category we use.

Security checks

We may compare account activity, phone verification, device behaviour, and wallet references when checking unusual access. These checks help us investigate a login or payment-status concern without treating a support message as proof of account ownership by itself.

Retention periods

We keep records only for the purposes and periods described in the Privacy Policy, including account administration, security review, payment reconciliation, and legal requests. When a stated purpose ends, the relevant record is handled according to our retention process.

Request changes

You can ask us to correct an inaccurate account detail, explain a data use, or clarify a retention point through the account support route. We may request account identifiers to confirm the request before changing a record.

Policy updates

When our data practice changes, we revise the Privacy Policy and keep the current wording accessible from the account area. Check the page before connecting a local wallet or completing a new phone-verification step.

Privacy Policy Questions Before Account Access

These answers address the searches we hear most often before an Indonesian account is opened or a wallet is connected. They explain the practical route for checking records, changing details, handling cookies, and asking about access. If your case involves a specific DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference, use the support path described above so we can match the request accurately.

The sonic88 Privacy Policy covers registration details, phone verification, login activity, device and browser records, cookies, support messages, and wallet-related references. It explains why we use each category, how retention is handled, and how you can ask for clarification or a correction.

Phone verification helps connect an account request with the person trying to access it and supports account-security checks. The Privacy Policy explains how verification records are used. Do not place a one-time code or wallet PIN in a support request.

Yes. When you use DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account, related references may form part of account and payment-status records. The policy explains the purpose of those records and the route for asking about a specific reference.

Open the support link from your account area and state which detail is inaccurate, such as a phone number or account record. Include an account identifier for verification, but never send your password, one-time code, or wallet PIN with the request.

Yes. Contact us through the account support route and name the cookie category or browser path you want clarified. Your phone, tablet, or desktop browser also provides cookie controls, while the Privacy Policy describes the purpose of cookies used on our pages.

Retention depends on the purpose described in the Privacy Policy, including account administration, security checks, payment reconciliation, and legal requests. We do not assign one period to every record. Ask support about a particular category and we will explain the applicable handling.

Yes. Account access and eligibility depends on local law, and our services are presented where local law permits. You can read the policy from the account area or contact support to ask how a local access condition affects a data request.

sonic88 Privacy Policy for Your Account Data

Where to Ask About Privacy Policy

What We Do With Your Account Records

Account data

Cookie controls

Security checks

Retention periods

Request changes

Policy updates

Privacy Policy Questions Before Account Access

01 What does the sonic88 Privacy Policy cover?

02 Why does sonic88 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a correction to my sonic88 data?

05 Can I ask sonic88 to explain its cookie use?

06 How long does sonic88 keep personal data?

07 Does access to this Privacy Policy depend on local law?

Related Pages