How We Handle Your Account Data
This is the bighoki55 privacy policy — the page that tells you what we collect when you open an account, what we never share, and how long records...
Our Privacy Posture and Your Rights
We collect the minimum needed to run your bighoki55 account: your sign-in credentials, the device you log in from, the payment reference you pick from DANA, OVO, GoPay or QRIS, and the lobby actions tied to your session. Where local law permits in supported regions of Indonesia, we keep these records encrypted and segmented from marketing systems. You can ask us to
export, correct or delete your account data at any time, and we'll respond within a reasonable window. We don't sell your details to third parties, and we don't pass payment metadata to advertisers. Cookies on the site stay functional and analytical only — never resold.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How This Policy Stays Honest
Six checks keep this document aligned with what actually happens on our servers. We treat the policy as a working contract, not a marketing page, so each clause maps to a real...
Quarterly Review
Our compliance lead re-reads every clause each quarter and flags drift between written policy and live practice. Any gap gets closed before the next publish cycle on this page.
Named Reviewer
Each revision carries the initials of the reviewer who signed it off. You can ask us who approved a clause and we'll tell you, including the date it cleared internal review.
Change Log
We keep a dated change log at the foot of this policy so you can see exactly what shifted between versions. Nothing rewrites silently behind your back.
Data Map
An internal map ties every field we collect to the system that stores it. If a clause here mentions data, that data exists in one place we can point to.
Vendor List
Processors we rely on for hosting, payments and fraud screening are listed by category. We update the list whenever a vendor changes scope on your account data.
Local Counsel
Indonesian counsel reviews region-specific clauses, especially around DANA, OVO, GoPay and QRIS payment metadata, so the wording matches what supported regions actually require of us.
Consistency Across Our Policy Pages
This privacy page sits alongside our terms, cookie notice and account closure pages. The seven points below show how we keep wording consistent so you don't get one...
| Shared Definitions | Words like account, session and payment reference mean the same thing on every legal page. We define them once and reuse them so clauses don't quietly contradict each other. |
|---|---|
| Same Retention Windows | Retention timelines stated here match the figures on our terms page. If we update one, we update the other in the same publish so you never see two different numbers. |
| Aligned Contact Routes | The privacy email on this page is the same address quoted on the cookie and account-closure pages. One inbox, one team, one reply thread per request. |
| Matching Jurisdiction | Region wording — supported regions of Indonesia, where local law permits — appears identically across legal pages so the geographic scope never drifts between documents. |
| Unified Change Log | Each policy page carries its own dated log, but entries cross-reference when a change touches more than one document, making the audit trail simple to follow. |
| Same Reviewer Pool | The compliance leads who sign this policy also sign the sibling pages. You're not getting four different voices writing four different sets of rules. |
| Plain-English Standard | Every legal page on bighoki55 follows the same readability target. If a clause needs jargon, we add a short explainer instead of leaving you to guess. |
What Shapes This Policy Page
Below are the visible elements we built into the privacy page itself — the layout choices that make the document easier to read, search and reference. They're not payment features; they're the bones of...