Reference

Privacy Policy for Your solana 4d Account

Our Privacy Policy explains what we collect when you open an account, use the mobile browser, or contact support about DANA, OVO, GoPay or QRIS.

Account clarityPayment recordsCookie choicesContact route
solana 4d Privacy Policy for Your solana 4d Account
HELP WITH YOUR DATA

Where to Ask About Privacy Policy

A clear contact path helps when your account details or payment record needs attention. Start from the account help route rather than sending identity documents through an unverified channel. Tell us which account step caused the issue, such as phone verification, a QRIS receipt or a wallet status showing incorrectly. We use the details you provide to locate the request and respond with the next privacy step.

Team online

Account help

Use the account help route to ask which personal details we hold, why a phone verification record is needed, or how to correct an account field. Include your registered contact detail so we can distinguish your request from another solana 4d account.

Wallet record

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and date rather than a wallet password or secret code. We can then locate the payment status while limiting the sensitive data included in your privacy request.

Access request

If you want a copy, correction or deletion request, state the action clearly and use the same account contact used during phone verification. We may ask for an account step to confirm the request belongs to you before making a change.

DATA HANDLING DETAIL

What Our Privacy Policy Covers

We keep this policy practical by linking each data use to an account action. A phone number supports verification, a payment reference helps reconcile a wallet status, and a device session helps…

Account details

We may collect your name, phone number, login records and verification status when you create or use an account. These fields help us confirm the account path and answer a request about access without treating unrelated browsing activity as an identity record.

Payment evidence

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account payment can create a reference, amount, timestamp and status record. We use those fields to match a receipt with your account and investigate a stalled cashier status without requesting your wallet secret.

Cookies

Cookies and similar browser storage can remember a session, language setting or security signal. On a mobile browser, they help keep your account path connected from phone verification to the lobby. You can manage browser cookie controls, although some account functions may then need another check.

Device security

We may record device and connection signals linked to a login, such as browser type, session time and security events. These signals help us investigate an unfamiliar sign-in and protect the account; they are not a request for unrestricted access to your device.

Retention

We retain account, payment and support records for as long as needed for account administration, dispute handling, security checks or legal duties. When a record no longer serves one of those purposes, our process moves it toward deletion or anonymisation where applicable.

Your requests

You can ask us to access, correct or delete personal data, subject to identity checks and legal exceptions. Send the request through account help, identify the relevant record, and tell us whether you need a copy, a correction or removal.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we expect before an account is opened or a payment query is raised. They explain the practical route for data access, corrections, cookies and payment records on solana 4d. If your question concerns eligibility, access depends on local law, so include your account region when you contact us.

The Privacy Policy covers account details, phone verification, browser cookies, device security signals, payment references and support messages. It also explains retention and the route for requesting access, correction or deletion. The policy applies when you create an account, sign in, use the mobile browser or contact us.

We use your phone number to support account creation, phone verification and account recovery checks. It can also help us connect a privacy request to the correct account. We do not need your DANA, OVO or GoPay secret code to handle a normal account or data request.

A payment may produce a reference, timestamp, amount and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those details to reconcile the account record and investigate a receipt or pending status. Wallet passwords and secret codes should not be sent to us.

Use the account help route and ask for a personal data copy. Include your registered contact detail, the account step involved and the date of your request. We may confirm phone verification or another account detail before releasing data, so the request is connected to the right person.

Yes, you can ask for a correction or deletion through account help. State which field or record is affected, such as an account contact detail or QRIS reference. We may retain some records for security, disputes or legal duties, and we will explain any applicable limitation.

Cookies can keep a mobile browser session connected, remember a language choice and support security checks between phone verification and account access. You can adjust cookie controls in your browser. If you block required cookies, we may ask you to verify the account again or some functions may not work.

We retain records while they are needed for account administration, payment reconciliation, security checks, disputes or legal duties. After that need ends, the record moves toward deletion or anonymisation where applicable. A request through account help can ask which retention reason applies to a specific record.