Reference

Privacy Policy for Your Wallet Data

tanganemas Privacy Policy shows how we collect, use, protect and retain the account details connected to your lobby, including phone verification before access and wallet records from DANA…

Account dataWallet recordsCookie choicesPhone verification
tanganemas Privacy Policy for Your Wallet Data
CONTACT ROUTES

Privacy Policy Help Through Your Account

A clear contact route helps you act on this Privacy Policy without sending sensitive details to the wrong place. Start from the support contact shown inside your account, describe whether the request concerns login data, a wallet receipt or a correction, and include only the reference needed to locate it. We use the account step and phone verification result to help confirm that the request belongs to you.

Team online

Account data request

Use the support contact displayed after login when you want to ask what account details we hold, why a phone verification record appears, or how to request a correction under this Privacy Policy.

Wallet record check

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference and status shown in your account. We use that limited detail to trace the wallet record without asking for your wallet password.

Privacy contact path

If your request concerns cookies, device signals, retention or deletion, identify the account email or phone number through the stated support route. We may ask for an account step before changing personal data.

DATA PRACTICE

Six Ways We Handle Your Account Data

Our privacy process follows the path your account takes: you enter details, complete phone verification, sign in, use a device and connect a wallet.

Account details

We collect details you submit for account creation and phone verification, then use them to provide account access, protect against unusual login activity and respond to a request linked to your account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can include a reference, amount, time and status. We use these fields to match activity and resolve receipt questions.

Cookies and devices

Cookies and device signals help remember session choices, identify a repeated login and protect the account. You can manage cookie settings in your browser, although some account steps may then work differently.

Security checks

We may review login events, phone verification and device changes when an account request looks unusual. These checks help us protect your details before discussing wallet records or changing account access.

Retention periods

We keep account, security and transaction records for the period needed for their stated purpose, dispute handling or a legal requirement. When a category is no longer needed, we remove or separate it.

Your requests

You can contact us through the account support route to ask for access, correction, deletion or an explanation of processing. We may verify your account before acting, and local law can affect eligibility.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the details you are most likely to check before opening an account or connecting an Indonesian wallet. We explain what we collect, why payment references appear, how cookies work on mobile and which account step helps us process a request. If your situation is not covered, use the support contact shown in your account.

It covers account details, phone verification, login events, device signals, cookies, support messages and wallet references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security checks and how to request access, correction or removal where local law permits.

A payment rail creates a reference, amount, time and status that may be needed to match activity to your account. We use those details for receipt questions, status checks, security and dispute handling, not as permission to collect unrelated wallet credentials.

When you sign in on a phone, we may receive session, browser and device signals used for account continuity and security. These signals can appear when you move from login to the mobile lobby; cookie controls in your browser can change how that path works.

Use the support contact displayed inside your account and ask for an access request under this Privacy Policy. State the account phone number or email used at login, provide only the requested reference, and complete any account check needed before we disclose personal details.

Yes, you can ask us to correct inaccurate account details, a phone verification record or a linked contact detail through the stated support route. We may compare the request with your login and verification records before changing it, and local law can set limits.

We retain each category for the period needed for its stated account, security, dispute or legal purpose. Wallet references and login events may therefore follow different periods. When a record is no longer needed, we remove it or keep it in a separated form.

Where local law permits, you can request deletion of eligible personal data through the account support contact. We first confirm the request belongs to you, then assess whether a record must remain for security, a transaction dispute or a legal requirement before responding.