Reference

topcar55 Privacy Policy for Indonesia

Our Privacy Policy explains what we collect when you open a topcar55 account, why phone verification is needed before account access, and how we handle device, wallet and…

Account clarityWallet data careDevice-aware accessLocal-law wording
topcar55 topcar55 Privacy Policy for Indonesia
CONTACT ROUTES

Privacy Questions Through Your Account

A clear support route helps you ask about the Privacy Policy without sending sensitive details through an unrelated channel.

Account support path Use the support route attached to your signed-in account when you need a copy of personal records or want to ask how phone verification data is used. We can connect the request to your account step without asking you to post private details publicly.
Wallet receipt check For a DANA, OVO, GoPay or QRIS question, share the relevant receipt reference through account support rather than forwarding your wallet password or full security code. We use the reference to locate status records and keep the request focused on your Privacy Policy rights.
Access correction request If a device record, phone number or account detail appears wrong, tell us which field needs attention and why. We may ask you to complete an account check before changing it, so another person cannot alter your records through an unverified request.
HANDLING PRACTICES

What We Do With Account Data

We apply the Privacy Policy through ordinary account controls rather than broad collection for its own sake.

Account details

We use the details you submit to create and maintain your account, respond to requests and apply access checks. Phone verification may be required before entry. If a name or number changes, contact us through the account support path so we can confirm the request first.

Device signals

A mobile browser and a desktop browser can create different sign-in records. We use practical device and session signals to protect account access, identify unusual login patterns and reduce confusion when you move from a phone to another device.

Cookies and sessions

Cookies may retain essential session choices, sign-in state and security controls while you move through account pages. Clearing browser cookies can end a session or require another account check. Your browser settings provide controls for optional cookie behaviour where those controls are available.

Wallet references

We handle transaction references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks. These references help us match a receipt or status request. We do not need your wallet password for that purpose, so never include it in a support message.

Security checks

We may compare phone verification, sign-in records and device signals when an account request looks unusual. These checks protect your records and can delay a change until we confirm it is really you. Keep your account credentials private and sign out on shared devices.

Retention requests

We keep records only for the account, security, payment-status or legal purpose that requires them, subject to local requirements. Through support, you can ask what we hold, request a correction or ask whether deletion is available; access depends on local law.

Privacy Policy Answers For Account Holders

These Privacy Policy answers address the account actions you are most likely to ask about before opening an account or checking a wallet status. We keep the examples practical: phone verification, mobile sessions, cookies, QRIS receipts and support requests. If a request depends on a legal requirement, we explain the next account step through support.

The topcar55 Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains why we use each category, how you can request access or correction, and when a legal or security reason may limit a request.

Phone verification helps connect account access to the person completing the account step and helps us protect records from an unverified change. We may use the verification result for access and security checks, not as a public profile. Eligibility depends on local law.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records. We use them to match a receipt or status request. Send only the needed reference through support, never a wallet password.

We may use device and session signals such as browser context, sign-in timing and security events to recognise unusual access. A mobile browser and desktop browser can show separate records. These details support account protection and are handled under the Privacy Policy.

You can ask for a copy, correction or clarification through the support path connected to your account. State the record involved, such as a phone number or QRIS reference, and complete any identity check we require. Access depends on local law and record-retention duties.

Cookies can keep an essential session active, remember security settings and reduce repeated sign-in confusion. If you clear them, your mobile or desktop browser may ask you to authenticate again. Browser controls can manage optional cookies where those controls are available.

Retention depends on the purpose of the record, such as account security, receipt matching, support handling or a legal requirement. We do not promise one period for every category. Ask through account support what applies to your record; where local law permits, deletion may be considered.