LEGAL REFERENCE

How sedia4d Handles Your Account Data

This is the sedia4d privacy policy — the page that spells out what we collect when you open an account, why we keep it, and how long it...

Account dataDevice signalsPayment referencesIndonesia scopeRetention rules
Enter Game Lobby Read FAQ
sedia4d How sedia4d Handles Your Account Data

Privacy Posture and Jurisdiction Scope

Our privacy posture applies where local law permits and across supported regions in Indonesia. We collect the minimum we need to run your account: your contact details, login credentials, session signals, and a payment reference token tied to your chosen rail. We don't sell your data, and we don't share it with marketing networks outside the scope of running the lobby you

signed up for. Wallet identifiers from DANA, OVO, GoPay and QRIS are tokenised on receipt, so the raw wallet numbers never sit in our long-term storage. Requests to access, correct, or delete your record can be raised through the support paths below, and we respond within the windows Indonesian data rules expect.

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

HELP CHANNELS

Privacy Contact Paths

Privacy Inbox Email the privacy desk directly when you want a copy of your record, a correction, or a deletion request. We acknowledge within one business day and confirm the outcome inside the statutory window.
In-Lobby Chat Open the chat bubble from any signed-in page and ask for the privacy team. The agent routes your ticket to the data handler on duty and shares a reference number for follow-up.
Account Settings Head to your account settings to download your data, toggle marketing preferences, and review the device list tied to your login. Changes apply immediately across your sedia4d sessions.
WHY VISITORS TRUST US

Editorial Trust Signals for This Policy

Reviewed Quarterly

Our policy text is reviewed every quarter against Indonesian data rules and the wallet partner agreements behind DANA, OVO, GoPay and QRIS. Any change is dated at the foot of this page.

Plain Language

We rewrite legal clauses into English a reader can actually parse. If a paragraph needs a lawyer to decode, it doesn't belong on this page and gets sent back for another pass.

Named Owner

A named data protection lead signs off every revision. That person also handles escalations when a ticket can't be closed by the front-line privacy desk inside the first response window.

Change History

Older versions of this policy stay accessible on request, so you can compare what changed between the version you accepted and the one currently published on sedia4d.

Scoped Sharing

We share data only with the wallet rails, fraud tooling and identity checks that keep your account safe. Each partner is listed by category in the details section above.

Indonesia Focus

This document is written for the Indonesia audience first. Cross-border transfers, when they happen, follow the safeguards our regional counsel signs off before any record leaves the country.

Consistency Across Our Legal Pages

Privacy vs Terms
This policy explains data handling; the terms page covers account conduct. The two cross-reference each other so a clause never lives in only one place without a pointer.
Privacy vs Cookies
Cookie behaviour gets its own page for granular toggles. This policy summarises the categories and links out when you want the per-cookie breakdown.
Privacy vs KYC
KYC document handling is described here at a category level and detailed on the verification page, with retention windows aligned between both documents.
Privacy vs Payments
Wallet tokenisation is described identically on the payments page so the rules you read here match what you see at checkout for DANA, OVO, GoPay and QRIS.
Privacy vs Support
Support transcripts are referenced here and on the help page using the same retention figure, so a ticket you raised is governed by one consistent rule.
Privacy vs Marketing
Marketing opt-ins are summarised here and managed on the preferences page. Toggling off in one place toggles off everywhere within the same session.
Privacy vs Security
Security controls cross-reference this page when explaining encryption, device binding and session expiry, so the language matches end-to-end.
AT A GLANCE

What This Policy Page Shows You

Section Anchors A jump menu at the top of the policy lets...
Last Updated Stamp Every revision carries a visible date stamp at the foot...
Rights Summary Card A short card near the top lists your data rights...
Glossary Tooltips Hover any underlined legal term and a tooltip explains it...
Printable Version A print-friendly layout is one click away if you want...
Contact Footer The page ends with the privacy desk email, the in-lobby...

Privacy Policy Questions

We collect your contact details, login credentials, the device signals tied to your session, and a tokenised reference for the wallet rail you chose. Nothing beyond that is needed to run your account day to day.

Active account data stays for as long as you use sedia4d. After closure, we retain the minimum required by Indonesian financial rules, then purge. Exact windows per category are listed in the details section above.

Only the reference token needed to settle a transaction on DANA, OVO, GoPay or QRIS. The wallet partner sees what they need to clear the payment and nothing about your lobby activity beyond that.

Yes. Open account settings and use the data export button, or email the privacy desk. We package your record into a readable file and deliver it inside the statutory response window.

Raise a deletion request through the privacy inbox or in-lobby chat. We confirm your identity, close the account, and purge data outside the records we're legally required to retain for audit purposes.

Primary storage sits with regional providers serving Indonesia. Any cross-border transfer, when it happens, follows the safeguards our regional counsel signs off before the record leaves the country, in line with local rules.

Material changes trigger a notice on your next sign-in and an email to the address on file. The last-updated stamp at the foot of the page always reflects the current revision date.