Reference

ekotogel Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your ekotogel account, from phone verification to DANA, OVO, GoPay and QRIS references.

Account dataWallet referencesDevice controlsPrivacy requests
ekotogel ekotogel Privacy Policy For Your Account
CONTACT ROUTES

Support For Wallet Privacy Requests

A clear contact path helps when you need to ask about personal data linked to an account or a wallet receipt. Include your registered phone number, the relevant payment rail and a short description, but do not send a wallet PIN or password. We use the account details you provide to locate the correct record and respond to privacy requests from Indonesia, including requests made from Denpasar.

Team online

Account data request

Ask us to identify the account details held for you by using our support contact path. We may request an account step or phone verification before discussing private records.

Wallet reference check

For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date. We can investigate the stored status without asking for your wallet PIN, passcode or full banking credentials.

Correction request

If your phone number or account detail is inaccurate, tell us which field needs correction and why. We review the request against account-security signals before making a change.

SECURITY PRACTICE

Account Security Across Devices

Privacy protection works alongside the account steps you already know: phone verification before account access, a login check when device behaviour changes and a record of important account actions.

Account details

We use your phone number and submitted account fields to create access, complete phone verification and connect your requests with the right record. Keep those details current so privacy replies reach you safely.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create transaction references, amounts and status markers. These help us reconcile a receipt without storing your wallet password.

Device signals

A mobile browser or desktop session may provide device type, browser version, login time and network signals. We use these details to detect unusual access and protect the account during verification.

Cookies

Cookies can keep a session active, remember language or help us understand whether a page is working. You can adjust cookie controls in your browser, although some account steps may then need repeating.

Retention

We retain account, security and transaction records only for the period needed to provide the requested service, resolve disputes, maintain records or meet applicable legal duties. Storage duration can vary by record type.

Changes and removal

You can contact us to request access, correction or removal of personal data. We may verify account ownership first, explain any record that must remain, and confirm what action was taken.

Privacy Policy Questions For ekotogel

These Privacy Policy answers address the questions we expect before account creation: what we collect, how wallet references work, which device details matter and how you can request a change. If your case involves a specific receipt or login event, include its reference through our support contact path.

It covers account details, phone verification, device and browser signals, cookies, payment references and privacy requests. It also explains when limited data may be shared for a requested service or where local law permits.

No. We use payment references and status details for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Do not send a wallet PIN, password or full banking credential in a support message.

Phone verification helps connect an account request with the correct account and reduces mistaken access changes. We may ask for this account step before discussing personal data or processing a correction request.

You can contact us through the privacy contact path and request access to personal data connected with your account. We may confirm account ownership first, then explain the records we can provide.

Send the registered phone number, identify the inaccurate field and describe the correction needed. We compare the request with account-security signals before changing details, and we will explain the outcome.

Cookies can support a session, remember language and show whether an account page works correctly on your mobile browser. Browser controls let you adjust them, but some login steps may need repeating.

The Privacy Policy is available for you to read, while account access and eligibility depends on local law. If a request is restricted by applicable rules, we will explain the relevant limitation.