Reference

Privacy Policy For Your ekatoto Account

Our Privacy Policy explains what account, device and wallet data we use when you access ekatoto, and why each step matters.

Account dataWallet recordsDevice accessPolicy requests
ekatoto Privacy Policy For Your ekatoto Account
HELP WITH DATA

Three Ways To Ask About Privacy

Privacy questions should reach the account path that can identify your records correctly. Start from the support route inside your signed-in account, especially when your question concerns a phone check, wallet reference…

Account support path Use the signed-in support route for a Privacy Policy question about your phone verification, account details or sign-in history. We can ask you to confirm account ownership before discussing records or applying a requested change.
Wallet record query For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, mention the payment reference and approximate date. Do not send your wallet PIN or full password; we only need a traceable reference.
Access assistance If a device session or login prompt blocks your privacy request, explain the device path and account contact used. We use that context to separate a genuine request from an unverified access attempt.
HANDLING DETAILS

Six Privacy Controls Behind Your Account

The practical side of our Privacy Policy is visible in the way we handle account access and records.

Account identity

We store the account details you provide, such as your contact number and verification status, to recognise your account during sign-in and support requests. If a detail is wrong, ask us to correct it through the account-linked support path.

Phone verification

A clear phone verification step helps us distinguish the account holder from an unknown person using the same device. We record the verification result and related account event, not your private conversation content.

Device signals

A mobile browser or desktop session can produce device and session signals used to detect unusual access. We use these signals for security checks and account protection, including when you switch from mobile to desktop.

Payment references

Payment data can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its status. We use those details to match your account request and resolve a cashier record, not to request your wallet PIN.

Cookies and sessions

Cookies and session storage help keep your signed-in path working and remember security choices for the current visit. You can manage browser storage, but clearing it may require you to verify your account again.

Retention and requests

We keep records only as long as needed for account security, transaction questions and legal duties. You can ask what data is held, request a correction, or ask about removal where local law permits.

Answers About The ekatoto Privacy Policy

The questions below focus on the points that matter before you open an account or send a wallet payment. Our Privacy Policy applies to account access, device sessions, support contacts and transaction references, so you can use these answers to choose the right request path. Where a legal restriction applies, access depends on local law.

The ekatoto Privacy Policy covers account details, phone verification, device and session signals, support messages, cookies and payment references. It explains why we use each category for access, security, transaction handling and legal duties, including records connected with DANA, OVO, GoPay and QRIS.

We may collect the contact details you submit, your phone verification result, sign-in events, device signals and account activity needed to operate security checks. Payment references from bank transfer, virtual account or local wallets can also be linked to the relevant account request.

Device and session data helps us identify unusual sign-in behaviour and protect the account path. For example, a change from mobile browser to desktop may create a new session signal. We use that context for security checks, not as a substitute for your phone verification.

The Privacy Policy treats DANA, OVO, GoPay and QRIS references as transaction data connected with your account. We may use a reference, status and timing to match a payment question. Do not send a wallet PIN, full password or other secret credential in a support request.

Use the support route inside your signed-in account and state whether you want access, correction or removal. Include the account contact and the specific record concerned. We may verify ownership first, and a removal request is handled where local law permits.

We retain account, security and transaction records for the period needed to protect access, answer disputes and meet applicable legal duties. The exact period can vary by record type. Ask through the account-linked support path if you need a retention explanation for a specific record.

Yes. Use the access help route connected to the account prompt and explain that your request concerns the Privacy Policy. Give the account contact and a short description, but no password or wallet PIN. We may request additional proof before discussing personal records.