Reference

Privacy Policy For Your spin508 Account

Our Privacy Policy explains how spin508 handles your account details, wallet records, device data and support requests from the moment you open an account.

Account dataWallet recordsCookie choicesSecurity requests
spin508 Privacy Policy For Your spin508 Account
CONTACT ROUTES

Get Privacy Policy Help Beside Your Account

A clear contact path matters when a privacy question affects your account or wallet status. Our support route is available for questions about the Privacy Policy, a phone verification record, a device entry or a payment receipt linked with your account. Tell us which account step raised the concern and include only the details needed to locate it. We can then explain the relevant policy section or identify the request path. The support route shown beside the cashier is also the right place when a DANA or QRIS record needs checking.

Team online

Policy questions

Use the support channel beside the account and cashier areas when you need an explanation of the Privacy Policy, data categories or a request step. Include your account identifier and the subject of your question, while leaving passwords, wallet PINs and one-time codes out of the message.

Wallet records

For a DANA, OVO, GoPay or QRIS record, tell us the payment rail, date shown in your account and the status displayed beside the transaction. We use those details to locate the relevant record without asking you to send private wallet credentials.

Access concerns

If a phone verification step or unfamiliar device entry concerns you, contact support through the account help route near the cashier path. We can explain the security record, ask for an account check and direct you to the right Privacy Policy request.

DATA PRACTICES

Six Ways We Handle Personal Data

The Privacy Policy is practical because each data category has a reason connected with account access, wallet records or security.

Account details

We use the details you enter during account creation to identify your account, support phone verification and respond to requests about the Privacy Policy. Keep your contact details current so an access question can be matched with the correct account record.

Payment status

A wallet record may show the rail used, such as DANA, OVO, GoPay or QRIS, together with an amount and status supplied through the account flow. We use this data to reconcile a request and answer receipt or pending-status questions.

Device signals

When you sign in, we may record device and browser signals, connection details and security events. These records help us investigate an unfamiliar access attempt without treating your phone model or browser as a public account detail.

Cookie settings

Cookies can keep selected settings available during your visit and help pages work across a mobile path from sign-in to the lobby. Your browser controls whether some cookies remain, while required technical cookies may still support account access.

Retention periods

We retain personal data for the period needed to provide account support, reconcile wallet activity, maintain security records or meet an applicable legal requirement. When a record no longer serves one of those purposes, handling follows the current retention process.

Your requests

You can contact us to ask about access, correction, deletion where available or the purpose of a data record. We may request an account check before acting, because changing personal data without confirming the account could affect phone verification.

Privacy Policy Questions About spin508

These Privacy Policy answers address the account and access questions we expect you to ask before opening an account. They explain what may be recorded, why wallet and device details appear, how cookies fit into the mobile path and where to send a request. For a case tied to your own account, use the support route beside the cashier so we can check the relevant record. Where access is discussed, it depends on local law.

The spin508 Privacy Policy covers account details, phone verification, wallet status, payment receipts, device signals, cookies, security events and support requests. It explains why we handle each category, how retention works and how you can ask about access, correction or another available data request.

Yes. The Privacy Policy covers records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may retain the payment rail, status and related account reference so we can reconcile a wallet request and respond when a receipt or status needs checking.

Device and browser details help us identify unusual sign-in activity, investigate an access concern and protect the account after phone verification. These signals can include device type, browser details, connection data and security events; they are handled for account security rather than displayed as public profile data.

Cookies can remember selected settings and help the account path work when you move from sign-in to the lobby on mobile or desktop. Your browser provides controls for some cookies. Required technical cookies may remain necessary for page operation, access checks and security functions.

You can contact us through the support route attached to your account and ask for a correction. State which detail is wrong and why you believe it should change. We may complete an account check first, especially when the request affects phone verification or wallet records.

We keep a record for as long as it supports account service, payment reconciliation, security handling or an applicable legal requirement. The period can differ by data category. You can ask support about a particular record, and we will explain the relevant retention reason under the Privacy Policy.

Use the support channel shown beside the account and cashier areas, then identify your request as a Privacy Policy matter. You can ask about a data category, access, correction or another available change. Do not include your password, wallet PIN or one-time verification code.