Reference

Privacy Policy for araislot and Your Account

Our araislot Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or use DANA and QRIS at the cashier.

Account dataWallet referencesCookie choicesYour requests

Explore Our Lobby Read FAQ

How Local Wallet Data Fits This Policy

araislot Service availability depends on jurisdiction. Users are responsible for checking local law before access.

When you create an account, we use the details needed to verify access and keep your sign-in connected to your account record. A DANA, OVO, GoPay, or QRIS payment can create a transaction reference, status, amount, and time record; these details help us match a cashier

1
action without needing the contents of your private wallet. Bank transfer and virtual account references may be handled in the same way. We use this data for account administration, payment checking, fraud prevention, support responses, and legal duties that apply to our service. Your eligibility and
2
access depends on local law, and our handling of personal data follows the choices and rights described in this Privacy Policy. If a payment status needs checking, we ask for the account step or receipt detail relevant to that transaction rather than unrelated personal material.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP CHANNELS

Get Help With Privacy Requests

A clear support path helps you ask about personal data without explaining your whole account history. Start from the account help route when you need a copy request, a correction, or an explanation of a wallet reference. If login or a cashier status is involved, include only the transaction date, payment rail, and receipt reference needed for us to locate the record.

Team online

Account help

Use the support route connected to your account when you want to ask what personal details we hold or why a particular detail was used.

Payment reference

For DANA, OVO, GoPay, or QRIS questions, share the relevant receipt reference and payment date; please do not send a wallet password or private access code.

Access concern

If a mobile sign-in or account verification step affects your privacy request, tell us the device path and account stage so we can respond without asking for unrelated data.

DATA PRACTICE

Data Choices From Login Through Lobby

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We may collect your sign-in details, verification information, and account settings so we can connect your access request to the correct account and respond to privacy questions.

Device signals

A mobile browser can send device, browser, session, and security signals. We use these signals to maintain a sign-in session and investigate unusual account access.

Cookies

Cookies can remember a session, support security checks, and show the right account state. Your browser settings can control some cookies, although access functions may then behave differently.

Payment records

A DANA or QRIS transaction can leave a reference, amount, time, and status record. We use those fields to match cashier activity and answer receipt questions.

Retention

We retain account, security, and transaction records for the period needed for their stated purpose, dispute handling, account protection, or duties that apply where local law permits.

Change requests

Ask us to correct, explain, or address eligible personal data through account help. Include your account identifier and the specific field or record so we can verify the request.

Your Questions About Privacy Policy

These answers address the privacy searches you may make before opening an account or checking a cashier record. They focus on account data, device access, local wallets, cookies, retention, and the steps for contacting us.

The araislot Privacy Policy covers account details, verification, device signals, cookies, payment references, security records, retention, and the ways you can ask about or change eligible personal data.

We do not need your private DANA or QRIS wallet password for a cashier status check. We use relevant transaction references, status details, dates, and account records to match payment activity.

Device and browser signals help us maintain your mobile session, recognise unusual access, and connect a privacy request to the right account. They can include browser type, session details, and security signals.

Use the account help route and identify the account field or record you want corrected. We may ask for an account step that confirms your identity before handling the request.

This Privacy Policy explains that cookies can support sign-in sessions, security checks, and account-state display. You can adjust browser settings, but some access functions may respond differently afterward.

We keep payment references for the period needed to match cashier activity, address disputes, protect accounts, or meet duties that apply where local law permits. The record can include rail, amount, time, and status.

Yes, where local law permits. Contact us through account help with your account identifier and a clear request for the data connected with you; we may verify access before responding.

Privacy Policy for araislot and Your Account

Get Help With Privacy Requests

Account help

Payment reference

Access concern

Data Choices From Login Through Lobby

Account details

Device signals

Cookies

Payment records

Retention

Change requests

Your Questions About Privacy Policy

01 What does the araislot Privacy Policy cover?

02 Does araislot store my DANA or QRIS wallet password?

03 Why does araislot collect device data during login?

04 How can I request a correction to my account data?

05 How does the Privacy Policy handle cookies?

06 How long does araislot keep payment references?

07 Can I ask what personal data araislot holds about me?

Related Pages