Reference

Privacy Policy for Your gip4d Account

Your account, wallet choices and device access stay covered by a clear Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet recordsDevice choicesCookie controls

Browse The Lobby Read FAQ

How Your Account Data Is Used

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

Our Privacy Policy describes the account details we need to create access, confirm your phone and keep your session connected to the correct device. We use payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account to match a cashier action with your account,

1
not to create unrelated profiles. Login records, device signals and support messages help us investigate stalled access or an unclear payment status. We retain records only for operational, security or legal purposes that apply to the service. Access and eligibility depends on local law, and you
2
can ask us about a data use, correction or deletion request through the account support path.

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

CONTACT YOUR WAY

Three Ways To Ask About Privacy

A privacy question should not interrupt your account flow, so we keep the request path close to login and cashier status details.

DATA CONTROL ROOM

Six Privacy Checks We Keep Clear

We handle this policy area through practical account controls rather than vague promises. The same records that connect your phone verification, wallet reference and device session can help us answer a specific…

Purpose of collection

We collect account details to create access, confirm your phone, connect your session and answer support requests. Payment references from DANA, OVO, GoPay and QRIS help identify the cashier event you ask us to check.

Cookie choices

Cookies and similar device storage can keep login preferences or help us understand an active session. You can clear them through your browser settings, though clearing storage may require phone verification when you return.

Account security

We use phone verification and session signals to reduce mistaken access between devices. Never share your password, wallet PIN or verification code; if a session looks unfamiliar, contact us through the account support path.

Retention approach

We keep account, payment-reference and support records only while needed for service operations, security checks or legal duties. A deletion request may be limited where a record must remain for an applicable obligation.

Changing your details

Ask us to correct an account name, phone detail or other personal record through support after login. We may request a matching account step before changing data that could affect wallet or device access.

Who receives requests

Our account support team handles privacy questions and routes payment-reference issues to the relevant operational check. We do not need your wallet PIN or full payment credentials to start a request.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or ask us to change stored details. We keep the wording practical: what we collect, why a wallet reference appears, how device access works and where to send a request. If your situation is different, use the account support path and describe the exact record you want us to check.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security steps and how to request access or correction.

We use your phone number to create and confirm account access, connect the correct session and help investigate a login issue. Phone verification does not require you to send us a wallet PIN or a payment password.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account steps. These references help us match a cashier event with your account when you request support.

Use the account support path after login and ask for access to your stored personal data. Include your account identifier and the records you mean, such as device history or a QRIS reference. We may ask for an account check before responding.

You can request correction or removal through account support. Tell us which record is wrong or no longer needed, such as a phone detail or saved device signal. Some records may remain when security, service operations or local law requires retention.

Cookies or browser storage can remember session preferences and help keep your login connected to the right device. You can clear them in your browser settings. After clearing them, we may ask for phone verification before account access continues.

Requests, account eligibility and certain data rights depend on local law and the location connected to your access. We apply the relevant process where local law permits and explain any account step needed to confirm your request.

Privacy Policy for Your gip4d Account

Three Ways To Ask About Privacy

Six Privacy Checks We Keep Clear

Purpose of collection

Cookie choices

Account security

Retention approach

Changing your details

Who receives requests

Privacy Policy Questions From Indonesia

01 What does the gip4d Privacy Policy cover?

02 Why does gip4d need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a copy of my gip4d data?

05 Can I ask gip4d to correct or remove data?

06 How does gip4d use cookies on my phone?

07 Where does Privacy Policy access depend on local law?

Related Pages