LEGAL REFERENCE

How 1kalibet Handles Your Account Data

This is our privacy policy in plain English. We explain what we collect when you open an account with 1kalibet, why we keep it, and how long it...

Privacy PolicyData HandlingAccount RecordsIndonesiaLast Updated
Tour the Lobby Read FAQ
1kalibet How 1kalibet Handles Your Account Data

Policy Posture and Jurisdiction Notes

We process your personal data under the framework that applies where local law permits, and we keep our handling aligned with supported regions across Indonesia. The fields we collect — name, contact, device fingerprint, transaction references — are tied to a single purpose: keeping your 1kalibet account verifiable and your sessions safe. We don't sell your records. We share them only with

the licensed processors who run our identity checks, fraud screens and payout rails, and only to the depth each task needs. You can ask us to export, correct or close your data trail at any point, and we'll act on it inside the window our policy commits to.

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

HELP CHANNELS

Privacy Contact Paths

Team online

Privacy Inbox

Write to our privacy desk for data export, correction or deletion requests. We acknowledge within one business day and complete most cases inside the window our policy commits to for Indonesia accounts.

In-App Chat

Open the account drawer, tap the help icon and choose the privacy thread. Your message routes straight to a trained agent who can pull your file and walk through any field you want clarified.

Escalation Line

If a privacy reply doesn't resolve your question, ask for escalation in the same thread. A senior reviewer takes the case, re-reads your records and responds with a written decision you can keep.

EDITORIAL CLARITY

Editorial Trust Signals for This Policy

Reviewed Quarterly

Our privacy team re-reads this policy every quarter and after any change to our casino, slots or sportsbook stack. Every revision carries a date stamp so you can see what shifted since your last visit.

Named Owner

A named data protection lead signs off every clause. That person owns the inbox, drives the audit log and answers escalations — not a rotating queue of unnamed agents behind a generic form.

Plain-Language Drafting

We draft in the same English you'd hear from a counter agent in Jakarta, not in legal shorthand. If a clause needs a defined term, we define it the first time it appears on the page.

Aligned With Processors

Our wording mirrors the contracts we hold with identity, payment and hosting processors. What you read here is what they're bound to deliver when your data crosses into their systems.

Change Log Kept

Every edit goes into an internal change log with author, date and reason. You can request the summary of changes that affected your account window during any support thread.

Indonesia-Specific Notes

Where Indonesian rules add a step — local payment confirmations through DANA, OVO, GoPay or QRIS, regional consent prompts — we call it out in the clause rather than hiding it in a footnote.

Consistency Across Our Policy Pages

Same DefinitionsAccount, session, device and transaction mean the same thing here as on our terms and cookie pages. One glossary feeds every policy document we publish.
Shared Date StampPrivacy, terms and cookie pages move together on revisions, so the effective date you see on one matches the others within the same release week.
Unified ContactThe privacy inbox listed here is the same address quoted across our terms and account-closure flow. You never chase a different desk for the same question.
Matching RetentionRetention windows quoted in this policy match the figures inside our terms. If a number changes, it changes in both places on the same day.
Single Processor ListThe processor categories named here mirror the cookie page categories one-to-one, so consent choices and data sharing line up cleanly.
Consistent EscalationEscalation steps follow the same ladder across privacy, payments and account disputes — first agent, senior reviewer, written decision you can archive.
Same Jurisdiction WordingWhere local law permits and supported regions language is reused verbatim across pages so there's no doubt which framework governs your account.
PLATFORM SNAPSHOT

What Defines This Policy Page

01
Clause Index A short index sits at the top of long sections so you can jump to retention, sharing or your rights without scrolling through the whole document on a phone screen.
02
Inline Definitions Defined terms are bolded the first time and explained in the same line. No popovers, no glossary tab — the meaning stays next to the sentence using it.
03
Effective Date Banner The current effective date sits in a fixed banner at the page head. If we revise the policy, the date moves and the previous version stays linked for reference.
04
Rights Checklist Your rights — access, correction, export, deletion, objection — appear as a tight checklist with the request route next to each, so you know exactly which channel to use.
05
Processor Categories We group third parties into named categories — identity, payment, hosting, analytics — and explain what each category sees, rather than burying a long list of vendor names.
06
Indonesia Footnotes Region-specific notes appear as footnotes tied to the clause they qualify, covering local payment confirmations and consent prompts relevant to Indonesia accounts.

Privacy Policy Questions

We collect the identity fields needed to verify you, the contact channel you choose, and the device and session signals our security layer reads. Payment references attach only when you fund or withdraw through DANA, OVO, GoPay or QRIS.

Core identity and transaction records stay on file for the retention window our regulator sets, then move to a sealed archive. Marketing preferences and optional fields are purged sooner, usually within the first cycle after closure.

Access is role-gated. Support agents see contact and ticket history, payments staff see transaction references, and privacy reviewers see the full file only when a request or escalation requires it. Every read is logged internally.

Only with the processors who run identity checks, payments and hosting, and only to the depth each task needs. We don't sell records, and we don't pass your file to advertisers or unrelated brands under any arrangement.

Send the request from the email tied to your account or open the privacy thread inside the app. We confirm receipt within a business day and complete the action inside the window written into this policy.

We update the effective date banner, log the change internally and notify account holders through the channel you've consented to. The previous version stays linked from the page so you can compare clause by clause.

Your account is handled under the framework that applies where local law permits across supported regions. Indonesia-specific footnotes call out any extra step, and our privacy lead answers cross-border questions in writing on request.