Reference

Your Privacy Policy, Clear At A Glance

This page explains what cbtf247 collects, why we keep certain records, and how you can ask us to correct or remove details tied to your account.

Data UseCookiesRetentionSecurity

Explore Lobby Read FAQ

What We Record And Why

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

We collect only the details needed to run your account, verify access, process requests, prevent misuse and answer privacy questions. That can include contact details, login activity, device signals and payment references linked to your wallet record. If you use UPI, Paytm, PhonePe or Google Pay,

1
the status and reference line may be stored so we can match the transaction to your account and resolve disputes. Access, processing and retention can vary by region, and when eligibility is discussed it depends on local law and is available where local law permits. We
2
may also keep a limited trail of support messages to confirm what was requested and when, then remove or reduce it when the stated purpose ends.

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

REQUEST ROUTES

Where To Send Privacy Requests

For privacy requests, the fastest route is the contact channel linked to your account.

Email check Write from the email linked to your account and say whether you want access, correction or deletion. Using the registered address helps us match your request and keep the reply tied to the right record.

Account message If you can still access the account, send the request from the secured message area and include the mobile number or wallet reference we should verify. We use that to confirm identity before any change.

Extra verification When a matter needs another check, we may ask for a fresh confirmation before sharing a copy or changing stored data. That extra step protects your records from being altered by the wrong person.

DATA SAFEGUARDS

How We Protect Your Records

We store only what we need to run your account, settle transaction logs and respond to privacy requests.

Data collection

We collect only the details needed to run the account, process deposits or withdrawals, and reply to privacy requests. That usually includes contact details, device signals, login logs and payment references tied to the wallet.

Cookies

Cookies help remember your session, language choice and whether you have already completed a step. They also help us detect repeated failed logins and keep the page working across mobile and desktop.

Account security

When you sign in, we may use device checks and unusual-location alerts to reduce unauthorised access. If something looks wrong, we can pause a session and ask you to confirm the request through your registered contact.

Retention

We keep records for as long as needed to manage the account, settle disputes, meet audit duties and respond to lawful requests. After that, the record is either removed or stored in a limited form where law requires it.

Sharing

Only the service partners that help with hosting, messaging, payments and fraud checks may see limited data, and only for the task they perform. We do not pass your record around for unrelated use.

Changes

If you want to correct a detail, ask for a copy or request deletion where allowed, use the contact path linked to your account. We will verify first, then act on the part we can change.

Questions About This Policy

These answers cover the points people ask about before sending a privacy request: what we store, how cookies work, how long records stay with us and which contact path to use. If your region has different rules, we apply the one that controls there, and we may need extra verification before making any change.

We keep only the details needed to run your account, confirm logins and handle requests. That can include contact details, device signals, support messages and payment references connected to your wallet activity.

Cookies remember your session, language choice and the state of any form you started. They also help us spot repeated failed logins and keep the page working properly on mobile and desktop.

If you use UPI, Paytm, PhonePe or Google Pay, we may store the reference and status beside your account record. That helps us reconcile wallet activity, answer disputes and keep the audit trail readable.

Retention depends on the record type, the reason it was collected and any legal duty that applies. Some records stay only while your account is active, while others remain longer for dispute handling or statutory duties.

Yes, where local law allows it. Send the request through the contact route linked to your account, and we will verify it before changing the record or removing the part we are allowed to remove.

Use the registered email or in-account message channel so we can match your request to the right profile. If extra confirmation is needed, we will ask for it before sharing a copy or making any change.

Yes. Any access, processing or eligibility point depends on local law and is available where local law permits. If a rule differs by region, we follow the rule that applies to your account location.

Your Privacy Policy, Clear At A Glance

Where To Send Privacy Requests

How We Protect Your Records

Data collection

Cookies

Account security

Retention

Sharing

Changes

Questions About This Policy

01 What data do you collect from my account?

02 Why do you use cookies on this page?

03 How do you use my payment record?

04 How long do you keep my data?

05 Can I ask for correction or deletion?

06 Who should I contact about privacy?

07 Does local law affect access or eligibility?

Related Pages