Reference

lingkartoto Privacy Policy Explained

lingkartoto sets out how we collect and use your account, device and wallet details when you open access to Live Baccarat, Garuda Gems or other lobby areas.

Clear data usesWallet record contextYour request pathIndonesia access
lingkartoto lingkartoto Privacy Policy Explained
CONTACT ROUTES

Browse Support Paths for Privacy Requests

A clear contact route helps when you want to ask about a Privacy Policy matter rather than a lobby question.

Account access If phone verification blocks your account, contact support through the account route and state…
Wallet record For a DANA, OVO, GoPay or QRIS record question, provide the transaction reference and…
Data request Use the privacy contact route to ask for a copy, correction or removal review.
DATA PRACTICES

Switch Through Key Privacy Controls

We handle this policy area around the actions your account actually takes: sign-in, phone verification, wallet status checks and access from your device.

Account details

We use your submitted account details to create access, complete phone verification and respond to account requests.

Device sessions

When you sign in on a phone or desktop, technical session details can help us recognise access patterns and investigate…

Cookie choices

Cookies can support sign-in continuity and security checks. Your browser settings let you control some cookies, although changing them may…

Wallet records

A DANA, OVO, GoPay or QRIS reference may be retained with account activity so we can match a payment query.

Retention timing

We retain records for the period needed for account servicing, security review and applicable legal duties.

Change requests

You can ask us to correct account data or explain its use.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the questions that arise before an account is opened or when a wallet record needs checking. We keep the route specific: identify the account, describe the request and use the support contact shown for privacy matters. Where local law permits, we will explain the available next step.

It covers account details, phone verification, device sessions, cookies, wallet references and support requests connected with your access. It also explains security use, retention and ways to request correction.

Phone verification helps connect an access request to the correct account and reduce unauthorised disclosure. We may complete that check before changing personal details or answering a record request.

Yes. The policy covers payment references supplied for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to service accounts and trace related questions.

You can send a correction request through the privacy contact route. Include the account phone detail and describe the field that is wrong; we may verify you before making a change.

Cookies may help maintain sign-in continuity and security checks when you use a phone browser. Browser controls can limit them, but some account functions may not behave as intended afterward.

We keep records for account servicing, security review and applicable legal duties for the period needed for those purposes. You can ask support to explain retention for a specific record.

Use the data request contact route and include your registered phone detail, request type and any relevant reference. Never send a wallet PIN; phone verification may be requested before disclosure.