Cookie notice
Uses the same retention windows quoted here and links back to this page for the master definitions of personal data categories.
LEGAL REFERENCE
How hari88 Handles Your Account Data
This is our privacy posture in plain language. We tell you what we collect when you open an account with hari88, why we keep it, and how long...
Account dataSession logsPayment referencesCookie controlsRetention windows
Policy Posture and Jurisdiction Notes
We collect the data your account needs to function: your identity check fields, your contact handle, your session timestamps, and the payment references that match deposits to your wallet. We process this only where local law permits and only within the supported regions our licence covers. Your records sit on encrypted infrastructure with role-based access — our support agents see what they
need to help you, nothing more. If you close your account, we retain the minimum set required by our regulator and purge the rest on a documented schedule. You can ask us what we hold on you at any time, and we'll respond inside the window our jurisdiction sets. Payment context chips below show the e-wallet routes referenced in your transaction records.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PLAYER SUPPORT
Reaching Our Privacy Desk
Privacy mailbox
Send your data questions to our privacy inbox and a named officer picks it up. We confirm receipt the same day and give you a reference number you can quote on any follow-up message.
Live chat escalation
Open chat from any lobby page, type 'privacy' and the agent routes you straight to the compliance queue. Useful when you want a deletion request logged while you're still signed into your account.
Written request line
For formal subject-access requests we accept signed letters at the address listed in our footer. We process these in the order received and confirm completion against the reference you supplied.
WHY VISITORS TRUST US
How We Keep This Policy Honest
Named officer
A real person owns this policy, not a shared inbox. Their sign-off appears on every revision we push, and their name is on file with our licensing body for the supported regions we operate in.
Quarterly review
We re-read the policy every quarter against the rules our regulator publishes. If a clause needs to change, the new version goes live with a dated note so you can see exactly what shifted.
Encryption at rest
Account fields, identity documents and payment references sit on encrypted storage with key rotation. Only staff with a documented business reason can decrypt, and every read is logged for audit.
Access logging
Every internal lookup against your record leaves a trail. If you ever ask us who touched your file, we can answer with timestamps rather than guesses, which keeps our team honest.
Third-party audits
An external assessor checks our handling controls against the standard our licence references. We act on their findings inside the remediation window and keep the reports on file for inspection.
Plain-language drafts
We write this page ourselves rather than buying a template. If something reads vaguely, that's a bug — tell us and we'll rewrite the clause in the next quarterly pass.
BENCHMARKED
Consistency Across Our Policy Pages
Terms of service
References this policy for any clause that touches your data, so the two documents never contradict each other on what we keep.
KYC notice
Identity-check fields described there match the collection list in this policy, with the same lawful basis and the same purge schedule.
AML statement
Transaction monitoring duties are explained without repeating sensitive thresholds, and the data points it relies on are listed here too.
Complaints page
Routes privacy complaints to the same named officer mentioned above, with identical response windows for the supported regions.
Marketing preferences
Opt-in toggles surface the same categories defined here, so turning something off in your account turns it off across our stack.
Account closure
The closure flow quotes the retention minimums set out in this policy and confirms the purge date before you confirm.
What This Policy Page Shows You
Plain summary
The top of the page gives you the short version in five badges so you can leave with the gist if you only have thirty seconds to spend on us.
Detail block
The legal notice section is the binding text. It's written tightly enough to read in one sitting but specific enough that our regulator can map it to their checklist.
Contact paths
Three routes to our privacy desk sit mid-page so you never have to dig through a footer to find out where data questions actually land.
Trust panel
Six signals explain how we keep the policy honest — who owns it, how often it's reviewed, and which controls back the promises.
Sibling links
The comparison row points to every neighbouring document so you can check we're saying the same thing in cookies, terms and KYC.
FAQ block
The questions section answers the things our privacy desk actually gets asked, in the order they tend to come up after you open an account.
Privacy Questions We Hear Most
Your identity-check fields, a contact handle, session timestamps and the payment references tied to your wallet. We don't ask for anything we can't justify against a lawful basis in our supported regions.
We keep the minimum our regulator requires and purge the rest on a documented schedule. The closure flow shows you the exact retention date before you confirm, so there's no guesswork.
Yes. Email the privacy mailbox or open chat and ask for a subject-access request. We confirm receipt, give you a reference number, and respond inside the window our jurisdiction sets.
DANA, OVO, GoPay and QRIS transactions leave a payment reference on your account so support can match deposits to your wallet. We don't store your wallet credentials — only the reference our processor returns.
Only staff with a documented business reason, and every read is logged. If you ask us who touched your file, we can answer with timestamps from the access log rather than vague assurances.
We re-read it every quarter against current rules. When a clause changes, the new version goes live with a dated note at the top so you can see exactly what shifted and when.
Raise it with our privacy desk first and we'll work it through. If you're still not satisfied, you can escalate to the regulator named in our licence for the supported region you signed up from.