Reference

scratchcash Privacy Policy for Wallet Data

Our Privacy Policy explains what scratchcash collects when you open an account, sign in on mobile, or use DANA, OVO, GoPay and QRIS details.

Account dataWallet recordsDevice choicesPrivacy requests
scratchcash scratchcash Privacy Policy for Wallet Data
PRIVACY HELP ROUTES

Three Routes For Privacy Help

A clear contact path helps you act on this Privacy Policy without sending sensitive details into the wrong place. Start from the support link inside your account, include your registered phone number and the exact request, then let us match it to your account record. If a wallet receipt or device entry concerns you, name the payment rail and browser or phone path involved.

Team online

Account support form

Use the signed-in support form for access, correction or deletion requests. We may ask for your registered phone number and account details before changing personal data.

Wallet status route

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the receipt reference and date. We use those details to locate the relevant payment entry.

Privacy request path

If you cannot sign in, contact us through the account access route and state that your request concerns the Privacy Policy. Do not send a password or full wallet credentials.

SIX DATA CONTROLS

Six Controls Behind Your Account Data

We keep this policy practical by linking each privacy control to something you can recognise in your account journey.

Purpose-based collection

We collect account details to create access, verify the registered phone and protect sign-in. We collect game or lobby activity, such as Medusa or Mega Fishing entries, only where it supports an identified account or security purpose.

Cookie choices

Cookies and similar browser storage can remember session state and security settings. On a mobile browser, you can clear site data through your browser controls, though doing so may sign you out.

Account protection

Phone verification, sign-in events and device signals help us detect unusual access. We do not ask for your password in a support request, and you should keep verification codes private.

Payment references

We may retain a payment reference, amount status and selected rail for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet password to check a receipt.

Retention choices

We keep personal records only as long as needed for the stated purpose, account security, dispute handling or a legal requirement that applies. When retention ends, we delete or separate the record.

Change requests

To request access, correction or removal, send the relevant account identifier through our support path. We confirm ownership first, explain any limitation, and record the result against your request.

Seven Privacy Policy Questions Answered

These Privacy Policy answers focus on the searches we expect before you open an account or connect an Indonesian wallet. They cover the records created during phone verification, mobile access, game activity and payment status checks, while keeping the next privacy step clear.

It covers account, phone verification, device, cookie, game activity and payment reference data linked to your access. It also explains our purposes, retention approach, security controls and request process.

We use your registered phone number to create and protect account access, complete the stated verification step and connect a privacy request to the correct account. We do not ask for your verification code.

Yes. It covers references and status connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These details help us match receipts without requesting your wallet password.

We may receive browser, device and sign-in event details needed for session handling and account security. Clearing browser storage can remove session data, so you may need to sign in again.

Send a correction request through the signed-in support form, include your registered phone number and describe the field that is wrong. We confirm account ownership before making an account record change.

You can ask us to remove eligible personal data through the privacy request path. We assess the request against account security, dispute handling and legal duties, then explain what we can do.

Access depends on local law and account eligibility. Where local law permits, the policy describes how we handle your data; if a rule limits access, that rule takes priority.