Reference

jepangqq Privacy Policy For Your Account

Your account details, device signals and wallet references stay connected to a clear Privacy Policy, so you can understand what we use and why.

Clear data purposesWallet record clarityAccount access controlsIndonesia policy context
jepangqq jepangqq Privacy Policy For Your Account
HELP PATH

Privacy Help Through Your Account Path

A clear contact route matters when a name, phone number or wallet reference needs attention. From your signed-in account, use the support path near the cashier area and describe the specific record you want us to check. You can include a payment receipt or transaction reference, while hiding your PIN and other secret credentials. We use the details you send only to locate the request and respond to you.

Team online

Account request

Tell us whether you need access, correction or removal of a personal record. Include the email or phone number attached to your account so we can match the request safely.

Wallet question

For DANA, OVO, GoPay or QRIS concerns, send the transaction reference and visible status rather than a wallet PIN. This helps us investigate the payment record without asking for secret credentials.

Support route

Use the support channel shown after account login when a privacy request involves a receipt, device sign-in or phone verification. We may ask account questions before discussing personal details.

DATA PRACTICES

Data Handling From Login To Wallet

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We may store the contact details you enter during account creation and phone verification. These details help us recognise your account, send account-related replies and check that a privacy request comes from you.

Device signals

Your browser type, sign-in time and basic device signals can help us identify unusual access. The same checks apply whether you open the lobby on a phone in Surabaya or on a desktop.

Cookies

Cookies can keep a session active, remember necessary settings and help the account path load correctly. You can manage cookies through your browser controls, though some account functions may then need another sign-in.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain the reference and status needed to reconcile your account. We do not ask for your wallet PIN or bank password.

Account security

Phone verification and sign-in checks help protect your account from unauthorised access. Never share a verification code with anyone; if a sign-in looks unfamiliar, contact us through the signed-in support path.

Retention requests

We keep records only as long as needed for the stated account, payment, security or legal purpose. To request a change, send the record name and reason; we will check identity before applying an update.

Questions About jepangqq Privacy Policy

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain what we collect, how wallet records are matched, how to request a change and what happens when access depends on local law. If your question is more specific, use the account support path with the smallest useful amount of detail.

The jepangqq Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number for account identification and the verification step before account access. It can also help us match a support request, but we do not need your wallet PIN or bank password.

No. Our Privacy Policy distinguishes a payment reference or status from a secret credential. We may receive transaction details needed for reconciliation, but you should never send us a DANA, OVO or QRIS PIN.

Sign in, open the support path near the cashier area and name the record you want changed. Include your account phone or email, but remove passwords, verification codes and wallet secrets from your message.

We retain each record for the account, payment, security or legal purpose that requires it, then assess whether it is still needed. A retention request can be sent through account support for checking.

You can open the account path from a supported mobile browser, complete phone verification and reach the policy or support links from your account area. Availability depends on local law and local access conditions.

Use the support channel displayed after login and select the privacy-related route, then describe the issue with a transaction reference or account detail where relevant. We may verify account ownership before sharing personal data.