Reference

spin189 Privacy Policy for Your Account

Our Privacy Policy explains what account and wallet data we collect, why we use it, and how you can ask for changes.

Account dataWallet recordsCookie choicesAccess requests
spin189 spin189 Privacy Policy for Your Account
REQUEST ROUTES

Three Privacy Request Paths for Your Account

Privacy questions should reach the team with enough account context to locate the right record. We keep the route practical: begin from the login screen when you need account data, use the cashier path for a wallet receipt, and select the privacy request route when you want a correction or deletion check. Your request may require account verification before we disclose or change personal data.

Team online

Account data request

Open account support from the login screen and state whether you need access, correction or deletion details. We may ask for phone verification before discussing records linked to your account.

Wallet record query

For DANA, OVO, GoPay or QRIS records, start beside the cashier status and include the transaction reference. This helps us separate a payment receipt from unrelated account activity.

Privacy change request

Use the privacy request route in account support to ask about stored data, cookie choices or retention. We will explain any limit that applies under local law before changing the record.

DATA PRACTICES

Six Data Safeguards Behind Our Privacy Policy

We handle privacy as an account operation, not a hidden page. Our process connects login checks, cashier references, device sessions and support records so you can understand why a detail exists.

Collected account details

We may collect your phone number, account identifiers, login events and verification results. These details help us connect your request to the correct account without relying on a display name alone.

Cashier references

DANA, OVO, GoPay, QRIS and bank transfer activity can create reference numbers, amounts and status records. We use these details to trace a receipt and resolve a stalled cashier update.

Cookie controls

Cookies can keep your session active, remember selected settings and help us detect unusual access. You can ask support how a cookie category affects your account, rather than sharing wallet credentials.

Login protection

Phone verification is part of account access, while session and device signals help identify unusual sign-ins. If a login looks unfamiliar, contact account support before changing payment details.

Record retention

We retain account, security and transaction records only as long as needed for service, dispute handling, fraud checks or legal duties. The applicable reason can be requested through the privacy route.

Changes and contact

Ask for a copy, correction or deletion check through account support. Include the affected account step or receipt reference; we verify ownership first and explain any restriction before processing the request.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers address the practical questions you may have before opening an account or using the cashier. They cover account data, local wallet references, cookies, device access and request handling. If your situation is specific, use the account support route with the relevant receipt or login detail so we can identify the correct record.

It covers account details, phone verification, login events, cookies, cashier references, support records, retention and privacy requests. It also explains how DANA, OVO, GoPay and QRIS status data may be handled.

Phone verification helps connect access requests to the account owner and supports login protection. We may use the result when you ask for account data, change details or discuss a wallet record.

Yes. The policy covers references, status details and transaction context connected with DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity. We use them to match cashier records.

Start from account support through the login path and request access to your stored data. We verify account ownership first, then explain which records can be supplied and any legal restriction.

You can request a correction or deletion check through the privacy route in account support. Some security, dispute or transaction records may need to remain where local law permits.

It describes cookies used for session continuity, selected settings and unusual-access checks. Ask support about a cookie category if you want to understand its effect before changing your browser settings.

The same Privacy Policy applies when you move from smartphone login to the lobby. Session, device and verification details may be recorded to protect access, and eligibility depends on local law.