Data Collected
Privacy lists every field; KYC explains the verification ones; cookies cover passive signals. The three together describe the full record we hold.
This is our privacy policy — the plain-English version of how we treat the details you share when you open an omiqq account. We cover what we collect...
omiqq processes your personal data where local law permits, and the rules shift depending on which supported region you sign in from. For Indonesia accounts we follow the data-protection framework that applies to electronic services, meaning your name, contact handle, KYC scans and wallet references stay on systems we control. When you fund through DANA, OVO, GoPay or QRIS we receive only
the transaction tokens — your wallet PIN never touches our servers. We keep records for the retention window the regulator sets, then we purge. If you sit outside a supported region, our policy defaults to the stricter standard, and lobby access pauses until your status is confirmed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
If something in this policy needs clarifying, or you want to act on a data right, three contact paths reach our privacy desk directly. We answer in the order requests arrive, and each channel logs your ticket so nothing slips between shifts.
Write to [email protected] with your account handle and the request type. We reply within two working days, and complex data-export tickets close inside the statutory window our region sets.
Open the chat bubble from any logged-in page and type 'privacy' to route straight to the data team. Useful when you need a quick read on what we hold against your handle.
For formal data-erasure or correction notices, post addressed to our registered compliance contact. Include a photo ID page so we can match the request to the account on file without delay.
This document isn't drafted once and forgotten. Six checks sit behind every line, and we list them so you can see the editorial weight we put on data...
Our retained counsel in Jakarta reads each policy revision before it goes live. They flag any clause that drifts from...
Every three months our compliance lead samples live tickets against the wording here. If the lobby behaves differently from what...
DANA, OVO, GoPay and QRIS integrators check the sections that touch their tokens. They confirm we describe the data hand-off...
Our infrastructure engineers contribute the storage and encryption language. They write what they actually run, so the technical claims here...
A dedicated editor strips jargon after legal approval. You shouldn't need a law degree to know what you signed up...
Each change carries a date and a short note describing what moved. Older versions stay on file for two years...
Our terms, cookie notice and KYC pages share a spine with this privacy policy. Here's how the seven core themes line up across documents, so you never get conflicting answers when you...
Privacy lists every field; KYC explains the verification ones; cookies cover passive signals. The three together describe the full record we hold.
Privacy sets the headline period. Terms repeats it inside the account-closure clause. Both numbers match — we update them together or not at all.
Privacy names the payment and verification partners. Terms references the same list when describing service delivery. No partner appears in one without the other.
Privacy explains access, correction and erasure. Terms confirms these survive account closure for the retention window. Wording is intentionally identical between docs.
Privacy describes encryption at rest and in transit. Our security page repeats the technical detail. Claims are kept consistent so audits don't catch a mismatch.
Privacy uses 'where local law permits'. Terms uses 'supported regions'. Same meaning, applied uniformly across every page that touches access.
All policy documents revise on the same quarterly cycle. When privacy changes, terms and cookies are reviewed in the same sprint to keep the set coherent.
The privacy page itself follows a layout we keep consistent across legal documents. Six visible elements anchor the experience, so you can find the clause you...
A sticky sidebar lists every clause heading. Tap one and the page jumps to that section. Useful when you've been pointed at a specific paragraph and don't want to read end-to-end.
The header carries the policy version and the date it went live. If a support agent quotes 'clause 4.2 of v2.4', the stamp confirms you're reading the same document they are.
A link at the foot opens the change log. Each entry describes what shifted, in one line, so you can scan revisions without comparing two long documents side by side.
A boxed summary near the top lists the actions you can take — export, correct, erase — with the contact path for each. It's the practical bit, kept above the longer legal language.
A short note states which region's rules govern this version. If you sign in from outside that scope, the note points you to the appropriate document for your access path.
A print toggle reformats the page for paper or PDF capture. Handy if you want a snapshot of the policy as it stood on the day you opened your account.