Reference

sora89 Privacy Policy for Your Account

Our Privacy Policy explains what sora89 collects when you open an account, verify your phone, use DANA or QRIS, and contact support.

Clear collection rulesWallet record detailsAccess request pathIndonesia account context
sora89 sora89 Privacy Policy for Your Account
CONTACT YOUR WAY

Three Ways to Ask About Privacy

A direct request helps us locate the right account record without exposing details to the wrong person. Use the support link shown in your account area, include the email or phone connected to your account, and tell us whether your question concerns cookies, wallet records, phone verification or a personal-data request. We may ask for an account check before sharing anything.

Team online

Account support link

Open the support link from your signed-in account and describe the Privacy Policy question. Adding your registered phone number helps us match the request to the correct account record.

Payment record query

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate date. We use those details to locate status records without asking you to send a wallet password.

Data rights request

Ask for access, correction or deletion through the same support path. We confirm account ownership first, then explain the applicable retention period and any limits under local law.

SIX DATA CHECKS

What We Do With Your Personal Data

Privacy choices work best when each account step has a clear purpose. We separate sign-in details from payment references where practical, limit internal access to operational needs and retain records only for…

Account opening

When you create an account, we collect the details needed to establish access and send account messages. Phone verification helps us confirm that the requested account step belongs to you.

Wallet references

DANA, OVO, GoPay and QRIS may produce payment references or status details. We use them to match a request, not to request or store your wallet password.

Cookie controls

Cookies can remember a session and help us understand page errors. You can manage browser cookie settings, although disabling them may require another sign-in on your device.

Account security

We use account checks, session controls and limited staff access to reduce improper entry. Never send a password or one-time phone code through a support request.

Retention periods

We keep account and payment records for operational, dispute or legal needs, then remove or restrict them when the applicable retention period ends or a valid request applies.

Policy changes

If this Privacy Policy changes, we update the policy page and identify the revised section. Checking the page before opening a new account keeps your choices current.

Privacy Policy Questions for sora89

These answers address the questions we expect you to ask before opening an account or linking a local wallet. If your situation is unusual, use the account support path and include only the details needed to identify your request.

The sora89 Privacy Policy covers account details, phone verification, device sessions, cookies, payment references, support messages, retention and requests to access, correct or remove personal data.

No. Our Privacy Policy distinguishes wallet status and payment references from wallet credentials. Do not send a DANA, OVO, GoPay or QRIS password in a support message.

Phone verification helps connect an account request to the person controlling the registered number. It also supports account recovery and helps us check identity before sharing personal data.

Use the support link inside your signed-in account, state that you are making a Privacy Policy data request, and provide your registered phone or email for an ownership check.

Yes, where local law permits. Send a correction or deletion request through account support. We first confirm ownership and then explain records that must remain for legal or dispute purposes.

Yes. The Privacy Policy applies when you sign in from a phone, tablet or desktop. Device type, session details and cookie settings may differ, but the same data principles apply.

Yes. Access and eligibility depend on local law. Our Privacy Policy explains data handling for permitted access, while your location determines whether account access is available.