Reference

Privacy Policy for Your pagmatic4d Account

The pagmatic4d Privacy Policy shows how we handle your account, phone verification, device details and payment references when you use the lobby.

Account clarityWallet contextMobile access
pagmatic4d Privacy Policy for Your pagmatic4d Account
HELP ROUTES

Privacy Questions, Account Help Paths

A clear contact route matters when a data question and an account issue arrive together. We keep privacy support close to the account-help path so you can describe the request without sending wallet credentials or a full payment password. Include the phone number linked to your account, the relevant date, and a short description; we use those details to locate the right record. The same route can help when a receipt or status check needs a privacy explanation.

Team online

Data request

Ask us to explain the personal data connected with your account. Include your verified phone number and the subject of your request, but leave out your PIN, wallet password and one-time code. We may ask for account confirmation before discussing records.

Correction path

If your name, phone contact or account detail is inaccurate, send the existing value and the correction you want. We compare the request with the account record, then tell you whether the change can be made and what step follows.

Payment privacy

For a DANA, OVO, GoPay or QRIS receipt question, share the transaction reference and date rather than wallet login details. We use the reference to check status and explain which payment record is held, where local law permits.

SIX DATA CONTROLS

Six Controls Behind Our Privacy Policy

Privacy work is part of the account path, not a separate page you can only find after a problem.

Phone verification

Before account access is completed, we use the phone verification result to confirm that the account request belongs to you.

Session security

Login time, device signals and browser details can help us spot an unusual session or repeated access attempt.

Cookie choices

Cookies can keep your login path and selected page settings consistent between screens.

Wallet references

Payment records are used to reconcile a request, receipt or status check.

Retention handling

We keep account, security and transaction records only for the period needed for their stated purpose or an applicable legal…

Change requests

You can contact us to request access, correction or clarification about personal data linked to your account.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers focus on the practical questions you may have before opening or using a pagmatic4d account from Indonesia. They cover the records attached to phone verification, wallet references, cookies, device sessions, correction requests and contact steps. If your circumstances involve a location or eligibility question, access depends on local law; our support route can explain the policy process without asking for secret payment credentials.

It covers account and phone-verification data, device and browser signals, cookies, payment references, support messages, retention and requests to access or correct your records. It applies when you use the website on mobile or desktop, where local law permits.

No. We use transaction references and status details to reconcile DANA, OVO, GoPay or QRIS activity. Do not send a wallet password, PIN or one-time code to support. The Privacy Policy distinguishes payment records from private wallet credentials.

Phone verification helps us connect an account request with the person seeking access and helps protect a session when recovery is needed. We record the verification result and related security details for that purpose, subject to the handling described in our Privacy Policy.

Yes. Send a correction request through the privacy support path with your verified phone number, the detail that is wrong and the replacement value. We confirm the account before discussing records, then explain the result under the pagmatic4d Privacy Policy.

Cookies can preserve login continuity and page preferences as you move between account screens and the lobby. Browser settings can remove or restrict them, but necessary cookies may be required for access. The Privacy Policy explains their limited account and session purpose.

We retain payment references, account records and security logs only for the stated operational purpose or an applicable legal requirement. After that need ends, we remove or anonymise records where appropriate. A specific retention request can be sent through the privacy contact path.

Use the privacy support route and state whether you want access, correction, clarification or another data request. Include your account phone number and relevant date, but never your PIN or wallet password. We may verify ownership before responding, where local law permits.