LEGAL REFERENCE

How yogapro slot Handles Your Account Data

This is the privacy policy for yogapro slot. We wrote it so you can see, in plain English, what we collect when you open an account, why we...

Privacy PolicyAccount DataIndonesiaPlain EnglishLast Reviewed
yogapro slot How yogapro slot Handles Your Account Data

Policy Posture and Jurisdiction Notes

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

PLAYER SUPPORT

Privacy Contact Paths

If something in this policy is unclear, or you want to exercise a data right, reach us through one of these channels. Privacy queries are handled by a named team rather than general support, so the routing matters.

Team online

Data Requests Inbox

Email our privacy desk for access, correction, portability or erasure requests tied to your yogapro slot account. We acknowledge inside two working days and resolve within the statutory window for your region.

In-Lobby Privacy Chat

Open the chat bubble while signed in and tag the message as a privacy matter. The agent will route you to the data team rather than billing, so your request hits the right queue immediately.

Postal Notice Address

For formal notices or regulator-mediated requests, our registered correspondence address is published in your account footer. Use this channel when you need a paper trail beyond the email record.

WHY VISITORS TRUST US

Editorial Trust Signals for This Policy

This policy is reviewed by people, not auto-generated. Here's how we keep it honest and current.

Named Policy Owner

A single data protection lead signs off every revision of this page. Their initials and the review date sit at...

Quarterly Review Cycle

We re-read the full policy every quarter and after any material change to how the lobby or wallet flow handles...

Legal Counsel Sign-off

Indonesian counsel reviews wording before it goes live, particularly clauses touching cross-border transfer and retention. We don't push policy changes...

Plain-English Mandate

We avoid stacked legalese where ordinary words work. If a paragraph reads like boilerplate, flag it and we'll rewrite. Clarity...

Versioned Change Log

Every published version of this policy is archived with a timestamp. You can ask for a previous version and we'll...

Independent Audit Hooks

Our data handling is structured so an external auditor can verify the claims on this page against actual logs. We...

Consistency Across Our Policy Pages

This privacy page sits alongside our terms, cookie notice and account-closure policy. We keep the wording aligned so you don't get one promise here and a different one...

Privacy vs TermsThe terms govern your account contract; this page governs your data. Where they touch — for instance on account closure — both pages use identical retention windows.
Privacy vs CookiesCookie specifics live on the cookie notice. This page references categories only and links out, so updates to one don't leave the other stale or contradictory.
Privacy vs KYC NoticeIdentity verification details are mirrored here and on the KYC page. The lawful basis, retention period and deletion trigger match word-for-word across both.
Privacy vs Wallet NoticeDANA, OVO, GoPay and QRIS data flows are described consistently with the wallet help page, so technical and legal copy agree on what leaves your device.
Privacy vs Marketing PrefsOpt-in and opt-out language matches the preferences screen exactly. If you toggle marketing off there, this policy commits us to honour it everywhere.
Privacy vs Closure PolicyWhat we keep after you close your account is stated identically on both pages, including the legal hold period and the anonymisation step that follows.
Privacy vs Complaint PathEscalation routes named here mirror the complaints page, so a privacy issue and a service issue follow the same documented ladder up to the regulator.
AT A GLANCE

Visible Elements of This Policy Page

These are the on-page features that shape how the privacy text reaches you. They sit around the policy itself and make it easier to read on a phone...

Anchored Section Index A sticky index runs down the side on desktop and...
Last-Reviewed Stamp The header carries a visible review date and version number...
Inline Right-of-Action Buttons Next to each clause about a data right, a small...
Bahasa Toggle A language switch lets you flip the policy text into...
Print and PDF Export You can export the full policy as a dated PDF...
Change-Highlight Mode Toggle this on to see what changed since the previous...

Privacy Policy Questions We Get

We collect your registered name, contact handle, date of birth for age checks, device and session metadata, plus the e-wallet reference tied to your first deposit through DANA, OVO, GoPay or QRIS. Nothing beyond that at signup.

We hold core account records for the period Indonesian financial and tax law requires after closure, then anonymise or delete them. The exact window is published in the retention clause above and matches the closure policy.

Yes. Send an access request through the privacy inbox or the in-lobby chat. We acknowledge inside two working days and deliver a structured export within the statutory window for your supported region, free of charge.

Only the minimum needed to settle a transaction. DANA, OVO, GoPay and QRIS receive the reference and amount; they don't get your gameplay history. Their own privacy notices govern what happens on their side.

Encrypted backups and some infrastructure services may sit outside Indonesia where local law permits. Those partners are bound by written data processing agreements, and the safeguards are listed in the cross-border clause of this policy.

Material changes trigger an in-account notice before they take effect. Minor edits are logged in the change history at the foot of this page. The change-highlight mode shows you exactly what moved between versions.

Start with our privacy desk, then our data protection lead, then the relevant Indonesian supervisory authority. The full ladder, with contact details for each step, is mirrored on the complaints page so the path is consistent.