Reference

Privacy Policy For Your ful500 Account

Our ful500 Privacy Policy shows what account, device and wallet details we collect, why we use them and how you can ask about them.

Account clarityWallet contextMobile accessYour choices
Browse Our Lobby Read FAQ
ful500 Privacy Policy For Your ful500 Account
CONTACT ROUTES

Three Ways To Ask About Privacy

You do not need to guess where a privacy question belongs. Start from the account help route when your question concerns sign-in, phone verification or a request to change account details.

Account help Use the account support route for access, phone verification and requests to correct your personal details. We ask for the contact detail attached to your account before discussing private records, helping us avoid sending account data to the wrong person.
Wallet status When your question concerns DANA, OVO, GoPay or QRIS records, open the cashier help path and include the transaction reference shown there. We use that reference to separate a wallet-status question from a wider request about your account data.
Privacy request For access, correction or deletion questions, send the request through the contact route linked from your account. Tell us which record you mean and which contact detail identifies you; we may ask for one further account check before taking action.
DATA PRACTICES

Six Practical Privacy Commitments

We keep this policy useful by describing the points you encounter during an ordinary account session.

Account records

We use the details you submit during account opening and phone verification to create access, connect your requests to the right account and respond to support. If a record is wrong, tell us what needs correction through the account contact path.

Device signals

When you sign in from a phone or desktop browser, we may record device type, browser session, approximate access timing and security events. These signals help us identify unusual access; they are not a substitute for the account details you provide.

Cookie controls

Cookies and similar browser storage can keep a session working and remember selected settings. You can clear them through your browser controls, although doing so may require another sign-in or phone verification before account access resumes.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may be stored as a reference for status checks and account support. We use the reference to trace the request, not to ask for your wallet password.

Security checks

We may pause a request when sign-in behaviour, device changes or account details do not match. A phone verification step or an ownership question can be required before we disclose records or change contact details.

Retention requests

We keep records only for operational, security or legal needs described by this policy and then remove or separate them when those needs end. Ask us what applies to a particular record, and we will explain the available action.

Privacy Policy Answers For ful500

These Privacy Policy answers address the searches we hear most often before account opening. They cover the records created by a mobile session, local wallet references, phone verification and requests made through support. If your question is not listed, use the account contact path and identify the relevant record without sending a wallet password or full payment credentials.

It covers account details, phone verification, device and session records, cookie use, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use those records and how you can ask about access or correction.

We collect the details needed to create and protect your account, including contact details, phone verification results and sign-in records. Your browser can also provide device and session signals. We use these records for access, security, support and legal needs described in the Privacy Policy.

Yes. The Privacy Policy covers a mobile browser session as well as desktop access. We may record device type, browser events and session timing so we can protect sign-in and diagnose access problems. Clearing browser storage can require you to sign in and verify your phone again.

We may keep a transaction reference, amount status or payment channel label needed to match a request with your account. That can include DANA, QRIS, OVO, GoPay, bank transfer or virtual account records. We do not ask for your wallet password through support.

You can ask for access or correction through the account contact path. State which record you mean and use the email or phone attached to the account. We may complete an ownership check before sharing records or changing account details, protecting your account from an unrelated request.

Cookies and browser storage can maintain a sign-in session and remember selected settings. You can remove them using your browser controls. After removal, some account functions may ask for a fresh sign-in or phone verification. The policy treats cookie use as a session and preference matter.

You can contact us to ask whether a particular record can be removed. We first check the request and any legal, security or transaction duty that requires retention. If deletion is available, we explain the scope; if not, we explain why that record must remain.

Related Pages

ful500 Indonesia Account information About Us Live Blackjack Gold Garuda Flight Megaways