Reference

Privacy Policy for Your tahun33 Account

DANA, OVO, GoPay and QRIS records are covered alongside your login details in the tahun33 Privacy Policy, so you can see what we collect before opening an account.

Clear data categoriesWallet record handlingAccount contact pathIndonesia access context
tahun33 Privacy Policy for Your tahun33 Account
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact path helps when you want to ask what data we hold or correct an account detail. Start from the support route connected to your tahun33 account and include the phone number or email used during registration, without sending a password. We use the account record to locate your request, then explain the next step in writing. If your question concerns a wallet status, attach the relevant reference while hiding any full card or banking credentials.

Team online

Account request

Use the account support route to ask about stored details, phone verification or a correction. Include your registered contact detail so we can match the request to the correct tahun33 record without asking you to disclose a password.

Payment record

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and date through support. We can check the associated status while you keep your wallet PIN, one-time code and complete bank credentials private.

Policy question

When a Privacy Policy point is unclear, write the section or subject you mean and tell us what action you want. We will use the contact route shown in your account to explain access, correction or deletion steps.

DATA PRACTICES

How tahun33 Handles Your Data

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

Account details

We may collect your registration contact, phone verification result and account identifiers so we can open the correct account session.

Device signals

Login time, browser or mobile device signals can help us spot an unusual access attempt.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be recorded to match a payment status with your account.

Cookies

Cookies and similar browser storage can keep a session working, remember selected settings and help us understand an access error.

Retention

We keep account, support and transaction records for the period needed to provide the requested service, protect accounts and meet…

Security changes

Before changing phone details, access credentials or an account contact, we may ask for verification linked to the existing record.

Privacy Policy Answers For tahun33

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain what data is used, how you can reach us and what happens when your request involves login, device or payment records. If your situation is not listed, send the specific account subject through the contact route and we will assess it under the same policy.

It covers account details, phone verification, login and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity. It also explains our uses, retention approach, security checks and request routes.

A payment reference lets us match a wallet or bank transfer status with the correct account and investigate a receipt question. We may record the reference and status, but you should never send a wallet PIN, one-time code or complete banking credential.

You can contact us through the support route linked to your account and ask for the data access process. Include your registered contact detail and the categories you mean, such as login records or QRIS references, so we can assess the request accurately.

Send a correction request from the account contact route and identify the detail that needs changing. We may verify your existing phone or email before editing the record, which helps prevent another person from changing your account information.

The same policy applies when you use a phone browser to sign in, complete phone verification, enter the lobby or check a wallet status. Device and session signals may be used to protect access and diagnose a failed login or QRIS step.

You can submit a removal request through the account support route, explaining which records you mean. We assess the request against active account needs, security protection, transaction reconciliation and applicable legal duties before confirming what can be removed.

Yes. Account access and eligibility depend on local law and are available where local law permits. If you need to understand how that affects a data request, contact us with your account region and the Privacy Policy subject you want clarified.