LEGAL REFERENCE

How hoki236 Handles Your Account Data

This is the hoki236 privacy policy — written plainly so you know what we store, why we store it, and how long we keep it. We collect what's...

Data we collectHow we use itYour controlsRetention windowsContact paths
Account access Read FAQ
hoki236 How hoki236 Handles Your Account Data

Policy Posture and Jurisdiction Scope

Our privacy posture applies where local law permits and across supported regions in Indonesia. We process the identifiers you submit at signup — name, contact, device fingerprint — to verify your account and meet KYC duties. Session logs and wallet references tied to DANA, OVO, GoPay and QRIS are stored only for the windows required by financial recordkeeping rules. We don't sell

your data to third parties. Sub-processors (cloud hosting, fraud screening, payment routing) work under written terms that mirror this policy. If our jurisdiction footprint changes, we publish the update here before it takes effect, so you can review and adjust your account preferences first.

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

PLAYER SUPPORT

Privacy Contact Paths

Data Requests Inbox Email our privacy desk to request a copy...
Live Chat for Policy Queries Open the chat widget from any page and...
Escalation Channel If a privacy response doesn't resolve your concern...
WHY THIS PLATFORM

Editorial Trust Signals for Policy Review

Plain-Language Drafting

We rewrite legal clauses into clear English so you can scan the policy in one sitting. No buried definitions, no...

Versioned Changes

Every revision carries a date stamp and a short note describing what shifted. You can see the prior wording on...

Named Review Team

A small internal group reviews this policy each quarter against current Indonesia data rules and our sub-processor list. They sign...

Third-Party Audits

Our payment routing for DANA, OVO, GoPay and QRIS sits behind audited processors. Their attestations are referenced where this policy...

Data Minimisation

We ask for the fields needed to verify your identity and run your sessions. Optional fields stay optional, and we...

Breach Notification

If a security event touches account data, we notify affected holders directly through registered contact channels within the timelines our...

Consistency Across Sibling Policy Pages

Terms of Service
Our terms reference the same data categories you'll see here, so definitions don't drift between documents. If wording shifts in one, it's pushed through to the others on the same date.
Cookie Notice
Cookie handling lives in its own notice but mirrors the retention windows defined below. Session cookies clear when you log out; preference cookies follow the account-life rule.
KYC Policy
Identity checks pull from the same dataset described in this privacy policy. Nothing extra is collected at KYC stage beyond what's already disclosed on this page.
AML Statement
Anti-money-laundering checks share storage windows with wallet activity logs. Both align to the financial recordkeeping rule referenced under the policy posture section above.
Complaints Procedure
Privacy complaints flow through the escalation channel listed here and the wider complaints procedure. Tracking IDs match across both so the trail stays single-threaded.
Sub-Processor List
The named list of vendors handling hosting, fraud screening and payment routing is published separately and updated whenever this policy changes scope or geography.
Account Closure Notes
Closure rules referenced here are echoed in the account closure page, including which records persist for legal recordkeeping after your account is wound down.
SERVICE CONTEXT

What Defines the Policy Layout

Date-Stamped Sections Each block in the policy carries the date it was...
Defined Terms Up Front Key terms — account data, session data, wallet reference —...
Retention Tables Storage windows sit in a compact table format so you...
Rights Checklist Your rights — access, correction, deletion, portability — are listed...
Sub-Processor Anchors Where a sub-processor is mentioned, we link to the current...
Change Log Strip A change log strip at the foot of the policy...

Privacy Policy Questions

We collect your name, contact details, date of birth and a device fingerprint for security. Wallet identifiers tied to DANA, OVO, GoPay or QRIS are stored only as references, not full credentials, alongside session activity.

Active account data stays while your account is open. After closure, records required for financial and KYC rules are held for the window your local law sets, then purged. Retention tables in the policy list each category.

Yes. Email the privacy desk from your registered address and we'll compile your stored data into a readable export. Responses land within the timeframe your jurisdiction sets, typically under thirty days from a verified request.

We don't sell your data. Sub-processors handling hosting, fraud screening and payment routing for DANA, OVO, GoPay and QRIS receive only what they need to run their service, under contracts that mirror this policy.

Open the rights checklist in the policy and use the listed contact path for correction or deletion. Some records must be retained for legal reasons even after deletion — we'll tell you which ones during the request.

We publish revisions on this page with a date stamp and a short note describing what shifted. Material changes are surfaced inside your account before they take effect, so you can review and adjust preferences.

A named internal team reviews the policy each quarter against current Indonesia data rules and our sub-processor list. They sign off on changes before publication and document the rationale in our internal change record.