Reference

ekototo Privacy Policy for Indonesian Accounts

We explain which account data, device signals, and payment traces we collect, including activity tied to DANA, OVO, GoPay, and QRIS.

Account dataCookiesDevice logsSupport chat
ekototo ekototo Privacy Policy for Indonesian Accounts
HELP CHANNELS

Where to Send Privacy Requests

Fast privacy help matters when you want a correction or need a record check. Use live chat from the account menu, send mail to privacy@ekototo.

Live Chat Open live chat from the account menu and tell us which record you want checked, corrected, or removed. We reply in English, and the queue is watched daily from 09:00-23:00 WIB.
Email Send a message to [email protected] with your registered email, phone number, and the change you want. We use it for data access, correction, or deletion requests after identity checks.
Privacy Form Use the form under Settings > Privacy when you need a copy of your data or a change to your device settings. We confirm the account first so the record goes to the right place.
HOW WE HANDLE DATA

Security, Cookies, and Retention

We keep this policy practical: account data stays tied to your login, cookie settings follow the device you use, and session logs help us spot unusual access.

Account Data

We store your registered name, contact details, login history, and the messages you send to support. Those records help us verify your account, answer privacy requests, and keep a clear trail when you ask for a correction.

Cookies

Cookies remember language, session state, and device preferences so you do not need to reset them on each visit. You can clear them in your browser, or block them there if your device settings allow it.

Device Security

We log device type, browser version, and IP signals to catch unusual access and protect your account. If you change phones or laptops, we may ask you to confirm the new device before sensitive changes.

Retention

We keep records only as long as needed for account operation, dispute handling, fraud checks, and legal duties. After that, we delete or de-identify them according to our retention schedule.

Correction Requests

If your name, phone number, or email changes, send the update from the account menu or via support. We will match it against your registered details before we edit the record.

Contact Path

For privacy questions, reach us through live chat, email, or the form under Settings > Privacy. Use the registered email address so we can locate your account fast and answer clearly.

Privacy Policy Questions We Hear

These are the questions people ask before they open an account or send a privacy request. We keep the answers short, because you should be able to check the rule, the channel, and the next step without reading a long wall of text. If your case depends on local law, we will say so plainly and point you to the correct contact path.

We collect the details needed to create and secure your account: name, contact data, login history, device signals, and any message you send to support. We use them only for account handling, security, and privacy requests.

Yes. Cookies save session state, language choice, and device preferences so your page loads the way you left it. You can clear or block them in your browser settings whenever your device allows that control.

Open the account menu, choose Settings > Privacy, and send the update request there, or use live chat and email. We usually ask for your registered email and one matching detail before we change the record.

We keep it only for the time needed to run the account, settle a dispute, meet legal duties, or complete a security check. After that, we delete or de-identify it according to our retention schedule.

No. Payment names only help us match a transaction to your account. The same privacy rules apply to DANA, OVO, GoPay, QRIS, and any other supported method we list inside your account.

You can reach live chat, email [email protected], or the form under Settings > Privacy. Send it from your registered email so we can find the right account and answer your request faster.

Yes. Where a feature depends on location or local law, we only make it available in places where local law permits it. If access changes, we explain the reason through support.