Terms of Service
Defines the contract; this policy explains the data side of that contract. Wording is cross-checked so the two pages never contradict each other on retention or lawful basis.
This is the tridewa privacy policy — the page that tells you exactly what we collect when you open an account, why we hold it, and how long...
Where local law permits, we process your personal data on the basis of contract performance and our duty to operate a compliant lobby for supported regions. That means we hold the identifiers tied to your tridewa account — name, contact, device fingerprint, transaction trail — for as long as your account is active and for the retention window our auditors require. We
do not sell your data. We share it only with payment partners, KYC vendors and regulators when a request is lawful. If you close your account, residual records remain under statutory retention before secure deletion. Questions about scope, lawful basis or cross-border handling go to our policy desk and we respond inside our published service window.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Three direct channels to reach the team that owns this policy. Use whichever fits the request — data access, correction, deletion or a question about how a specific field is handled inside your tridewa account.
Email our data team for access, correction or deletion requests tied to your tridewa account. We acknowledge inside one working day and resolve within the statutory window for supported Indonesia regions.
Open the chat widget from any tridewa page and ask for the privacy queue. Agents route policy questions to the right reviewer rather than answering them at the front line, so you get accurate handling.
Most consent toggles, marketing preferences and session-data switches sit inside your account settings. Adjust them yourself at any time and the change takes effect across our lobby immediately.
Editorial trust signals for the people who maintain this page.
Each revision of this policy is signed off by a named data lead inside tridewa, not an anonymous compliance pool. That's how we keep accountability visible when you ask who approved a wording change.
We re-read the full policy every quarter against current Indonesia data rules and our payment partner contracts. Drift between what we wrote and what we actually do gets caught early, not at year-end.
Before publishing, the draft goes through a plain-English pass so the clauses read like a brand talking to you, not a template. Legal accuracy stays — the jargon goes.
Every third party touching your data is listed in our internal map with purpose, region and retention. When the map changes, this policy changes — they don't drift apart.
Material updates carry a date and a short note describing what shifted. You'll see the latest revision date at the foot of this page so you always know which version applies.
An external counsel reviews substantive rewrites before they go live. That second pair of eyes keeps this policy aligned with how Indonesia regulators read consent and lawful-basis language.
How this policy lines up with our sibling legal pages.
Defines the contract; this policy explains the data side of that contract. Wording is cross-checked so the two pages never contradict each other on retention or lawful basis.
Covers browser-side identifiers in detail. This policy references it rather than duplicating, so a cookie change updates in one place and flows through here.
Sets out which documents we ask for and why. This policy describes how those documents are stored, who sees them, and when they're purged from our systems.
Covers transaction monitoring obligations. We point to it from the lawful-basis section so you can see why some data is held longer than the standard retention default.
Lives inside your account settings. This policy describes the consent model behind those toggles and confirms that switching them off stops the relevant processing right away.
The intake form for access, correction and deletion. The policy tells you what each request covers; the form handles execution. Both share the same response timelines.
Internal document that triggers our notification duty. This policy summarises what you'd hear from us and within what window if a qualifying incident affected your account.
Visible elements that define how the privacy page reads, not the cashier.