LEGAL REFERENCE

How wap cuantoto Handles Your Account Data

This is our privacy policy in plain English. We explain what we collect when you open an account, why we hold it, and how long it stays with...

Account dataCookies disclosedWallet privacyIndonesia-awareRevisable anytime
Account access Read FAQ
wap cuantoto How wap cuantoto Handles Your Account Data

Policy Posture and Jurisdiction Notes

We collect only what's needed to run your account: your contact details, verification documents where local law permits, device fingerprints used for fraud checks, and the transaction trail tied to your wallet top-ups. Wallet identifiers from DANA, OVO, GoPay and QRIS are tokenised by the payment side and we never store raw wallet credentials. Marketing preferences are opt-in and revocable from your

dashboard. For supported regions in Indonesia, retention follows the shorter of the legal minimum or seven years after your last session. Cross-border processing happens only with vendors bound by data-protection terms equivalent to ours, and we publish updates to this policy in-page so you can see the diff.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

24/7 SUPPORT

Reaching Us About Your Data

If you want a copy of what we hold, a correction, or a full erasure where law permits, use one of the paths below. Our privacy desk replies separately from general support...

Privacy inbox Email our data desk and a named handler picks up the thread. We confirm receipt within one business day and resolve standard access requests within fourteen days where local law permits.
Live chat escalation Open chat from any lobby page and ask for the privacy queue. The agent transfers you out of general support so your case is logged against your account, not a generic ticket.
Postal channel For formal erasure or rectification notices you'd rather send on paper, our registered correspondence address is listed at the foot of every page on this brand site.
PLATFORM TRUST SIGNALS

Editorial Trust Behind This Policy

This document isn't a template. We review it on a fixed cadence and sign off internally before pushing changes.

Named reviewers

Two internal owners — a data lead and a compliance lead — must both sign off on any wording change...

Quarterly refresh

We re-read this policy every quarter against the current Indonesia regulatory posture and our payment-vendor contracts, then publish the revised...

Vendor due diligence

Every processor that touches your record is reviewed annually. Contracts include audit rights, breach-notice windows, and the same retention ceilings...

Plain-language rule

If a clause can't be explained in one sentence to someone opening their first account, we rewrite it. Legal precision...

Change log on file

Every revision to this page is timestamped in an internal changelog. If you want to see what shifted between two...

Separate breach protocol

We keep an incident-response plan distinct from general operations. If a personal-data event ever occurred, affected accounts would be contacted...

Consistency With Our Other Policy Pages

This policy reads the same way as the rest of our legal stack — same defined terms, same retention ceilings, same contact desk.

Terms of ServiceDefined terms like 'Account', 'Session' and 'Wallet Identifier' mean the same thing here as in the Terms. We don't redefine words across pages to suit a clause.
Cookie NoticeOur cookie page lists each tracker by category; this privacy page explains the legal basis we rely on to set them. The two are written to be read together.
KYC PolicyVerification documents are described here in summary; the KYC page details what we accept. Retention windows match exactly between the two documents.
AML StatementTransaction monitoring data referenced here is governed by the AML statement's retention rules. Both pages cite the same seven-year ceiling for supported regions.
Account ClosureThe closure page explains the mechanic; this page explains what survives closure in our records and for how long, so you don't have to cross-read to understand erasure scope.
Complaints PathComplaints about data handling follow the same escalation ladder as service complaints, but route to the privacy desk first rather than general support, as noted above.
Marketing PreferencesThe preferences centre is the operational control; this policy is the legal basis. Toggling off in one place is reflected in the other within a single session.
QUICK SIGNAL

What This Policy Page Actually Shows You

Beyond the legal text, the page is laid out so you can find the clause that affects you without scrolling the whole thing.

01
Anchored clauses Each major clause has its own anchor link. Share a clause directly with a friend or paste it into an email and the recipient lands on the exact paragraph rather than the top of the page.
02
Last-updated stamp A visible date sits at the head of the document. When we revise wording it moves immediately, so you can tell at a glance whether what you read last month still applies today.
03
Glossary inline Defined terms are bolded on first use and hover-explained. You don't need to jump to a separate glossary tab to understand what 'Wallet Identifier' or 'Session Token' means in context.
04
Mobile-first layout The clauses reflow cleanly on phone widths. If you're checking the policy on the train before opening your account, the text stays readable without pinch-zoom.
05
Print-friendly view A print stylesheet strips navigation and keeps the clause numbering intact, so a saved PDF reads the same as a paper copy filed for your records.
06
Diff on request If you want to see what changed between two dates, our privacy desk emails a side-by-side diff. We keep this offline rather than auto-publishing every revision marker on-page.

Common Questions About This Privacy Policy

Your contact details, the verification documents local law requires, device signals used for fraud checks, and a transaction history tied to your wallet. Nothing extra is captured for marketing unless you opt in from your dashboard yourself.

No. Raw wallet credentials never reach us. The payment side tokenises your identifier and we hold only the token plus the transaction reference, which is enough to reconcile your account without exposing the underlying wallet.

For supported regions in Indonesia we retain records for the shorter of the legal minimum or seven years from your last session. After that window expires, identifying fields are purged from active systems on a rolling schedule.

Yes. Email our privacy inbox from the address tied to your account and we'll package an export within fourteen days where local law permits. Identity confirmation is required before any data leaves our systems.

Only with processors we've contracted for payments, verification, fraud screening and infrastructure. Each is bound by data-protection terms equivalent to ours. We don't sell your data to advertisers or list brokers under any circumstance.

The last-updated stamp at the top of the page moves the moment we publish a revision. Material changes also trigger an in-account notice the next time you sign in, so you can re-read before continuing.

Our named data lead handles first response, with the compliance lead signing off on resolutions involving erasure, rectification or third-party disclosure. Both names are on file and can be confirmed by writing to the privacy inbox directly.