LEGAL REFERENCE

How raja878 Handles Your Account Data

This is the raja878 privacy policy — a plain reading of what we collect when you open an account, how we store it, and where it travels. We've...

Data ScopeRetentionYour RightsCookiesContact Path
raja878 How raja878 Handles Your Account Data

Policy Posture & Jurisdiction Notes

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

24/7 SUPPORT

Privacy Contact Paths

Three direct routes if you want to act on your data rights, raise a concern, or simply ask what we hold about your raja878 account.

Team online

Privacy Inbox

Email our data team for access, correction or erasure requests tied to your raja878 account. We aim for a written reply within seven working days, with verification questions first.

Live Chat Desk

Our chat agents can route privacy questions to the right reviewer without you re-explaining. Open chat from the lobby footer, mention privacy, and you'll be tagged for that queue.

Postal Notice

For formal notices or regulator-led requests, a postal address is published in the footer. Mark the envelope Privacy Officer so it reaches the reviewer rather than general operations.

WHY VISITORS TRUST US

Editorial Trust Around Policy Review

Six checkpoints that explain how this policy was written and how it stays current.

Drafted In-House

Our compliance team drafts each clause against the lobby flows you actually use, then legal counsel reviews wording before publication. No template was lifted from another brand without fresh review.

Versioned Revisions

Every change carries a date stamp and a short note describing what moved. You can scan the header to see when DANA, OVO, GoPay or QRIS handling text was last touched.

Indonesia-Aware

We follow Indonesian data-protection developments closely and adjust language when guidance shifts. The policy is written in en-ID English so the meaning matches local expectations, not foreign templates.

Minimum Collection

We document the smallest data set needed for each function. If a feature does not require a field, we do not request it at sign-up or during your session.

Vendor Review

Payment processors and game providers receive only the fields their integration needs. Each vendor is reviewed annually and listed by category in this document for your reference.

Reader Feedback

If a clause reads ambiguously, tell us. We log reader queries and rewrite passages that confuse more than one person, because a policy that is not understood is not really consent.

Consistency Across Sibling Policy Pages

Seven points where this privacy policy lines up with our terms, cookie notice and account-closure pages.

DefinitionsAccount, session, and transaction are defined the same way here as in our terms. If a word appears capitalised, the meaning is shared across every legal page on raja878.
Retention WindowsThe retention table here matches the one referenced in the terms of service. When regulators require longer holds, both pages cite the same statutory minimum so you never see contradictions.
Cookie Cross-LinkThis page summarises cookies; the cookie notice expands them. Both documents share category names so a tag flagged here as analytics is also analytics there.
Closure FlowAccount closure references the erasure rights stated in this policy. Closing your account triggers the deletion path described in the data-rights section, with the same exception list.
Vendor CategoriesGame providers, payment rails and analytics tools are grouped identically across pages. DANA, OVO, GoPay and QRIS sit under payment processing on every document, never relabelled.
Contact RoutesThe privacy inbox listed here is the same address used in our terms for data complaints. One inbox keeps your correspondence in a single thread for faster handling.
Revision DatesWhen this policy is revised, the terms and cookie notice are checked the same week. Date stamps are published together so you can see the documents move as a set.
PLATFORM SNAPSHOT

What Defines Our Policy-Side Layout

Six visible elements that shape how this privacy document reads on raja878 — not payment rails, but the editorial scaffolding around the policy itself.

Clause Anchors Each clause carries a short anchor link so you can...
Plain-Language Boxes Beside dense legal language we add a short plain-language box...
Revision Banner A banner near the top shows the last update date...
Section Index A sticky index lists every section in order. On mobile...
Glossary Tooltips Hover or tap a defined term to see its meaning...
Print Layout A print stylesheet renders the policy as a clean A4...

Privacy Questions Readers Send Us

At registration we collect identity fields, contact details and a payment reference for DANA, OVO, GoPay or QRIS. Session logs are added once you sign in. We do not request data unrelated to running your account.

Active account data is held while you play with us. After closure we keep statutory records for the period Indonesian regulators require, then anonymise or delete the rest. The retention table in this policy lists each category.

Yes. Email the privacy inbox from the address tied to your account, and we will verify identity before sending an export. We aim for seven working days, longer only if the request is unusually broad.

Game providers receive only the fields their integration needs to render your session, such as a hashed account ID. They do not receive your name, contact details or payment references from raja878.

We store the transaction reference and amount, not your wallet credentials. The processor holds the sensitive fields under their own policy. Our record links the reference to your account for reconciliation and dispute handling.

This page summarises essential, preference and analytics cookies. The cookie notice expands each category with vendor names and durations. You can adjust non-essential categories from the cookie panel at any time.

The revision banner at the top of this page updates with the date and a one-line note. Material changes also trigger an in-lobby message the next time you sign in, so you are not caught unaware.