Reference

Read the susubet Privacy Policy

The susubet Privacy Policy explains what we collect when you create an account, complete phone verification, browse Dragon Tiger or use DANA and QRIS.

Account dataWallet recordsDevice choicesYour requests
susubet Read the susubet Privacy Policy
REQUEST HELP DIRECTLY

Find help for privacy requests

A clear support route helps when you need to ask about a record, correct an account detail or understand a wallet reference. Start from the support path inside your account and include the email or phone number attached to your profile. If you cannot sign in, use the account-access contact route shown on our site; we may ask for phone verification before discussing private account data.

Team online

Account data route

Ask us to explain or correct account details through the support path connected with your profile. Include your registered contact detail so we can match the request safely.

Wallet record route

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, send the date and transaction reference. Do not send a wallet password or full security code.

Access assistance

If login stalls, tell us the device path you used and whether phone verification completed. We use those details to locate the right account record without exposing it.

HOW RECORDS ARE HANDLED

Explore how we handle your data

We designed this policy around the records you actually meet: account creation, phone verification, mobile browsing and wallet status checks.

Collection points

We collect details you submit during account creation, plus login, phone verification and support records. Device and browser signals can help us recognise a sign-in attempt and protect your account.

Cookie choices

Cookies and similar files can remember a session, preserve selected settings and help us understand navigation between the lobby and account area. Your browser controls can limit or remove them.

Payment references

We retain transaction references rather than asking for your wallet password. Records may identify DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity for account checks.

Account security

Phone verification, sign-in signals and unusual access checks help us decide whether a request comes from the account holder. Never share a password or one-time security code.

Retention periods

We keep records only as long as needed for the purpose described in the Privacy Policy, account support, security checks or a legal requirement. Some transaction records may remain longer.

Change requests

You can ask us to correct eligible account details, explain a processing purpose or request deletion where allowed. We may verify ownership before making a change.

Check Privacy Policy answers first

These Privacy Policy questions cover the decisions you are most likely to make before opening an account. We focus on account data, device activity, local wallets and contact steps, so you can choose whether to continue with a clear understanding of our handling practices where local law permits.

It covers account details, phone verification, login and device signals, support messages, cookies, wallet references and retention. It also explains your rights and how to contact us about eligible requests.

Phone verification helps us connect a request or sign-in with the correct account and reduce unauthorised access. We may use its result when you ask about private account or wallet records.

It can cover transaction references associated with DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. We use those references for account checks and support, not for wallet passwords.

We may receive browser, device, session and sign-in signals, along with cookie settings. These details help maintain access and detect unusual activity when you browse from mobile or desktop.

Yes. Contact us through the account support path with the detail you want corrected. We may confirm ownership through your registered contact detail before changing the record.

Retention depends on the purpose, account support needs, security work and applicable legal requirements. The Privacy Policy explains why some transaction or verification records may remain after other data is removed.

Use the privacy or account support path shown on our site and describe your request clearly. Include your registered contact detail, but do not send passwords, wallet PINs or security codes.