Reference

terminaljp Privacy Policy And Your Account

Our Privacy Policy explains how terminaljp handles the account, wallet and device details you provide when you open an account and access the lobby.

Clear data purposesWallet record controlsPhone verificationCookie choices

Browse Our Lobby Read FAQ

Open The Privacy Policy Before Account Access

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

This Privacy Policy applies when you create, verify or use your terminaljp account, contact our support desk, or connect a wallet for a transaction. We may handle your name, phone number, account activity, payment references, device details, security logs and messages sent to support. DANA, OVO,

1
GoPay and QRIS may provide transaction status or reference data needed to match a deposit or withdrawal request. We use those records to operate the account, investigate mismatches and protect access. The policy applies where local law permits, and local legal requirements can affect eligibility, retention
2
or the way a request is handled. If you use a shared phone, sign out after checking the lobby and keep your verification code private.

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

CONTACT ROUTE

Get Privacy Policy Help Through Support

A clear contact route matters when a Privacy Policy question concerns your account rather than a general request. We ask you to contact our support desk from the email or account contact linked to your terminaljp profile, so we can match the request safely. Include the subject of your request, the phone number on the account and any relevant payment reference, while leaving out your password or verification code. We can then explain the next step for access, correction, deletion or a wallet record question.

Team online

Account contact

Use the support route connected to your account when you need a Privacy Policy answer. We may ask you to confirm your registered phone number before discussing account data, helping us avoid sending personal details to the wrong person.

Wallet question

For a DANA, OVO, GoPay or QRIS record question, include the transaction reference and approximate date. We use that pair to locate the relevant entry without asking you to send a password, one-time code or full wallet credentials.

Access request

If you want to see, correct or remove personal data, state the request plainly through support. We confirm identity through the account path, explain any legal reason a record must remain, and tell you what action follows.

DATA PRACTICE

Explore How We Handle Your Privacy

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account data

When you open an account, we use your submitted contact details to create the profile and complete phone verification. Keeping those fields accurate helps us identify your account when you ask for a copy, correction or access change under this Privacy Policy.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us connect a wallet event with the correct account record. We do not need your wallet password for that matching step, and support can ask for a receipt reference when a status needs checking.

Device security

Your mobile browser may send device, session and sign-in signals that help us spot an unfamiliar access pattern. These signals support account protection; they are not a reason for us to request your private verification code.

Cookie controls

Cookies can keep a session working and help us understand page loading on mobile or desktop. You can manage browser cookie settings, although blocking required cookies may prevent the Privacy Policy page or account path from working as intended.

Retention checks

We retain account, support and transaction records only for the operational, security or legal purpose that requires them. A request to remove data may be limited when a payment or account record must remain for a lawful retention period.

Request changes

You can ask us to access, correct or delete eligible personal data through the registered account contact. Describe the exact field or record, complete our identity check, and we will explain the result and any restriction under local law.

Browse Privacy Policy Answers For terminaljp

These Privacy Policy answers cover the searches we hear most often before account access. They explain the practical difference between account data, payment references, cookies and security logs, along with the steps you can take through support. If your question involves a specific record, include its date and reference so we can identify the right account entry.

The terminaljp Privacy Policy covers data connected with your account, phone verification, sign-in activity, device signals, cookies, support messages and wallet transactions. It also explains why we use those records, how retention works, and how you can request access or correction where local law permits.

We may collect the contact details you submit when opening an account, your phone verification status, sign-in records, device signals and messages sent to support. We use these details to provide account access, protect the profile and respond to a Privacy Policy request.

Yes. The Privacy Policy covers payment references and status data connected with DANA, OVO, GoPay and QRIS transactions. Those records help us match a wallet event to your account and investigate a receipt or status mismatch without asking for your wallet password.

Contact support through the email or account route linked to your terminaljp profile and name the field you want corrected. Include your registered phone number for identity checking, but do not send a password or verification code. We will explain the next step and any applicable legal restriction.

Cookies can keep your session active and help us understand whether pages load correctly on your mobile browser. You can change cookie settings in that browser. Blocking required cookies may interrupt account access, while optional cookie choices can affect measurement or saved preferences.

We keep each record for the operational, security or legal purpose connected to it, rather than using one identical period for every field. Payment and account records may need longer retention. Support can explain the reason when you ask about a particular record.

You can submit a deletion request through the registered account contact. We first verify that you control the account, then check whether any record must remain for security, payment reconciliation or a legal obligation. Where local law permits deletion, we explain what will be removed and when.

terminaljp Privacy Policy And Your Account

Get Privacy Policy Help Through Support

Account contact

Wallet question

Access request

Explore How We Handle Your Privacy

Account data

Payment matching

Device security

Cookie controls

Retention checks

Request changes

Browse Privacy Policy Answers For terminaljp

01 What does the terminaljp Privacy Policy cover?

02 What account data does terminaljp collect?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a correction to my terminaljp data?

05 How does terminaljp use cookies on mobile?

06 How long does the Privacy Policy allow data to remain stored?

07 Can I ask terminaljp to delete my personal data?

Related Pages