Reference

tugubet Privacy Policy For Your Account

tugubet Privacy Policy explains how we collect, use and protect the details connected with your account, wallet activity and device access.

Account dataWallet recordsCookie choicesAccess requests
tugubet tugubet Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A clear contact route helps when your account details do not match a wallet receipt or when you want to ask what we retain.

Account privacy request Use the support channel shown after login to ask about a data record, correction or access request. Include your registered phone detail so we can identify the right account without requesting your DANA, OVO, GoPay or QRIS security code.
Payment record question If a wallet receipt or bank transfer reference appears in your account, send the transaction date and visible reference through support. We can check the payment record against your account while keeping private wallet credentials out of the conversation.
Policy contact path For a Privacy Policy question, mention whether you are asking about cookies, retention, phone verification or account access. Our support route can direct the request to the right privacy handling process where local law permits.
DATA HANDLING DETAILS

What We Do With Account Information

Privacy Policy choices matter most when they connect to real account actions, so we describe the handling behind sign-in, wallet checks and device sessions.

Phone verification

We use the phone detail you submit to support account access and verification steps. If that detail changes, contact us through the account route before creating a second profile, so we can assess the requested correction against the existing record.

Cookie controls

Cookies can help remember a session or measure how the policy page is reached. Where controls are available, you can adjust optional cookie choices in your browser or the site prompt; necessary session functions may still operate.

Wallet matching

A DANA, OVO, GoPay or QRIS reference may be used to match a payment status to your account. We do not need your wallet PIN or one-time security code to investigate a receipt or status question.

Account security

We use sign-in details, device signals and verification events to help detect unusual account access. Keep your password private, sign out on shared devices and contact support if a session or profile detail does not look familiar.

Retention periods

We retain account and payment records only as long as needed for the purposes described in this Privacy Policy, including security, dispute handling and legal duties. The period can differ by record type and applicable local requirements.

Change requests

You can ask us to access, correct or clarify personal data connected with your profile. State the requested change and the registered account detail; we may verify your identity before acting, and the outcome depends on local law.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or using the site from Indonesia. We explain the records connected with verification and local wallet activity, the practical contact route, and the limits that can apply when a request conflicts with security or legal duties. If your question is not listed, use the support path shown in your account.

It covers information connected with account creation, phone verification, sign-in, device access, support messages, cookies and payment references. That can include details linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account when needed to identify and reconcile an account transaction.

Phone verification helps us connect an account request with the phone detail you supplied and reduce mistaken or unauthorised access. We may ask you to confirm that detail when you request a correction or access to records, subject to the requirements that apply where you are located.

Our Privacy Policy does not require you to send a wallet PIN, password or one-time security code through support. We may retain visible transaction references, status details or receipt information needed to match a DANA, OVO, GoPay or QRIS payment with your account.

Use the support channel shown after login and state that you want an account data access request. Include your registered phone or email detail and specify the records you mean, such as profile data, cookie choices or payment references. We may verify identity first.

Yes, you can request a correction through the account support route. Tell us which profile field is wrong and provide the accurate replacement detail. We may compare the request with phone verification or account history before making a change, and the result depends on local law.

Retention depends on the type of record and why it was collected. We may keep account, security or payment records for the period needed to resolve disputes, protect access or meet legal duties. The applicable period can vary, and we explain the request path if you need clarification.

Where local law permits, you can adjust optional cookie choices through the site prompt or your browser settings. Necessary session cookies may still be used for sign-in and account security. If the available controls do not answer your question, contact us through support.