Reference

Your Privacy at 777jil, Explained Simply

Our privacy policy spells out what we collect from your account, what your wallet passes to us, and the steps you can take to see, correct or remove that data.

Local wallet contextOne-time PIN sign-inCookie controlData copy requests
777jil Your Privacy at 777jil, Explained Simply
PRACTICE, NOT PROMISES

How 777jil Handles Your Records

Carrying out the policy is the part that matters, so here is how it works day to day. Your data sits behind the same sign-in that protects your wallet balance, and staff who open payment records work from a need-to-know list. Access logs let us trace who looked at what and when. Cookies are split between the ones the lobby cannot run without and the ones you can refuse in your browser. Once the retention period ends, records are deleted or anonymised. Want a copy of what we hold, or a correction? The support paths above are how you ask.

Secure Sign-In

Your account opens with a one-time PIN sent to the mobile number you gave us. We store that number for verification and account alerts, not for marketing lists you never agreed to receive.

Cookies We Set

Session cookies keep you logged in between pages, and a small set of analytics cookies show us which screens stall on mobile networks. Clearing them in Chrome or Safari is fine; sign-in simply asks again.

Data We Hold

Profile details, deposit and cash-out references from bKash, Nagad and Rocket, and device logs. Nothing beyond what the account, payment matching and dispute handling actually need to work.

Retention and Removal

Transaction records stay while your account is open and for the period local rules require afterwards, then we delete or anonymise them. Email us to ask for your copy or a correction to a field.

HELP DESK ROUTE

How to Reach Our Data Team

Privacy questions reach a real desk, not a form that goes quiet. Open live chat inside your account and put the word privacy in the first line so it lands with the right team, or email us from the address registered on your account. Keep your mobile number and the transaction reference handy if your request involves a bKash, Nagad or Rocket payment. We answer in the order requests arrive and confirm in writing once a change is done.

In-Account Live Chat Sign in, tap the help bubble at the bottom of the lobby and type privacy first. The agent already sees your account state, so you skip the identity questions before the real conversation starts.
Email Our Data Desk Write from the address on your account so we can match the request without extra checks. Attach the bKash, Nagad or Rocket reference if a payment record is the reason you are writing.
Wallet Reference Check For anything touching a deposit or cash-out record, send the wallet name, the amount and the transaction ID. That lets us pull the exact entry instead of guessing which payment you mean.

Privacy Questions We Get Asked

These are the privacy questions that land on our support desk most often. Read them before you open an account if you want the short version of how data moves between your wallet, our systems and the people who check payments. Each answer stands alone, so jump straight to the one you need.

Your name, mobile number, date of birth and the wallet number you link, plus device and login logs. Payment references from bKash, Nagad or Rocket come through when you deposit or cash out.

Yes. Email from your registered address and ask for your account data. We check the request against your registered mobile number, then send the file to that same address and confirm completion.

No. We never see your wallet PIN and nothing in our system asks for it. If anyone claims to be from 777jil and requests that PIN, stop the conversation and report it to support.

Sign in and correct your profile wherever a field is editable. For anything locked, such as a linked wallet number, send the request through support with your mobile number and the exact change you need.

Sign-in cookies are required, because without them the lobby cannot tell who you are. Analytics cookies are optional and you can block them in your browser settings, though some pages may then load differently.

Contact our data desk through in-account chat and mark it privacy, or email from your registered address. Include what happened and when. We log it, check the account access trail and reply.
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.