Reference

Open klgesing Privacy Policy

This page explains how klgesing collects, uses, stores, and shares your data when you open an account, move through the lobby, or contact support.

Data useCookie controlAccount checksLocal law
klgesing Open klgesing Privacy Policy
PRIVATE HELP DESK

Open Privacy Support Paths

If you want help with a privacy request, we route it through the same channels we use for account support.

Email us Send your privacy request from the email linked to your account. We use that detail to confirm identity, then handle access, correction, or deletion requests within the limits set by local law.
Live chat Use live chat after sign-in if you want a quicker route to the privacy team. We can point you to the right form, but we still verify the account before any change.
Secure ticket If you prefer a written record, open a secure ticket from your account area. That keeps the request tied to the right profile and helps us track the status without exposing extra data.
SECURE HANDLING

Explore Data Handling Practices

We handle data with a simple rule: keep what we need, protect what we keep, and remove what we no longer need.

What we collect

We collect the account details you share, the device signals that help us recognise a login, and the payment references that tie a deposit or withdrawal to the right record. That lets us keep the account trail accurate.

How we use it

We use those records to create your account, process UPI, Paytm, PhonePe, and Google Pay transactions, answer support questions, and check for misuse. The data stays tied to the reason you gave it to us.

Cookies and session data

Cookies help us remember language, session state, and display settings. If you clear them, those preferences reset, but you can sign in again and set them anew from the browser you prefer.

Account security

Security checks compare logins, device changes, and repeated failed attempts. When something looks unfamiliar, we may ask for a verification code before we let the session continue, so account changes stay linked to you.

Retention rules

We keep records only as long as needed for account operation, dispute handling, fraud checks, tax duties, or other legal duties. After that period ends, the record is deleted, anonymised, or archived as required.

Your requests

You can ask for a copy, correction, or deletion of your data. Write from the contact route linked to your account, and we will check identity first before acting where local law permits.

Browse Privacy Policy Questions

If you want a quick path through the common privacy points, the answers below cover what we collect, why we keep it, and how you can ask for changes. Each answer stays tied to account use and the limits set by local law, so you can see what happens to your data before you contact us. We also point out where a verification check is needed, because we will not change a record until we know the request came from you.

It covers the data we collect when you open an account, browse the lobby, deposit through UPI, Paytm, PhonePe, or Google Pay, and contact support. It also explains retention, cookies, security, and request handling.

We may record your name, contact route, device data, IP address, login history, payment references, and messages you send to us. We keep only the fields that help with access, verification, support, or legal duties.

Payment references help us match deposits and withdrawals to the right account, confirm the route used, and resolve mismatches. We do not use those references for unrelated marketing or extra profiling.

We keep it for the time needed to run your account, handle disputes, complete checks, and meet legal duties. After that, we delete, anonymise, or archive it based on the record type.

Yes. Write to our privacy team from the address linked to your account, or use live chat after sign-in. We verify identity first, then make the change if local law allows it.

Start with support, and ask for the privacy team if your request needs a record search or a formal correction. We keep a written trail so you can track what changed and why.