Reference

katana35 Privacy Policy for Indonesia Accounts

katana35 Privacy Policy explains what we collect when you open an account, how we use account and wallet records, and how you can contact us about your data.

Clear data purposesWallet record detailsAccount access controlsContact and change requests
Explore The Lobby Read FAQ
katana35 katana35 Privacy Policy for Indonesia Accounts
CONTACT YOUR WAY

Get Help With Privacy Policy Requests

A privacy question should not leave you searching through the lobby. Use the support contact route shown inside your account and include the phone number or email attached to your profile, the request type, and any relevant payment reference. We can then locate the right record without asking you to send a password or full wallet credentials. If access depends on local law, we will explain the applicable path.

Team online

Account support route

Open the support contact path from your signed-in account when you need a copy, correction, or explanation under this Privacy Policy. We use your verified account details to match the request.

Payment record check

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, share the transaction reference only. We use the receipt and status trail to identify the relevant record.

Security concern

If you notice an unfamiliar login or device event, contact us through the account support path and change your password. Do not send your password, wallet PIN, or one-time code.

CONTROL YOUR RECORDS

What We Do With Privacy Requests

We handle privacy requests through the same account trail used for phone verification and payment status checks. That lets us separate your records from another account and reduce accidental disclosure.

Data we receive

We may handle your submitted profile details, verified phone number, login events, device signals, support messages, and transaction references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

Why records are used

Account and device records help us complete phone verification, restore a valid session, check wallet status, investigate payment mismatches, answer support requests, and protect access from unusual activity.

Cookies and device use

Cookies and similar device storage can keep your session, remember selected settings, and help us understand technical failures. You can manage available browser permissions, although some account screens may then behave differently.

Account security

We use phone verification and login-event checks as part of account protection. Keep your password and one-time code private, and contact support promptly if a device appears that you do not recognise.

How long we retain data

We keep records for as long as needed for the stated purpose, account support, security checks, transaction reconciliation, or applicable legal duties. The period can differ between profile, cookie, and payment records.

Requests and corrections

You can ask us to access, correct, or clarify eligible personal data through the signed-in support route. Include your account contact and request detail so we can verify ownership before responding.

Answers About katana35 Privacy Policy

These Privacy Policy answers cover the searches we hear most often before account opening. They explain the records linked to phone verification, mobile access, cookies, local wallets, and support requests without asking you to share sensitive credentials. If your situation is unusual, use the account contact path and describe the specific record or event you want us to check.

It covers personal details you submit, phone verification, login and device events, cookies, support messages, and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use your phone number to support account verification, help match you with the correct account, and protect login activity. Keep the number current so a privacy request can be checked safely.

Yes. The Privacy Policy explains that DANA and QRIS references may be used to confirm payment status, reconcile an account record, answer support questions, and investigate a mismatch without requesting your wallet PIN.

You can submit an access request through the signed-in support route. Include your account contact and describe the records sought; we verify ownership before sharing eligible data or explaining any restriction.

Cookies can keep your session active, remember settings, and help diagnose device errors. If you restrict them in your browser, login or account screens may require extra steps or display differently.

Yes, you can request a correction through account support and identify the inaccurate field. We may ask for verification before changing profile, phone, device, or transaction-linked information.

Use the account support path, describe the date or device event, and change your password. Never include a password, wallet PIN, or one-time code in a Privacy Policy request.

Related Pages

katana35 Indonesia Account information About Us Live Dealer Lobby Access guide