LEGAL REFERENCE

How We Handle Your Account Data

This is the syair sentana privacy policy. We wrote it so you can see, in plain language, what we collect when you open an account, why we hold...

Plain-language policyIndonesia-alignedVersioned & datedAccount-data focusedUpdated on change
Tour the Lobby Read FAQ
syair sentana How We Handle Your Account Data

Policy Posture & Data Handling Scope

Our privacy posture follows the regulations that apply where you sit. For Indonesia residents that means PDP Law alignment, with data stored only as long as your account is active or as record-keeping obligations require. We collect what's needed to open and secure your lobby session: identity confirmation, contact channel, device fingerprint, and the wallet reference you use to fund the account.

We don't sell your details to third parties, and marketing contact is opt-in. Where local law permits cross-border processing for fraud checks, that transfer is logged. You can request access, correction, or deletion through the channels listed further down this page.

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

HELP CHANNELS

Reach Us About Your Data

If you have a privacy question, three contact paths are open. Each one routes to the same data-handling desk — pick whichever fits your week.

Team online

Privacy Inbox

Email the team that owns this policy directly. Use the address listed in your account footer; we acknowledge within one business day and resolve standard data requests within fourteen.

In-Account Ticket

Open a ticket from inside your lobby with the subject line marked Privacy. The thread sits in your account history so you keep a full record of every reply we send back.

Live Chat Escalation

Start with chat, ask for the data-protection escalation, and the agent passes your case across. Useful when you need a quick confirmation that a deletion or correction has been logged.

WHY VISITORS TRUST US

How This Policy Is Reviewed

The policy isn't a static file. Here's who touches it, how often, and what triggers a refresh.

Legal Review Cycle

Indonesian counsel reads the policy at least twice a year and after every regulatory update from the relevant authority, so the wording you see reflects current obligations rather than last year's draft.

Versioned Drafts

Each published version carries a date and a change log entry. If a clause shifts, we mark what moved and why so returning account holders aren't surprised by silent edits.

Editor Sign-Off

Our compliance lead signs off before publication. No clause goes live on a developer push alone — that gate keeps the document grounded in policy rather than product convenience.

Plain-Language Pass

After legal locks the meaning, an editor rewrites for clarity. The aim: a reader without a legal background can still follow what data we hold and why.

Incident Trigger

Any data incident, even a contained one, forces a re-read of the affected section. If wording was vague, we tighten it before closing the incident ticket internally.

Reader Feedback

Confusion reported through chat or the privacy inbox feeds the next revision. If multiple readers ask the same clause, the clause gets rewritten in the following cycle.

Consistency Across Our Policy Pages

Our privacy policy lines up with the cookie, terms, and account-closure pages. Here's how the documents relate.

Scope
Privacy covers personal data. The cookie page covers browser storage. Terms cover the contract. Account-closure covers exit. Each links to the others where overlap matters.
Definitions
Words like account, session, and identifier carry the same meaning across all four pages. If we redefine a term, we update every page in the same release.
Retention
Retention windows quoted here match the windows quoted in account-closure. If one moves, both move, and the change log records the shift on each page.
Contact Paths
The privacy inbox listed here is the same address referenced in terms and cookies. One mailbox, one ticket queue — no scattered routing for data-related questions.
Update Cadence
All four policy pages share a review calendar. A scheduled cycle touches each document so wording drift between siblings is caught before publication.
Jurisdiction Notes
The Indonesia clauses you see here repeat verbatim in terms where relevant. Supported-region language stays identical across the set to avoid contradictory reads.
Version Stamps
Each sibling page carries its own date stamp but shares a release identifier. That lets you confirm two pages were updated together rather than weeks apart.
QUICK SIGNAL

What This Policy Page Looks Like

A few layout choices help you find clauses fast. Here's what you'll spot as you scroll the privacy document.

01
Anchored Sections Each clause has its own anchor link. Copy the link and share it with our desk when you're asking about a specific paragraph — saves both sides scrolling through the full document.
02
Date Stamp The header carries an effective date. If you opened your account before that date, the previous version is archived and reachable from the change log entry below it.
03
Change Log Every revision lists what moved. Reading the log is faster than re-reading the whole policy when you only want to know what shifted since your last visit.
04
Plain Summary Each major clause opens with a one-line summary in plain English before the formal wording. Skim the summaries; dive into the formal text only when you need the precise terms.
05
Cross-Links Where a clause touches cookies, terms, or closure, an inline link points to the sibling page. You won't have to guess where the related rule sits.
06
Print View A print-friendly layout strips navigation so you can save a clean PDF for your records. Useful if you want a snapshot of the policy as it stood on the day you opened the account.

Privacy Questions We Get Asked

Your name, contact channel, date of birth for age confirmation, the wallet reference you fund with — DANA, OVO, GoPay or QRIS — and the device signature of the browser you opened the account on.

For as long as the account is active, plus the retention window record-keeping rules require after closure. The exact window sits in the retention clause and matches what's quoted on the account-closure page.

Yes. Send the request through the privacy inbox or open a ticket marked Privacy from inside your lobby. We acknowledge within one business day and return the export inside fourteen.

Only with processors we need to run the service — payment routing, fraud screening, hosting. We don't sell data, and marketing partners receive nothing unless you've explicitly opted in from your account settings page.

Identifying details move to a closed-account archive for the legally required retention window, then they're deleted. Anything not bound by retention rules is removed on closure rather than held back indefinitely.

The header date updates and the change log records what moved. Material changes also trigger an in-account notice the next time you sign in, so silent rewrites aren't a concern.

Indonesia's personal data protection framework where you sit in supported regions. Where local law permits cross-border processing for fraud or hosting, that transfer is documented inside the relevant clause above.