Reference

top4d Privacy Policy For Your Account

Our Privacy Policy explains how top4d handles the details connected with your account, including phone verification, device signals and wallet references when you use pages such as Speed…

Account dataDevice signalsWallet referencesCookie choices
top4d top4d Privacy Policy For Your Account
REQUEST A RESPONSE

Switch To Support For Privacy Questions

A clear support path matters when you want to check a record, correct an account detail or ask why a security step appeared.

Account help For a copy, correction or access request, open account help after signing in and describe the specific record involved. We may ask for phone verification before discussing account-linked details.
Cashier status If a DANA, OVO, GoPay or QRIS reference looks incorrect, share the visible status and time shown in your account. We use those details to investigate without requesting your wallet PIN.
Policy request For cookie choices, deletion questions or a concern about data handling, send a focused request through our support path. Please write from the account contact route so we can verify ownership.
HOW WE HANDLE DATA

Browse The Controls Behind Your Privacy

Privacy work happens across account access, device checks, payment matching and support records rather than in one isolated screen.

Account details

We use your submitted account details to create and maintain access, complete clear phone verification and respond to account requests. You can ask us to correct information that no longer reflects your current details.

Payment references

Cashier records may show DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We compare status, amount and timing signals for reconciliation, while avoiding requests for wallet passwords or PINs.

Cookies and devices

Cookies can remember session choices, while device and browser signals help identify suspicious access. You can ask support about these records and adjust available cookie choices through the account path.

Security checks

A new phone, browser or unusual sign-in may trigger an additional account check. We use that event to reduce unauthorised access and may require phone verification before sharing private account details.

Record retention

We keep account, payment and support records only for operational, security or legal needs. When a record is no longer required, we remove it or separate it from direct account identification.

Change requests

You can request access, correction or deletion by contacting us through the signed-in support route. We verify the request, explain any legal retention need and confirm the action taken.

Ask About Privacy Policy Access

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening access. Each answer points back to a practical action, from checking cookies on your device to requesting a correction through support. If your location has a separate rule, access depends on local law.

It covers account details, phone verification, device and browser signals, cookies, payment references, support messages, security events and retention. It also explains how to request access, correction or deletion.

Phone verification helps connect an account request with the person who controls the account. We may use it before discussing private details, changing account information or responding to a record request.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use visible status and transaction details for matching and security.

We may receive browser type, device signals, session details and security events when you sign in from a phone or desktop. These details help identify unusual access and maintain a working session.

Open the signed-in account help route and specify the records you want to access. We verify ownership before responding, then explain the available data and any lawful reason for withholding part of it.

Yes. Send a correction request through the account support path with the affected detail and the replacement information. We may use phone verification before changing account-linked records.

Retention depends on the record and its operational, security or legal purpose. When that purpose ends, we remove the record or separate it from direct account identification where practical.