Sports / Casino
These terms govern your use of lodi666 and define the rights and obligations that apply when you access the platform from a supported region. Access to lodi666 depends on local law and is available only where permitted in your eligible region.
Our legal terms are written to be read, not buried. The core principle is straightforward: you use the platform under the rules that apply in your eligible region, and we hold ourselves to the same standard in return. Where local law restricts access, those restrictions apply regardless of how you reach the site. We do not override local eligibility rules. When you complete account registration, you confirm that you are accessing the platform from a region where this is permitted. That confirmation sits on your account record and can be reviewed at any time through your account dashboard after login. Transactions processed through Maya, GrabPay or Bank Transfer are subject to the terms of those payment providers as well as our own. We do not override the terms of any payment rail — we operate alongside them. Any dispute or question about a transaction should first be checked against your account wallet history, then raised with our support team if the record is unclear. We keep policy documents current and display the effective date at the bottom of each published version. If a material term changes, we notify account holders through the contact method recorded on their profile before the change takes effect.
Not everything on the platform falls under a single policy document. Understanding the scope helps you know where to go when a question comes up — whether that is your account settings, a transaction record or the terms of an external service you connected to your wallet.
Login, session management and account verification are governed by these terms. If your access is restricted due to a regional eligibility check, that decision flows from local-law requirements, not a discretionary platform setting.
Deposits and withdrawals through Maya, GrabPay or Bank Transfer are covered jointly by our transaction policy and the terms of each payment provider. Your wallet history in the account dashboard is the authoritative record.
Game content supplied by studios such as Pragmatic Play, PG Soft, CQ9 and Bigtime Gaming is governed by their respective content licences. We make those titles available in the lobby; the underlying game rules belong to each studio.
Any external service you connect — a bank, an e-wallet provider, or an identity verification service — operates under its own terms. Our policy does not extend to third-party platforms, and we are not responsible for their decisions.
Knowing your rights is only useful if you know how to act on them. Your account dashboard, accessible after login, is the starting point for most requests covered under this policy. Transaction records, account details and communication preferences are all visible there. If something looks wrong — a transaction amount that does not match what you authorised, or a detail on your profile that is out of date — you do not need to wait for a scheduled review cycle. You can raise a correction request at any time by contacting our support team directly. We log every request and provide a reference number you can use to follow up. For questions about how your data is stored or who can access it, the correct channel is our dedicated policy contact address, not general chat support. We respond to data-related requests separately from account-level queries so neither queue slows the other down.
Your full transaction and session history is available in the account dashboard after login. Filter by date or payment method to isolate the record you need. If a line item is unclear, note the reference number before contacting support.
Name, contact number and registered e-wallet details can be flagged for correction through account settings. Certain changes require identity verification before they take effect — the fields shown during the update process will indicate which steps apply.
Direct policy questions — eligibility, data retention, consent changes — go to our policy contact address. Include your account reference so our team can locate your record without asking for it twice.
If a first-contact response does not resolve your issue, you can request escalation by replying to the original support thread and marking it for review. We track escalation requests separately to keep response times consistent.
Policy questions and account-rights requests have specific contact paths. Using the right channel gets your question to the right team without delay. For general account issues, live chat is the quickest route. For data and policy requests, use the dedicated email address so your query is logged under the correct category from the start.
Available through the account dashboard after login. Use this channel for account access issues, transaction queries and general questions about your wallet history — including Maya, GrabPay and Bank Transfer records.
Send data-handling, retention and eligibility questions to our dedicated policy contact address listed in the full terms document. Include your account reference number and the specific section of the policy your question relates to.
For corrections to your registered details — contact number, e-wallet link, communication preferences — start in account settings. The fields there show which changes require additional verification before they are applied to your record.
Account security and data handling are not separate concerns — they are the same concern viewed from different angles. We apply access controls at the account level so that only you, or someone you have explicitly authorised, can change your registered details or initiate a transaction. Session tokens are not persistent across devices by default; if you log out on one device, that session closes. Cookies are used to maintain your logged-in state and to remember account preferences such as language and payment method. You can review and adjust cookie preferences through the settings link in the site footer. We retain account and transaction records for the period required by the applicable rules of the regions where we operate. After that retention period, records are deleted or anonymised according to our data schedule. Requests for early deletion are assessed case by case; contact our policy team with your account reference to start that process.
Account and transaction data is stored and processed in line with the requirements of the regions where access is permitted. We do not sell account data to third parties. Your wallet history — including Maya, GrabPay and Bank Transfer records — is visible only to you and authorised support staff.
We use cookies for session management and preference storage, not for cross-site behavioural tracking. Cookie preferences can be reviewed and adjusted at any time through the footer settings link without affecting your account login state.
Password changes, contact-detail updates and payment-method links all require the verification steps shown in your account settings at the time of the change. We do not process these changes over chat — only through the authenticated account path.
Records are kept for the period required under applicable regional rules and then deleted or anonymised. To request an earlier review of your data retention status, contact our policy team by email with your account reference included in the subject line.
These are the questions account holders ask most often about policy, eligibility and data rights. If your question is not covered here, use the policy email contact path described in the support section above.
Access to lodi666 depends on local law and is available only in eligible regions where such access is permitted. We do not make claims about specific licence jurisdictions. If you are unsure whether access is permitted in your area, check the eligibility notice shown during account registration.
Your transaction and session history is visible in the account dashboard after login. For a broader view of what data we hold — including records outside the dashboard — send a request to our policy email address with your account reference number. We respond to data access requests separately from general support queries.
Yes. Account details including linked payment methods can be flagged for correction through account settings. Some changes require identity verification before they take effect. The fields shown during the update process will indicate exactly which steps apply before you confirm the change.
After account closure, we retain records for the period required under applicable regional rules. Once that period ends, records are deleted or anonymised according to our data schedule. You can request an earlier review of your retention status by contacting the policy team by email with your account reference.
If a material term changes, we notify account holders through the contact method recorded on their profile before the change takes effect. The effective date of the current version is displayed at the bottom of the published terms document. We do not make retroactive changes without prior notice.
No. Policy and data requests are handled by a dedicated team separate from general account support. Use the policy email address listed in the full terms document, not the live chat channel, for questions about data retention, eligibility or consent. This keeps both queues moving without one delaying the other.