LEGAL REFERENCE

How rajawali988 Handles Your Account Data

This is the rajawali988 privacy policy page, written for you in plain language. We explain what account details we collect when you open an account, how we store...

Account dataPayment referencesContact recordsCookie notesRegion-aware
Browse the Lobby Read FAQ
rajawali988 How rajawali988 Handles Your Account Data

Our Privacy Posture and Data Scope

We collect only what's needed to run your rajawali988 account: your registered name, contact handle, login credentials and the e-wallet or bank reference you use for top-ups. Where local law permits, we keep these records in encrypted storage and retain them only as long as your account remains active or as supported regions require. We don't sell your data to advertisers. Processor

partners receive a payment token, not your full profile, and our cookie layer is documented in the sections below so you can adjust what's tracked while you browse.

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

PLAYER SUPPORT

Privacy Contact Paths for Your Questions

If anything in this policy is unclear, or you want a copy of the data we hold on your account, reach us through any of the channels below. Our privacy desk replies in Indonesian or English.

Team online

Privacy Email

Write to our privacy desk for data access requests, correction of your account profile or removal queries. We aim to acknowledge within one business day and resolve inside seven.

In-App Chat

Open the chat bubble after you sign in and ask for the privacy team directly. Your session is tied to your account, so we can verify identity without extra forms.

Postal Address

Prefer paper? Send a signed letter to our registered correspondence address listed in the account footer. Include your username so we can match the request to the right file.

WHY THIS PLATFORM

How We Review This Policy

Our policy isn't a copy-paste template. Here's who touches it before it goes live on rajawali988.

Legal Review

Indonesian counsel reviews wording every quarter so the policy reflects current data handling practice and any supported-region updates that affect how your account information is stored.

Security Sign-Off

Our security lead signs off on the encryption and retention claims in this document. If a control changes on the backend, the matching paragraph here changes the same week.

Editorial Pass

Plain-language editors rewrite anything that reads like boilerplate. You shouldn't need a lawyer to know what we collect, and that's the bar we hold this page to.

Processor Audit

Payment partners handling DANA, OVO, GoPay and QRIS references are audited annually. We confirm they only see the token slice we send, not your account credentials.

Version History

Every change to this policy is dated and kept on file. Ask the privacy desk and we'll send the diff between the version you signed up under and today's.

User Reports

If you flag a paragraph that doesn't match what you experienced inside your account, we investigate and respond. Feedback shapes the next revision of this page.

Consistency With Our Other Policy Pages

This privacy page sits alongside our terms, cookie and account-closure pages. Here's how they line up so you don't have to cross-check.

Data Scope
Privacy covers what we collect. Terms cover what you agree to. Both pages name the same data fields so there's no contradiction between them.
Retention Periods
Retention windows quoted here match the closure page exactly. When you close your account, the clock in that document is the same clock referenced above.
Cookie Layer
Our cookie notice expands on the tracking paragraph here. Anything you toggle off in the cookie banner is reflected in what this policy says we collect.
Payment References
Wallet tokens described here match the wording on the deposit help page. Same processors, same token shape, same retention rule across both documents.
Contact Channels
The privacy email above is the same address listed on the contact page. We don't run shadow inboxes — one route, one team, one reply.
Region Wording
Where local law permits and supported regions phrasing is used identically across legal pages. If one document updates, the others update the same day.
Version Dates
The footer date stamp on this page aligns with the terms page footer. If they disagree, the later date wins and the older page is being patched.
SERVICE CONTEXT

What's Visible On This Policy Page

The layout of this policy is designed so you can scan it without scrolling forever. Here's what each block on the page does for you.

01
Plain Summary The opening hero gives you the policy in two sentences. If you only read one block on this page, that's the one that tells you what we collect.
02
Scope Block The details section lists every data field tied to your account. No hidden categories, no vague 'other information' bucket — what's named is what we hold.
03
Contact Row Three direct routes to the privacy desk sit above the trust block so you don't have to hunt for a way to reach us when you have a question.
04
Review Signals The trust block names the teams that touch this page. You can see who reviews legal wording, security claims and the editorial pass before publication.
05
Cross-Check Grid The comparison block lines this document up against our terms, cookie and closure pages so you can verify nothing contradicts between them.
06
FAQ Footer The questions block at the bottom answers the queries our privacy desk receives most often. Read those before writing in — your answer may already be there.

Privacy Questions We Hear Most Often

Your registered name, contact handle, login credentials and the wallet reference tied to DANA, OVO, GoPay or QRIS top-ups. Nothing beyond that is stored against your account unless you submit it to the privacy desk directly.

Yes. Email the privacy desk from the address on your account, or open in-app chat after signing in. We aim to deliver a readable export inside seven business days where local law permits.

While your account is active, plus the retention window supported regions require for financial records. After that, identifiable fields are removed and only anonymised transaction counts remain on our reporting side.

No. DANA, OVO, GoPay and QRIS partners receive a payment token and the amount, not your account credentials or contact details. That separation is audited annually by our security team.

Yes. Use the closure flow inside your account or write to the privacy desk. Identifiable fields are removed once any outstanding payment reconciliation completes, usually within thirty days of your request.

No. We don't sell your account data to third-party advertisers. The only external parties who touch your records are the regulated processors named above and any authority we're legally required to respond to.

The footer date stamp updates whenever wording changes, and the version history is on file with the privacy desk. Material changes are also flagged inside your account before they take effect.