LEGAL REFERENCE

Our Privacy Policy, Written Plainly

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

Account dataCookiesYour rightsData retentionIndonesia
ramebola Our Privacy Policy, Written Plainly

How ramebola Handles Your Personal Data

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

HELP CHANNELS

Privacy Contact Paths

If you have a privacy question, a data-access request, or you want a copy of what we hold on your account, reach...

Privacy Inbox Email our data team directly with your account...
In-Account Form Sign in and open the privacy panel from...
Live Chat Desk Our chat agents triage privacy queries around the...
WHY VISITORS TRUST US

How We Review This Policy

This document is not static. We revisit it on a fixed cycle and whenever Indonesian data rules change, so what you read here matches how ramebola actually handles your file.

Quarterly Review

Our legal team reads the policy every quarter against current Indonesian data-protection rules and updates clauses that drift. Change dates are stamped at the foot of the page.

Named Data Officer

A named privacy officer signs off every revision. You can request their contact through the in-account form if your query needs escalation beyond first-line chat.

Plain-Language Drafting

We brief drafters to avoid jargon. If a clause reads like a contract template, we send it back so you can understand it on a phone screen.

Version Stamps

Each revision carries a version number and an effective date. Old versions stay archived so you can compare what changed between the policy you accepted and today's text.

Independent Audit

An external reviewer checks our retention windows and cookie register annually. Findings feed back into the next quarterly update before the policy is republished.

Reader Feedback

If a paragraph confuses you, the feedback link at the foot of this page goes straight to the drafting team. Reader notes shape the next revision.

Consistency Across Our Policy Pages

Our privacy policy sits beside our terms, cookie notice and account rules. The clauses below show how this page lines up with its siblings so nothing contradicts when...

Privacy vs Terms
Terms cover the rules of using your account; this page covers what we store about you. Where they touch — like account closure — wording is mirrored.
Privacy vs Cookies
Cookies sit in a sibling notice with the full register. This page summarises categories and points to the cookie page for the line-by-line list.
Privacy vs KYC
KYC checks generate data covered here. The KYC page explains which documents we ask for; this page explains how long we keep them.
Privacy vs Payments
Payment references — DANA, OVO, GoPay, QRIS — are processed under this policy. The payments page covers flow; this page covers retention.
Privacy vs Marketing
Marketing opt-ins are described here and mirrored in the preference centre. Toggling one updates the other within the same session.
Privacy vs Security
Security measures referenced here align with the controls listed on the account-safety page. No contradictions between the two.
Privacy vs Complaints
If a privacy request stalls, the complaints page tells you the escalation route. This page names the data officer who receives those escalations.
SERVICE CONTEXT

What This Policy Page Includes

The policy is laid out so you can find the clause you need without scrolling the whole document. The highlights below describe the visible blocks on this page and what each one carries.

01
Scope Block Opens with what data we cover and which ramebola surfaces it applies to. If a sub-brand or partner runs different rules, the scope block flags it up front.
02
Rights Panel Lists your access, correction, erasure and portability rights with the form route to exercise each. Indonesian residents see the local rule references attached.
03
Retention Table A short table showing how long each category sits with us — account file, session logs, payment reference, marketing flag — with the rule that sets the window.
04
Cookie Summary A summary of cookie categories used on ramebola pages, with a link out to the full register and the controls you can toggle from your browser.
05
Change Log Every revision logged with date and a one-line note on what shifted. You can scan it to see whether a clause you read last month still reads the same way.
06
Contact Footer The privacy officer route, the chat desk and the in-account form sit at the foot. Three paths, same destination, so you can pick whichever fits your query.

Privacy Policy Questions

We hold your registration details, verified identity documents, session logs, device fingerprints and the payment reference linked to your DANA, OVO, GoPay or QRIS top-ups. Nothing beyond what the account flow needs to run securely.

Sign in, open the privacy panel from your account menu and submit an access request. We confirm receipt the same day and return the file inside seven working days, packaged in a readable export.

Yes. Submit an erasure request through the in-account form or email the privacy desk. We remove or anonymise your file once any retention duties under Indonesian financial-record rules have lapsed for your account.

We don't sell your data. We share limited references with payment processors and verification partners strictly to run your account. Each partner is named in the retention table with the purpose and the data scope attached.

Open the preference centre inside your account and toggle the marketing flag off. The change applies straight away across email and in-app channels, and we log the timestamp on your privacy file for the record.

We review the document every quarter and whenever Indonesian data rules shift. Each revision carries a version number and an effective date at the foot of the page so you can track what changed between visits.

Escalate through the complaints page, which routes your file directly to the named privacy officer. Include your account reference and the original ticket ID so the officer can pick up the thread without delay.