Reference

Privacy Policy for your daddybet account

Your account data, UPI, Paytm and PhonePe records, cookie choices and support chats are covered here before you open your account with daddybet.

Account dataCookie choicesUPI recordsDeletion requests

Explore Lobby Read FAQ

How this policy applies in India

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

This Privacy Policy explains how we handle data connected with your account, wallet activity, identity checks, device signals and contact messages in India. Access and eligibility depend on local law and are available where local law permits; that same local-law frame can affect privacy rights, retention

1
periods and the documents we may need before acting on a request. We collect only the data needed to run your account, process UPI, Paytm and PhonePe records, protect the wallet, handle disputes and meet lawful requests. Some service partners may process data for hosting, payments,
2
fraud checks, analytics or customer care under written terms. We do not sell your personal data. If a privacy request cannot be completed, we tell you why and explain the next step.

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

CONTACT PATHS

Three privacy contact routes

Privacy questions need a clear route, not a maze. Use the account area for quick data requests, email us when you need a written trail, or send document queries through the secure…

Privacy email Send privacy requests through the email address shown in your account help area. Include your account ID, the request type and a reachable contact method so we can match your message safely.

Account chat Use chat for quick privacy questions about cookies, login alerts or recent account activity. We may move complex requests to email when a written record or identity check is needed.

Document channel If a request needs identity proof, use the secure upload path inside your account. Do not send sensitive images through open chat, public social pages or shared devices.

CARE CONTROLS

Six ways we handle data

Our privacy work follows the account journey: sign-in, wallet use, game session records, support contact and account closure.

Data collection

We collect account details, contact data, device signals, payment references and session records only when they are needed for account access, wallet checks, security, dispute handling or lawful requests.

Cookie choices

Cookies help keep you signed in, remember language choices and detect unusual access attempts. You can adjust browser settings, but some account, wallet and security functions may not work correctly without required cookies.

Security checks

We use login alerts, device history, session logs and wallet risk checks to protect account access. If activity looks unusual, we may pause sensitive actions until ownership is confirmed.

Retention periods

We keep records only for as long as needed for account operation, disputes, fraud prevention, tax or legal duties. After that, data is deleted, anonymised or kept in restricted archives.

Data requests

You can ask to access, correct, export or delete personal data. Some records may be retained when local law, payment disputes or security investigations require us to keep them.

Partner handling

Payment, hosting, analytics and customer-care partners may process limited data for assigned tasks. We do not allow them to use your personal data for unrelated purposes under our agreements.

Your Privacy Policy questions answered

These answers cover the privacy points you may want to check before opening or using an account. They explain personal data, payment records, cookies, access rights, deletion requests and contact steps in plain language. If your situation involves local legal rules, we review it under the law that applies to your request.

We collect account details, contact data, device signals, login records, payment references and support messages. We also keep session records linked to wallet and game activity when needed for security, disputes or legal duties.

We keep payment references to match wallet activity, verify requests, resolve disputes and meet legal record duties. These records are handled separately from promo preferences and are shared only when needed for processing or compliance.

Yes, you can request a copy of personal data linked to your account. We may first confirm ownership, then provide available records unless law, security checks or another person’s privacy prevents release.

You can ask us to correct inaccurate personal data, such as contact details or spelling errors. Some identity or payment fields may need proof before we change them, especially when wallet security is involved.

Cookies support sign-in, language settings, security checks and basic site measurement. You can manage them through your browser, but blocking required cookies may affect account access, payment confirmation or fraud checks.

You can ask for deletion where local law permits. We review the request, verify ownership and remove eligible data, while keeping records that must remain for disputes, security checks or legal duties.

Our customer-care and privacy teams handle requests through account chat, secure upload and email paths. For sensitive changes, we may ask for identity proof before sharing, changing or deleting account data.

Privacy Policy for your daddybet account

Three privacy contact routes

Six ways we handle data

Data collection

Cookie choices

Security checks

Retention periods

Data requests

Partner handling

Your Privacy Policy questions answered

01 What personal data do we collect?

02 Why do we keep UPI, Paytm and PhonePe records?

03 Can you ask for a copy of your data?

04 Can you correct account details?

05 How do cookies affect your account?

06 Can you ask us to delete your data?

07 Who handles privacy requests?

Related Pages