Reference

Your Data, Explained Without the Fog

Your account data sits on a short, checkable list: registration details, the wallet you pay from, and login records we use to spot a session that isn't yours.

What we hold on your accountWallet-linked payment recordsCookie and login controlsRequests handled by chat or email
fee999 Your Data, Explained Without the Fog
DATA REQUESTS

Where to Send a Data Request

Privacy questions move faster when they reach the right desk first. Chat is where most account-data requests start: we verify you with an OTP to your registered number, then work through the request with you. If you'd rather write, use the email tied to your account so we can match it to the profile. Anything about a wallet payment — a bKash transfer that didn't land, a Nagad reference you can't find — goes quicker when you paste the transaction ID from the app.

Live chat Open chat from the lobby footer on mobile or desktop and ask for the privacy desk. We confirm you with an OTP to your registered number before discussing any account data.
Email request Prefer writing? Send it from the email address tied to your account. Tell us what you want — a copy, a correction or closure — and we reply to that same address.
Payment reference If your question is about a bKash, Nagad or Rocket payment shown on your account, include the transaction ID the wallet app gave you so we can match the record quickly.
ACCOUNT CONTROL

How fee999 Handles Cookies and Logins

This page covers what we hold, why we hold it and how you get it changed. Three parts matter in practice: the data tied to your account, the cookies that keep a session alive, and the records that stay after you close. Each is limited to what the lobby and your account wallet need — when you sign in from a new phone, an OTP to your registered number gates the session before it opens. The request path is the same in Dhaka as anywhere else in Bangladesh; only the wallet you paid from changes.

What gets stored

Account details, wallet identifiers and device basics — the browser, network and login times we need to keep your account working and to notice a session that looks wrong.

Cookies in practice

Cookies keep you signed in and remember your language. Session cookies clear when you close the browser; preference cookies stay until you wipe them from your phone or desktop settings.

Retention

Transaction records stay longer than session logs because a wallet dispute can surface weeks later. When a record is no longer needed for that purpose, we remove it or strip it back.

Changes and closure

Ask for a correction, an export or account closure through chat or email. Closure removes your profile; some payment records are kept where local law says we must hold them.

Privacy Questions You Actually Ask

These are the questions our chat desk fields most often about account data, answered the same way we'd answer you in a live session. Most people want to know what's held, who sees it, and how to get something removed. If yours isn't here, use the chat or email path above: verify with the OTP sent to your registered number, then ask directly. No form and no waiting room.

Your registration details, the wallet numbers you pay from, and a log of logins and transactions. We don't keep your bKash, Nagad or Rocket PIN — that stays inside the wallet app on your phone.

Yes. Ask through live chat or from your registered email address, complete the OTP check, and we'll send you a copy of the account records we hold for you.

Only where it's needed to run the service — payment processing and the systems behind the lobby — or where local law requires it. We don't sell your details to outside marketing lists.

Send the request from your registered email or through chat. We close the profile and delete what we can; payment history that local rules require us to keep stays on file.

No. Your bKash, Nagad or Rocket PIN never reaches us. We store the transaction reference so the payment can be matched to your account wallet and checked at withdrawal.

Access depends on your local law and eligible regions. Where local rules differ from this page, local rules apply, and some features may not be offered to you.
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.