Sports / Live
This policy explains exactly what account and transaction data imbaslog collects when you use our lobby, how that data is stored, and what choices you have about it. Availability of our services depends on local law and eligible regions in Indonesia.
When you open an account on imbaslog, we collect the registration details you enter — your name, contact address and login credentials. When you add a payment method such as OVO or GoPay, the wallet reference linked to your account is stored so that your transaction history is readable from your account dashboard. We do not store full wallet PINs or one-time authentication codes issued by those services. Browsing data — pages visited, game sessions opened, device type — is collected to keep the lobby working correctly on your screen and to identify errors. This data is not sold to advertising networks. Where we engage third-party service providers for hosting or analytics, those providers are bound by data-handling terms consistent with this policy. Data is retained for as long as your account remains active and for the period required by applicable local regulations thereafter. You may request a summary of the data we hold on your account by contacting our support channel. Access to these services is available where local law permits, and eligibility depends on your jurisdiction.
The OVO account identifier linked at checkout is stored against your imbaslog profile for transaction history only.
GoPay payment references are recorded in your account transaction log and are accessible from your dashboard after login.
If you use DANA, the deposit amount and timestamp appear in your account wallet history, readable at any time from your profile page.
Browser type, session duration and page paths are logged to maintain lobby performance. This data is not shared with advertisers.
This policy applies to data we collect directly through your imbaslog account. It does not extend to third-party services you reach from our pages, whose own terms govern your data there. Understanding the boundary helps you know where to direct a data question.
Login events, password changes and session records tied to your account fall fully within this policy. You can review these from your account security settings after login.
Deposits and withdrawals processed via OVO, GoPay or DANA are logged under this policy. The payment provider's own privacy terms also apply to data held on their side.
Game session data — titles opened, round outcomes — is recorded within our system under this policy. Studio providers such as Habanero or PG Soft receive only the game-mechanics data needed to run each title.
Links to external sites, app stores or wallet provider pages are outside this policy's scope. We do not control how those services handle your data once you leave our platform.
You have several concrete actions available to you regarding the data imbaslog holds. Reviewing your stored details is the starting point: log in, open your account profile, and the fields we hold — contact details, linked wallet references, session history — are visible there. If anything is incorrect, you can edit contact fields directly in the profile form; for wallet reference corrections, the process is handled through our support channel because changing a linked OVO or GoPay reference requires identity verification steps shown on-screen during the request. Beyond correction, you may ask us to clarify what data we hold and why. We respond to data questions through the support paths listed on this page. Where local law grants the right to request deletion of an account and its associated data, you may raise that request through the same support channel; we will confirm the scope of what can be removed and the process timeline as shown in the response.
Log in to your account and open the profile section. Your stored contact details, linked wallet names and transaction log are all visible from that single page.
Contact fields can be updated directly. To change a linked OVO or GoPay reference, contact support — the verification steps are shown during the request flow.
If you want to understand what specific data we hold on your account, send a message through the support channel. We will respond with the relevant details.
Where local law permits, you may ask us to close your account and remove associated data. Submit this through support; the response will confirm what is removable and the process.
If you have a question about how we handle your data, the fastest path is through the live chat widget at the bottom of any page after you log in. For written requests — data reviews, correction requests or removal inquiries — the support email is the right channel. Response times are shown in the confirmation message you receive after submitting.
Open the chat widget after logging in to your account. For data and privacy questions, start the conversation with your account email so our team can locate your record quickly.
Send written data requests — including review, correction and removal — to our support email. The address is shown in your account dashboard under the Help section after login.
Many data queries can be resolved without contacting us. Log in, open your profile, and check the transaction log and stored details directly — the current state of your data is shown there.
Data handling at imbaslog follows a straightforward structure: collect what is needed to run your account, keep it for the period local regulations require, and give you clear access to what we hold. Cookies used on the site are limited to session management and lobby performance — no advertising or cross-site tracking cookies are placed without a disclosed purpose. Account security relies on the login credential system you set up at registration; we do not hold unencrypted passwords. For wallet data, OVO and GoPay references are stored as account identifiers, not as active payment authorisations. Where third-party analytics are used, the data shared is aggregated and does not identify individual accounts.
Cookies on imbaslog manage your login session and lobby display preferences. No third-party advertising cookies are placed. You can review cookie settings in your browser at any time.
Passwords are stored in encrypted form. We do not see your plain-text password. If you suspect unauthorised access, change your credentials from the account security page and contact support.
We keep your account data for as long as your account is active and for the period required under applicable local regulations after closure. The exact period depends on your jurisdiction.
When this policy changes, the updated version is posted here with the revision date shown at the top of the page. Continuing to use your account after a posted update means you have seen the revised terms.
These are the data and privacy questions we hear most often from account holders in Indonesia. If your question is not answered here, the support team is available through live chat or email.
At registration we collect the name, contact details and login credentials you enter in the form. We do not collect data beyond what the registration fields ask for. Your submitted details are visible in your account profile after login.
The wallet identifier you link at checkout — your OVO or GoPay reference — is stored against your account for transaction history purposes. We do not store wallet PINs or authentication codes issued by those services.
Log in and open your account profile. Your stored contact details, linked wallet references and transaction history are displayed there. For a formal data summary, contact support through the email channel listed in your dashboard.
Where local law in Indonesia permits, you may request account closure and data removal. Submit this request through the support channel. We will confirm which data can be removed and the process steps in our response.
Studios receive only the game-mechanics data needed to run each title — such as session tokens. They do not receive your full account profile, contact details or wallet references. Their own terms govern data on their side.
The revised policy is posted on this page with an updated date at the top. We recommend checking here periodically. Continuing to use your account after a posted update indicates you have reviewed the revised terms.