Privacy vs Terms
Terms govern how you use the lobby; this page governs the data we hold. They reference each other but never duplicate clauses, so a change here does not silently amend the contract you accepted at sign-up.
This is the trana4d privacy policy — the page that tells you what we collect when you open an account, why we need it, and how long we...
trana4d collects the minimum data needed to run your account: your sign-in details, verification fields, device fingerprint, and the wallet reference you link for top-ups. Where local law permits, we retain transaction logs for the period required by Indonesian financial regulation, then we purge them. We never sell your information to third parties, and marketing contact stays opt-in. You can request a
copy of your record, ask us to correct a field, or close the account entirely — our support desk processes those requests inside one business cycle. This policy applies across every supported region we operate in, and any change is published on this page with a fresh effective date so you always read the current version.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If anything in this policy needs clarifying, or you want to action a data request, these are the channels our privacy desk monitors. We aim to respond inside one business cycle.
We treat the privacy page as a living document. Here's what shapes how it gets written, reviewed and revised across the year.
Our compliance team re-reads this policy each quarter against Indonesian data rules and updates wording where regulators have shifted expectations. The effective date at the top tells you which review cycle you're reading.
Every clause goes through a plain-English pass so you don't need a lawyer to parse it. If a sentence can be shortened without losing meaning, we shorten it before publishing the new version.
A single internal owner signs off on what we collect and why. That person answers escalations from our support desk and approves any new field added to the sign-up flow.
Material edits are noted with a short change summary so returning account holders can see what shifted since their last visit. Cosmetic fixes like typos do not trigger a new effective date.
Our data handling is reviewed by an external assessor on an annual basis. Findings feed back into this policy and into the technical controls our engineering team operates behind the lobby.
If you spot wording that reads ambiguously, the privacy inbox accepts feedback alongside formal requests. We've rewritten several clauses on the back of account-holder questions over the past year.
Our terms, cookie notice and privacy page are written as a set. Here's how this page lines up with the rest so you can read across them without contradictions.
Terms govern how you use the lobby; this page governs the data we hold. They reference each other but never duplicate clauses, so a change here does not silently amend the contract you accepted at sign-up.
Tracking technologies are summarised here and detailed in the cookie notice. Consent toggles live in your account settings, and rejecting non-essential cookies does not block lobby access.
Identity verification fields are listed here, while the KYC page explains the document review steps. Retention windows match across both pages so there is one source of truth for how long we hold scans.
DANA, OVO, GoPay and QRIS data flows are described here at a policy level; the payments page covers the operational side. Wallet tokens are stored, raw card numbers are not.
Marketing contact is opt-in and revocable. This page sets the rule, the preferences panel applies it, and unsubscribing from email does not affect transactional account messages you still need to receive.
Support transcripts are retained under the windows declared here. Agents see only the fields needed to resolve your ticket, never the full record unless escalation rules require it.
Account closure triggers the deletion timeline noted in this policy. Some records persist for regulatory reasons even after closure, and those carve-outs are listed in plain language rather than buried.
These are the visible building blocks of our privacy page so you know where to look for each topic without scrolling the whole document twice.
A short list of the fields we capture at sign-up and during play, written without jargon. If a field is optional, we mark it optional so you know what you can skip.
Each data category is paired with a purpose — account security, regulatory reporting, fraud checks or service improvement — so nothing sits in our system without a reason you can read.
We state how long each category stays on file and what triggers deletion. Windows align with Indonesian financial record-keeping rules where those rules apply to our operation.
Access, correction, export and closure controls are described in one block so you can action them in a single sitting rather than hunting across multiple help articles.
We list the narrow circumstances where data leaves our systems — payment processors, regulators, our auditor — and confirm we do not sell account information to advertisers.
The effective date and a short change summary appear at the top of the page after every material edit, so returning account holders can read just the delta instead of the whole policy.