Reference

How desavr handles your data

Your account can connect Turbo Blackjack, Fruit Party, Spribe Aviator and payment records from UPI, Paytm, PhonePe or Google Pay, so this Privacy Policy explains what account data…

India data contextUPI recordsCookie choicesAccount requests

explore lobby Read FAQ

Privacy terms for India access

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

This Privacy Policy applies when you create an account, browse the lobby, use wallet tools, contact our team or send privacy requests through desavr.com. We collect only the data needed to run your account, check security events, process UPI, Paytm, PhonePe or Google Pay records, respond

1
to your messages and meet legal duties that apply to our service. Access and eligibility depend on local law and are available where local law permits. If a rule in your location restricts access, we may need to limit account activity, verify details or retain certain
2
records for audit and dispute handling. We do not sell your personal data. Where service partners help with hosting, fraud checks, payment routing or messaging, they receive only the data needed for that task under contract terms.

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

CONTACT ROUTES

Where to send privacy requests

Privacy questions should reach the right desk without sending extra documents in open chat.

Privacy email Use the privacy address on desavr.com for access, correction, deletion or cookie-choice requests. Mention your registered email or phone number, the request type and any relevant date range so we can locate the right account record.

Account chat Account chat can pass privacy matters to the data team when you are logged in. For your safety, our agents may ask for limited checks before discussing wallet records, session activity or device-linked access details.

Payment query path For privacy questions tied to UPI, Paytm, PhonePe or Google Pay, share the payment method name, transaction date and account email. Do not paste bank PINs, one-time codes or full card data into messages.

DATA CARE

Cookies, records and account security

Our privacy work covers the account details you give us, the records created while you use the site and the security logs that help protect access.

Account details

When you join, we collect details such as your name, contact data, login credentials and account settings. These fields help us identify your profile, send account messages and apply the privacy choices you request.

Payment data

UPI, Paytm, PhonePe and Google Pay records may include method type, reference IDs, timing and status. We use those records to reconcile wallet activity, check disputes and meet finance-related legal duties.

Cookie settings

Cookies and similar tools support login sessions, language choices, fraud checks and site measurement. You can manage browser settings, though blocking some cookies may affect account sign-in or secure payment steps.

Security logs

We keep device, IP, browser and session records to detect unusual access and protect your account. These logs are reviewed only by teams that need them for security, support or compliance checks.

Retention periods

Some records can be removed after your request, while payment, dispute and security records may need longer storage. We keep data only for valid service, legal, fraud-control or accounting reasons.

Change requests

If your name, email, phone number or privacy preference is wrong, contact us from the account channel you normally use. We may verify identity before making changes to protect your data.

Privacy Policy questions answered

These answers explain how the Privacy Policy works for your account, payment records, cookies and privacy requests. They are written for the way you use desavr in India, including UPI, Paytm, PhonePe and Google Pay contexts. If your question is specific to your account, contact us from the same email or phone number linked to your profile.

It covers account details, contact data, login records, device data, payment references, cookie data and messages you send us. It also covers security logs created when you access the site or manage your wallet.

We use payment records to match wallet activity, process requests, investigate failed or delayed transfers and meet finance-related duties. We do not ask for bank PINs, one-time codes or unrelated banking data.

Yes, you can ask for access to data linked to your account. We may verify your identity first, then share the data we can provide under applicable law and account-safety rules.

Send a correction request from your registered email, phone number or logged-in account channel. Tell us which field is wrong, provide the accurate detail and allow time for identity checks.

Retention depends on the data type. Account data may remain while your account is active, while payment, dispute, security and legal records may be kept longer where valid duties require it.

No. Cookies help with sign-in, security, preferences and site measurement. Some are needed for the service to work, while browser settings can limit others if you prefer less tracking.

Use the privacy contact path on desavr.com and include your registered email or phone number. We will review what can be deleted and explain if legal or dispute records must remain.

How desavr handles your data

Where to send privacy requests

Cookies, records and account security

Account details

Payment data

Cookie settings

Security logs

Retention periods

Change requests

Privacy Policy questions answered

01 What personal data does this Privacy Policy cover?

02 Why do you collect UPI, Paytm or PhonePe records?

03 Can I ask for a copy of my account data?

04 How can I correct wrong account details?

05 How long do you keep my data?

06 Do cookies track everything I do?

07 Who should I contact about deletion requests?

Related Pages