Reference

Privacy Policy For Your Account Path

parking4d uses a clear Privacy Policy to explain what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextPhone access checksPolicy request path
parking4d Privacy Policy For Your Account Path
CONTACT YOUR DATA TEAM

Privacy Policy Help Near Account Access

A clear contact path matters when your Privacy Policy question concerns a phone check, a wallet record or an account sign-in.

Account support Use the support route connected to your account when you want to ask how we handle your profile data, phone verification record or sign-in history. We may ask for account details so we can confirm ownership before discussing private data.
Wallet status query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, include the payment rail and the relevant account event. We use that context to locate a transaction reference while keeping the request focused on Privacy Policy handling.
Data change request Ask us to correct account details or explain a stored record through the same support path. We review the request against your account access and may need a phone verification step before changing or disclosing personal data.
HOW WE HANDLE RECORDS

Device, Cookie And Account Safeguards

The Privacy Policy is practical: it connects each data type with a reason for keeping it and a route for your request.

Account details

When you open an account, we store the details needed to identify that account and support its access path. Phone verification helps us check ownership before we discuss private records or process a request to change account data.

Device sessions

A sign-in from your phone or desktop can produce session, browser and device signals. We use them to recognise access events, investigate unusual sign-in activity and connect a Privacy Policy request with the correct account session.

Cookie choices

Cookies can keep a session working and help us remember settings across the account path. Your browser controls some cookie choices; if a cookie question affects access, tell support which device and browser you used.

Wallet references

Payment records may show a rail such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account and a related reference. We use that narrow context for reconciliation and support rather than treating it as a general profile.

Retention purpose

We keep records for as long as needed for the stated account, security, support or transaction purpose, subject to local requirements. When a retention purpose ends, handling follows our deletion or restriction process where local law permits.

Request verification

Before we disclose, correct or restrict personal data, we may compare your request with account and phone details. This step protects your records from an unverified message and gives us a clear audit trail for the policy response.

Privacy Policy Questions About parking4d

These Privacy Policy answers address the account questions you are most likely to have before opening access from Indonesia. We explain the data connected with login, devices, cookies and local wallet references without turning the policy into a general lobby description. If your case involves a specific account event, include that detail through support so we can respond to the right record.

The Privacy Policy covers data linked to your account, phone verification, device sessions, cookies, support requests and wallet references. It explains why we handle each type, how we protect access and how you can ask for correction, restriction or clarification where local law permits.

We may collect account identifiers, contact details used for access, phone verification results, sign-in events and support messages. If you use DANA, OVO, GoPay, QRIS, bank transfer or virtual account, we may also receive a transaction reference needed to match the account event.

Yes. The Privacy Policy covers device, browser and session signals created when you sign in from a phone or desktop. We use these signals for account security, session continuity and access checks, not as a reason to request unrelated personal details.

Use the account support route and state which detail needs correction, removal or restriction. We may ask you to complete phone verification or provide matching account details before acting. That check confirms the request comes from the account owner where local law permits.

We treat DANA and QRIS references as transaction context connected with your account, alongside OVO, GoPay, bank transfer or virtual account records. We use that context to check wallet status, answer support requests and maintain a necessary account history.

Retention depends on the purpose for collecting the data, such as account access, security, wallet reconciliation or a support request. We keep records only as needed for those purposes and applicable local requirements, then follow deletion or restriction procedures where local law permits.

Contact us through the support path connected with your account and describe the Privacy Policy concern in clear terms. Include the device path or payment reference only when relevant. We may verify your phone or account details before discussing private records.