Live / Slots
This page sets out the terms that govern your account with jili z — what you agree to, how your data is handled, and the routes available when you need to raise a policy question. Access to this platform depends on local law and is available only in eligible regions.
Our legal terms are written for members accessing the platform from eligible regions under local law. We do not make guarantees about jurisdiction coverage — if your region's law restricts access, these terms do not override that restriction. What we commit to is clarity: the terms shown in your account dashboard at login reflect the version currently in effect, and we update the published date whenever a material change is made. For transactions, policy context covers the payment rails you use — Maya, Coins. ph, and PESONet — as funding routes whose processing is governed by each provider's own terms alongside ours. If a transaction falls outside an expected range or triggers a review, the record is visible in your account wallet section, and our policy support channel is the right place to raise it. Session and account data we hold is covered under our data handling section below. We retain records for the period required by operational necessity and applicable rules — not indefinitely. You have practical routes to review what we hold, request corrections, and ask us to act on your request. Those routes are listed in the Rights section of this page and remain available to you at any time after account creation.
Maya transactions are subject to our payment terms and Maya's own provider terms simultaneously.
Coins. ph wallet transfers fall within the transaction scope of this policy.
PESONet transfers are logged in your account wallet and covered under our transaction records policy.
Not every element of your account experience is governed by the same policy layer. Understanding the scope prevents confusion when you need to raise a question — you will know which channel applies.
Login credentials, session controls, account verification steps, and your stored preferences are all within the scope of this policy. Questions about access fall to our policy support channel.
Deposits and withdrawals processed through Maya, Coins. ph, or PESONet are within scope for record-keeping and query purposes. The payment provider's own terms also apply to each transfer.
Game content from PG Soft, CQ9, Habanero, and PlayStar is supplied by those studios. Our terms cover your access to that content; studio-level rules are outside our direct policy scope.
External links, third-party verification tools, or partner services operate under their own terms. We do not extend this policy to cover third-party conduct — check those services directly.
Your rights under this policy are not passive. You can act on them at any time through your account or through our policy contact channel. Start with your account dashboard — transaction records, session history, and stored personal details are all visible there after login. If something looks wrong, the correction route is available without waiting for a support escalation. For data-level requests — asking what we hold, requesting a correction, or querying a retention period — the policy contact address in the Support section of this page is the direct route. We aim to acknowledge requests within a reasonable period and we track each one to resolution. Raising a question through that channel creates a record on both sides, which is useful if the matter needs further review.
Your account dashboard shows transaction history, session logs, and personal data we hold. Log in and navigate to account settings to see the current state.
If your stored name, contact detail, or payment record is wrong, you can submit a correction request through the policy contact channel with the relevant account reference.
For any clause you want to clarify — scope, data retention, transaction rules — contact us via the policy support path. We log every query and respond in writing.
If your query is not resolved at first contact, ask for escalation. We track open policy queries and escalate when a first response does not address the issue.
Three contact routes are open for policy-related questions. Use the one that fits your query type — general questions go to live chat, formal written requests go to the policy email, and account-specific access issues go through the account help path in your dashboard.
Open the chat widget from any page on jili z to reach a support agent for policy clarifications, account questions, or transaction queries in real time.
For written data requests, correction submissions, or formal policy inquiries, email our policy address listed in the Contact section of your account dashboard.
Navigate to Settings > Help inside your account for guided steps covering access issues, session control questions, and wallet record queries.
We handle account data with a clear retention posture — we keep what operational rules require and nothing beyond that. Cookies used on jili z are limited to session management and functional preferences; analytics cookies are noted in our cookie disclosure, which you can review from the footer of any page. Account security relies on login verification steps visible at the point of access — we do not publish the specific mechanism here, but the steps are shown when you log in. For any security concern, the policy email channel is the right route.
We retain account and transaction records for the period required by operational rules. After that period, records are removed unless a live query requires them to be held.
Session and functional cookies keep your account state intact across pages. The full cookie list is in our footer disclosure — you can adjust preferences from there at any time.
Verification steps are shown at login. If you suspect unauthorised access, use the Account Help path immediately — we can place a hold on the account while the matter is reviewed.
Written data requests and correction submissions go to the policy email address in your dashboard. We acknowledge each request and respond with a reference number.
These are the policy questions we receive most often. If yours is not here, the live chat and policy email channels are open for anything not covered below.
Access to jili z depends on local law and is available only in eligible regions. The policy applies to accounts created where access is permitted. If local law restricts access in your region, that restriction is not overridden by these terms.
Log in and go to your account settings — much of your stored data is visible there directly. For a full data request, contact us via the policy email address listed in your dashboard. We respond in writing with a reference number.
Yes. Submit a correction request through the policy email channel with your account reference and the detail that needs to change. We review it and confirm the correction in writing once it is applied.
We keep records for the period required by operational necessity and applicable rules. After that period, records are removed unless a live policy query requires them to remain on file. The retention period is not published as a fixed number of days.
Transaction queries related to Maya, Coins. ph, or PESONet are within our policy scope. Start with the wallet section of your account dashboard for the current record, then raise a query through live chat or the policy email channel if the record is missing or unclear.
Ask the agent to escalate. We track open policy queries and escalate when a first response does not address the issue. You will receive a reference number so the matter stays on record until it is resolved.