How belegendwin Handles Your Account Data
This Privacy Policy sets out what we collect when you open an account with belegendwin, how we store it, and the choices you keep over it. We've written...
Policy Posture and Jurisdiction Notes
We process your data where local law permits and only for supported regions inside Indonesia. The categories we keep are limited to what an account needs: identity fields you submit at sign-up, session logs from the lobby, transaction references when you fund through DANA, OVO, GoPay or QRIS, and support messages you send us. We don't sell your data, we don't share
it with advertising brokers, and we keep retention windows tied to regulatory duties. If a request from authorities arrives, we answer only when the legal basis is documented and the scope is narrow.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How This Policy Is Reviewed
Our Privacy Policy isn't a one-off document. It's reviewed on a fixed cadence by people who actually own the systems your data passes through.
Quarterly Review
Our compliance lead reads the policy line-by-line every quarter against the live data flows behind the lobby, so the wording you see here matches what the account systems actually do.
Engineering Sign-Off
The engineers who run our payment and session services approve every change before it ships. If a clause names DANA, OVO, GoPay or QRIS, the rail owner has read it.
Legal Counsel
Indonesian counsel reviews jurisdiction wording, retention windows and lawful-basis claims. We document their notes against each version so you can see what changed and when.
Version History
Each policy update is dated at the top of this page. Material changes trigger an in-app notice the next time you sign in to your account.
Named Owner
A named Data Protection contact owns this document inside belegendwin. The role isn't outsourced and the inbox is monitored on working days from our Indonesia desk.
Audit Trail
Access to stored account data is logged at the row level. Internal reviews sample those logs monthly to confirm only authorised staff opened records tied to a real ticket.
Consistency With Our Other Policy Pages
This page sits alongside our Terms, Cookies and AML notices. Where wording overlaps, the meaning has to match across all four — here is how we keep that...
What Shapes This Policy Page
The layout of this Privacy Policy is built so you can find a specific clause without scrolling the whole document. These are the structural elements we...
Clause Anchors
Each section carries a permanent anchor link, so support agents can send you straight to the paragraph that answers your question instead of asking you to scroll the entire policy.
Last-Updated Stamp
A dated stamp sits at the top of the page and changes only when wording changes. If the date hasn't moved, the policy you read last time is the policy in force today.
Plain-Language Summary
Above each legal block we keep a short plain-language line explaining what the clause means in practice for your belegendwin account, without altering the legal effect underneath.
Data Category Table
A table groups data into identity, session, transaction and support categories. You can see at a glance which category a field belongs to and how long we keep it.
Rights Checklist
Your rights — access, correction, deletion, objection, portability — are listed as a checklist with the exact channel to use for each one, not buried inside paragraphs.
Change Log Link
A link at the foot of the page opens the change log. Every material edit since the policy was first published is recorded there with a short note on what moved.