LEGAL REFERENCE

How hitam138 Handles Your Account Data

This is our privacy policy — the plain-English version of what hitam138 collects when you open an account, why we keep it, and how long it stays on...

Indonesia-alignedAccount-holder firstPlain EnglishUpdated regularlyData minimisation
hitam138 How hitam138 Handles Your Account Data

Our Privacy Posture and Your Rights

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

HELP CHANNELS

Reach Us About Privacy Matters

Team online

Privacy Inbox

Email our data team directly when you want a copy of your account file, a correction, or a deletion request. We aim for a written response within five working days.

Live Chat Desk

The chat widget in your account dashboard routes privacy questions to a human agent. Use it for quick clarifications about cookies, session logs, or what a specific data field means.

Compliance Officer

For formal complaints or regulator-facing queries, ask the chat agent to escalate to our compliance officer. They handle audit trails, lawful-basis questions and any cross-border data concerns you raise.

EDITORIAL CLARITY

How We Keep This Policy Honest

Quarterly Review

Our legal team re-reads this policy every quarter against current Indonesian rules. If wording drifts from practice, we rewrite the section and stamp the revision date at the foot of the page.

Named Authors

The policy is maintained by hitam138's in-house data protection lead, not an outsourced template farm. That means the person who wrote it is the person who answers your questions.

Vendor Audits

Payment processors and KYC partners we share data with are audited annually. We check their security posture, breach history and sub-processor list before renewing any contract that touches your account.

Encryption Baseline

Account credentials, wallet references and identity documents sit behind TLS in transit and AES at rest. Internal access is role-gated, logged, and reviewed when staff change roles or leave hitam138.

Breach Protocol

If something goes wrong, we tell you. Our incident plan commits to notifying affected account holders and the relevant Indonesian authority within the timelines local law sets out.

Version History

Older versions of this policy stay accessible on request. You can compare what changed between revisions so nothing gets quietly rewritten without you having a chance to see it.

BENCHMARKED

Consistency Across Our Policy Pages

01

Privacy Policy

This page — covers what data hitam138 collects, why, and the rights you keep over it. The anchor document the other policy pages reference.

02

Cookie Notice

Sister page focused only on browser-side storage: session cookies, analytics tags and the consent banner. Same tone, narrower scope, links back here for account data.

03

Terms of Service

Sets out the contract between you and hitam138. Privacy is referenced but not duplicated — for data questions, this policy is the controlling text.

04

KYC Statement

Explains identity verification steps. Lists the documents we ask for; this privacy policy explains how long we keep them and who else sees them.

05

Retention Schedule

A table-format companion that maps each data category to its storage period. Reads alongside this page when you want exact numbers rather than narrative.

06

Marketing Preferences

Controls what email and push messages reach you. Opting out there does not delete your account data — that's handled through the request route described above.

07

Complaints Path

Documents how to escalate beyond our compliance officer. Same contact ladder referenced in the support cards on this page, written for formal disputes.

What This Policy Page Shows You

Last Updated Stamp

At the foot of every revision you'll find the date the policy was last edited. Check it before sending a query so we both know which version we're discussing.

Section Anchors

Each heading on this page has a direct link. Copy the URL with the anchor attached when you want to point a friend or an advisor at one specific clause.

Plain-Language Sidebar

Where a paragraph uses a legal term, a short explanation sits beside it. We'd rather you understand the clause than admire the vocabulary on first read.

Contact Card

The privacy contact block stays pinned in the support section above. No hunting through footers — the inbox you need is one scroll away from any clause.

Rights Checklist

A short list of the requests you can make — access, correction, deletion, portability — sits inside the legal notice. Use it as a menu when you write to us.

Change Log Link

A link to previous versions lives near the update stamp. If a clause moved or softened, you can read the older wording side by side with the current one.

Privacy Questions We Hear Most

Your name, date of birth, contact details, a verification document, the wallet handle you use for DANA, OVO, GoPay or QRIS, and standard device and session logs. Nothing beyond what the account flow shows.

For the period Indonesian financial and gaming rules require after your last activity, then we delete or anonymise. The retention schedule page lists exact windows for each category if you need specifics.

Yes. Email our privacy inbox from the address registered to your hitam138 account. We'll verify it's you, then return a structured export within the timeframe local law sets, usually inside one calendar month.

No. We don't sell account data and we don't hand it to ad networks. Marketing you receive comes from hitam138 directly, and you can switch it off in your preferences without closing the account.

Wallet references for DANA, OVO, GoPay and QRIS are tokenised by the processor. We store the token and the transaction record needed for accounting; the underlying wallet credentials never sit on hitam138 servers.

Send a deletion request from the chat desk or privacy inbox. We close the account immediately and remove personal fields, keeping only the minimum transaction history that financial regulations in supported regions require us to retain.

Material changes trigger an in-account notice and an email to the address on file. Minor edits — typos, link fixes — get a quiet revision-date bump that you can spot through the change log.