Reference

Privacy Policy for your account

This page explains how cricmatch365 collects, uses and stores account details, device signals and payment records, so you can see what sits behind each request on your profile.

Clear data useAccount-linked requestsCookie handlingIndia support routes

Explore Lobby Read FAQ

Policy scope for India

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

This policy explains what we collect when you use cricmatch365, why we keep it and when we share it with payment or service partners. For deposits and account checks, references from UPI, Paytm, PhonePe and Google Pay may be stored so we can match the entry,

1
confirm the account and settle disputes. Access to some functions depends on local law and is available where local law permits. If a request cannot be completed in your region, we will say so plainly and point you to the next available step. We keep the
2
policy practical: use only the data needed, limit access to staff who handle the request, and remove or anonymise records when the purpose ends or a legal duty requires a different timeline.

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

REQUEST ROUTES

How to send a request

If you want to ask about access, correction or deletion, we keep the routes simple.

Email request Send any privacy request to the email on your account, and we will match it with the record before we act. Use the same address for corrections, access requests or a copy of what we keep.

In-account message If you are already signed in, the message area lets you submit the request without opening a fresh thread. That helps us keep one trail for changes, questions and follow-up confirmations.

Postal letter For formal notice, you can write to the postal address shown in your account area. We keep that route open for requests that need a signed letter or a paper trail under local law.

HANDLING STANDARDS

How we handle your data

We keep this policy work practical: collect only what is needed, limit who can open private records, and use cookies only for session handling, language choice and device checks.

Data used for the account

We use your contact details, login record and payment references only to open, run and verify the account you asked for. We do not keep extra fields unless they are needed for a request or a legal duty.

Cookies and device records

Cookies and similar logs help us remember language choices, keep sessions stable and spot unusual access. You can clear them in your browser, though some page settings may reset after that.

Access controls

Account access is protected by login checks and device verification when needed. If we see a new device or an unusual sign-in pattern, we may ask for another confirmation before showing private pages.

Retention windows

We keep records only for the period needed to run the account, handle a request, settle a dispute or meet a legal duty. After that, we remove or anonymise the data under our standard process.

Request changes

If your contact details change, send the update through support and we will compare it with the account before replacing the old entry. If law limits a change, we will explain the reason and the remaining route.

Who handles it

Our privacy team and support desk both receive requests, but one person follows each case so it does not bounce around. Keep your account email handy, because it helps us match the request faster.

Common privacy questions

We answer the questions we hear most about data handling, cookies, payment references and request routes, so you can see how your record is treated from sign-in to change requests. Where a local rule applies, we follow it first and explain the next step in simple terms. That makes it easier to check what we keep, what we change and who you can contact if something looks wrong.

We keep the details needed to create and manage the account, such as your contact fields, login record, device signals and the payment references that come with UPI, Paytm, PhonePe or Google Pay use. We do not ask for more than the task requires.

Yes. Cookies and similar tags help us keep you signed in, remember language choices and spot unusual access. If you clear them in your browser, some settings may reset, but the account record stays in place.

Yes. Send the updated field from the email linked to the account, and we will compare it with the record before changing it. If local law limits a requested change, we will tell you what can and cannot move.

We keep payment references only to match deposits, withdrawals and account checks. That can include UPI, Paytm, PhonePe or Google Pay references, plus the time and amount needed to reconcile the entry.

We keep records for as long as they are needed to run the account, answer a request, settle a dispute or meet a legal duty. After that, we remove or anonymise them under our standard process.

Use the email, in-account message box or postal address listed on your account page. Add the email tied to the account, say what you want changed, and our privacy team will route it to the right person.

Where a request is allowed, we process it and share the result through the contact route you used. If a rule in your location stops part of it, we explain the limit and the reason in plain terms.

Privacy Policy for your account

How to send a request

How we handle your data

Data used for the account

Cookies and device records

Access controls

Retention windows

Request changes

Who handles it

Common privacy questions

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

02 Do you use cookies on my device?

03 Can I ask for a correction to my details?

04 How do you handle payment records?

05 How long do you keep my records?

06 Who should I contact for a privacy request?

07 What if local law limits a request?

Related Pages