Reference

Privacy Policy for your India account

Before you open an account, this Privacy Policy explains how boost777 handles account details, cookies, KYC files, device signals and payment records linked with UPI, Paytm, PhonePe and…

India account dataUPI privacy contextKYC file handlingCookie choices

Explore the Lobby Read FAQ

How our policy applies in India

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

This Privacy Policy applies when you create an account, verify your identity, use the wallet, contact support or adjust privacy choices on boost777. We collect details needed to run your account, check age and identity where required by law, process payment records and protect the account

1
from unauthorised access. Payment names such as UPI, Paytm, PhonePe and Google Pay are used here as context for the records we may receive or create, such as transaction reference numbers, timestamps and status messages. We do not sell your personal data. We share it only
2
with payment handlers, verification partners, security vendors or authorities when a valid legal reason applies. Access and eligibility depend on local law and are available where local law permits. If a local rule requires longer record keeping, that rule may affect deletion timing.

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

CONTACT ROUTES

Three privacy contact paths

Privacy requests need a clear route, not a general message left in the wrong queue. Use the channel that matches your issue so we can verify your identity, locate the right account record and reply without exposing personal data to another person. We may ask for extra proof before changing data, sharing a copy or closing a request, because privacy support must protect the account as well as answer it.

Team online

Privacy email

Send privacy questions from the email linked to your account. We use that address to match your request, ask for needed proof and reply with the next privacy step.

Account chat

Use chat for simple privacy questions such as cookie settings, login alerts or where to find account data. For sensitive changes, chat may move you to email verification.

KYC request ticket

If your request concerns identity files, upload status or document correction, choose the KYC ticket route. That keeps file access narrow and tied to the right account check.

DATA HANDLING

Six ways we protect your data

Our Privacy Policy is written around the account flow you actually use: registration, login, payment records, KYC, support and security checks.

Limited collection

We ask for account details, contact fields, device signals and verification data when they serve a clear account, payment, security…

Cookie control

Cookies help keep sessions active, remember language choices and flag unusual login activity.

KYC file care

Identity files are handled through restricted tools and are checked only by teams that need them for verification, fraud checks…

Payment record handling

UPI, Paytm, PhonePe and Google Pay records may include reference numbers, status codes and timestamps.

Access protection

When you request a copy, correction or deletion, we first confirm that the request comes from you.

Retention checks

Some records can be removed after account closure, while payment, KYC or dispute records may need to stay for legal…

Privacy Policy questions before you join

These answers focus only on privacy: what data we collect, why it is used, who may see it and how you can contact us about changes. If you open your account, the same policy applies across mobile and desktop sessions. Where the answer depends on law, eligibility or record keeping, we explain the practical effect in plain terms.

We collect account details, contact fields, login signals, payment references, KYC files and support messages when needed for account access, wallet records, security checks, verification or legal duties.

For UPI, Paytm, PhonePe and Google Pay, we may store transaction references, timestamps, status messages and account matching records. These details help trace wallet activity and answer payment privacy questions.

Yes, you can contact us from the email linked to your account and request a copy. We may verify your identity first so private records are not sent to another person.

Cookies support login sessions, language choices, security alerts and basic site measurement. You can manage them in your browser, but essential cookies may be needed for account and wallet actions.

KYC files are available only to teams and service partners that need them for verification, security checks, fraud prevention or legal duties. They are not used as general support attachments.

Yes, send the correction request through privacy email or the account support route. We may ask for proof before changing details that affect identity, payment records or account recovery.

You can ask for deletion, and we will check what can be removed. Some payment, KYC, security or dispute records may need to stay where law or account safety requires retention.

Privacy Policy for your India account

Three privacy contact paths

Privacy email

Account chat

KYC request ticket

Six ways we protect your data

Limited collection

Cookie control

KYC file care

Payment record handling

Access protection

Retention checks

Privacy Policy questions before you join

01 What personal data does boost777 collect?

02 How does the policy cover UPI and Paytm?

03 Can I ask for a copy of my data?

04 How do cookies affect my account privacy?

05 Who may access my KYC files?

06 Can I correct wrong account details?

07 Can my account data be deleted?

Related Pages