Reference

Your Privacy Policy at up365

Speed Baccarat, Crash X, Bingo and UPI wallet actions create account records, and this Privacy Policy explains how up365 collects, uses, stores and shares that data.

Account data controlsCookie choicesUPI record handlingPrivacy contact path
up365 Your Privacy Policy at up365
CONTACT CHANNELS

Help Paths for Your Privacy Requests

Privacy questions deserve a clear route, not a generic inbox. Use the contact path that matches your request so we can locate the right account record, payment reference or device session without…

Privacy email Send privacy requests from the email linked to your account and include your username, mobile number ending, and the subject you want handled, such as correction, deletion, cookie concern or data copy.
Account help desk Use account help when your privacy concern is tied to login access, KYC checks or profile details. We verify ownership first, then route the request to the team that handles account data.
Payment privacy check For UPI, Paytm, PhonePe or Google Pay records, share the transaction reference and date. We use that reference to trace wallet entries without exposing unrelated payment data in the reply.
DATA CARE

Control Over Your Account Data

We handle privacy from the point where you first create credentials through every login, wallet movement, game launch and support message.

Data collection

We collect account details, contact fields, KYC records, device signals, cookies, wallet references and support messages. Each data type is tied to account access, payment matching, safety checks or service replies.

Use of data

Your data helps us create your account, confirm transactions, manage login security, answer privacy requests and keep records required for disputes or legal duties. We do not ask for unrelated details.

Cookie handling

Cookies help remember session status, language choice, device type and security checks. You can adjust browser settings, though some account and wallet actions may need certain cookies to function correctly.

Account security

We use ownership checks, limited staff access, session monitoring and secure storage practices to reduce unauthorised access. If a privacy reply includes sensitive data, we confirm account control first.

Record retention

Records stay only while needed for account service, payment tracing, tax, legal, dispute or safety reasons. When a record is no longer needed, we delete, mask or separate it from active account use.

Your choices

You can ask to correct profile fields, receive a copy of eligible data or request deletion where the law allows. Some records must remain until required checks or disputes are complete.

Privacy Answers Before You Join

These answers explain the privacy choices you have before and after opening an account. They focus on data collected during registration, wallet use, cookies, verification, account access and support contact. If your situation involves a specific transaction or identity check, send the relevant reference so we can answer accurately.

We collect the details needed to create and protect your account, such as name, contact fields, login credentials, device signals and verification records. Payment references are stored when you use UPI, Paytm, PhonePe or Google Pay.

Payment records help us match wallet entries, confirm refunds or withdrawals, answer disputes and meet record-keeping duties. We use transaction references rather than exposing full payment data wherever a shorter reference is enough.

Yes, you can request a copy of eligible account data through the privacy email or account help path. We confirm account ownership first, then share the data that can be released under applicable law.

Send a correction request from your registered email or through account help. Include the field that needs changing and any required proof, so we can update the record without affecting unrelated account data.

We keep records while they are needed for account service, payment tracing, tax, legal, dispute and safety reasons. After that period, we delete, mask or separate them from active account use.

Cookies store session, device and preference data that helps account pages work and helps us detect unusual access. You can change browser cookie settings, but some secure account actions may not work without them.

Access and eligibility depend on local law and are available where local law permits. We may use region signals, account checks and verification records to decide which account features can be enabled.