Reference

panjat4d Privacy Policy for Your Account Data

Our panjat4d Privacy Policy explains what we collect when you open an account, verify your phone, sign in from a mobile browser, or use DANA and QRIS.

Clear data purposesWallet record contextAccount access controlsRequest path included
panjat4d panjat4d Privacy Policy for Your Account Data
REQUEST ROUTES

Reach Support About Your Account Data

A clear support route helps when a privacy question is connected to login or wallet status. Use the support link attached to your account to ask about a stored detail, a phone verification record, or a payment reference. We keep your request focused on the account and transaction context, including cases where a DANA or QRIS status needs checking.

Team online

Account data request

Tell us which account detail you want clarified, such as your phone verification record or sign-in history. Include the account identifier shown in your account area so we can locate the correct record.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account references, share the visible transaction reference rather than a wallet password. We use that detail to check the matching account event.

Access concern

If your account opens differently on mobile and desktop, contact us through the account support path. We can separate a device sign-in signal from the personal details held for your account.

DATA CONTROL

Explore How Account Data Stays Controlled

We treat privacy as an account process rather than a broad statement. The policy explains why a record exists, how it supports account access or payment matching, and how you can ask…

Collected account details

We may handle details needed to create and protect your account, including contact data, phone verification results, sign-in events, and device signals. We use these records for the stated account purpose rather than unrelated requests.

Cookies and sessions

Cookies and session markers can help keep your account area connected while you move from login to the lobby on a mobile browser. They may also help us identify an interrupted session without storing your wallet password.

Account security

Phone verification before account access gives us an account event to check when login stalls. We also use sign-in and device signals to investigate unusual access without asking you to post private credentials in a support request.

Retention of records

We retain account, support, and payment references only for the period connected with their stated purpose, account protection, or a legal requirement. A request can ask us which category applies to a particular record.

Policy changes

If this Privacy Policy changes, we will present the updated wording through the policy area so you can check the new data purpose before continuing with account access or wallet activity.

Changing your details

Ask us to correct an inaccurate account detail through the support path linked to your account. State the field that needs changing and provide the account identifier, while keeping passwords and wallet credentials private.

Browse Privacy Policy Answers Before Opening

These Privacy Policy answers address the account questions we expect you to ask before opening access from Indonesia. They cover payment references, cookies, device activity, corrections, and contact steps, while access remains subject to local requirements and the wording depends on local law.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps connect account access with the correct account and gives support a record to check when login stalls. We handle the result for account access and protection purposes described in the Privacy Policy.

Yes. It explains how we may retain a DANA or QRIS transaction reference to match a wallet event with your account, check a payment status, and respond to a related support request.

Cookies and session markers can keep your sign-in connected while you move from a mobile browser to the lobby. They help recognise an interrupted session but are not a request for your wallet password.

Yes. Use the account support path, identify the field that appears inaccurate, and include your account identifier. We can then assess the correction request against the relevant record and policy purpose.

Retention depends on the record category, its account or security purpose, and any applicable legal requirement. Ask support about a specific account, support, or payment reference for a category-based explanation.

Use the support link connected with your account and describe the privacy issue without sending passwords or wallet credentials. Access and eligibility depends on local law, and we will address the relevant policy path.