Reference

scatter333 Privacy Policy, Clearly Explained

The scatter333 Privacy Policy tells you what account, device and wallet data we use, why we need it and how you can ask for a change.

Account dataWallet recordsDevice choicesPolicy requests
scatter333 scatter333 Privacy Policy, Clearly Explained
CONTACT ROUTES

Privacy Help Along Your Account Path

You can ask us about the Privacy Policy without leaving the account area.

Account access Use the account support route when you want to know which profile data we…
Wallet records For DANA, OVO, GoPay, QRIS or bank transfer questions, send the relevant reference through…
Policy changes If you want to correct, export or remove eligible data, contact us through the…
DATA PRACTICE

Six Ways We Handle Your Data

We keep the Privacy Policy practical by linking each data choice to an account action. Your browser, wallet reference and phone verification record serve different purposes, so we do not describe them…

Account data

We use your account details to create the profile, confirm phone ownership and connect support requests with the correct account. We do not need your DANA or QRIS wallet password for this process.

Device signals

A mobile browser may provide device and session signals that help us identify unusual sign-in activity. These signals support account protection and are not a replacement for your phone verification step.

Cookies

Cookies can keep a session open and remember basic choices on the lobby or policy page. You can manage or clear them through your browser settings, although some account steps may then need repeating.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match cashier activity and receipts. We use the reference for status checks rather than collecting a wallet password.

Account security

We limit account data access to operational needs such as verification, payment status and support. If a sign-in or wallet status stalls, we may ask for matching account details before replying.

Retention requests

We retain records only for the operational or legal period that applies to the record. You can ask what remains, request a correction or ask whether deletion is available where local law permits.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often before account access. We explain what to send, which records may be involved and how local law affects a request, whether you are checking a mobile session, a wallet reference or a phone verification step.

It covers account details, phone verification, device signals, cookies, payment references, support requests and activity linked to your account. It also explains retention, security handling and available data requests.

Yes. The Privacy Policy covers DANA and QRIS references used to match deposits, receipts and status checks. We do not need your wallet password, and the reference remains tied to the relevant account record.

You can contact support through the account path and ask which eligible data is held about you. We may confirm your phone number or another account detail before preparing the response.

Send a correction request through the policy support route, identify the affected account field and explain the change. We may compare it with your phone verification record before updating the account.

Our mobile browser pages may use cookies for session continuity and basic choices. You can clear or restrict them in your browser settings, though login or policy access steps may need repeating.

Retention depends on the record type and the operational or legal period that applies. Payment references may remain for status checks, while you can ask support what data is still held.

Account access and eligibility depends on local law. If a policy request concerns a blocked sign-in, include your account phone detail through support so we can explain the available path.