Reference

Privacy Policy For Your twitspin Account

twitspin keeps this Privacy Policy focused on the data you share when opening an account, checking wallet status or entering the lobby.

Clear data purposesCookie choicesAccount access rightsWallet record handling
Browse Our Lobby Read FAQ
twitspin Privacy Policy For Your twitspin Account
PRIVACY HELP

Get Help With A Policy Request

A clear contact route matters when you want to ask about personal data. Start from the account help path and choose the privacy request option so we can match your message to the correct account record. Include the email or phone detail used during account access, but do not send a password, one-time code or full payment credential. If your wallet status stalls after a DANA, OVO, GoPay or QRIS action, the same route can connect your payment receipt question with the relevant account record.

Team online

Privacy request

Use the privacy request path in account help to ask what personal data we hold, why it is used or which records relate to your twitspin access. We may ask for an account detail so we do not disclose data to the wrong person.

Access correction

Tell us which account detail needs correction and provide the current version you want us to check. For a phone or email change, we may require an account step or phone verification before updating the record.

Wallet record check

For a receipt or wallet-status question, attach only the reference needed to locate the event. DANA, OVO, GoPay and QRIS providers retain their own records, so we may direct part of the request to that provider.

DATA PRACTICES

What We Do With Your Account Data

We keep the Privacy Policy practical by linking each data use to an account action. Your phone verification supports account access, device signals help identify unusual login behaviour, and transaction references help…

Account details

When you open an account, we use the details you provide to create your profile, send account messages and complete access checks. We do not need your password in a privacy request, and our support route will tell you which account detail is required.

Phone verification

Phone verification links an access request to the account detail you supplied. It can help us distinguish your login from an unusual attempt. If you request a phone change, we may retain the old and new verification event for security records.

Device behaviour

Your device and browser may send technical signals such as session details, language settings and sign-in time. These signals help keep an account session working on mobile or desktop and help us investigate suspicious access without reading unrelated device content.

Cookies

Cookies can keep your session available, remember a selected setting or show us whether a page responds correctly. You can manage cookies through your browser controls, although disabling some cookies may affect account access or the way a privacy request is submitted.

Payment references

A DANA, OVO, GoPay or QRIS transaction may create a reference, amount, status and time in our records. We use those fields to match receipts and status checks. Wallet providers remain responsible for data held in their own systems.

Retention and changes

We keep records only for the period connected to service delivery, security, dispute handling or a legal duty. If you ask for deletion or correction, we assess the request against those duties and tell you what we can change, keep or restrict.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect you to ask before opening access from Indonesia. They explain the practical route for data requests, cookies, wallet references and account security without turning the policy into a general description of the lobby. If your situation is not covered, use the privacy request path in account help and include the account detail we can safely use to locate your record.

The twitspin Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and transaction references. It explains why we use each category, how security checks work and how you can ask about your records when access is available where local law permits.

Open account help and select the privacy request path, then ask for access to your personal data. Include the email or phone detail linked to the account, but never include your password or one-time code. We may verify your identity before releasing account records.

It covers the DANA or QRIS references that reach our systems, such as a transaction status, time or reference used to match an account question. DANA and QRIS may hold additional records under their own terms, so we may direct that part of your request to them.

Device and browser signals help keep your session working and help us identify unusual access. We may use sign-in time, browser details or session markers, but this does not give us access to unrelated content on your phone or computer.

Yes. Send a correction request through account help and identify the field that appears wrong. We may ask for phone verification or another account step before changing email, phone or profile details, because an unauthorised change could affect future access.

Retention depends on the type of record and why we collected it. Account, security, payment-status and support records may remain while needed for service, dispute handling or legal duties. If you request deletion, we assess which records can be removed or must remain.

You can manage cookies through your browser settings. Session cookies may be needed to keep account help and a privacy request available, while other cookies support page measurement. Turning cookies off can change how the page or account access behaves on your device.

Related Pages

twitspin Indonesia FAQ Payment Help Badminton Uber Cup Bet FAQ Access guide