Reference

pos 4d Privacy Policy: Your Data And Account Path

Clear account, device and wallet handling sits at the centre of our pos 4d Privacy Policy.

Account clarityWallet recordsDevice controlsLocal-law access

How Our Privacy Policy Covers Your Details

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

Our Privacy Policy describes the details we receive, why we use them, and how you can ask about them. A phone number supports account verification, while login records, device signals and security events help us detect unusual access. Payment references can appear when you use DANA,

1
OVO, GoPay, QRIS, bank transfer or a virtual account; we use those references to match account activity rather than asking for unrelated personal details. Game activity, such as a Dragon Tiger session or a Counter-Strike 2 lobby visit, may be linked to your account history so
2
we can answer account questions accurately. Cookies and similar device storage help keep your session working. We retain records for the period needed for security, support and legal duties, then remove or restrict them through our retention process. Eligibility and access depends on local law, and
3
this Privacy Policy applies where local law permits.

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

CONTACT ROUTES

Privacy Questions Reach The Right Support Path

A direct support path helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record.

Account support chat Ask about a Privacy Policy request, phone verification record or login event through the account support chat. We match your request to the account step involved and avoid requesting passwords.

Wallet record check Send the payment reference, not your wallet password, when asking about DANA, OVO, GoPay or QRIS data. We can trace the account record and explain what was stored for that transaction.

Access request route Request a copy, correction or deletion assessment through support after account verification. Tell us which detail concerns you, and we will explain the available route where local law permits.

HANDLING PRACTICES

Six Practical Privacy Controls We Use

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

Phone verification

Before account access, we use the phone number you provide to confirm the account path. This reduces mistaken matches when you ask us to correct personal details or investigate a login.

Device signals

Login time, browser or device signals may be recorded to identify unusual access. These signals support account security and are not treated as a request for unrelated content from your device.

Cookie choices

Cookies and similar storage keep your session connected and remember necessary settings. You can manage browser permissions, although restricting essential storage may interrupt the account path or require another login.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain matching references and status details. We use them to resolve receipt questions without storing a wallet password.

Retention handling

We keep personal and account records only for security, support and legal needs connected to the service. When a retention period ends, records are removed or restricted under our internal process.

Change requests

You can ask us to access, correct or assess deletion of your details through account support. We verify the request against your account before making a change where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before account access. They cover the data connected with phone verification, wallet references, cookies, device behaviour and requests for changes. If your situation is different, use account support and describe the specific record or action you want us to check.

It covers account details, phone verification, login and device signals, cookies, payment references, game activity records, retention and requests to access or correct your information.

Phone verification confirms that an account request belongs to you. It helps us connect support questions with the right record and investigate unusual login activity without asking for your password.

Yes. We may keep payment references, receipt details and status information for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity so support can trace an account transaction.

Cookies and similar storage keep your session active and preserve necessary settings. Browser controls can restrict them, but essential restrictions may interrupt login or require you to start the account path again.

You can contact account support with a request for access to your personal and account records. We verify your identity first, then explain the available response where local law permits.

Use account support and identify the detail that needs correction, such as a phone record or payment reference. We compare the request with your verified account before updating eligible records.

We retain records for the time needed for security, support and legal duties. After that need ends, the records are removed or restricted through our retention process, subject to local law.

pos 4d Privacy Policy: Your Data And Account Path

Privacy Questions Reach The Right Support Path

Six Practical Privacy Controls We Use

Phone verification

Device signals

Cookie choices

Payment references

Retention handling

Change requests

Privacy Policy Answers For Your Account

01 What does the pos 4d Privacy Policy cover?

02 Why does pos 4d ask for phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 How are cookies used under this Privacy Policy?

05 Can I ask pos 4d for a copy of my data?

06 How do I correct details covered by the Privacy Policy?

07 How long does pos 4d keep my account data?

Related Pages