Slots / Mobile
Your ic88e account runs on a small set of things: what you type at sign-in, the wallet references behind Nagad, Rocket and Bank Transfer movements, and the device data your browser sends. This page walks through each of those in plain words, plus the choices you have over them. Access to the site depends on your local law and eligible regions.
We keep this page short because most people read it on a phone, between other things. In plain terms, we hold three groups of data: the details you type when you open an account, the references created when you move money through Nagad, Rocket or Bank Transfer, and the technical logs your browser leaves when it loads a lobby page. That is the whole list at headline level. Where you live matters here. Privacy rules differ between countries, and what we may collect or keep depends on the law that applies to you and on whether your region is eligible to use this site. We would rather say that plainly than promise something your local rules do not allow. Where a rule requires us to hold a transaction record for a fixed period, we hold it, and neither your request nor ours shortens that period. Cookies are the part you ask about most. We set them to keep your signed-in session alive as you move between screens, so you are not typing a password each time. You can clear them from your phone settings whenever you like; the trade-off is a fresh sign-in. We do not sell your data. Sharing happens only where a payment rail needs a reference to complete or reverse a transfer, or where the law compels it.
The policy you are reading covers the parts of ic88e that we run ourselves: the sign-in screen, your account area, the wallet records tied to Nagad, Rocket and Bank Transfer, and the lobby pages served to your phone or browser. It does not stretch to everything you tap. When a payment app opens its own screen to confirm a transfer, that screen belongs to the payment provider and follows its own privacy terms, not ours. The same holds for an external page you reach from a link. Knowing the line helps when something goes wrong. A transfer that looks wrong on your account sits with us, because the reference is in our records and we can look at it. A confirmation step that failed inside the payment app sits with the provider. Four areas, four answers — the cards below set each one out, so you know who to ask first. What we may hold also depends on your local law and on eligible regions. If the site is not available where you are, there is no account for this policy to describe.
Covered here: what you type at the sign-in screen and inside your account area — the phone number or address you register, the password you set, and the device details your browser sends when a session opens. We use them to let you back in and to spot a sign-in that looks unusual for your device.
Every Nagad, Rocket and Bank Transfer movement leaves a reference on your account. That reference, with the amount and the time it was recorded, sits inside this policy, because we need it to match a transfer, answer your question about it, and keep the wallet ledger straight. What a payment app shows on its own screen falls outside it.
The lobby you load on your phone sets cookies so a session survives a screen change. Those cookies and the pages they point to are covered. So are the game titles we display, including the ones supplied by studios such as Habanero or PlayStar — though a studio's own site, if you visit it, follows different terms.
Outside this policy: the confirmation screens inside Nagad and Rocket, the page your bank shows during a Bank Transfer, and anything you open from an outside link. Those services answer to their own privacy terms and their own support desks, so a question about them should go there rather than to us.
You do not need to write a formal letter to use the choices on this page. Three things cover most requests: seeing what we hold, fixing something that is wrong, and asking us to explain a decision. Start inside your account area, because the records we can show you are the same ones you see there — the details you registered, the wallet references behind your Nagad, Rocket and Bank Transfer transfers, and the sign-in history attached to your device. If something is out of date, correct it in the account fields rather than messaging us; the change takes effect sooner. Where a correction cannot be made from your side, message the support route published on this site and say which field is wrong and what it should say. Keep it specific: the phone number, the reference, the date. Requests that depend on your local law — a copy of your records, a deletion request — are handled under that law, and some records tied to a completed transfer may have to stay for the period the rules set.
Open your account area and read the profile fields, the wallet references for Nagad, Rocket and Bank Transfer, and the sign-in list attached to your device. If you want a compiled copy rather than the screens, ask through the support route and say which period you need covered.
Wrong number, wrong spelling, an address you no longer use: fix it in the account fields first. Anything the screen will not let you edit should go to support with the field name, the current value and the correct one, so the change is made once rather than over two rounds.
If a copy or a correction is taking time, reply on the same thread instead of opening a new one, and quote the reference you were given. That keeps your request with the person already holding it, and it means you are not re-explaining your account from the start.
If you think a record is being held that should not be, or that someone else reached your account, say so on the published support route and include the date plus the device you were using. We can then check the sign-in list with the right timeframe in front of us.
We do not publish a list of phone lines, because a number you cannot verify is worse than no number. What we do keep visible is the support route published on this site. Use it for anything to do with this policy: a copy request, a correction, a question about how a Nagad or Rocket reference is stored, or a concern about a sign-in you did not make. Say what you need in the first message. Account number, the reference if there is one, the date, and the device you were on. Vague messages cost you a round trip. If your question is about the confirmation screen inside a payment app, or about a Bank Transfer page your bank controls, that desk holds the record, not us. Ask there first and come back to us only if the reference still does not match your account.
The contact link published here is the main path for policy questions. Use it for copy requests, corrections and sign-in concerns, and include your account number plus the date of the record you are asking about. One clear message saves a day of back and forth.
Most answers are already on screen once you sign in: the profile fields you registered, the wallet references behind your Nagad, Rocket and Bank Transfer movements, and the devices attached to your session. Read those first, then message us about the part that still does not look right.
For a confirmation that failed inside Nagad or Rocket, or a Bank Transfer page your bank runs, the provider keeps the record. Their desk can trace it with the reference you were shown. Come back to us if that reference never lands on your account.
Data handling here follows a simple rule: keep what the account needs, and not much else. The profile fields you register, the references behind your wallet movements, and the logs from your sign-in are the working set. Cookies sit above that to hold a session together between screens. Clearing cookies in your phone settings signs you out, and the next visit starts clean. Sign-in safety is the part we ask you to share. Keep your password to yourself, and treat a message asking for it as a message from someone who is not us — we do not ask for it through chat. If you signed in on a phone you no longer use, change the password and tell support on the published route, with the date, so the sign-in list can be checked against that timeframe. Retention works the other way round: references tied to a completed transfer stay for the period local rules set, and a request from you cannot shorten it. Everything else goes when the account closes.
The working set is small: what you register, what a transfer leaves behind, and what your browser reports at sign-in. We do not build a wider profile from it, and we do not sell it. Anything beyond that set has to be justified by a legal requirement in your region.
A cookie holds your signed-in session so a screen change does not throw you back to the login form. Clear them from phone settings and you sign out; the next visit asks for your password again. Clearing cookies does not delete the account or the records tied to it.
Your password stays with you. We do not ask for it in a chat message, and a request that arrives that way is not from us. If you signed in on a phone you no longer use, change the password, then tell support with the date so the sign-in list can be checked.
References attached to a completed transfer stay for the period your local rules set, and no request shortens that. Other account fields are removed when you close the account. If you want to know which of your records falls on which side of that line, ask and we will say.
These are the questions that land in our support route again and again, answered without the legal padding. If yours is not here, the route published on this site takes it, and a short message with your account number and the date gets a faster reply than a long one. Where an answer depends on your local law or on whether your region is eligible for the site, we say so instead of guessing on your behalf.
Three groups: the profile fields you register, the references behind your Nagad, Rocket and Bank Transfer movements, and the technical logs from your sign-in. That is the working set. If you want to see it, most of it is already on screen once you sign in.
Only what a transfer needs: a reference and enough to match the movement to your account. The payment app runs its own screens and keeps its own records under its own terms. We do not pass your account data to a provider for any other purpose.
Ask on the support route published on this site and say which period you need covered. Requests that depend on your local law are handled under that law, so what we can compile, and how far back, follows the rules where you are. Site access itself depends on eligible regions.
You can clear cookies from your phone settings at any time. The consequence is simple: the session ends and you sign in again on the next visit, and a few display choices reset with it. Your account and its records are untouched by that step.
References tied to a completed transfer stay for whatever period your local rules set, and a request from you cannot shorten it. Other fields go when the account closes. Ask if you need to know which of your records sits in which group.
Change your password first, then message support on the published route with the date and the device you were using. We can check the sign-in list against that timeframe. If a payment app screen is involved, that provider's desk holds its own record.