Reference

jayatogel Privacy Policy for Indonesia

jayatogel Privacy Policy explains how we collect, use and protect the account, wallet and device details connected with your access.

Account recordsWallet detailsCookie choicesMobile access
jayatogel jayatogel Privacy Policy for Indonesia
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact path helps when your account record or wallet reference needs attention. Use the support route connected to your account area and describe the request in plain English, including the phone number tied to your account and the relevant transaction reference. We use those details to locate the correct record without asking you to send a password or complete wallet credentials.

Team online

Account correction

Ask us to correct a name, phone number or account detail through the account support route. We may verify ownership before changing records linked to DANA, OVO, GoPay or QRIS activity.

Privacy access request

Request a copy or explanation of personal data connected with your account. Include the phone number used for verification so we can separate your request from another account.

Wallet record query

For a payment-status question, send the wallet rail and reference shown in your account, such as QRIS or bank transfer. Never send a PIN, password or one-time security code.

DATA PRACTICES

What We Protect Behind Your Login

Your privacy choices work alongside the account controls you use every day. We separate identity checks from payment references, limit internal access to operational needs, and record security events so unusual sign-ins…

Collected account data

We collect the phone number and account details needed for access, together with verification status, sign-in time and device signals. We do not need your wallet PIN or bank password to match a transaction.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match payment status and resolve disputes. We retain the reference rather than asking for your private payment credential.

Cookies on mobile

Cookies can keep your session and selected privacy settings available on the same browser. If you clear them on Android or iPhone, sign in again and choose your settings when prompted.

Account security

Phone verification supports account ownership checks, while sign-in and device events help us identify unusual access. Keep your password and verification code private; our support route will not need either.

Retention choices

We keep account, security and payment references for the time needed to operate access, resolve disputes and meet applicable obligations. When that purpose ends, records are deleted or anonymised where suitable.

Requesting changes

You can ask for access, correction or clarification through the support path beside your account area. We may confirm your identity first, and some requests depend on local law or an active legal duty.

Privacy Policy Answers Before Access

These Privacy Policy answers address the account and wallet questions you may have before opening access. We keep each response tied to the records we actually use, from phone verification and mobile cookies to payment references and requests sent through support.

The Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes.

No. We use transaction references and payment status to match account activity. Your DANA or QRIS PIN, bank password and one-time security code should stay with you and should not be sent to support.

We use your phone number to create and locate your account, complete phone verification before access, support sign-in checks and respond to account requests. We do not treat it as a wallet password.

Yes. Send an access or correction request through the account support route, naming the phone number connected with your account. We may verify ownership, and the outcome depends on local law.

Clearing cookies removes browser session preferences from that device, but it does not automatically erase account or transaction records. Sign in again and contact support if you need a formal data request.

We retain payment references, account records and security events only for operational needs, dispute handling and applicable legal duties. Once the purpose ends, we delete or anonymise records where appropriate.

Yes. Use the support path linked on our account access page and ask about a specific data practice. Access or eligibility is where local law permits, and we will explain the applicable request route.