Reference

Privacy Policy For Your lokitoto Account

Our Privacy Policy shows how lokitoto handles the details linked to your account, including phone verification, wallet records and device access.

Account data explainedWallet records coveredCookie choices availableIndonesia access wording
lokitoto Privacy Policy For Your lokitoto Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path helps when you want to understand a Privacy Policy entry or check a wallet record connected to your account. We keep the request focused: tell us which account step, device session or payment reference concerns you, and we will route the question to the right handling team. You can reach us through the support route shown near the account and cashier areas, without sending your password or full wallet credentials.

Team online

Policy questions

Ask about the Privacy Policy through the account support route. Include the email or phone detail attached to your account and name the section you want explained, so we can respond without asking you to expose a password.

Wallet data check

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, share its reference and date through support. We can compare the account ledger with the cashier status while keeping your wallet PIN, one-time code and full login secret private.

Account access help

When phone verification or a device session blocks your account, use the support link beside the login path. We may ask for a verification detail already held on the account, but we will not ask for your password.

DATA HANDLING

What Our Privacy Policy Does For You

We write this Privacy Policy around the moments that matter: opening an account, checking a wallet status, returning to the lobby on mobile and asking for a correction.

Account details

We use your account name, phone detail and verification result to connect the right person with the right account. Phone verification comes before account access, helping us reduce mistaken records when you move between a mobile browser and a desktop session.

Payment references

A DANA, OVO, GoPay or QRIS entry can carry a payment reference, status and time. Bank transfer and virtual account checks use similar transaction details so support can trace a cashier question without receiving your wallet PIN.

Cookies and sessions

Cookies and similar session tools help remember a signed-in state, language setting and security check. You can manage browser cookie controls, although removing necessary cookies may sign you out or prevent the account path from working correctly.

Device security

We may record device type, browser signals and session time to identify unusual login behaviour. These details help protect your account when you open Super Bingo on mobile and later return to the same account from another device.

Data retention

We keep account, security and transaction records only for the period needed for the stated service purpose, account queries and applicable legal duties. When a record no longer needs to be retained, our handling follows the deletion or restriction process available under local law.

Change requests

You can ask us to correct an inaccurate account detail, explain a stored record or request a permitted restriction. Send the request through support with your account identifier and the exact change; we may verify ownership before making an account-level update.

Privacy Policy Answers For lokitoto

These Privacy Policy answers focus on the account and payment questions you are most likely to ask before opening an account. We keep each answer tied to a practical step, from phone verification and cookies to a DANA receipt or a request to change stored data. If your situation is not covered, our account support route can take the question forward where local law permits.

The lokitoto Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references and support requests. It explains why we use each category, how retention works and how you can ask for access, correction or a permitted restriction.

Yes. Privacy Policy coverage includes the reference, status and timing connected with DANA, OVO, GoPay and QRIS activity. We use those details to match a cashier request and answer a status question, not to collect your wallet PIN or one-time code.

Phone verification connects account access to the contact detail you provide and helps reduce mistaken or unauthorised sessions. The verification result can be stored as an account security record, while the one-time code itself should remain private and should not be sent to support.

Use the account support route and state whether you want a data copy, an explanation or a correction. Include your account identifier and the specific record, such as a phone detail or QRIS reference. We may verify ownership before handling the request.

Our Privacy Policy treats necessary cookies as session and security tools for the mobile browser path. Browser settings can remove or block them, but doing so may sign you out or interrupt phone verification. Optional cookie choices can be changed through your browser controls.

We retain account, security and payment records for the period needed to operate the requested service, answer account questions and meet applicable legal duties. The exact period can differ by record type. You can ask support to explain the retention basis for a specific entry.

You can request a permitted restriction or object to a stated use by contacting support through the account route. Tell us which data category and purpose concern you. We will assess the request under the Privacy Policy and where local law permits.