Reference

Open your privacy terms before joining

Account opening, wallet records and cookie choices sit under one Privacy Policy at cbtf7, so you can see how your personal data is handled before you create an…

Account data useCookie choicesUPI and Paytm recordsCorrection requests

Explore the lobby Read FAQ

Explore how cbtf7 handles account data

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

This Privacy Policy explains what we collect, why we collect it, how long we keep it and when we share it with service providers. We use your name, contact details, device data, login records and wallet references to run account access, verify requests, secure sessions and

1
match payment activity. Where payment data is involved, UPI, Paytm, PhonePe and Google Pay references are used as context for receipts, refunds and support checks, not for unrelated outreach. Access to the account area depends on local law and is available where local law permits. You
2
can ask us to correct your details, raise a data request or close an account record subject to checks required for security, disputes and legal duties.

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

HELP ROUTES

Check privacy help before you join

Privacy questions need a clear path, not a maze. Use the routes below when you want to ask what we hold, correct a field, query a cookie setting or understand why a document was requested. We may ask you to confirm account ownership before we discuss personal data. That keeps your records from being shared with the wrong person and helps us close each request with a clear answer.

Team online

Account privacy desk

Write to our account team when you need a copy of key personal data, a correction to contact details or an explanation of how login records are used during access checks.

Wallet record queries

Use this route for privacy questions linked to UPI, Paytm, PhonePe or Google Pay references, including receipt matching, failed payment traces and data shown on your account statement.

Cookie and device help

Contact us if you want to understand cookies, device identifiers or browser storage used for session security, language preference, fraud checks and keeping you signed in on a known device.

ACCOUNT SAFETY

Browse account controls and data care

We write this policy from the operator side, so the wording follows how the account system actually works.

Data we collect

We collect account details you enter, contact fields, login timestamps, device signals, payment reference numbers and support messages so we…

How cookies work

Cookies help remember session status, language choice and security checks.

Payment record use

UPI, Paytm, PhonePe and Google Pay references are stored with wallet activity so deposits, refunds and support checks can be…

Access protection

Account changes, password resets and sensitive privacy requests may require identity checks.

Retention periods

We keep data for the period needed to provide account service, settle disputes, meet legal duties and protect the platform.

Request handling

When you ask for access, correction or deletion, we record the request, verify ownership and respond through the contact route…

Start with privacy questions answered

The answers below focus only on privacy, account data and your control choices. They explain what we collect, how payment references are handled, why cookies appear and how to contact us for changes. If your question needs account-specific checking, we may ask for proof that you control the account before we respond with personal data.

We collect the details you provide when opening or managing an account, plus login records, device data, payment references and support messages. We use these records for access, security, wallet matching and support replies.

We keep payment references to match deposits, trace failed transactions, process refunds and answer wallet questions. We do not need your full bank login details for these checks, and you should never share them.

Yes. You can contact us and ask for a copy of account data linked to you. We may verify ownership first, then share data that can be released under applicable legal and security rules.

Send us the field that needs correction and the current account contact route. For sensitive details, we may request proof before changing records, because privacy changes must protect your account from unauthorised edits.

Cookies support sign-in status, security checks, language choices and page performance checks. You can manage cookies through your browser, though some account functions may not work correctly if essential cookies are blocked.

We share limited data with providers that help run payments, security checks, hosting, analytics and support tools. They receive only what is needed for the task, and their use is tied to service delivery.

A privacy request does not automatically close your account. Some changes may affect sign-in, payments or verification. Access also depends on local law and is available where local law permits.

Open your privacy terms before joining

Check privacy help before you join

Account privacy desk

Wallet record queries

Cookie and device help

Browse account controls and data care

Data we collect

How cookies work

Payment record use

Access protection

Retention periods

Request handling

Start with privacy questions answered

01 What personal data do we collect?

02 Why do we keep UPI, Paytm and PhonePe references?

03 Can you ask for a copy of your data?

04 How can you correct account details?

05 How are cookies used on the site?

06 When do we share data with service providers?

07 How do privacy requests affect account access?

Related Pages