Reference

Privacy Policy for trans4d Accounts

Our Privacy Policy explains how we handle the account details, device signals and payment records connected with your trans4d access.

Clear data purposesWallet record contextAccount access choicesCookie controls
trans4d Privacy Policy for trans4d Accounts
CONTACT PATHS

Get Privacy Policy Help

A clear contact path matters when you want to ask what data we hold or correct an account detail.

Account support chat Use the support chat linked from your signed-in account when you need help finding…
Payment record help For a wallet question, send the payment receipt and the rail used, such as…
Policy request route When you want access, correction or deletion guidance under this Privacy Policy, state the…
DATA HANDLING

What We Do With Your Records

We keep the Privacy Policy practical by separating account operation from unrelated use of your details.

Account details

We use the details supplied during account creation and phone verification to create your profile, confirm ownership and respond to…

Mobile sessions

When you move from login to the lobby on a phone, we record session and device signals needed for access…

Wallet matching

DANA, OVO, GoPay and QRIS transactions can create references used to match a payment with your account.

Cookies and choices

Cookies can keep a session active, remember a language or device choice and support security checks.

Security records

Sign-in events, phone verification results and unusual access signals help us protect your account from mistaken or unauthorised use.

Retention requests

We retain records for as long as needed for the purpose described in this Privacy Policy, account servicing and required…

Privacy Policy Questions For You

These Privacy Policy answers focus on the account questions you are most likely to ask before opening access or using a local wallet. We explain the practical route for data requests, cookies, payment references and phone verification, so you can decide what to provide and where to contact us. If your situation involves eligibility or access, it depends on local law.

The trans4d Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains why we use each category, how we protect account access and how you can ask about correction, access, retention or deletion through the stated contact route.

Phone verification helps us confirm that an account request belongs to you and prevents support from disclosing records to the wrong person. We may use the verification result for account security and a privacy request, but you should never send your password or one-time code to our support team.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS when those references are used to match a transaction, check its status or answer your support request. We recommend sending receipts only through the signed-in account route shown for payment help.

Use the policy contact route shown on the trans4d page and state that you want access to your account data. Include the account phone number through the secure form, not in a public message. We may verify ownership before locating records and explaining the available response format.

You can request a correction when an account detail is inaccurate or out of date. Send the request through the account support path, identify the affected detail and provide the replacement carefully. We may ask for phone verification so the change is applied to the correct profile.

Cookies can support login sessions, security checks and saved device preferences. Your browser lets you remove or block them, but the account path may then ask you to sign in again or repeat a security check. The Privacy Policy explains these uses without requiring you to share wallet credentials.

Contact us through the route displayed with the Privacy Policy and ask which retention period applies to the record category in question. Mention whether your request concerns account details, support messages, device sessions or DANA, OVO, GoPay or QRIS references so we can direct it accurately.