Reference

timsestoto Privacy Policy Explained

timsestoto Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet data controlCookie choicesPolicy contact path
timsestoto timsestoto Privacy Policy Explained
CONTACT WHEN NEEDED

Privacy Help Beside Account Support

A clear contact route matters when you want to question a record, correct an account detail or understand a cookie choice.

Account request Use the support path in your signed-in account when you want to ask what personal details we hold. We may ask you to complete the same phone verification step used for account access before releasing or changing account-linked records.
Wallet query For a DANA, OVO, GoPay or QRIS reference, send the transaction date, rail name and visible status rather than a wallet password. This lets us investigate a matching record while limiting the sensitive details included in your request.
Access issue If a privacy page or account control does not load on your phone, try the signed-in browser path on your desktop and tell support which device failed. We use that device detail to separate an access fault from an account permission question.
DATA HANDLING PRACTICE

What We Do With Your Details

We handle privacy as part of the account path, not as a separate promise hidden from the cashier or lobby.

Account records

We use your account details to create access, complete phone verification, maintain sign-in security and respond to requests about the Privacy Policy. We avoid asking for unrelated details, and you can contact us when a profile field is inaccurate or no longer needed.

Device signals

A phone, tablet or desktop can send browser type, operating system, session timing and security events. These signals help us keep an account session consistent when you move from the login page to a lobby such as Live Dealer Lobby.

Cookie controls

Cookies can remember a session choice, support page security and show whether a policy control has been used. You can adjust cookies through your browser settings, although restricting them may require another sign-in before account pages open.

Payment references

A wallet or bank record may contain a rail name, amount reference, status and time linked to your account action. We use those fields to check DANA, QRIS, bank transfer or virtual account questions without requesting your wallet PIN.

Retention steps

We keep personal details while they support account security, a requested service or a legal need. When the relevant purpose ends, we remove, anonymise or restrict the record according to our operational process rather than keeping it without a reason.

Your requests

You can ask us to access, correct, restrict or remove eligible personal details through account support. We confirm your identity first, explain the result in clear terms and tell you when a security or legal reason prevents a requested change.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account, device and wallet questions you may have before using timsestoto. We keep the wording practical: what we collect, how we verify a request, how cookies affect a session and how Indonesian payment references are handled. If your question is not covered, use the support path connected with your account and include only the details needed to identify the issue.

It covers account details, phone verification, device and browser signals, cookie activity, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account actions. It explains why we use those records, how long we retain them and how you can request a change.

Phone verification helps us confirm that the person requesting account access or a privacy change is connected with the account. It also supports security checks when a sign-in or wallet-status question looks unusual. We do not ask you to send a password or wallet PIN through support.

Yes. The Privacy Policy covers payment references connected with your account, including a DANA or QRIS status, time, rail name and matching transaction reference. We use those details to answer an account question or resolve a status mismatch, not to request private wallet credentials.

You can request access to eligible personal details through the signed-in account support path. We confirm your identity before responding, which may include the phone verification step. Our response explains the records available and any security or legal reason that limits what we can provide.

Cookies can keep a session active, support account security and remember whether a policy control was selected. You can manage them in your browser on a phone or desktop. If you block necessary cookies, we may ask you to sign in again before account pages load.

We retain personal data while it serves an account, security, support or legal purpose. After that purpose ends, we remove, anonymise or restrict the record through our retention process. A request can be assessed sooner, although some records may need to remain for security or legal reasons.

Use the support path inside your account and state which detail needs correction, such as a phone record or contact field. Include the account identifier needed to locate it, but exclude passwords and wallet PINs. We verify the request, assess the record and explain the next step.