LEGAL REFERENCE

How rimbaslot Handles Your Account Data

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

Policy v3.2Indonesia scopePlain-languageAccount data onlyUpdated quarterly
rimbaslot How rimbaslot Handles Your Account Data

Policy Posture and Jurisdiction Notes

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

SUPPORT

Privacy Contact Paths

Data Officer Email Write to our privacy desk for access, correction...
In-Account Privacy Panel Sign in and head to the privacy panel...
Live Chat Escalation Open chat from the lobby footer and ask...
EDITORIAL CLARITY

Editorial Trust Signals for This Policy

Legal Review

Every clause on this page is checked by counsel familiar with Indonesia data rules before it goes live. We log the review date internally and reflect it in the version stamp at the top of the document.

Version History

We keep older versions of the policy available on request so you can see what changed between revisions. Material edits trigger an in-account notice rather than a silent footer update.

Named Data Owner

A single accountable owner signs off on policy changes at rimbaslot. That person also handles regulator correspondence, so requests don't bounce between teams when you raise a privacy ticket.

Processor Register

We maintain a written register of every vendor touching your data — KYC, payments, analytics — and refresh contractual safeguards annually. The register is available to regulators on demand.

Breach Protocol

If a security incident touches account data, our protocol notifies affected holders inside the regulatory deadline and gives concrete steps you can take to protect the account on your end.

Minimal Collection

We collect only the fields needed to run your account, clear DANA, OVO, GoPay or QRIS transactions, and meet anti-fraud duties. Optional fields stay optional and are clearly marked at sign-up.

Consistency With Our Other Policy Pages

Terms of Service
Privacy clauses here mirror the data-handling references inside our terms. Where the terms point to retention or KYC, this policy expands the detail without contradicting the contractual wording you accepted at sign-up.
Cookie Notice
Cookie-level tracking sits in a separate notice but uses the same legal bases listed here. Consent toggles you set there feed straight into the preferences recorded against your rimbaslot account.
KYC Policy
Identity verification rules sit in our KYC page. This privacy document explains what happens to the documents you upload — how long they're kept and which processors see them during checks.
AML Policy
Anti-money-laundering retention overrides standard deletion windows where Indonesia law requires longer storage. Both pages reference the same statutory periods so there's no gap between the two.
Acceptable Use
Behaviour rules live in acceptable use; this page only covers the data captured when those rules are enforced. Investigation records follow the retention table published below in our policy panel.
Marketing Consent
Promotional contact preferences are governed by the consent record described here. The marketing page itself tells you what campaigns run; this one tells you how the opt-in is stored and revoked.
Complaints Procedure
If you disagree with how we've handled your data, the complaints page lists the escalation ladder. This policy names the data officer who receives the first-tier privacy complaint at rimbaslot.
SERVICE CONTEXT

What Shapes This Policy Page

Version Stamp A dated version number sits at the head of the...
Plain-Language Blocks Each clause is written in short paragraphs rather than dense...
Rights Summary A rights summary near the policy panel lists access, correction...
Retention Table A retention table shows how long each category of data...
Processor List A named processor list inside the page tells you which...
Change Log A change log at the foot summarises every revision in...

Privacy Policy Questions

We store the identity fields you enter at sign-up, contact details, device markers, and transaction references linked to DANA, OVO, GoPay or QRIS. Optional profile fields are clearly marked and stay blank unless you fill them in yourself.

Retention follows our published table. Core identity and KYC files stay for the statutory minimum required in Indonesia for anti-fraud and tax duties; marketing consent records and optional fields are purged on a shorter timer once closure is confirmed.

Yes. Sign in, open the privacy panel on your dashboard, and request the export. We package the record in a portable format and deliver it inside the statutory window, or sooner where the file is straightforward.

Only the verification processor named in our register and the internal compliance team handle your KYC files. The documents are not used for marketing, not shared with affiliates, and are deleted on the schedule set out in the retention table.

Toggle the marketing switch off in your account preferences or reply STOP to any message. The change applies immediately to future campaigns; transactional notices about your account and payments continue regardless because they're not marketing.

Material edits trigger an in-account notice the next time you sign in, plus an entry in the change log at the foot of this page. Minor wording fixes are logged but don't always trigger the in-account banner.

Start with the data officer email listed on this page. If you're not satisfied with the response, our complaints procedure names the regulator you can approach in Indonesia and the evidence you should bring to the escalation.