Reference

samba189 Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use and protect the account, wallet and device details connected with your samba189 access.

Account clarityWallet recordsDevice choicesPolicy access
samba189 samba189 Privacy Policy for Your Account
CONTACT ROUTES

Check Privacy Questions Through Support

A clear support path helps when you want to ask what account data we hold or why a wallet record appears in your history. Start from the account help route beside the cashier area and describe the issue without sending a wallet password. We may ask for an account identifier or payment reference so we can locate the correct record. Your request is handled as a privacy matter, not treated as a public message.

Team online

Account data request

Ask us to clarify the account details linked to your phone verification, sign-in history or access status. We will use the account path to keep the request connected to you.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date rather than a password. This helps us match the record without exposing private wallet credentials.

Policy correction path

If a detail is outdated or incorrect, contact support through the account help route and state the change you need. We may request verification before changing personal account information.

HANDLING DETAILS

Explore How We Handle Your Records

We keep privacy work tied to identifiable account actions rather than vague promises. The points below show what we do with sign-in details, payment references, cookies and device information, plus how you…

Account data

We use details such as your phone number, account identifier and verification status to create access, confirm the right account and respond when you ask about your personal records.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us reconcile account activity. We do not ask for your wallet PIN, bank password or one-time code.

Cookies and settings

Cookies can remember sign-in preferences, security events and privacy choices on your browser. You can manage browser cookie settings, though some account functions may then need another check.

Device signals

We may record browser, operating-system and device signals used during access to identify unusual sign-in patterns. The same checks can apply when you move from mobile to desktop.

Retention choices

We retain records only for the operational, security or legal purpose described in the policy. When a retention purpose ends, records are deleted, anonymised or kept only where a requirement applies.

Your request

You can ask what personal data we hold, request a correction or raise a privacy concern through support. We may verify your account first so another person cannot change your records.

Browse Privacy Policy Answers

These answers cover the questions we expect before an account is opened: what we collect, how wallet records are used, what happens on another device and how to contact us. For a case-specific answer, use the support path and include only the details needed to locate your account.

It covers account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, virtual account and bank transfer.

Phone verification helps connect account access to the correct person, reduce mistaken account changes and protect payment records. We may request this check before discussing or changing personal account details.

Yes. The Privacy Policy explains how we use DANA and QRIS references, along with OVO, GoPay, virtual account and bank transfer details, to match an account payment without collecting wallet passwords.

Yes. Contact us through the account help route and request access to your personal records. We may ask for account verification before replying, so your information is not disclosed to another person.

Send a correction request through support, identify the account detail that needs changing and complete any requested verification. We will assess the request against account security and applicable requirements.

A change from mobile to desktop may create new device and sign-in signals. We use those signals for account protection, while the Privacy Policy explains how related records are stored and retained.

Use the privacy link on our site to open the current text before account access. Service availability and eligibility depend on local law, so the policy should be read with that condition.