LEGAL REFERENCE

Privacy Policy at datajitu

This is the privacy policy page for datajitu. We've written it in plain language so you can see exactly what account data we hold, how long we keep...

Account dataCookiesRetention windowsIndonesia scopeYour rights
datajitu Privacy Policy at datajitu

Our Privacy Posture and Scope

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

PLAYER SUPPORT

Reach Our Privacy Desk

If something in this policy isn't clear, or you want to exercise a data right, use one of the contact paths below. Our privacy desk answers separately from general support so your request stays on the policy track.

Team online

Privacy email

Write to [email protected] for data access, correction or deletion requests. Include the email on your account so we can match your record without asking for extra identifiers from you.

In-account ticket

Open a ticket from your account dashboard and tag it Privacy. This routes straight to the policy team and keeps a timestamped trail you can refer back to during follow-ups.

Live chat handoff

Start with lobby chat and ask for the privacy desk. The agent escalates your case, shares a reference number, and the privacy team picks it up within one working day in Indonesia.

TRUST MARKERS

How We Review This Policy

This policy isn't a one-time document. We revisit the wording when Indonesian rules shift, when a new payment rail like QRIS expands, or when a lobby feature changes...

Editorial owner

Our compliance lead owns this page and signs off every revision. No marketing copy slips in — the wording you...

Version dates

Every update carries a visible effective date at the top of the policy. If we change how we handle your...

Legal review

Indonesian counsel reviews this policy at least twice a year, plus whenever a regulator publishes new guidance. Their notes shape...

Security audit

Our infrastructure team runs quarterly checks on how account data, session logs and payment references are stored. Findings that affect...

Vendor checks

Any third party that touches your data — payment processors, game providers, analytics — is listed internally and re-screened yearly...

User feedback

Privacy questions from your tickets feed back into this page. If the same clarification comes up repeatedly, we rewrite the...

SIDE BY SIDE

Consistent Across Our Legal Pages

Our privacy policy lines up with the other legal pages on datajitu. The comparison below shows where this page sits relative to terms, cookies and account rules so you don't have to...

01

Privacy vs Terms

Terms cover what you agree to when using the lobby. This privacy page covers what we do with the data generated by that use — two separate documents, written to stay consistent.

02

Privacy vs Cookies

The cookie notice lists trackers in detail. This page summarises why we set them and links across, so you only read the deep technical list when you actually want it.

03

Privacy vs KYC

KYC rules sit in the account verification page. Here we explain what happens to the documents you upload, how long we hold them, and when they're purged from our systems.

04

Privacy vs Payments

Payment terms describe DANA, OVO, GoPay and QRIS flows. This policy describes the data those flows generate — transaction references, timestamps, amounts — and how we protect it.

05

Privacy vs Marketing

Marketing preferences are managed in your account. This policy explains the legal basis for any message we send and how to withdraw consent without closing the account itself.

06

Privacy vs Security

Security pages describe controls. This page describes data — the two are written together so an engineer reading both sees the same model you do as an account holder.

07

Privacy vs Regional

Regional notices flag jurisdiction-specific rights. This page is the general baseline; the regional addendum extends it where Indonesian law gives you stronger protections in supported regions.

AT A GLANCE

What Defines This Policy Page

Beyond the legal wording, a few editorial choices shape how this privacy page reads. The elements below are the visible signals that this is a policy document written for people, not a wall of...

01
Plain wording We rewrote the standard clauses in everyday English so you don't need a lawyer beside you. Where a legal term is unavoidable, we add a short line explaining what it means for your datajitu account.
02
Effective date The header carries the current effective date and the previous one. You can see at a glance whether the wording you read last month is still the wording that governs your account today.
03
Section anchors Each policy section has a stable anchor link. If our privacy desk replies to your ticket with a deep link, it lands you on the exact paragraph that answers your question — no scrolling.
04
Indonesia scope The policy is written for Indonesia first. Wording around supported regions, local rights and retention windows reflects the rules that apply to you, not a generic global template borrowed from another market.
05
Change log A short change log lives at the bottom of the policy. You can scan what shifted between versions without reading the full document again whenever we publish an update.
06
Contact block Every section ends within reach of the privacy desk contact block. You're never more than a screen away from the email and ticket path that gets your request to the right team.

Privacy Policy Questions

We collect what you give us at signup, what your device sends during a session, and the references generated when you move money through DANA, OVO, GoPay or QRIS. Nothing beyond what the lobby needs to run.

Active account data stays while your account is open. After you close it, we hold the minimum required by Indonesian law — usually for tax, anti-fraud and dispute windows — then the record is purged from our live systems.

Yes. Email the privacy desk or open a ticket tagged Privacy from inside your account. We return a structured export within the statutory window that applies in your supported region, no charge for the first request.

Only what's needed to settle a transfer. DANA, OVO, GoPay and QRIS receive the references their rails require — amount, timestamp, account identifier — and nothing about your lobby activity or game history travels with it.

Material changes trigger an in-account notice and an email to the address on your record. Minor edits — typos, clarifications — appear in the change log at the bottom without a separate notification being sent.

Yes, from your account preferences at any time. Withdrawing marketing consent doesn't close the account or affect the service messages we still need to send about logins, transactions and policy updates relevant to you.

Data is held on infrastructure that meets our security baseline, with regional storage where Indonesian rules require it. Vendors that process data on our behalf are bound by contracts mirroring the protections set out in this policy.