Reference

Privacy Policy for your India account

Our Privacy Policy explains how account details, UPI, Paytm, PhonePe records, cookie choices and support messages are handled when you open an account with qp618.

India account dataUPI Paytm PhonePe recordsCookie choicesData request steps
Explore lobby Read FAQ
qp618 Privacy Policy for your India account
CONTACT ROUTES

Reach us about privacy choices

If your privacy concern relates to login access, payment records or cookie settings, contact us from the same account whenever possible.

Privacy email Send your request to our privacy mailbox with your registered email or mobile number. We will confirm receipt, check account ownership and reply with the next privacy step that applies to your request.
Chat handoff Start with chat if you are already logged in and need help finding cookie controls or account data options. The chat team can pass privacy requests to the right internal team after verification.
Account access help Use account recovery only when you cannot reach your privacy controls. We may ask for payment reference checks or device confirmation before changing data linked to UPI, Paytm or PhonePe activity.
ACCOUNT DATA PRACTICE

How your account data is handled

Privacy work is tied to real account actions: registration, login checks, wallet entries, support chats and preference settings. We separate payment references from public account areas and restrict internal access by role.

Data we collect

We collect details you provide, such as mobile number, email, account name and support messages, along with technical signals like device type, IP address and session activity needed to secure your account.

Payment records

UPI, Paytm, PhonePe and Google Pay references are stored to match wallet activity, check disputes and meet record duties. We do not place these payment references in public account areas.

Cookie controls

Cookies and similar tools help keep you signed in, remember preferences and detect unusual access attempts. You can block or clear cookies in your browser, though some account features may then work differently.

Access security

We use verification steps before showing or changing account data. That may include checking your registered contact details, recent device pattern or payment reference so another person cannot alter your privacy choices.

Retention approach

We keep account and transaction records for as long as they are needed for operations, security, disputes, tax or legal duties. After that, data is deleted, blocked from use or anonymised.

Change requests

You can ask us to correct details, provide eligible data or remove data where the law allows. If full removal is not possible, we will explain the record duty that applies.

Privacy questions for India account holders

These questions focus on how our Privacy Policy works for your account, payment records, cookies and support contact. They are written for day-to-day choices, not legal jargon. If your situation involves a dispute, locked account or a shared device, contact us from your registered email or mobile number so we can connect the request to the right account.

We collect the details needed to create and protect your account, such as mobile number, email, login activity, device signals and support messages. Payment references are stored separately for wallet matching and record duties.

We use local payment references to confirm wallet entries, resolve mismatches, check disputes and meet record duties. These records are not used as public profile content and are shared internally only with authorised teams.

Yes, you can ask for eligible account data through the privacy contact path. We will verify your identity first, then provide the data we can share or explain any legal restriction that applies.

You can ask for deletion of eligible data. Some records may need to remain for security, tax, dispute or legal reasons, and we will tell you if a record duty prevents full removal.

Cookies help keep sessions active, remember preferences and detect unusual access. You can clear or block cookies in your browser or device settings, but some account actions may require fresh verification after that.

Support messages are available only to teams that need them to answer your request, check account ownership or handle a privacy action. We keep access limited and tie messages to the relevant account.

Access or eligibility depends on local law and is available where local law permits. If a legal requirement affects your account, we will handle related data according to this Privacy Policy and applicable rules.

Related Pages

qp618 Login FAQ Berry Burst Temple Tumble