Reference

nilla88 Privacy Policy For Your Account

The nilla88 Privacy Policy explains what we collect when you open an account, sign in, use the lobby, or check a wallet status.

Account dataWallet recordsCookie choicesContact route
nilla88 nilla88 Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Help Near Your Account

A clear contact route matters when you want to ask about the Privacy Policy, correct an account detail, or understand a wallet record.

Account support path Use the support route inside your account for Privacy Policy questions, data corrections, or access requests. Tell us the account step involved, such as phone verification or sign-in, so we can match your request with the correct account record.
Wallet record check For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, send the payment reference rather than a full wallet password. We use the reference to locate the transaction record while limiting unnecessary details.
Receipt status route When a receipt or status needs checking, contact support from the account area close to the cashier path. We can explain which record is held, why it is needed for account administration, and what details may be corrected or removed.
DATA HANDLING

Six Practical Privacy Controls

Privacy is easier to understand when each control connects to a real account action. We separate sign-in details from payment references, use browser storage to remember selected settings, and review requests through…

Account details

We collect the details you enter when opening an account and the information needed to complete phone verification before account access. Keeping these details accurate helps us respond to a correction request and distinguish your account from another account using the same device.

Payment references

A DANA, OVO, GoPay, or QRIS payment may create a reference, amount, status, and time record. Bank transfer and virtual account activity can create similar references. We use these details to reconcile account activity, not to request your wallet password.

Cookie settings

Cookies and similar browser storage can remember sign-in preferences, security settings, or the page state you selected. You can review browser controls on your phone or desktop, although changing them may require another sign-in or remove saved preferences.

Account security

We may check device, browser, session, and phone-verification signals when an account signs in. These checks help us identify unusual access and protect account records. Do not send passwords or one-time codes through a support message when asking about privacy.

Retention periods

We keep records only for the operational, security, dispute, or legal purpose connected to them. A payment reference may need to remain available after a receipt is issued, while a temporary session record can have a shorter life. We can explain the reason for a retained record.

Change requests

You can ask us to access, correct, or clarify personal data connected to your account through the support path. Include your account contact detail and the requested change. We may ask for account verification before discussing records or applying an amendment.

Answers About nilla88 Privacy Policy

These Privacy Policy answers address the searches we hear most often before account creation. They explain how account information, cookies, wallet references, device details, and contact requests fit together. If your situation concerns access or eligibility, the answer also keeps the local position clear: access depends on local law and is available where local law permits.

The nilla88 Privacy Policy covers account details, phone verification, browser and device signals, cookies, support messages, and payment references. It explains why we use each category, how retention is considered, and how you can ask about access or correction through the account support path.

We keep payment references so we can match a DANA or QRIS transaction with the correct account, receipt, and status. The record can include a reference, amount, and time, but you should not send a wallet password. We use the information for reconciliation and support.

Yes, you can contact us through the account support route and ask what personal data is connected to your account. We may first confirm account ownership through the phone-verification details already held, then explain the available records and any limits required by local law.

The Privacy Policy explains that cookies or browser storage may remember sign-in preferences, security settings, and page state. You can manage them in your mobile or desktop browser. Removing them may clear saved choices and require you to sign in again before account access.

We may use device, browser, session, and phone-verification signals to check unusual sign-in activity and protect account records. These signals are handled for security and access administration. They do not replace your responsibility to keep passwords and one-time codes private.

Retention depends on why a record exists. Payment references may remain available for reconciliation, disputes, security checks, or required operational records, while short session details may last for less time. Contact us if you want the retention reason for a particular account or wallet record.

Send a correction request through the support path inside your account and identify the field or record that needs attention. Include your account contact detail, but not your password or wallet code. We may verify ownership before changing information, where local law permits.