Reference

Privacy Policy for Your tante777g Account

The tante777g Privacy Policy explains what we collect when you open an account, sign in on mobile, or use DANA, OVO, GoPay and QRIS payment steps.

Account dataWallet recordsCookie choicesAccess requests
tante777g Privacy Policy for Your tante777g Account
CONTACT YOUR WAY

Privacy Help for Login and Wallet Records

A clear contact route matters when a Privacy Policy question concerns your own account rather than a general explanation.

Account contact path Use the support contact shown after login when you want to ask what personal data we hold. We may request an account step or phone verification before discussing private records, so a request is connected to you rather than another account.
Payment record check For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate date through the account support route. We use that reference to locate the wallet event without requesting your wallet password, PIN or other secret credentials.
Access recovery If your phone verification or login stalls, start with the account help path and explain whether the issue appears on mobile or desktop. We use the device and session details you provide to investigate access while keeping unrelated account data out of the request.
DATA HANDLING DETAILS

What Our Privacy Controls Cover

We keep this policy practical by linking each privacy choice to a real account action. A login creates security records, a payment creates a matching reference, and a mobile visit may create…

Account security

Phone verification helps us check that an account request comes from the account holder. We may review sign-in time, device type and security events when access looks unusual. These records support account protection and are not a reason to ask you for a private wallet PIN.

Cookies and sessions

Cookies can keep a signed-in session working, remember selected settings and help us understand whether a login page loads correctly. On mobile, browser storage may support the path from phone verification to the lobby. You can manage cookie settings through your browser controls.

Wallet references

Payment records can include a method name, transaction reference, amount and status supplied by the payment route. This applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use the record to reconcile activity, investigate disputes and display the correct account status.

Device behaviour

When you move between a phone and desktop, we may receive browser, operating system and connection details tied to the session. These details help us identify failed loads or unusual sign-ins around Live Blackjack Gold, Barong Dance Slots or other account pages without replacing your account identity.

Retention requests

We keep personal data only while it serves account security, transaction matching, dispute handling or a legal requirement. A deletion or retention question should include the account contact path and requested record type. Some records may remain when a legal or security reason requires continued storage.

Changes and corrections

You can ask us to correct a phone number, account detail or inaccurate transaction description through support. We verify the request before changing data, then may retain the earlier value in a security or transaction history where needed to explain what changed and when.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect before registration. They explain the information connected with a phone-verified account, mobile browsing, local wallet references and requests made through support. If your situation involves a legal restriction or a record that cannot be identified from the available details, we may ask for clarification before responding. For account-specific help, use the signed-in contact path and keep passwords, PINs and one-time codes private.

The Privacy Policy covers account details, phone verification, login and device events, cookies, support messages and payment references. It explains how we use those records to provide access, check security, reconcile DANA, OVO, GoPay, QRIS and bank transfer activity, and respond to requests about your data.

We use phone verification to connect an account request with the person seeking access and to reduce mistaken or unusual sign-ins. The event may include a time and security result. If access or eligibility is discussed, it depends on local law and the applicable account checks.

Yes. The Privacy Policy includes payment references and status information linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those details to match a receipt with your account. We do not need your wallet PIN or password for that matching step.

Cookies and similar browser storage can keep a session active, remember selected settings and help us identify a failed account page. On a phone, they may support the path from login to account pages. Your browser controls provide options to delete or restrict cookies.

Yes. Send a correction request through the signed-in account contact path and name the detail that appears wrong, such as a phone number or account label. We may verify your identity first. If a historical transaction record must remain unchanged, we can explain that distinction.

Retention depends on why the record exists. Account security events, payment references and support messages may remain while needed for access protection, reconciliation, disputes or legal duties. You can ask us to explain a particular retention period, although some records cannot be removed immediately.

Use the support contact shown inside your account and request a copy or explanation of the data linked to you. Include the relevant account step, date range or payment reference, but do not send a password or one-time code. We may complete an identity check before replying.