LEGAL REFERENCE

How benuajitu Handles Your Account Data

This is the benuajitu privacy policy — the page that tells you exactly what we collect when you open an account, how we store it, and who can...

Plain-English PolicyIndonesia-FocusedAccount Data OnlyUpdated RegularlyReader-Friendly
benuajitu How benuajitu Handles Your Account Data

Our Privacy Posture For Indonesia Accounts

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

SUPPORT

Reach Us About Your Privacy

If a privacy question comes up — about your data, a correction request, or how a payment reference is logged — we...

Privacy Inbox Email our privacy desk for data access requests...
Live Chat Open the chat bubble on any benuajitu page...
Policy Updates Feed Subscribe inside your account to receive a note...
WHY THIS PLATFORM

Editorial Trust Behind This Policy

This policy isn't a template. It's reviewed by people who actually run the benuajitu account flow, and it ships with the editorial signals you should expect from a...

Named Reviewers

Each policy revision is signed off by a named member of our compliance team before it goes live. You're not...

Version History

We keep a dated log of every change to this privacy policy. If you want to know what the text...

Plain-English Drafting

We rewrite legal jargon into sentences you can scan on a phone. The aim is for you to finish the...

Indonesia-Specific

This document is written for Indonesia accounts, with wallet references like DANA, OVO, GoPay and QRIS handled the way local...

Independent Review

An external policy advisor reads this page each cycle and flags anything ambiguous. Their notes feed back into the next...

Reader Feedback Loop

When you ask a privacy question that the policy doesn't answer cleanly, we treat that as a drafting bug. The...

Consistency Across Our Policy Pages

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

Data Scope
The data categories listed here match what's named in our terms and cookie notice — same fields, same labels, same retention windows.
Retention Windows
How long we keep account data is stated identically across pages. If a number changes here, it changes everywhere in the same release.
Access Rights
Your right to request, correct or close is described the same way in this policy and in the account settings help text inside the lobby.
Wallet References
DANA, OVO, GoPay and QRIS handling is described once and cross-linked, so the cashier page and this policy never disagree about what's logged.
Update Cadence
Privacy, terms and cookie notice are reviewed on the same cycle. You won't see a fresh privacy policy paired with a stale terms page.
Contact Routes
The privacy inbox, chat path and update feed listed here are the same routes referenced in our terms and account help — no orphan email addresses.
Jurisdiction Wording
Phrases like 'where local law permits' and 'supported regions' are used consistently so the geographic scope reads the same on every legal page.

What This Policy Page Shows You

The privacy page has its own layout cues so you can find the part you need without scrolling the whole document. Here are the visible elements...

Dated Header

The top of the page carries the effective date and the previous version's date. One glance tells you whether the policy you're reading has shifted since your last visit.

Section Anchors

Each policy block has a stable anchor link. You can share a direct URL to the data-retention paragraph or the access-rights section without sending the whole page.

Change Markers

When wording moves between versions, the affected paragraphs carry a small marker for thirty days. You see what's new without re-reading text you already accepted.

Plain-Text Toggle

A toggle strips styling and shows the policy as plain text, useful when you want to copy a clause into an email to your own records or advisor.

Glossary Tooltips

Hover or tap any underlined term to see a one-sentence definition. Words like 'processor', 'retention' and 'controller' open inline rather than sending you elsewhere.

Print-Friendly View

A print layout collapses navigation and renders the policy as a clean document. Useful if you keep a paper copy of the policies you've agreed to across services.

Privacy Policy Questions We Hear

We collect identity fields, contact details, your chosen wallet reference, and basic device signals needed to keep the session secure. Nothing beyond what the account flow shows you on screen at sign-up is stored.

Active account data stays while your account is open. After closure, we retain limited records for the period local law requires, then remove them. Exact windows are listed in the retention paragraph above.

Yes. Email the privacy inbox from the address on your account and we'll prepare an export. In supported regions we aim to deliver it inside the statutory window, usually well before the deadline.

Only the transaction reference needed to settle a deposit or withdrawal. DANA, OVO, GoPay and QRIS processors do not receive your lobby activity, login times, or anything beyond the cashier event itself.

The dated header updates and a change marker sits next to any moved paragraph for thirty days. If you've subscribed to the policy feed, a note also lands in your account inbox.

Where local law permits, yes. Open a request through the privacy inbox or chat, confirm identity, and we'll process closure. Some records are retained for the statutory minimum before final deletion.

Use the privacy inbox or live chat and quote the section anchor. We treat unclear wording as a drafting issue, so your question often shapes the next version of this page directly.