Reference

pacutogel Privacy Policy For Your Account

Our Privacy Policy explains what account data we collect, why we use it, and how you can ask about changes before opening an account.

Clear data purposesWallet detail handlingPhone verification contextPolicy access on mobile
pacutogel pacutogel Privacy Policy For Your Account
DIRECT POLICY HELP

Get Policy Help Near Your Account

A clear support path matters when a Privacy Policy question arrives beside a login or wallet check. We keep policy requests connected to the account route, so you can identify the relevant phone number, payment reference or device without sending unrelated details. From Denpasar or another Indonesian location, use the available support chat path to ask about data access, correction, retention or account privacy. Access remains subject to local law.

Team online

Policy questions

Use our support chat when you need to understand which account details we hold or why a phone verification step appears. Include the account contact you use with pacutogel, and we can direct the request to the policy handling path without asking you to repeat unrelated wallet details.

Wallet references

For a Privacy Policy request connected to DANA, OVO, GoPay or QRIS, share the payment reference only through the account support route. We use that reference to locate the relevant record, while the wallet balance, PIN and private access code remain yours to protect.

Access concerns

If a mobile or desktop sign-in looks unfamiliar, contact support before sending additional documents. Tell us the device path, approximate access time and account contact. That gives our team a focused starting point for checking account security and explaining the data involved.

DATA HANDLING DETAILS

How We Apply This Privacy Policy

The Privacy Policy is applied through ordinary account steps rather than hidden profile settings. We separate identity details, payment references and device signals by purpose, then limit access to the operational reason…

Account records

When you open an account, we use the submitted contact details to create your access record and send account-related replies. Phone verification happens before account access is completed, helping us connect a request to the correct account without relying on a public name alone.

Payment data

A DANA, OVO, GoPay or QRIS reference can be retained with the account event it relates to. Bank transfer and virtual account records follow the same purpose: matching a submitted payment event and resolving a status question, not collecting your wallet PIN.

Cookies

Cookies can keep your session and account route working between pages. They may also record basic page activity used to maintain the site. You can review cookie controls in your browser, although blocking required cookies may interrupt login or the move from account access to the lobby.

Device signals

We may use device type, browser details and sign-in timing to identify an unusual access pattern. A mobile path and a desktop path can therefore produce different security checks. These signals support account protection and are not a request for your device passcode.

Retention choices

We retain account and transaction references only for the operational, security or legal period that applies to the record. When that period ends, the record can be removed or separated from direct account use. A retention request can be raised through the same support route as a data access request.

Change requests

You can ask us to correct account details, explain a data use, provide the data connected to your account or clarify deletion limits. Send the request through support with your account contact and the specific change. We verify account ownership before making an alteration.

Privacy Policy Questions About pacutogel

These Privacy Policy answers cover the practical searches we expect before account access: collected data, wallet references, cookies, mobile devices, correction requests and local eligibility. We keep the wording direct so you can decide what to ask before using the support path. For any request involving your account, we may need to confirm ownership first, and every access decision depends on local law.

Our Privacy Policy covers contact details, phone verification records, sign-in activity, device signals and payment references connected to your account. We use these details for account access, security, support and transaction status checks. We do not need your DANA, OVO, GoPay or QRIS wallet PIN.

Phone verification helps us confirm that the person requesting account access or a data change controls the account contact. It can also reduce mistaken replies when several records share similar details. We use the verification event for account security and policy requests, subject to local law.

Yes. The Privacy Policy explains how we handle payment references linked to DANA, OVO, GoPay and QRIS activity. Those references help us match an account event or investigate a status question. We do not ask for your wallet PIN, private wallet password or device passcode.

Cookies can keep your account session active and help the page remember the route between sign-in and the lobby. Some cookies support basic page activity checks. You can manage them through your browser settings, but blocking required cookies may affect account access or page continuity.

You can contact support to request the account data connected to you, ask why a record is used or request a correction. Include your account contact and describe the exact record. We verify ownership before responding, and the available action depends on local law.

We keep records for the period needed for account operation, security, payment matching or an applicable legal requirement. The period can differ between a phone verification event, a device signal and a DANA or bank transfer reference. Ask support to explain the retention status of a specific record.

Use the support chat path connected to your account and state that your request concerns the Privacy Policy. Mention whether you need access, correction, deletion clarification or retention details. Providing the account contact and relevant reference helps us route the request without collecting unnecessary extra data.