Reference

Privacy Policy For Your talas98 Account

talas98 Privacy Policy explains what account, device and wallet details we use when you open an account, verify your phone and enter the lobby.

Account dataDevice choicesWallet recordsYour requests

Explore Our Lobby Read FAQ

How Indonesia Data Requests Are Handled

talas98 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to details you submit during account opening, the phone verification step before account access, and activity connected with the lobby. That can include your contact details, sign-in records, device type, approximate connection data and payment references. When you use DANA, OVO, GoPay,

1
QRIS, bank transfer or a virtual account, we use the payment status and reference needed to match your account request; we do not ask for wallet credentials inside the lobby. We use records to provide account access, check unusual sign-in activity, answer support questions and meet
2
applicable legal duties. Requests to view, correct or remove eligible data are assessed individually. Access depends on local law, and some records may need to remain available where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where To Ask About Personal Data

A clear contact path helps when you want to understand a Privacy Policy choice or check a record linked with your account. Tell us the phone number or account identifier connected to the request, describe the change you need and avoid sending a wallet password or full payment credential. Our support desk can direct account, receipt and privacy questions to the right handling path. Keep your request specific so we can verify ownership without exposing another person's details.

Team online

Account access

For a Privacy Policy question tied to phone verification or sign-in, include your account identifier and the device type you used. We will ask for ownership details before discussing records, so a request about your account does not reveal data to another person.

Wallet records

If a DANA, OVO, GoPay or QRIS reference appears beside your account, send the visible reference and date rather than wallet credentials. We can explain which payment record is attached to the account and route a correction request for assessment.

Privacy requests

For access, correction or deletion questions, state the exact data concern and the phone number linked to your account. Our support desk can confirm the next step, explain any legal limit and tell you when more ownership checks are needed.

DATA PRACTICES

Six Privacy Controls Behind Your Account

Privacy depends on small account controls working together, so we explain what each one does rather than leaving the policy abstract.

Account details

We use the details you enter at account opening to create your account, send account-related responses and match later privacy requests. Before discussing those details, we may compare your request with the phone verification step used for account access.

Device signals

A mobile browser can provide device type, session data and connection signals that help us keep sign-in activity connected to the right account. These signals are used for account protection and service operation, not as a substitute for your account details.

Cookie choices

Cookies or similar storage can retain a session, language choice or selected device setting. Clearing them may require you to sign in again. Our Privacy Policy explains the purpose of this storage, and support can address a question about a particular browser session.

Payment references

We record the reference, status and timing needed to connect a wallet or bank payment with your account. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI details are handled as payment context, not as wallet passwords.

Security checks

Phone verification and sign-in checks help us respond when account access looks unusual. If you contact us after a device change, we may ask for account ownership details before discussing Privacy Policy records or changing the contact information on file.

Retention requests

We assess a request to view, correct or remove personal data against its purpose and any applicable legal duty. Contact the support desk with the relevant account identifier; we will explain what can change, what must remain and why.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the questions we expect before you open an account or ask about an existing record. They cover the data connected with sign-in, mobile use, local wallets, payment references, cookies and requests for correction or removal. Where a question depends on jurisdiction, we will assess it under applicable rules and tell you the handling path through our support desk.

It covers account details, phone verification, sign-in activity, device and session signals, cookies, payment references and support requests connected with your account. It also explains why we use each category, how long records may remain and how you can ask about access or correction.

No. Our Privacy Policy concerns the payment reference, status and timing needed to match a transaction with your account. We do not ask you to send a wallet password to support. For a payment question, provide the visible reference and date instead.

Phone verification links an account request to the right person, while device and session signals help us investigate unusual sign-in activity. We use those details for account access and protection. A device change can lead to an ownership check before records are discussed.

Contact our support desk with your account identifier, the data category involved and the change you are requesting. We first check account ownership, then assess the request under applicable rules. The Privacy Policy process may allow access or correction where local law permits.

We retain records for the period needed for the stated account, security, support or payment purpose, and for any applicable legal duty. The exact period can differ by record type. Ask support about a specific record and we will explain the relevant handling path.

You can ask us to assess cookie, session or device records connected with your account. Clearing browser storage may sign you out and remove a local setting immediately. Our Privacy Policy request process determines what can be removed or must remain.

Account and data handling depends on local law. Where local law permits, we process requests using the steps described here, including ownership checks and purpose-based retention. If a local rule changes the response, our support desk will explain that limitation for your request.

Privacy Policy For Your talas98 Account

Where To Ask About Personal Data

Account access

Wallet records

Privacy requests

Six Privacy Controls Behind Your Account

Account details

Device signals

Cookie choices

Payment references

Security checks

Retention requests

Privacy Policy Questions Before Account Access

01 What does the talas98 Privacy Policy cover?

02 Does talas98 store my DANA, OVO, GoPay or QRIS password?

03 Why does Privacy Policy mention my phone and device?

04 How can I request a copy or correction of my data?

05 How long does talas98 keep account and payment records?

06 Can I ask for cookies or device records to be removed?

07 Does Privacy Policy access apply everywhere in Indonesia?

Related Pages