Mobile / Slots
ze55 collects and uses account data only to run your sessions, process wallet transactions through Nagad, Rocket and Bank Transfer, and keep your account secure. What we collect, why we hold it, and how you can act on it — that is what this policy covers.
When you open an account with us, we collect the information you submit during registration — your name, contact details and the credentials you choose. When you make a deposit or withdrawal through Nagad, Rocket or Bank Transfer, our payment processing layer records the transaction reference and amount so your wallet history stays accurate and disputes can be resolved. We also collect device and session data — browser type, IP address, and session timestamps — because these help us detect unusual access patterns and protect your account from unauthorised use. Cookies and similar technologies keep your session active across pages and remember your lobby preferences; you can manage cookie behaviour through your browser settings. We do not sell your personal data to third parties for their own marketing. We share data only where our platform operations require it — for example, with payment processors handling your Nagad or Rocket transaction, or with compliance functions required under applicable jurisdiction rules. Retention periods depend on the category of data: active account data is held while your account remains open; transaction records are kept for the period required by applicable rules in eligible regions. Accessing this platform and the terms under which your data is processed depend on your local law and the regions where this service is available.
Transaction references from Nagad deposits and withdrawals are recorded in your wallet history so you can verify each movement without contacting support.
Rocket payment records are linked to your account session log. If a transaction reference is disputed, the record on file is the first point of investigation.
Bank Transfer entries carry a reference ID visible in your account. We hold these for the retention period required under applicable rules in eligible regions.
IP address, browser type and session timestamps help us identify access anomalies. This data is not shared with advertisers.
Not every element of your account session falls under this policy in the same way. Some parts — like what you do inside a third-party game — are governed by that provider's own terms. Understanding the scope helps you know exactly who is responsible for which data at each step of your session.
Login credentials, session tokens and device records you generate when you sign in to ze55 fall fully within this policy. We control how this data is stored, used and deleted.
Deposit and withdrawal data processed through Nagad, Rocket or Bank Transfer is covered here for the records we hold. The payment processor's own privacy terms also apply to their side of the transaction.
Pages you browse, lobby categories you open and game tiles you click generate behavioural data we use to improve navigation. This is covered by this policy and by our cookie notice.
Game content delivered by studios such as Pragmatic Play, PG Soft or Habanero runs inside their own environment. Data you generate there is subject to those providers' policies, not solely ours.
You have practical options here — not just abstract rights. If you want to see what data we hold against your account, you can submit a data access request through our support route and we will respond with a summary of the records on file. Found something incorrect in your account details? Log in, go to your account settings page, and update the relevant fields directly. For name corrections or document-linked details, contact support with the corrected information and we will review it. If you believe we are holding data beyond the retention period relevant to your region, raise it with support and we will check the applicable rules. Requests to close an account and erase associated data are handled through the same support route — note that transaction records required under applicable jurisdiction rules may be retained even after account closure. Availability of these rights depends on your local law and the eligible regions where this service operates.
Submit a data access request via support. We will respond with a summary of what account, session and transaction data we hold for you.
Most contact details can be updated directly in account settings. Document-linked fields require a support request with the correct information attached.
If something in this policy is unclear or you believe your data has been handled incorrectly, open a support query and describe the issue specifically.
Account closure and associated data deletion requests go through support. Some transaction records may be retained under applicable regional rules even after closure.
If you have a question about how your data is handled, or you want to act on any of the rights described in this policy, use one of the contact routes below. Keep your account reference ready — it speeds up how we locate your records and respond accurately.
Open the chat widget from any page while signed in. Describe your privacy question and include your account reference so the agent can pull up your record without delay.
Send your data query to the support email address shown in the Help section of your account. State the nature of the request clearly — access, correction or deletion.
Your signed-in account area has a Help or Contact page listing the current support routes. This is the published location — check there for the most current contact details.
Knowing how we handle data day-to-day is more useful than general assurances. Each item below describes a specific practice — from cookie behaviour to account security — so you can verify it against what you see in your account.
We use session cookies to keep you logged in and preference cookies to remember your lobby view. You can adjust or clear cookies through your browser settings at any time; doing so may log you out of the current session.
Unusual login attempts — new devices, unfamiliar IP locations — trigger a verification step before access is granted. If you receive a verification prompt you did not expect, contact support immediately.
Active account data is held while your account is open. After closure, transaction records are kept only for the period required under rules applicable to your eligible region — not indefinitely.
When this policy changes in a material way, we update the version date at the top of this page. Continuing to use your account after an update means you have seen the revised terms. Check this page periodically if you want to stay current.
These are the questions we see most often from people reading this policy. If your question is not here, open a support query and we will respond with a specific answer.
We collect the details you enter at registration — name, contact information and login credentials — plus device and session data generated when you sign in. Transaction references from Nagad, Rocket or Bank Transfer deposits are also recorded in your account wallet history.
Yes. Submit a data access request through live chat or the support email shown in your account's Help section. Include your account reference so we can locate your records quickly and provide a clear summary.
Basic contact details can be updated directly in account settings after you log in. For document-linked fields — such as a name correction — contact support with the accurate information and we will review the change against your account records.
Studios like Pragmatic Play, PG Soft and Habanero operate their own game environments. Data generated inside those games is subject to their own privacy practices. We do not pass your registration data to studios for their independent use.
We retain transaction records — including Nagad, Rocket and Bank Transfer entries — for the period required under rules applicable to your eligible region. Active account data that is not subject to retention requirements is removed after closure is processed.
Your account data is tied to your account credentials, not to a specific device. Signing in from a new phone or browser generates a new session record. If the login comes from an unrecognised device, a verification step may be triggered before access is granted.