Reference

How We Handle Your Data

This page explains what we collect when you open an account, confirm your device, or move funds through DANA, OVO, GoPay, or QRIS.

Account checksCookie useLocal law

Browse Lobby Read FAQ

What We Keep and Why

jeptoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

When you use jeptoto, we keep only the data needed to run the account, match a payment, and answer privacy requests. That can include your email, device type, login time, IP address, cookie data, and the status of DANA, OVO, GoPay, or QRIS transactions tied to

1
your account record. We use those details to prevent duplicate logins, match a payment to the right account, and keep records for dispute handling or legal retention where the law asks for it. We do not keep more than we need for those tasks. If you
2
ask for access, correction, or deletion, we first verify the request from the contact method on file, then check the account history and respond through the same channel or the registered email. When local law sets a different rule, that rule applies.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST PATHS

Where to Send Privacy Requests

If you want to check, correct, or close a privacy request, start from the contact channel on your account. We answer from the registered email, in-app chat, or the help form, and we keep the case tied to the exact account until it is closed. For faster matching, include your payment method, such as DANA or QRIS, and the date of the last successful action. We reply during 09:00-21:00 WIB.

Team online

Registered email

Send your request from the email on the account if you need access, correction, or deletion steps. We use that address to verify you before we touch the record, and we answer in the same thread.

In-app chat

Open chat after you sign in when you need a faster privacy check. Include the date, the payment method you used, and the last account action so we can find the right file without delay.

Help form

Use the form if you cannot sign in. It goes to the privacy queue, we reply during 09:00-21:00 WIB, and we keep the case linked to your request until it closes.

SAFE HANDLING

How We Protect Policy Records

Our policy handling is built around narrow access and clear logs. We record the reason a staff member opens a case, the time of the change, and the device used to approve…

Data scope

We collect only the details needed to run the account, match a payment, and answer a privacy request. That usually means email, device type, login time, IP address, and the transaction reference for DANA, OVO, GoPay, or QRIS.

Cookie use

Session cookies keep you signed in while you move between pages, and preference cookies remember language and display choices. They are small records, not content files, and they help us keep the session steady.

Account security

When a change request arrives, we first verify the email on file and may ask for one recent account detail. This extra check prevents someone else from changing your record without permission.

Retention

We keep records only for the time needed to run the account, settle a dispute, or meet a legal retention rule. After that, we remove or de-identify the data where our process allows.

Sharing limits

We share data only with staff or vendors who need it to process a request, secure the system, or meet a legal duty. Every recipient is bound to use the data for that limited purpose.

Change requests

If you want access, correction, or deletion steps, use the registered email or in-app chat. Tell us what you want changed, and we will reply with the next step or the legal reason we cannot.

Common Privacy Questions You Ask

Use these answers when you want the short version before you open a request. Each item below points to the data we keep, how long we keep it, and how you can reach us through the registered email or in-app chat. If your question depends on your region, local law decides the final rule, and we follow that rule before we make a change.

We keep the details you send during account creation, plus login records, device type, and payment references tied to DANA, OVO, GoPay, or QRIS. We use them to verify the account and answer support requests.

Cookies help us keep your session active, remember language choice, and recognize repeated logins from the same device. We do not use them to collect more data than is needed for account use and support.

Yes. Send the request from the email on file or through in-app chat, tell us what needs to change, and we will check the account record before we update it or explain any limit set by law.

We keep records only for as long as needed to run the account, settle a request, or meet legal retention rules. When the retention period ends, we remove or de-identify the data where our process allows.

Access is limited to staff who need it for verification, support, security, or legal duties. We do not open your records to unrelated teams, and any vendor handling data must follow our written controls.

Use the help chat inside your account, send an email from the address on file, or use the contact form. Add your payment method, recent date, and request type so we can match the record quickly.

How We Handle Your Data

Where to Send Privacy Requests

Registered email

In-app chat

Help form

How We Protect Policy Records

Data scope

Cookie use

Account security

Retention

Sharing limits

Change requests

Common Privacy Questions You Ask

01 What data do you collect when I open an account?

02 Why do you use cookies?

03 Can I correct my details?

04 How long do you keep records?

05 Who can see my privacy records?

06 How do I contact you about privacy?

Related Pages