Reference

Open the Privacy Policy

Open your account and read how we handle your data across UPI, Paytm and PhonePe records; access depends on local law and is available where local law permits.

Account dataCookie choicesLocal law

Browse Lobby Read FAQ

Explore how this policy works

esball Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

We collect the details you enter for your account, the device and browser signals that reach our pages, and the transaction references tied to UPI, Paytm, PhonePe and Google Pay. Those records help us run logins, match deposits and withdrawals, spot duplicate requests, and answer account

1
questions without asking you to repeat the same facts. We also keep session cookies and error logs so we can remember language choice, protect sign-in state, and fix broken pages when something fails on your screen. When we share data with service partners, we do so
2
only for tasks such as hosting, messaging, fraud checks, or payment routing, and we expect them to handle it under strict use limits. If local law gives you a right to access, correct, or delete data, we follow that rule where it applies and explain what
3
we can do next.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT ROUTES

Switch to the contact paths

Use the path that is easiest for you. If you want to ask about a record, ask for a correction, or check what we keep, send…

DATA AND ACCESS

Browse data handling and security

At esball we keep the policy narrow: we use only the account, device, cookie and payment records needed to run your login, match activity, and answer privacy requests.

Account records

We keep the name, contact detail, login history, and payment references you submit so your profile stays matched to the right account. These fields also help us confirm changes when you ask for a correction or a copy.

Cookies and session data

Cookies keep you signed in, remember language choice, and help the page load with the settings you last used. They also tell us when a session looks unusual so we can protect access and reduce repeat logins.

Payment traces

UPI, Paytm, PhonePe, and Google Pay references are stored with transaction timestamps and status logs. That record helps us reconcile deposits, track withdrawals, and respond if a payment is disputed later.

Security controls

We limit staff access, log admin actions, and watch for repeated failed logins or device changes. When a request needs identity confirmation, we ask for a detail that matches the account rather than extra personal data.

Retention periods

We keep records only as long as needed for account handling, support, legal duty, or dispute work. After that window, we delete, anonymise, or archive the data so it is no longer used in active systems.

Your privacy requests

You can ask to see, correct, or delete data where local law allows it, and you can ask us to explain how a record is used. Send the request through support and we will route it to the right team.

Browse common privacy questions

These questions cover the parts of the policy that matter most when you open an account, send a payment, or ask for changes. If your situation depends on local law, we follow the rule that applies where you are and explain what we can do next. We keep the answers practical so you know which record we hold, why we hold it, and how you can reach us without hunting through extra pages.

We collect the details you submit, such as name, contact method, login history, device signals, and the payment references tied to UPI, Paytm, PhonePe, or Google Pay. We use them to run the account and answer support requests.

Payment records help us match deposits and withdrawals to the right account, fix missed entries, and answer disputes with a clear trail. We keep only the fields needed for that task and store them under access controls.

Cookies remember your sign-in state, language choice, and a few page settings so you do not have to reset them each time. We also use them to spot unusual sessions and reduce login problems.

Yes, where local law permits. Send a request through support, and we will confirm your account before sharing the record categories we can disclose and the format allowed for that request.

Tell us which field is wrong and include any detail that helps us locate it, such as the mobile number on the account or a payment reference. We will check the record and update it if the request is valid.

We keep it only for the period needed to run the account, meet legal duties, settle disputes, or meet retention rules. After that period, we delete, anonymise, or archive the record so it is no longer active.

Use the email, in-account message, or form listed on this page. The privacy team handles access, correction, deletion, and general questions, and we will ask for only the details needed to identify your account.

Open the Privacy Policy

Switch to the contact paths

Browse data handling and security

Account records

Cookies and session data

Payment traces

Security controls

Retention periods

Your privacy requests

Browse common privacy questions

01 What data do you collect when I open an account?

02 Why do you keep my payment records?

03 Do cookies change how you use the site?

04 Can I ask for a copy of my data?

05 How do you correct a wrong record?

06 How long do you keep my data?

07 Who should I contact about privacy?

Related Pages