Reference

Privacy Policy For Your adipati99 Account

Our Privacy Policy explains how we use the details connected with your adipati99 account, including phone verification, device access and wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet checksCookie choicesDevice access
adipati99 Privacy Policy For Your adipati99 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path helps you ask about the Privacy Policy without mixing a data request with a game or wallet question.

Account privacy request Use the account support path to ask what personal details are linked to your…
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears unclear, include the date, amount…
Access and cookie help Tell us whether you are using a mobile browser or desktop browser, plus the…
DATA HANDLING DETAIL

What The Privacy Policy Covers

We keep the Privacy Policy practical by connecting each data category to an account action you can recognise.

Account details

We use the phone number and account credentials you provide to identify your account, complete the access step and respond…

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank-transfer reference can be stored with an account record to reconcile a…

Cookies and settings

Cookies may remember a session choice, language setting or access preference on your browser.

Device security

We may record device type, browser details, sign-in time and basic access signals to identify unusual account activity.

Retention period

We retain personal data only for the account, payment, security or support purpose that requires it, while applicable local requirements…

Your requests

You may ask what data we hold, request a correction or ask how a record is used.

Privacy Policy Answers For adipati99

These Privacy Policy answers address the account questions you are most likely to have before opening access. We focus on the practical details: what we collect during phone verification, why a wallet reference may appear in a record, how browser cookies affect a mobile session and how to contact us about a correction. If your situation is not covered here, send a focused request through the account support path and avoid sharing passwords, wallet PINs or unrelated personal details.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references, support messages and retention. It explains why we use each category, how we protect account access and how you can request clarification or a correction where local law permits.

We may retain a payment reference connected with DANA or QRIS so we can match a receipt, check a status question or resolve an account record. We do not need your wallet PIN for that process. Send only the reference requested through the support path.

Contact us through the account support path and state that your request concerns the Privacy Policy. Include your account phone number and the data category you want clarified. We verify account ownership first, then explain the available response and timing under local law.

Phone verification connects the access request to the correct account and helps us avoid discussing private records with the wrong person. We use the verification result for account security and support handling, not as permission to collect unrelated contacts or content from your device.

Yes. Your mobile browser provides cookie controls that can clear or restrict stored preferences. If you remove them, you may need another login step and some account settings may not remain remembered. The Privacy Policy explains the cookie purpose without requiring access to your personal files.

Retention depends on why the record exists, such as account access, payment reconciliation, security or support, and may also depend on local requirements. Ask us to identify the category linked to your account. We will explain whether correction or deletion is available where local law permits.

You can request a correction through the support path by naming the inaccurate field and confirming account ownership. Do not send your password or wallet PIN. We will check the record, explain any necessary verification and process the request when the Privacy Policy and local law allow it.