Reference

dragspin Privacy Policy, Clearly Explained

Our dragspin Privacy Policy shows what account, wallet, device and cookie data we handle when you open an account and access the lobby.

Account dataWallet recordsCookie choicesPhone verification

Explore Our Lobby Read FAQ

How Our Policy Covers Wallet Records

dragspin Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details you provide during account creation, including your contact details, phone verification status and security activity. We also record transaction references needed to match a deposit or withdrawal request with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. A payment

1
provider may handle its own records under its own terms, while we use the data available to us to check status, resolve a receipt question and protect account access. We collect device and browser signals to identify unusual login patterns, maintain session continuity and remember cookie
2
choices. Where local law permits, we may retain records for security, dispute handling or legal requests. Access depends on local law, and you can ask our support team what data is connected to your account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Need Privacy Policy Help With Access?

A clear contact path helps when your Privacy Policy question involves an account detail, wallet record or device session.

Account data request Ask us to explain the personal data connected to your dragspin account. Include your registered phone or email, then complete any identity check we request before we disclose account-specific details through the support path.

Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the transaction reference and date. We use those details to check a receipt or status without asking you to share your wallet PIN.

Cookie or device concern If a mobile browser keeps an old session or cookie choice, tell us the device type and browser path you used. We can explain the relevant Privacy Policy section and suggest the account access step to repeat.

HANDLING DETAILS

What We Do With Your Account Data

We keep this policy practical by linking each data category to an account task you can recognise.

Data we receive

We may receive your name or contact details when you create an account, plus phone verification results and support messages. Payment records can include a reference, amount, method and status for DANA, OVO, GoPay, QRIS or bank-based transfers.

Cookie controls

Cookies can keep your session active, remember a selected setting and help us understand whether a page works correctly. You can clear or restrict cookies in your browser, although a fresh login may then be required to reach your account.

Account security

We use phone verification, login events and device signals to help protect your account. Never send us a password, wallet PIN or one-time code in support messages. If a login looks unfamiliar, contact us through the account support route.

Retention approach

We keep personal and transaction records only for as long as needed for the purpose described in this Privacy Policy, account security, dispute handling or a lawful request. The period can differ by record type and applicable local requirements.

Who receives data

We may share necessary details with service providers that help operate account access, security, payment status checks or website delivery. They receive only the data needed for that task, while DANA, OVO, GoPay, QRIS and banks manage their own separate records.

Requesting a change

You can ask us to correct an inaccurate account detail, explain a data use or address a Privacy Policy concern through support. State the requested change clearly, use your registered contact, and complete identity checks before account data is altered.

Privacy Policy Questions About dragspin

These Privacy Policy answers cover the questions we expect you to ask before opening an account or connecting a local wallet. We keep the wording tied to real account steps, including phone verification, mobile browser access and payment status checks. If your situation is not covered, contact support from the account route and tell us which data record or policy point you want us to examine.

The dragspin Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains how we use those records for account access, security, status checks and lawful requests when you use the website where local law permits.

We may receive a transaction reference, method, amount and status for DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use that record to match your account activity and investigate a receipt question; we do not ask for your wallet PIN.

Yes. Phone verification helps connect your phone number to the correct account and supports security checks before account access. We may retain the verification result and related account event under the retention approach described in the Privacy Policy, subject to applicable local requirements.

Cookies can keep a mobile browser session active, remember a setting and help us check page performance. You can clear or restrict them through your browser controls. Doing so may remove a saved session, so you might need to complete the account login step again.

You can contact support using the email or phone linked to your account and ask what data is held or request a correction. Describe the record clearly, such as a contact detail or payment reference, and complete identity checks before we respond.

The retention period depends on the type of record and its purpose. We may keep account, security and payment references for account protection, dispute handling or a lawful request, then remove or anonymise them when they are no longer needed.

Yes. Ask support which service provider category relates to your question, such as website delivery, account security or payment status checks. We will explain the relevant Privacy Policy position, while DANA, OVO, GoPay, QRIS and banks remain responsible for their own records.

dragspin Privacy Policy, Clearly Explained

Need Privacy Policy Help With Access?

What We Do With Your Account Data

Data we receive

Cookie controls

Account security

Retention approach

Who receives data

Requesting a change

Privacy Policy Questions About dragspin

01 What does the dragspin Privacy Policy cover?

02 What payment data does dragspin receive from DANA or QRIS?

03 Does the Privacy Policy explain phone verification?

04 How do cookies affect my dragspin account?

05 Can I request a copy or correction of my data?

06 How long does dragspin keep account and payment records?

07 Where local law permits, can I ask about data sharing?

Related Pages