Reference

mos5 tebet Privacy Policy Explained

mos5 tebet Privacy Policy shows how we collect, use and protect the details connected with your account, including phone verification and DANA, OVO, GoPay or QRIS records.

Account clarityWallet recordsCookie choicesAccess requests
mos5 tebet mos5 tebet Privacy Policy Explained
CONTACT ROUTES

Ask About Your Privacy Policy

A clear contact path helps when you want to ask about the Privacy Policy or a record linked to your account.

Account support Use the signed-in support route for a Privacy Policy question, access request or correction…
Wallet record help If your concern involves DANA, OVO, GoPay or QRIS status, send the transaction reference…
Policy clarification For questions about cookies, device signals, retention or a correction, mention the exact Privacy…
DATA CONTROL

How We Handle Account Privacy

Our privacy process follows the account actions you take rather than treating every detail as permanent profile data.

Account data

We use details such as your account identifier, verified phone reference and login history to provide access and answer account requests. A request about another mos5 tebet account cannot be completed from your session without the required identity check.

Payment references

Wallet and bank records are handled as payment references and status evidence, not as a request for your wallet PIN. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear in a confirmation trail when you use an available rail.

Cookies and devices

Cookies can remember a session path between login and the lobby, while device signals help us detect repeated or unusual access. On a phone, you can adjust cookie permissions in the browser settings; the same controls apply on desktop.

Account security

We use phone verification, session checks and account activity signals to reduce unauthorised access. Keep your verification code private and sign out on shared devices. If a login looks unfamiliar, use the account support route and describe the event.

Retention choices

We retain records only while they support account operations, payment reconciliation, security checks or legal duties. Retention can differ by record type. You may ask us to explain a record's purpose, request correction or ask whether deletion or restriction is available.

Request changes

To request access, correction, deletion or a use restriction, contact us through the signed-in support route and identify the relevant account record. We may verify your phone or account details first, then respond according to applicable law.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening or using your mos5 tebet account. They cover data collection, wallet references, mobile cookies, corrections and requests for account access. If your situation is not listed, use the support path above and avoid sending passwords, wallet PINs or unnecessary identity documents.

It covers data connected with account creation, phone verification, sign-in, device signals, cookies, support messages and payment references. It also explains how we use those records for access, security, payment status checks and legal duties, where local law permits.

Phone verification helps us connect an account request with the correct person and reduce unauthorised access. It can also support a privacy request when you ask to see or correct account data. Keep every verification code private and do not place it in support messages.

Our Privacy Policy does not ask you to provide a DANA, OVO, GoPay or QRIS PIN. We may receive a payment reference or status confirmation from the selected rail. For help, send the receipt reference only, never your wallet password or security code.

Cookies can keep a browser session connected while you move from login toward the lobby, and device signals can help identify unusual access. You can change cookie permissions in your mobile browser. Some sign-in or session functions may not work as expected after changes.

Yes, you can ask for access to account records through the signed-in support route. Include your account identifier and the type of record requested, such as phone verification or a QRIS receipt. We may confirm your identity before sharing data, subject to applicable law.

Send a correction request through account support and identify the inaccurate field or payment reference. We may ask you to complete an account check before changing it. If the record comes from DANA, OVO, GoPay, QRIS or a bank rail, we may need matching evidence.

The period depends on the record and whether it supports account operation, payment reconciliation, security or a legal duty. Our Privacy Policy does not set one period for every record. You can ask support to explain the purpose and whether deletion or restriction is available.