LEGAL REFERENCE

Privacy Policy at pipetbet

This page sets out how we handle the personal data you share when you open a pipetbet account, fund it with DANA, OVO, GoPay or QRIS, and move...

Data handlingIndonesia scopeYour rightsPlain EnglishUpdated regularly
pipetbet Privacy Policy at pipetbet

How We Handle Your Account Data

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

SUPPORT

Reach Our Privacy Desk

If you want to exercise a data right, raise a concern, or simply ask what we hold about you, our privacy desk...

Privacy Inbox Email our data protection contact and include your...
In-App Chat Open the live chat from inside your account...
Postal Address Written requests can reach our compliance team at...
EDITORIAL CLARITY

How This Policy Is Maintained

Our privacy text isn't a static file. It gets reviewed when the platform changes, when payment partners shift, and when Indonesian regulators or supported-region authorities publish fresh guidance that touches our duties.

Reviewed Quarterly

A named compliance owner walks through every clause each quarter, flags anything stale, and signs off the revised version before it replaces the live document on this page.

Legal Counsel

External counsel familiar with Indonesian data rules reads our draft before publication and challenges any wording that's vague, over-broad or out of step with local expectations.

Plain-English Pass

We strip legalese after the lawyers finish so the version you actually read stays readable. If a clause still feels dense, our editors rewrite it.

Change Log

Material edits are dated at the foot of this page. You can scan the log to see what shifted, when, and which section of your account record it touches.

Vendor Audits

Payment processors, KYC vendors and hosting providers are audited annually. Anyone who can't show current data-protection controls is removed from the supply chain.

Staff Training

Every pipetbet team member with account access completes privacy training before login is granted, and refreshes it each year against the current threat picture.

Consistency Across Our Policy Pages

This privacy text sits alongside our terms, cookie note and account rules. The points below show how they line up so you don't have to cross-read three documents...

Same Definitions
Words like 'account', 'wallet', 'session' and 'verified user' carry the same meaning here as they do in our terms and cookie notice.
Shared Retention
Retention windows quoted here match the ones referenced in our account-closure clause, so closing your account triggers the same erasure schedule.
Aligned Contact
The privacy inbox above is the same desk listed under our terms for data questions, avoiding the runaround between separate addresses.
Cookie Cross-Link
Cookie categories described briefly here are detailed in full inside our cookie notice, and the consent toggles control both documents.
KYC Overlap
Identity checks described in our terms rely on the lawful bases set out in this policy, so the two documents read as one process.
Regional Scope
Where this policy refers to supported regions, our terms use the same regional list. Updates to one trigger a parallel update to the other.
Version Parity
All policy documents share a version number stamped at the foot, so you can confirm you're reading the matched set in force today.
QUICK SIGNAL

What This Policy Page Includes

Below is the layout you'll see as you scroll. Each block addresses one slice of how we treat your data so you can jump to the part that...

Scope Block Opens the policy by naming who it applies to —...
Data Categories Lists the categories we collect: identity, contact, device, transaction and...
Retention Table Sets out how long each data category stays on file...
Rights Panel Walks through access, correction, erasure, portability and objection rights so...
Sharing Map Shows the third parties who touch your data — payment...
Update Notes Closes with the change log, the effective date and the...

Privacy Questions We Hear Often

We hold the identity details you gave at sign-up, your transaction history across DANA, OVO, GoPay and QRIS, your device fingerprint, and the sessions you ran on our casino and sportsbook. Nothing more without a lawful basis.

Yes. Send a request from the email tied to your account and we'll return a structured export inside the response window our licence sets, after verifying the request comes from the named holder.

Closure triggers our retention schedule. Identity and transaction records stay archived for the period our licence demands, then move to the deletion queue. Marketing preferences are cleared immediately on closure.

No. We don't sell or rent your data to third-party marketers. Sharing is limited to payment partners, KYC checkers, hosting providers and regulators with a lawful basis in supported regions.

Our cookie banner appears on first visit. You can accept essentials only, or allow analytics. The cookie notice details every category, lifespan and vendor, and your choice is remembered on your account.

Material edits trigger a banner on your next login and a dated entry in the change log at the foot of this page. Minor wording fixes are logged without a banner but stay visible.

A named compliance reviewer on our privacy desk picks up your request, checks the verification, and replies directly. The same reviewer handles access, correction and erasure so nothing gets handed around.