Reference

Privacy for Aviator and Live Tables

Aviator, Live Football Odds and Dragon Tiger sit behind one account flow, so this Privacy Policy explains what we collect before you open the lobby and why.

Account dataDANA checksOVO checksGoPay checksQRIS receipts

Browse Lobby Read FAQ

How We Use Your Account Data

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

Your account needs a working phone number, login name and payment trail so we can keep wallet records clear and respond when you ask about a transaction. We use data from registration, sign-in, lobby activity, device type, IP region, DANA, OVO, GoPay and QRIS references to

1
run account access, detect unusual sessions and answer support requests. We do not ask for more profile data than the account flow needs, and we keep policy decisions tied to your own wallet history, security checks and contact records. When local law affects access, we apply
2
it only where local law permits and explain the account step that needs attention.

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

CONTACT PATHS

Privacy Help Through Real Channels

Privacy questions should reach the same team that can see your account status, ticket history and wallet references.

Live chat Open live chat after sign-in when you need a quick privacy check on device sessions, cookies or a recent DANA, OVO, GoPay or QRIS reference tied to your wallet.

Email support Send privacy requests from your registered email so we can match the message to your account, confirm the login name and keep a written trail of correction or access requests.

WhatsApp follow-up Use WhatsApp for follow-up after a ticket is open, especially when we ask you to confirm the last login device, payment rail used or a changed phone number.

DATA HANDLING

What We Keep Around Your Lobby

We connect privacy controls to account actions you can recognize: registration, wallet checks, device sign-in and support tickets.

Registration fields

We collect your login name, phone number and email during account setup because those fields help us confirm account ownership when you ask for access, correction or wallet assistance.

Payment records

DANA, OVO, GoPay and QRIS references are kept with timestamps, wallet status and support notes so we can trace a privacy question to the exact account step involved.

Device sessions

Your device type, browser, IP region and login time help us spot account access that does not match your usual pattern, then ask for confirmation before exposing account details.

Cookie choices

Cookies remember session state, language and security prompts. You can clear them in your browser settings, but the next login may ask for extra checks before the lobby opens.

Retention reasons

We keep account, wallet and support data only for operational, security and legal record needs, then restrict access internally so support staff see what the ticket requires.

Change requests

When your phone number, email or name detail needs correction, contact us from the registered channel first; we may ask for the last login path before making the change.

Answers on Data, Devices and Rights

These questions cover the privacy steps you are most likely to need before or after opening an account. The answers focus on data we collect, how we use it, how you can ask for changes and what happens when device or payment checks affect access.

We collect the details needed to create and protect your account: login name, phone number, email, password record, device data and payment references when you use DANA, OVO, GoPay or QRIS.

We keep payment references to match wallet activity with your account, answer transaction questions and investigate unusual movement. The record normally includes rail name, time, status and the support ticket if you contacted us.

Yes. Contact support from your registered channel and tell us which detail needs correction. We may ask for your last login device or recent wallet reference before updating account contact data.

Cookies keep your session active, remember language choices and help security prompts work on mobile and desktop. If you clear cookies, the lobby may ask you to sign in again and confirm access.

Go to Profile > Security > Devices after sign-in to see recent device sessions where available. If something looks wrong, contact live chat and we will review the session trail with you.

Only team members handling account security, wallet checks or your open ticket should access the request. We keep the support record tied to your account so repeated checks do not require starting over.

Yes. Access and eligibility depend on local law and are available only where local law permits. If a rule affects your account, we explain the step involved through support or account messages.

Privacy for Aviator and Live Tables

Privacy Help Through Real Channels

What We Keep Around Your Lobby

Registration fields

Payment records

Device sessions

Cookie choices

Retention reasons

Change requests

Answers on Data, Devices and Rights

01 What personal data does pensiltoto collect when I open an account?

02 Why do you keep DANA, OVO, GoPay and QRIS references?

03 Can I ask to correct my phone number or email?

04 How do cookies affect my privacy in the lobby?

05 How can I check which devices have used my account?

06 Who can see my privacy request inside support?

07 Does local law affect my account access or data handling?

Related Pages