Reference

tor388 Privacy Policy For Your Account

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

Account clarityWallet recordsDevice controlsCookie choices

Explore Our Lobby Read FAQ

How This Privacy Policy Applies

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

Our Privacy Policy covers details you provide during account creation, including your contact details and the verification step required before account access. It also covers technical records from your phone or computer, such as browser type, session time and pages opened, plus transaction references connected with

1
DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these records to confirm that an account request matches the account holder, trace a wallet status question and protect the account from unusual access. We keep only what is needed for these purposes and
2
handle requests according to applicable requirements. Access and eligibility depends on local law, and this policy applies where local law permits.

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

CONTACT PATHS

Where To Ask About Privacy

A direct support path helps when you want to ask what data we hold or why a record appears beside your account.

HANDLING DETAILS

Six Practical Privacy Controls

Privacy protection works through ordinary account steps rather than hidden settings. We separate account identity from wallet references, record the device signals needed for session protection, and use cookies to remember necessary…

Data we collect

We collect details you enter for account creation and verification, payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account, and technical session data needed to keep account access functioning.

Why we use it

We use account and device details to confirm identity, detect unusual sign-ins, match a payment reference to the correct account, answer support requests and maintain records required for the account relationship.

Cookies on your device

Necessary cookies can keep a session open and remember security choices. Your browser settings can remove or block cookies, although doing so may require another account check before the lobby or privacy page loads.

Account security steps

Before we discuss personal records or change account contact details, we check the request against the account. Never share a password, wallet PIN or one-time verification code through a support message.

Retention of records

We retain account, verification and transaction references only for as long as needed for the stated purpose, account support and applicable obligations. When a record is no longer needed, our process removes or separates it.

Requesting a change

You can ask us to correct an inaccurate contact detail, explain a stored record or raise a deletion question through the account support route. We may need ownership confirmation before making any change.

Privacy Policy Answers For tor388

These Privacy Policy answers address the account questions you are most likely to have before opening access. They explain the records connected with verification, wallets, cookies and devices in plain terms. If your situation is not covered, use the privacy contact path and describe the specific record or request. We will first confirm that you are asking about your own account.

It covers details used for account creation and verification, payment references from supported rails, device and browser session records, necessary cookies, support messages and retention steps. It explains why we use each category and how you can ask about, correct or question a record.

Yes. We may keep a payment reference, amount status and related account link for DANA or QRIS, as well as OVO, GoPay, bank transfer or virtual account steps. We do not need your wallet PIN to investigate a status question.

Phone verification helps us connect an account request with the person requesting access and reduces mistaken or unauthorised changes. The Privacy Policy treats the verification detail as account data, so we use it for access checks, support and related security purposes.

You can request a correction through the account support path. State which contact detail or account record is inaccurate and provide the registered account identifier. We may confirm ownership first, then explain the change made or why further checking is needed.

Necessary cookies support session continuity, security checks and selected access settings on your phone or computer. You can manage them through browser controls. Blocking them may sign you out or trigger another verification step when you return.

We keep account, verification and transaction references for the period needed to provide account support, investigate a payment status and meet applicable obligations. The retention period can differ by record type. You can ask us to explain the reason for a stored record.

Yes. Send an access request through the privacy contact route with your registered account detail and the categories you want explained. We confirm ownership before sharing anything, and access or eligibility depends on local law and applicable requirements.

tor388 Privacy Policy For Your Account

Where To Ask About Privacy

Six Practical Privacy Controls

Data we collect

Why we use it

Cookies on your device

Account security steps

Retention of records

Requesting a change

Privacy Policy Answers For tor388

01 What does the tor388 Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 Why does tor388 ask for phone verification?

04 Can I ask tor388 to correct my personal data?

05 How does the Privacy Policy handle cookies?

06 How long does tor388 keep account records?

07 Can I request access to my tor388 data?

Related Pages