Reference

score088 Privacy Policy For Your Account

score088 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet recordsDevice privacyCookie choices
score088 score088 Privacy Policy For Your Account
CONTACT PATH

Ask Us About Privacy Policy

A clear support path helps you ask what data we hold or why an account check is needed.

Account data request Use the account help path to ask for a copy of personal data linked…
Wallet record question For a payment privacy question, name the rail involved, such as QRIS, DANA, OVO…
Correction request If your contact detail or account record is inaccurate, tell us which field needs…
HANDLING DETAILS

How score088 Handles Personal Data

We keep privacy work tied to practical account operations rather than collecting details without a purpose.

Account details

We use your submitted contact details to create and maintain the account, complete phone verification and respond to requests. We do not ask you to place a wallet PIN or account password in a support message, because those secrets should remain private.

Device signals

When you move between a mobile browser and desktop, we may record device and connection signals linked to sign-in security. These signals help us examine unusual access without treating the device itself as your identity or reading unrelated files.

Cookies

Cookies can keep an account session active and help us understand which policy page brought your question forward. You can adjust cookie settings in your browser; clearing them may sign you out and require phone verification again.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with account activity so we can match a receipt and resolve a status question. We do not need your wallet PIN to perform that check.

Retention review

We keep personal records only while they serve account access, security, support or a legal requirement. When a purpose ends, we assess whether the record can be removed, anonymised or retained for a documented reason.

Your request

You can ask what personal data is held, request a correction, or ask whether deletion is available under applicable rules. Send the request through account support with enough detail to find your profile, and we will use a verification step where needed.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions you may have before opening access. We keep the wording practical: what we collect, how a device is recognised, what a payment reference means and how you can contact us. If your situation is not covered, use the support route above and do not send secret credentials.

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

Our Privacy Policy does not require you to send a DANA, OVO, GoPay or QRIS PIN to us. We may keep a payment reference, selected rail, amount status and account link needed to match a receipt or answer a wallet query.

Phone verification connects an account with the contact detail you submitted and helps us respond to the correct account holder. The Privacy Policy treats that verification record as account data, and a new-device sign-in may require an additional security check.

On a mobile browser, cookies can preserve a session and remember the path back to account help. You can clear or restrict them through browser settings. The Privacy Policy explains that doing so may sign you out and require verification during the next access.

Yes, you can ask for the personal data connected with your account through the support path. Include your account email or phone detail, but not a password or PIN. We may verify your identity before sharing records, and availability depends on local law.

Send a correction request through account support and identify the field that is wrong, such as a contact detail. We may complete phone verification before changing it, then confirm the result in the same support conversation.

We retain data while it supports account access, security checks, payment receipt matching, support or an applicable legal duty. The Privacy Policy requires a purpose-based assessment, after which records may be removed or anonymised when continued storage is not needed.