LEGAL REFERENCE

How We Handle Your Account Data

This is the bigobet899 privacy policy — the document that explains what we collect when you open an account, why we hold it, and how long it stays...

Data we collectWhy we hold itYour rightsRetention windowsContact paths
bigobet899 How We Handle Your Account Data

Policy Posture and Jurisdiction Wording

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

24/7 SUPPORT

Privacy Contact Paths

If you want to raise a privacy question, correct a record or ask us to delete data we no longer need, our team is reachable through the channels below. We aim to...

Privacy inbox Email our data desk directly with the address tied to your account. Include the request type — access, correction, deletion or export — and we'll acknowledge inside 24 hours.
In-lobby chat Open the chat bubble after you sign in and ask for the privacy team. The agent routes your ticket to a data handler rather than a generic support queue, keeping context attached.
Written request For formal data subject requests we accept signed letters routed through the registered contact on file. We log every written request and confirm receipt before any action is taken on your record.
WHY VISITORS TRUST US

Editorial Trust Signals for This Policy

This policy isn't a copy-paste template. We review it on a fixed cadence so the wording matches what our systems actually do with your data.

Named owner

A named data protection lead signs off every revision of this document. You're not reading anonymous boilerplate — there's a person accountable for the contents and the responses you receive.

Versioned edits

Each change carries a date stamp and a short note describing what moved. If a clause about retention or processors shifts, you can see when and why it happened on this page.

Legal review

External counsel familiar with Indonesia data rules reviews material updates before they go live. We don't publish wording that hasn't passed that second pair of eyes first.

Processor register

We keep an internal register of every vendor that touches your data. Onboarding a new processor triggers a contract review and, where needed, an update to this policy.

Breach protocol

A documented incident plan covers detection, containment and notice timelines. If a qualifying event affects your account, you'll hear from us through the contact channel you registered.

Plain wording

We rewrite legalese into sentences you can actually parse. Where a technical term is unavoidable, we explain it in the same paragraph rather than burying it in a glossary.

Consistency Across Our Policy Pages

This privacy policy is one of several legal documents on bigobet899. We keep them aligned so you don't get conflicting answers depending on which page you land on.

Terms of Service
Account rules and contractual duties live in the Terms; data handling lives here. Both documents reference the same retention windows so the picture stays coherent.
Cookie Notice
Cookie categories and consent controls are documented in the cookie notice. This privacy policy points to it rather than duplicating the table, keeping a single source of truth.
KYC Statement
Identity verification steps are summarised here and detailed in the KYC statement. The lawful basis cited matches across both pages without rewording.
AML Notice
Anti-money-laundering record-keeping uses the same retention clock you'll see in this policy. Nothing in the AML notice extends storage beyond what we list here.
Complaints Policy
Privacy complaints route through the same channels described in the complaints policy, with one extra step for data subject requests handled by our privacy lead.
Marketing Preferences
Opt-in and opt-out controls referenced here mirror the toggles in your account preferences screen, so changing one place updates the other immediately.
Retention Schedule
The high-level retention table in this policy matches the detailed schedule kept by our compliance team. Audit reviews check both for drift each quarter.
AT A GLANCE

What This Policy Page Covers

Here's the layout of this document so you can jump to the section you actually need rather than reading top to bottom. Each block below maps to a clause in the full text.

01
Data categories A clear breakdown of identity, contact, device and transaction data we collect when you open and use your account, with examples drawn from real registration steps.
02
Lawful basis For every category we name the lawful basis — contract, legal duty, legitimate interest or your consent — so you can see why we're allowed to hold that field.
03
Retention windows Concrete time periods, not vague phrases. You'll see how long account records, transaction logs and verification documents stay on file before deletion or anonymisation.
04
Your rights Access, correction, deletion, portability and objection rights are listed with the steps to exercise each one. We tell you what we need from you to verify the request.
05
Sharing map A short map of who else sees your data — payment processors, KYC vendors, hosting partners — and the safeguards we keep in place for cross-border movement.
06
Update log A change history at the foot of the document showing the last review date and a one-line note on what shifted, so you can spot revisions without re-reading everything.

Privacy Policy Questions

We collect identity fields, contact details, a password hash and the device signals your browser sends. Once you transact, we add references to your DANA, OVO, GoPay or QRIS movements tied to that account.

Active account data stays for the life of the account plus the retention window required by local law for financial records. After that, fields are deleted or anonymised on a scheduled run, not held indefinitely.

Yes, where local law permits. Send a deletion request from your registered email and we'll verify it. Some records — like transaction logs — must be retained for the legal minimum before removal can complete.

No. We do not sell personal data. Marketing partners only receive aggregated, non-identifying metrics, and any targeted messaging you receive is based on preferences you set inside your own account screen.

Primary storage sits with hosting partners under written data processing terms. Where data crosses borders, we apply safeguards equivalent to the standards your jurisdiction expects, and we list the regions involved on request.

Email the privacy inbox or open the in-lobby chat and ask for the privacy team. State the right you want to use — access, correction, portability, objection — and we'll guide you through the verification step.

Material changes trigger a notice on your account dashboard and an email to your registered address. The update log at the foot of this page also records every revision with a short description and a date.