Reference

Legal terms for your account access

This page sets the legal rules for your account, your data, and your access path.

Access termsData rulesLocal-law check

Browse Lobby Read FAQ

Where our legal policy applies

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

We set one legal standard for every account, but access still depends on where you are and what local law allows. If your region is not permitted, we can keep the profile visible for reading and block any function that falls outside the rule set. That

1
applies to account creation, deposits, withdrawals, and dispute handling, and it also applies when you switch devices or browsers. When you send a payment through DANA, OVO, GoPay, or QRIS, the transaction record sits inside the same policy layer as your account data, so our checks
2
stay tied to the same identity and contact details. If you need clarification, use the verified email or phone on file so we can confirm the request without exposing your record to the wrong person.

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

CONTACT PATHS

How to reach us on legal matters

When you need a legal change or a question about access, we route it through the contact path tied to your profile. That keeps the request easy to trace and lowers the risk of someone else changing your record. Use the channel you already verified, then send the exact item you want checked, the email on file, and the time you noticed the issue.

Team online

Live chat

Open every day 08:00-24:00 WIB for access questions, record checks, and policy clarification. We answer inside the same session so your request stays linked to the account.

Use the number stored in your profile when you need a quick identity match or a correction. We compare it with the phone on file before we change anything.

Email

Send the full case, including your account email and the page you were reading. We reply in the same day when the queue is light, and we keep the thread attached to your record.

DATA & ACCESS

How we handle data and access

We keep this policy practical: only the data needed to run your account, answer your request, and meet the local rule set is retained.

Data handling

We store only the details needed for identity checks, account contact, and transaction records. If local law permits access, those records let us confirm who sent the request and why it belongs to your profile.

Cookies

Cookies remember your session, language setting, and device state so you do not repeat the same step on every page load. You can clear them in your browser, then sign in again on Android Chrome or iPhone Safari.

Account security

Your verified email or phone stays the key for sensitive changes. If a request comes from a new device, we pause it until the match is complete and the record is tied back to the same contact.

Retention

We keep legal and account records only as long as needed for service, security checks, and dispute handling. After that window, the file leaves active use and stays available only where local law requires it.

Change requests

To request a correction or deletion, send the exact field, the account email, and the reason. We use that copy to locate the record, confirm your identity, and log the change for audit tracing.

Access checks

If access is restricted by local law, we leave the profile visible but block the affected function. That separation helps you see what is available without pushing you into a wrong action.

Questions about access and records

If you want to know what the policy means for your account, start here. We answer how access is checked, which details we store, how to ask for a correction, and what happens when local law changes. The same process applies whether you opened the page on Android Chrome, iPhone Safari, or desktop, and the reply goes back to the contact on file.

Access depends on local law and is available only where local law permits. If your area is not permitted, we keep the account from using the blocked function and explain which part of the policy applies.

We keep the contact details, device signals, and transaction history needed to confirm who owns the request and how the account has been used. That lets us check the record without asking you to repeat everything each time.

Send the request from the email or phone number on file, name the exact field you want changed, and add the reason. We verify the match first, then update the record and log the change.

Some account records stay in storage for legal, security, or dispute reasons even after you stop using the profile. Where local law allows deletion, we remove what we can and keep only what must stay.

The same policy works on Android Chrome, iPhone Safari, and desktop browsers. If you switch devices, we may ask for another check before allowing a sensitive change on the account.

We reply through the verified channel on file, usually email or the chat thread tied to your account. If the message is about data or access, we keep the response short and tied to the request.

Payment records from DANA, OVO, GoPay, and QRIS sit inside the same legal file as your account profile. That helps us match the request, confirm timing, and answer you with the right reference.

Legal terms for your account access

How to reach us on legal matters

Live chat

WhatsApp

Email

How we handle data and access

Data handling

Cookies

Account security

Retention

Change requests

Access checks

Questions about access and records

01 Can I access jeptoto from Indonesia?

02 What data do you keep for legal checks?

03 How do I ask for a correction to my account data?

04 Can I ask for my account records to be removed?

05 Which device paths are covered by this policy?

06 How do you contact me about a legal request?

07 Do payment records follow the same policy?

Related Pages