Reference

tempo33 Privacy Policy For Your Account

Our Privacy Policy explains how we handle the account, wallet and lobby data you provide when you use tempo33.

Account dataWallet statusDevice accessPolicy requests
tempo33 tempo33 Privacy Policy For Your Account
CONTACT ROUTES

Reach Support About Privacy Requests

A direct support route helps you raise a Privacy Policy question without explaining your concern repeatedly. Start from the account help area or the cashier-related support path, then include the email or phone detail linked to your tempo33 account. We use that account step to locate the relevant record before discussing access, correction or deletion. If a payment receipt is involved, keep the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference available. Our support team can also clarify which request needs identity confirmation.

Team online

Account help

Use the account help route for a Privacy Policy request about your name, phone verification, login record or stored contact detail. We may ask you to confirm the account before discussing personal data, so another person cannot obtain details from a shared device.

Cashier records

For a wallet-data question, send the payment reference through the cashier support path. Mention whether it concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, and we can connect the request with the correct transaction record.

Access questions

If a privacy request affects account access, contact us before creating another account. Tell us whether you are using a mobile browser or desktop, and we can explain the next identity step where local law permits access to the service.

DATA PRACTICES

Explore How We Handle Your Data

Our Privacy Policy is practical: it connects each data use with an account action you can recognise.

Account details

We collect details needed to create and maintain your account, such as contact data and phone verification status. We use those details to recognise your account during login and support conversations, rather than asking you to repeat private data in every message.

Payment references

A DANA, OVO, GoPay or QRIS status can be linked with an account reference so we can investigate a cashier mismatch. Bank transfer and virtual account records may be handled in the same way, with the payment reference used for reconciliation.

Device records

When you move from a mobile browser to desktop, technical details may help us understand a login event or protect the account. We use device records for access and security checks, not as a reason to request unrelated personal content.

Cookies

Cookies can retain a session, remember a selected setting and help the Privacy Policy load consistently. Your browser controls whether cookies are accepted. Removing them may require you to sign in again or repeat a preference on the next visit.

Retention

We keep records only for the operational, security, dispute or legal purpose connected with them. A retention request should identify the account detail or payment reference involved, because different records may have different deletion eligibility.

Change requests

Ask us to correct an inaccurate account detail or explain how a record is used through account support. Include the phone or email connected with your account, and we can apply the appropriate verification step before making a change.

Browse Privacy Policy Answers For tempo33

These Privacy Policy answers focus on the account steps Indonesian customers usually need before opening or using tempo33. We cover the data connected with login, mobile access, cookies and local wallet records, along with the contact route for corrections or deletion requests. If your question concerns a particular transaction, include its reference rather than sending a full payment screenshot. Where access or eligibility is discussed, it depends on local law and the applicable account conditions.

The Privacy Policy covers data connected with your account, phone verification, login activity, device access, cookies, support conversations and payment status. It also explains retention, security handling and how to contact us about correction, access or deletion requests.

Phone verification helps us connect the account with the correct contact detail and reduce mistaken or unauthorised access. We may use the verification result during support or account recovery, while service access depends on local law and the applicable account process.

We use wallet details and payment references to identify transaction status and match a cashier update with your account. The same approach can apply to bank transfer or virtual account records. Send only the reference needed for the Privacy Policy request.

Yes. The notice includes technical records linked with your mobile browser or desktop session, such as login timing and device signals used for security checks. These records help us investigate access concerns without requiring unrelated content from your device.

Use account support and identify the data you believe is wrong, such as a contact detail or phone verification record. Include the account-linked phone or email so we can confirm ownership before reviewing and correcting the relevant entry.

You can submit a deletion request through account support. We first confirm the account and assess whether the record must remain for security, dispute handling or a legal requirement. Where deletion is permitted, we will explain the applicable next step.

Contact support with the page, device type and browser involved. Cookies may retain a session or setting, and clearing them can require another login. We can explain the relevant cookie use, while your browser provides the control for accepting or removing them.