Reference

Open your privacy choices

kmno4 connects your account, wallet records and lobby activity under one Privacy Policy, so you can see what data we collect and why.

Account data clarityCookie choicesUPI record handlingIndia support path
kmno4 Open your privacy choices
CONTACT ROUTES

Check your privacy support

Privacy questions should reach the team through clear routes, not scattered messages.

Account privacy request Send requests from the email or mobile number linked to your account, and include…
Wallet record query For UPI, Paytm, PhonePe or Google Pay privacy queries, share the transaction reference and…
Security concern If you think your login or device access has changed without your action, contact…
DATA CARE

Browse your data rights

Our Privacy Policy is written around the account actions you actually take: opening a profile, adding payment details, entering the lobby, contacting support and managing cookies.

Data we collect

We collect account identifiers, contact details, login events, device signals, payment references and support messages. Game choices such as Blackjack, Aviator or Bingo may create activity records linked to your account security checks.

How we use it

Your data helps us open your account, keep your wallet records matched, respond to privacy requests and detect unusual access. We do not sell personal data as part of this Privacy Policy.

Cookies and devices

Cookies help remember sessions, reduce repeated login checks and measure page errors. You can change browser settings, though some account features may need session cookies to keep your sign-in active.

Payment privacy

UPI, Paytm, PhonePe and Google Pay references are stored with transaction status, time and account link. We use them for reconciliation, support checks, fraud screening and legally required record keeping.

Retention practice

We keep records while your account is active and for periods needed for security, dispute handling and legal duties. When data is no longer needed, we remove it or reduce identifying details.

Your request path

You can ask to access, correct or delete eligible data through support. We may verify your identity first, then reply with the action taken or the legal reason for keeping records.

See your Privacy Policy questions

These questions cover how the Privacy Policy applies to your account, payments, cookies, security and privacy requests. If a request affects wallet records or verification data, we may need extra checks before acting. That keeps the response tied to your account and reduces the chance of data being sent to the wrong person.

We collect data needed for your account, such as name, contact details, login activity, device signals, payment references and support messages. Activity inside the lobby may also create records linked to account safety and service use.

UPI, Paytm, PhonePe and Google Pay references help match deposits or withdrawals to your account, answer payment queries and maintain required records. We do not use these references for unrelated account actions.

Yes, you can request access to eligible account data through support. We may ask for identity proof or account confirmation before sharing records, especially when wallet or login details are part of the request.

Contact support from your linked email or mobile number and state what needs correction. Some changes may require verification, because contact details, payment records and security alerts are connected to account ownership.

Cookies keep sessions active, remember basic preferences and help us detect page or login errors. You can change browser cookie settings, but some account actions may not work properly without required session cookies.

You can ask us to delete eligible data, and we will review the request against security, dispute and legal record duties. Some wallet, verification or transaction records may need to be kept for a set period.

Use the support route inside your account or the contact path on kmno4.co. Send the request from your linked details so we can verify ownership and respond without exposing data to another person.