Reference

Privacy Policy for your optiktoto account

Our Privacy Policy explains what we collect when you open an optiktoto account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
optiktoto Privacy Policy for your optiktoto account
CONTACT PATHS

Privacy questions, receipts and account help

You can ask about this Privacy Policy without describing your full account history. Start from the support route linked near account access, state the email or phone connected to your account, and…

Policy request Send a clear request through our account support route and mention the exact Privacy Policy issue. We will use the account contact detail you provide to locate the relevant record.
Wallet receipt For DANA, OVO, GoPay or QRIS questions, include the transaction reference and status shown in your account. Do not send your wallet PIN, password or complete security code.
Access trouble If sign-in stalls on your phone, describe the device and browser path, then request Privacy Policy assistance. We can separate an access issue from a data request before checking the account.
HANDLING YOUR RECORDS

How optiktoto handles cookies and records

Our handling process separates account operation from policy requests. Login and verification records help us protect access, while cookie controls help your browser remember settings and measure basic page activity.

Account details

We collect the contact and verification details needed when you open an account. Keeping your phone or email current helps us send account notices and match a privacy request to the correct record.

Cookie settings

Cookies can remember sign-in preferences, protect account sessions and show whether a page loads correctly. You can adjust browser cookie controls, although some account functions may require session cookies.

Wallet history

A DANA, OVO, GoPay or QRIS entry can include a rail name, reference and status result. We use those fields to reconcile the account record rather than requesting your wallet password.

Security checks

We may compare sign-in patterns, device signals and verification responses when an account change looks unusual. These checks help us protect your details before changing contact data or access settings.

Retention approach

We keep personal records only for the period needed for account operation, security checks, dispute handling and legal duties. When a record is no longer needed, our process is to remove or separate it.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. Include the affected field and your account contact detail so we can assess the request safely.

Privacy Policy answers for your account

These Privacy Policy answers focus on the questions you may have before opening an optiktoto account from Indonesia. They explain the practical request path, the records connected to local wallets and the limits that apply when access depends on local law. Contact support if your situation needs a record-specific response.

It covers account details, verification records, device and sign-in events, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your account contact detail for sign-in notices, verification steps, security checks and matching a Privacy Policy request to your account. Keep it current and never share your password.

A QRIS payment may create a record showing the selected rail, reference and status result. We use that information to reconcile your account without asking for your wallet PIN or private access code.

Use the support route connected to your account and ask for a data access request. State the account email or phone, describe the records sought and complete any limited identity check.

Yes. Tell us which account field is inaccurate and provide the current detail through support. We may verify ownership first, then assess the correction under the Privacy Policy and local requirements.

Cookies can keep a session active, remember selected settings and help us identify page errors. Browser controls can restrict them, but sign-in or account security functions may not work without necessary session cookies.

You can ask about removal through support, and we will assess the request against account security, dispute handling and legal retention needs. Access depends on local law and the record involved.