Terms of Service
Defines the account contract; this privacy page describes the data side of that same contract.
LEGAL REFERENCE
Your Privacy On hanomantoto, Made Plain
This page is our privacy promise to you, written in language you can actually read on a phone. We explain what we collect when you open an account...
Account DataSession LogsDevice SignalsCookie NoticeLast Updated
How We Handle Your Account Information
When you open an account with us, we collect the basics needed to verify you and run your sessions: name, contact details, date of birth, and the wallet handle you use to move funds. We store this where local law permits and only keep it as long as your account is active or our records duty requires. We share data with payment
partners and identity-check providers strictly to process your transactions and protect your balance. You can request a copy, a correction, or a deletion of your record by writing to our privacy desk, and we'll respond within the window Indonesian regulation expects.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
TRUST MARKERS
How This Policy Is Reviewed
We don't write this policy once and forget it. Here's who looks at it, how often, and what they check before any new version goes live on hanomantoto.
Quarterly Legal Review
Our retained Indonesian counsel reads this page every quarter against current data rules. Any wording that drifts from the live legislation gets flagged, rewritten, and dated before the new version replaces this one.
Internal Data Officer
A named data protection lead inside hanomantoto signs off on every change. They hold the master log of what we collect, where it sits, and which staff roles can read which fields.
Vendor Audits
Each payment and verification partner we use is audited yearly for how they store the data we pass them. If a vendor fails the check, we cut the integration before renewing.
Encryption Standards
Account credentials and wallet identifiers move through TLS in transit and are encrypted at rest. Internal tooling masks sensitive fields by default so staff see only what their role strictly needs.
Breach Protocol
If a security event touches your record, we contact you through the email on file and through the in-lobby banner. Our notification window follows the tighter of regulator deadlines or 72 hours.
Version History
Every policy revision is archived with a date stamp. You can request prior versions through the privacy inbox if you need to compare what was in force when you opened your account.
SIDE BY SIDE
Consistency Across Our Legal Pages
Our privacy policy lines up with the other legal documents on hanomantoto so you don't get conflicting answers. Here's how the pieces fit together.
Cookie Notice
Lists each cookie category; we cross-reference it here so consent choices stay aligned.
KYC Statement
Explains identity checks; this policy covers how those verification documents are stored and retired.
AML Procedure
Sets monitoring duties; we disclose here which transaction signals are retained for that purpose.
Payments Terms
Covers DANA, OVO, GoPay and QRIS flows; we mirror the data-sharing language used there.
Complaints Track
Routes disputes; privacy complaints follow the same intake form with a separate review queue.
Account Closure
Describes shutdown steps; this policy states what data survives closure and for how long.
SERVICE CONTEXT
What Shapes The Policy Side Of hanomantoto
The privacy layout you're reading isn't generic boilerplate. These are the design choices we made to keep policy reading actually readable on the phone you're holding.
Plain-Language Sections
Each clause is rewritten in everyday English instead of legal...
Dated Revisions
The header carries the last-updated stamp and the prior date...
Inline Definitions
Terms like processor, controller and retention window are defined the...
Mobile Anchor Links
Every heading on this page is its own anchor. Share...
Quick Request Forms
Access, correction and deletion requests run through a short form...
Indonesia-Specific Notes
Where local rules differ from regional norms — retention windows...
Privacy Questions We Hear Most
We capture your name, date of birth, contact email, phone number and the wallet handle you'll use for DANA, OVO, GoPay or QRIS. Device fingerprint and session IP are logged for fraud checks.
Yes. Send a request from the email tied to your account and we'll return a structured export within seven working days, where local law permits. The first request each year is free of charge.
Active records are retained while you play. Once closed, identity and transaction logs are held for the period Indonesian financial regulation requires, then permanently deleted from production and backup environments on a scheduled cycle.
Only what's needed to settle a transaction. DANA, OVO, GoPay and QRIS receive the wallet handle and amount; they don't see your gameplay history, and we don't see their internal customer records.
Strictly necessary cookies run by default to keep your session alive. Analytics and preference cookies wait for your consent through the banner. You can revisit those choices any time from the footer link.
We update the date at the top of this page and post an in-lobby banner for material changes. If a change affects how we use existing data, we'll email the address tied to your account before it takes effect.
Reply to our privacy desk first so we can re-review. If you remain unhappy, you can escalate to the relevant Indonesian data authority; we'll provide the case reference and any logs they request from us.