LEGAL REFERENCE

How We Handle Your Privacy at berkatbet

This is our privacy policy — the document that tells you what we collect when you open an account with berkatbet, why we keep it, and how long...

Account dataWallet recordsCookies disclosedYour rightsIndonesia scope
berkatbet How We Handle Your Privacy at berkatbet

Privacy Posture and Data Scope

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

SUPPORT

Privacy Contact Paths

If you have a privacy question, three channels reach our data team directly. Each one routes to the same internal queue, so pick whichever suits the moment.

Privacy Inbox Email our data team at the privacy address listed in your account settings. We confirm receipt within one business day and aim to close most data requests inside seven working days from that point.
Live Chat Open the chat bubble in the lobby and ask for the privacy desk. The agent flags your case, takes your account reference, and our data officer follows up by email so the trail stays written down.
Postal Address For formal requests — data export, erasure, or regulator correspondence — you can write to the postal address printed in the footer. We log every letter and reply on official letterhead.
TRUST MARKERS

How We Review This Policy

This policy isn't a one-and-done page. We review it on a schedule and after any change to how we process your data.

Quarterly Review

Our compliance team reads this policy every three months against the latest Indonesia data rules. If a clause stops matching...

Legal Sign-off

Every revision is signed off by external counsel familiar with Indonesian consumer-protection and financial-services rules. We don't push wording live...

Plain-Language Pass

After legal sign-off, an editor strips jargon so the clauses read cleanly in en-ID English. You shouldn't need a lawyer...

Change Log

Material changes are listed in a dated change log at the foot of this page. You can scan it in...

User Notice

When a change affects your rights or our retention windows, we email account holders before the new version takes effect...

Audit Trail

Internal access to your data is logged. If our team queries your records, the action is timestamped and tied to...

Consistency With Our Other Policy Pages

This privacy policy sits alongside our terms, cookie notice and KYC pages. The clauses below stay aligned across all of them so you don't read one thing here...

DefinitionsTerms like account, wallet, session and device carry the same meaning here as on our terms page. If a definition is updated, both pages move together in the same release.
Retention WindowsHow long we keep transaction logs is stated identically on the privacy policy and the KYC page. The figure is driven by financial record rules, not by our preference.
Cookie ScopeWhat we set, why, and how to refuse is detailed on the cookie notice and summarised here. Neither version contradicts the other; the cookie notice simply goes deeper.
Third PartiesThe list of processors — payment partners, KYC vendors, analytics — is the same name-for-name across this page and our processor register, which we publish on request.
Your RightsAccess, correction, erasure and portability rights read the same way here as in the account-closure flow. The wording matches so there's no surprise when you exercise one.
JurisdictionReferences to supported Indonesia regions and where local law permits use identical phrasing across legal pages. We don't soften the scope on one page and tighten it on another.
Contact RoutesThe privacy desk addresses listed here match those in the footer, the help centre and the terms page. One queue, one response time, no scattered inboxes.
PLATFORM SNAPSHOT

What This Policy Page Covers

Here are the visible building blocks of this policy page, so you know where to look for what.

01
Data Inventory A clear list of categories we collect — identity, device, wallet references, session logs — with a one-line reason next to each. No vague catch-all clauses dressed up as legal cover.
02
Purpose Map Each data category is matched to a specific purpose: opening your account, processing top-ups, fraud checks, or regulator reporting. If we can't tie data to a purpose, we don't keep it.
03
Retention Table A short table showing how long each category stays on file. Account-closure requests are honoured against this table, not against an open-ended internal preference.
04
Rights Panel A panel summarising your rights — access, correction, erasure, portability, objection — with the exact channel to use for each. No need to dig through dense paragraphs.
05
Cookie Summary A short summary of cookies set on this domain, with a link to the full cookie notice. Strictly necessary, analytics and preference cookies are listed separately.
06
Change Log Dated entries showing what shifted in the policy, when, and why. The most recent change sits at the top so you can confirm at a glance whether anything affects you.

Privacy Policy Questions

We collect the identity details you submit at sign-up, contact information, device and session data, and the wallet references tied to your DANA, OVO, GoPay or QRIS top-ups. Each item is mapped to a stated purpose.

We share with payment partners, KYC vendors and regulators only when there's a lawful basis. We don't sell your data, and our processor register lists every external party by name on request.

Retention follows the financial record-keeping rules that apply to us in supported Indonesia regions. Most transaction logs sit on file for several years; once the window closes, records are anonymised or deleted.

Yes. Email the privacy inbox or open chat and ask for a data export. We confirm your identity, then deliver the file inside the working-day window stated at the top of this policy.

Request closure through chat or the privacy inbox. We action the closure, then erase what we're allowed to erase. Records that financial rules force us to retain are locked down and not used for marketing.

Yes. Material changes trigger an email to account holders before they take effect, and the change log at the foot of this page records what shifted, when, and why in plain language.

Strictly necessary cookies for session security, plus optional analytics and preference cookies you can refuse. The full list with names, purposes and lifetimes lives on our cookie notice, linked from this page.