Sports / Live
This page sets out the legal basis on which imbaslog operates and the rights available to you as an account holder in eligible regions. Access to our platform depends on local law where you are located, and the terms here reflect that position clearly.
Our legal policy governs every interaction between you and the platform — from the moment you open an account to the point you make a transaction or raise a support request. Access to imbaslog is available only where permitted under local law in your eligible region; if local law in your area does not permit access to platforms of this kind, you should not proceed. We do not make legal eligibility determinations on your behalf — that responsibility rests with you. Transactions processed through OVO and GoPay are subject to the terms of those payment services in addition to our own policy. The platform scope covers account registration, wallet activity, game sessions and any communication with our support team. Where a third-party service is involved — such as a payment processor or a game studio — their terms apply to that part of the service alongside ours. We keep a record of your account activity in line with our data retention schedule. You can check the current state of your account records after login in your account dashboard. If any detail looks incorrect, the rights section further down this page explains the steps to raise a correction request.
Understanding the boundary of this policy helps you know where our obligations begin and where a third-party service takes over. The four areas below map that boundary clearly so you can direct questions to the right place.
Our policy covers the account registration process, login credentials, session management and any account-level action you take on the platform. Steps shown in your account dashboard after login are within our direct policy scope.
Deposits and withdrawals processed through OVO, GoPay or DANA are covered by our transaction policy up to the point of handoff to those services. Once funds leave our wallet to the payment provider, their own terms govern the transfer.
Game content supplied by studios available in the lobby — including titles like Barong Dance Slots or Fortune Fishing Game — is presented under agreements between us and those studios. Content accuracy and availability are part of our policy scope.
External services linked from or integrated with our platform — including payment rails and independent game studios — operate under their own separate terms. We are not liable for their policy positions, and their terms sit outside ours.
You have clear, actionable rights under this policy that do not require a legal background to exercise. Your account dashboard — accessible after login — is where most of these start. Transaction records, session history and registered account details are all visible there, and the dashboard reflects the current state of your data without delay. If a detail in your account looks wrong — a registered name, contact address or payment method record — you can raise a correction request through our support channel. We aim to respond to correction requests within the timeframe shown in the support section of this page. For broader questions about how we handle your data or what records we hold, a written request to our policy contact address is the direct route. The process is outlined in the trust section below.
Log in and open your account dashboard to see transaction history, session logs and registered details. The dashboard shows the current state of all records we hold against your account.
If a registered name, email or linked wallet detail is incorrect, submit a correction request via our support contact. Include your account reference and the specific field you need corrected.
For questions about data handling, retention schedules or the scope of our legal obligations toward you, send a written request to our policy contact address listed in the support section.
Account-level issues — including access problems, wallet mismatches or session disputes — go through our support team. Contact details and available channels are in the support section directly below.
Policy questions, data requests and correction submissions each have a direct route. Use the channel that matches your query type — general account help, a formal data request or a written legal notice — so we can route it to the right team without delay.
For account access issues, wallet record questions or general policy clarifications, contact our support team through the help channel shown in your account dashboard after login.
To request a copy of the data we hold on your account or to submit a formal correction, send a written request to our policy contact address. Include your registered account email and the scope of your request.
Formal legal notices — including objections, dispute filings or regulatory queries — should be submitted in writing to our designated legal contact. The address is available on request through the support channel.
Our approach to data, account security and retention is built around what you can verify in your own account. Nothing here is abstract — every commitment below maps to a visible step or a documented process you can follow.
We collect account registration data, session activity and transaction records linked to your wallet — including OVO, GoPay and DANA interactions. We do not share this data with third parties outside the scope described in this policy. The current data state is visible in your account dashboard.
Our platform uses cookies to maintain your login session, remember account preferences and measure how the lobby is used. Cookie settings are manageable through your browser. Continuing to use the platform after reading this notice confirms your awareness of that use.
Account access is protected through credential verification at login. If you believe your account details have been compromised, contact support immediately through the channel in your dashboard. We do not store payment PINs or wallet passwords on our side.
We retain account records for the period required by our operational policy. If you want to know the specific retention period for your account data, or to request a change, submit a written request through the policy contact route described in the support section above.
These are the questions we receive most often about how this policy works in practice. If your question is not here, reach out through the support channel in your account dashboard.
Access to imbaslog depends on whether local law in your region permits it. If you are in an eligible area in Indonesia, this policy applies to your account. It is your responsibility to confirm that access is permitted where you are located before proceeding.
After login, your account dashboard shows the current state of your registered details, transaction history and session records. If anything looks incorrect or incomplete, follow the correction request process described in the rights section of this page.
Contact our support team through the channel shown in your dashboard, include your account reference and name the specific field you believe is wrong. We will review the request and respond through the same channel. Written data requests can also be sent to our policy contact address.
Transaction records for OVO and GoPay activity within our platform are part of our account data. The point where funds transfer to those payment services falls under their own separate terms. Both sets of terms apply in sequence, depending on which part of the transaction is in question.
We retain account data for the period set out in our operational retention schedule. The exact period for your account data is available on written request. Submit that request through the policy contact route listed in the support section and we will respond with the specific detail.
Formal legal notices — disputes, objections or regulatory queries — must be submitted in writing to our designated legal contact address. Request that address through our support channel. Notices sent through general chat support will be logged but may not meet the threshold for a formal legal response.