Reference

gip4d Privacy Policy for Your Account

Our gip4d Privacy Policy explains what account details we collect, why we use them and how you can ask about your records before opening an account.

Clear data purposesWallet status contextPhone verificationIndonesia access terms
gip4d gip4d Privacy Policy for Your Account
CONTACT ROUTE

Ask About Your Privacy Policy Rights

A clear contact route matters when you want to question a data record or change an account detail. Start from the support path linked to your account and state the phone number or account reference connected with your request; this helps us separate your request from another account. If a wallet status stalls, include the payment receipt reference rather than sending wallet credentials. We use the same route for Privacy Policy questions, access requests and concerns about a device session. Your account page remains the practical starting point for a privacy request.

Team online

Account data request

Use the account support path to ask which personal details are connected with your gip4d profile. Include your account reference and the requested action, such as a copy, correction or clarification, so we can direct the request to the right record.

Wallet reference check

If your DANA, OVO, GoPay or QRIS status needs checking, send the receipt reference shown in your payment record. We do not need your wallet password or personal wallet access details to investigate a matching status.

Access concern

When an unfamiliar device session or phone verification issue appears, use the account help route before trying repeated logins. We can use the account reference and device details you provide to review the access concern without asking for your private wallet credentials.

HANDLING DETAILS

How We Handle Your Account Data

Privacy at gip4d is managed around the account steps you actually take: creating access, confirming a phone number, checking a payment reference and returning to the lobby from a recognised device.

Account creation

When you open an account, we collect the details needed to create your login path and connect phone verification with that profile. We do not describe a wallet password as part of our account record, and you should never send one through support.

Phone verification

A phone check helps us link an access request to the correct account before private account details are displayed. If the number changes, ask through the account support path so the record can be corrected after the required identity checks.

Cookies and sessions

Cookies can keep your session connected while you move from account access to the lobby on a mobile browser or desktop. Clearing browser cookies may sign you out and remove session preferences, but it does not automatically erase account records.

Device signals

We may use device and login signals to spot an unusual access pattern, protect your account and investigate a disputed session. These signals help with security decisions; they are not a request for your DANA, OVO, GoPay or QRIS password.

Retention period

We retain account, verification and payment-reference details for as long as needed for the purpose described, account protection or a legal obligation. To ask why a record remains, contact us with the account reference and the category of data concerned.

Change or deletion

You can ask us to correct, access or delete eligible personal details through the account support route. Some records may need to remain when security checks, transaction matching or legal duties require them; we will explain the reason connected with your request.

Privacy Policy Answers for gip4d

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening access. We keep the wording practical: what is collected, how a request is made, what cookies do and why a payment reference may appear in an account record. If your situation is not covered, use the account support path with your reference and ask for the relevant privacy team.

The gip4d Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references, retention and privacy requests. It explains why we use each category and how you can ask for access, correction or deletion where that request is available.

We use your phone number to create and protect the account access path, including a verification step before private details are shown. If your number is incorrect or no longer available, contact account support with your reference so we can explain the change process.

No. Our payment record may contain a route, receipt reference or status connected with DANA, OVO, GoPay or QRIS, but you should not send wallet passwords to us. Those credentials stay with the relevant wallet service and are not needed for a status check.

Use the support path connected with your account and ask for an account data request. Provide your account reference, phone number used for verification and the type of record you want to access. We may need additional checks before releasing private account details.

Yes, you can request a correction or deletion of eligible data through account support. We may retain records needed for account security, payment matching or a legal duty. Our reply will explain whether the requested change can be made and why any record remains.

Cookies help keep your session connected when you move between account access and the lobby on a mobile browser or desktop. Clearing them can sign you out or remove preferences, but it does not itself erase account data; request record changes through support.

For Indonesian customers, the Privacy Policy applies where local law permits, and access depends on local law. Before submitting account details, check the policy page and the access terms shown for your location. Contact support if you need clarification about a privacy request.