Cookies Page
Cookie wording mirrors this policy on data categories and retention so you never see two contradicting timelines between the pages.
This is the usd777 privacy policy — the page that tells you exactly what we collect when you open an account, why we store it, and how long...
We collect what we need to run your usd777 account: identity details for verification, device data for fraud checks, transaction records tied to your wallet, and the support messages you send us. We process this where local law permits and only inside supported regions of Indonesia. Third-party processors handle payments and identity checks under contracted data terms. You can ask us to
export, correct or delete your record at any time, subject to the retention windows our licence requires us to keep. We do not sell your data, ever, and marketing emails stay opt-in from the moment you register.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Our compliance team re-reads this policy every quarter against current Indonesia guidance. If wording shifts, we publish the new version with a dated changelog so you can see what moved and when.
A single privacy lead signs off each version of the page. That accountability sits inside usd777, not with an outside writer, so the words you read match how the brand actually behaves.
Every paragraph passes a readability pass before it goes live. We strip legal padding so the policy stays scannable on mobile, where most of you read terms before opening an account.
The vendors who touch your data — payment rails, KYC providers, hosting — are audited annually. We retain the reports and reference them when regulators ask how usd777 supervises its supply chain.
If something goes wrong we tell affected account holders quickly with the facts, the scope, and the steps we've taken. No spin, no buried updates — the notice lands in your inbox first.
We delete data the moment our retention window closes. Old logs do not linger on backup tapes indefinitely; the schedule is documented and the deletion jobs are logged for internal review.
Cookie wording mirrors this policy on data categories and retention so you never see two contradicting timelines between the pages.
Account responsibilities in the terms reference the same data definitions used here, keeping language aligned across the legal set.
Identity verification text uses identical retention windows, so what we say at sign-up matches what this privacy page commits to.
Opt-in rules described here match the toggles inside your dashboard one-to-one, with no hidden categories enabled by default.
Escalation paths for data complaints route through the same privacy inbox referenced above, avoiding split contact addresses.
The processor list cited here matches the names disclosed in our vendor register, refreshed on the same quarterly cadence.
Closure mechanics in the help centre repeat the seventy-two hour export window and deletion timing stated on this page.
A timestamp at the top of the page tells you when the policy last shifted. Older versions stay archived so you can compare what changed between any two dates.
We break the data we hold into clear buckets — identity, device, transaction, support — so you can find the section that applies to your specific question without scrolling the whole page.
Each category lists how long we keep it and why. The reasons cite the licence rule or the operational need, not vague phrases like "as long as necessary".
A dedicated block walks through access, correction, deletion and portability. Each right links to the dashboard control or the contact path that triggers the request.
Named vendors appear with their function and the country where processing happens. The list updates when we onboard or retire a partner, not on a delayed schedule.
The privacy inbox and chat route sit at the bottom of every section, so you never have to hunt for where to send a question once you've finished reading.