Reference

Privacy Policy for Your jepang77 Account

Our Privacy Policy explains how jepang77 handles the account details, device signals and wallet records needed for your access.

Account clarityWallet contextDevice choicesLocal access
jepang77 Privacy Policy for Your jepang77 Account
REQUEST ROUTES

Get Help With Privacy Requests

A clear contact path matters when a data question affects your account or wallet record. Start from the support contact shown inside your jepang77 account and describe the exact request, such as…

Account data request Ask for a copy of the personal data linked to your account through the support contact in your account area. We use the phone verification step to confirm that the request concerns your records.
Wallet record check For DANA, OVO, GoPay or QRIS receipts, include the transaction reference and date. We can direct the status question to the cashier path while keeping your wallet credentials private.
Correction request Tell us which account detail needs changing and why it is inaccurate. We may request a matching account detail before updating the record, so another person cannot alter your profile.
DATA PRACTICE

How We Protect Your Account Data

We handle privacy as part of the account path, not as a separate promise hidden from your wallet activity.

Account details

We collect details such as your phone number and verification result to create and secure your account. The same check helps us discuss private records with the correct account holder.

Payment references

A DANA, OVO, GoPay or QRIS entry can include a reference, amount status and time. We use these details to match a receipt or investigate a stalled wallet record.

Device signals

Login time, browser type and device signals can be recorded to identify unusual account access. On mobile, these signals help connect the login step with the lobby session.

Cookie choices

Cookies and similar storage may keep your session active or remember a selected setting. You can clear them in your browser, though this may require another login before account access.

Retention process

We keep personal records for the operational, security or legal period that applies to their purpose. When that period ends, records are removed or restricted through our retention process.

Change requests

Use the support contact inside your account to ask for access, correction or deletion. We confirm the request before changing a record and explain any limit that depends on local law.

Privacy Policy Questions Before Access

These Privacy Policy answers focus on the practical questions you may have before opening an account from Indonesia. We explain the records connected with login, wallets, cookies and mobile access, along with the account route for requesting a copy or correction. If your question concerns a specific DANA, OVO, GoPay or QRIS reference, keep its receipt details ready.

It covers account details, phone verification, login events, device signals, cookies, lobby session records and payment references. It also explains how you can request access, correction or deletion through our account support contact.

We use your phone number to create the account, complete the clear verification step and help prevent another person from discussing or changing your private account records.

Yes. The policy includes DANA, OVO, GoPay and QRIS references such as transaction status, date and receipt details used to match a wallet event or resolve a cashier question.

Open the support contact shown inside your account and state that you want a copy of your personal data. We verify the account first, then respond with the records we can provide.

Yes. Describe the inaccurate field and the correction you need through the account support route. We may ask for a matching verification detail before changing the account record.

Cookies may keep a session active or remember a browser setting when you move from mobile login to the lobby. You can clear them in browser controls, but a fresh login may follow.

A request may be limited when records must remain for security, operational or legal reasons. Account access and any eligibility discussion depends on local law, and we explain the applicable reason.