Terms of Service
Terms govern your account contract; this privacy page governs the data inside that account. They cross-reference each other and use identical defined terms throughout.
This is the evo303 privacy policy page. We wrote it so you can see, in plain language, what we collect when you open an account, why we keep...
We collect the minimum we need to run your evo303 account: your sign-in identifiers, device fingerprint for security, and the wallet reference you choose at cashier. Where local law permits, we store this data in supported regions and process it only for account, fraud and compliance reasons. We never sell your details to third parties. If a regulator in your jurisdiction requires
disclosure, we follow the narrow legal route and log the request. You can ask us to export or erase your record at any time, subject to retention rules tied to anti-fraud obligations. Payment chips below are listed for context — this policy covers the data you share when you use them, not the cashier itself.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If something in this policy is unclear, or you want to act on a data right, talk to us through one of the routes below. The privacy desk is staffed by the same team that maintains this page, so answers come back quickly and in the same plain tone.
Email our privacy desk directly from the address linked to your evo303 account. We acknowledge within one business day and resolve most data requests inside seven, with a written summary at close.
Open the chat bubble in the lobby and ask for the privacy team. The agent will route you, verify your account, and log the ticket so your request is traceable end to end.
Prefer paper? Send a signed letter to the registered address shown at the foot of this page. We treat postal requests with the same timelines as email and reply through your preferred channel.
This policy is not boilerplate. It is reviewed by our internal team before each release and reflects how evo303 actually runs day to day. The signals below show how we keep it...
Each revision is signed off by a named compliance lead at evo303. Their initials appear in the change log so you can see who approved the wording you are reading right now.
Every change carries a visible date at the top of this page. We do not silently edit clauses; if a paragraph shifts, the revision marker moves with it for transparent reading.
We write in short sentences and avoid jargon stacks. If a legal term is unavoidable, we explain it inline so you do not need a glossary tab open while you read.
The policy reflects how Indonesian wallets and bank rails actually move data, not a generic global template. Local context is built into the retention and disclosure clauses you see here.
An external counsel reads the document each cycle and flags anything that drifts from current Indonesian data norms. Their feedback is folded back before we publish a new version.
This page lives at one permanent address. Older versions stay archived and linked at the bottom so you can compare what changed between any two policy releases on evo303.
evo303 keeps a small family of legal pages. We make sure their wording lines up so you do not get conflicting answers depending on which one you opened first.
Terms govern your account contract; this privacy page governs the data inside that account. They cross-reference each other and use identical defined terms throughout.
Cookies sit in a sibling document. This policy points to it for browser-side tracking detail, while keeping account-side data handling here for clean separation.
Wallet flows have their own page. We mention DANA, OVO, GoPay and QRIS here only as context for the data they generate, not for fees or limits.
Identity checks are described in the KYC page. This policy explains how the documents you upload there are stored, encrypted and eventually purged.
If a privacy answer does not satisfy you, the complaints page is the next step. Both documents share the same escalation ladder and response-time commitments.
Opt-in choices live on a separate preferences page. This policy documents how those preferences are stored and honoured across email, SMS and lobby messages.
A short retention table sits alongside this page, listing each data category and its hold period so you can match the prose here to specific timeframes at a glance.
The layout of this page is built for quick reading on a phone. Each block below describes a visible element you will see as you scroll, so you can jump straight to the part...