Reference

What We Collect and Why

Your quenqv account runs on a small set of details you choose to share: a mobile number, a wallet reference, the device you sign in from. This page tells you plainly where each piece goes and how to get it changed.

Mobile number and login IDWallet reference for bKash, Nagad, RocketDevice and session logsSupport ticket history
quenqv What We Collect and Why
ASK THE DESK

How to Reach Our Privacy Desk

Live chat is the quickest route when a session looks wrong, because we can pull the device log while you are still in the lobby. Email suits a data request that needs a written trail. A ticket keeps a correction or closure thread in one place, and it carries a request ID you can quote back to us. Have your account ID ready either way.

Live chat Open the chat panel from any lobby page and put the question in one line. Keep your account ID handy so we can pull the right record instead of guessing at your login.
Email the desk Write to the support address pinned in your account area with the subject line Data Request. We reply only to the mobile number and address already registered on your account.
Account ticket For a correction or closure, raise a ticket under Settings, then Privacy. The request ID stays on that thread, so you can follow the same case until our team marks it done.
HOW WE HANDLE IT

Data Handling, Cookies and Retention

Almost every privacy question comes down to four things: what sits in our database, what a cookie does, who can reach your account, and how long a record survives. We keep the answers short. A one-time code gates every sign-in, wallet edits need that code again, and a closure request moves through the same ticket queue you can see.

Data we keep

Your mobile number, login credentials, the wallet reference for bKash, Nagad or Rocket, and the device records tied to each sign-in. Nothing beyond that is required to open or run your account.

Cookies and sessions

Session cookies keep you signed in and remember your chosen payment rail. Preference cookies store language and layout. Clear both from your browser and you will verify once more with a one-time code.

Account security

A one-time code goes to your registered mobile at login. On an unrecognised device we ask for that code again before any wallet change is allowed, so a leaked password alone cannot move funds.

Retention and changes

Transaction records stay attached to your account for as long as local rules require. Ask our desk to fix a wrong number or close the account, and we confirm in writing once it is done.

Privacy Questions You Might Ask

These are the ones that land in our inbox most often, answered the way we would answer them on chat. If yours is not here, the desk is one message away and we would rather you asked than guessed.

Raise a ticket under Settings, then Privacy, or email the desk from your registered address. We confirm receipt, verify you with a one-time code, then send the extract for your account.

Yes. Ask our desk to close it. Access stops straight away, we remove what local law lets us remove, and we keep only the transaction records a payment dispute or a rule still requires.

No. You approve the transfer inside your own wallet app, so the PIN stays with bKash, Nagad or Rocket. We receive the amount, the reference number and the time of payment.

Only the wallet operator handling that transfer, plus our payments team when a credit needs checking. Your number does not go to advertisers and we do not sell it onward.

Records stay while your account is open, then for the period local rules set for payment disputes. Once that period ends, they come out of the live system and off backup rotation.

The cookies here are first-party, used for sign-in and for remembering your language and payment rail. Tracking scripts from outside ad networks are not part of how this site runs.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.