1. Acceptance of These Terms
These Terms and Conditions govern access to and use of the Administrator website, control panel, reseller tools, device activation workflows, Android application, and related management features. By visiting the public site, downloading the APK, logging into the panel, configuring a device, generating an activation code, assigning a DNS route, transferring credits, or otherwise using any part of the service, you agree to be bound by these terms. If you do not agree with them, you should not use the site, panel, or application. These terms are written to reflect the actual operating behavior of the platform rather than to bury key points in vague boilerplate.
The service is intended for business, operational, or administrative use in the context of IPTV app deployment, device onboarding, customer activation, subscription control, and reseller account management. That means the platform is not just a generic website. It is an operational environment where actions inside the panel can affect live devices, active accounts, expiry dates, routing behavior, credit balances, and customer access. Anyone using the service should therefore understand that account credentials, role permissions, and activation workflows have real consequences. These terms are meant to set clear expectations so that administrators, resellers, sub resellers, and end users know the rules that apply before relying on the platform.
2. Description of the Service
The platform provides a reseller-oriented control environment for an Android application and related device workflow. Key features may include app download access, first-launch activation flow, device registration, activation code generation, status management, per-device DNS assignment, remote STB model selection, remote media player selection, overlay behavior control, reload profile commands, master route or secure gateway handling, hidden portal routing, expiry control, renewal actions, credit-based account management, plan creation, reseller hierarchy support, sub reseller controls, audit logging, session controls, exports, and public support contact presentation. Public pages on the site describe the service and may provide a route to reseller login, while the protected panel provides the account-level management tools.
The exact feature set available to any specific user depends on role permissions, current configuration, app build, and deployment choices. For example, admin accounts may have access to site-wide settings, reseller creation, credit pullback, security configuration, and exports. Resellers may have access only to the devices, credits, DNS profiles, and customers under their own scope. Sub resellers may have narrower controls. Customer-facing app behavior depends on activation status, assigned slot, code validation, remote command state, and app-to-panel communication. We reserve the right to improve, reorganize, or refine these features over time so long as we do not do so in a way that intentionally misrepresents the service.
3. Eligibility and Account Responsibility
You are responsible for ensuring that you are authorized to use the service, to create an account, or to operate a reseller or sub reseller business through the panel. If you create, manage, or use an account, you are responsible for the accuracy of the information you provide and for maintaining the confidentiality of your credentials. This includes username, password, authentication settings, recovery routes, and any support contact details published through the platform. You may not share credentials carelessly, reuse another user’s session intentionally, or allow unauthorized users to operate under your access level.
If you are an administrator, you are also responsible for managing reseller and sub reseller access responsibly. If you are a reseller or sub reseller, you are responsible for the customer devices, credits, DNS settings, and account actions within your scope. Any action performed through your account may be treated as your action unless you can show that credentials were compromised without your fault and reported promptly. Because the platform supports activation, device routing, and account hierarchy, account security is a core operational duty, not a casual preference. We strongly encourage strong passwords, role separation, and two-factor authentication where available.
4. Role-Based Access and Operational Boundaries
The platform uses role boundaries to organize responsibility and reduce conflicts. Admin accounts may manage global settings, plans, credits, resellers, sub resellers, site content, exports, and security features. Resellers may manage only their own customers, plans, devices, DNS profiles, and subordinate accounts where permitted by their plan or credit tier. Sub resellers may have an even smaller scope. These boundaries are part of how the service is delivered. They are not merely visual restrictions. Users must not try to bypass them, interfere with another account’s scope, or obtain information or controls outside their allowed role.
Any attempt to manipulate the panel, hidden routes, signed launch paths, account ownership, or role logic in order to gain unauthorized access may result in suspension, termination, audit review, or legal response where appropriate. This includes abusing exported data, sharing protected access, trying to alter signed flows, automating unauthorized scraping, probing restricted routes, or misrepresenting account ownership. Because the platform is designed around per-device control and per-account business separation, interference with those boundaries threatens not only security but also the reliability of the reseller model itself.
5. Device Registration, Activation, and DNS Assignment
A core function of the service is the registration and control of app installations. When a device launches the application, the panel may receive a generated device ID, an app-level MAC-style identifier, status information, current app settings, and metadata needed to create or update a device record. That record may remain pending until an authorized panel user generates or applies an activation code. Once a device is activated, the panel may assign the correct DNS slot or service path, push supported app settings, update device status to enabled, and control expiry, renewal, reload profile behavior, or suspension over time. Users of the panel acknowledge that this activation and routing model is fundamental to the platform.
Resellers, sub resellers, and administrators are responsible for making correct device assignments. If the wrong DNS slot is assigned, if a remote app command is pushed incorrectly, if an expired device is not renewed, or if a pending device is not approved, the customer experience may be affected. The platform provides the tools to manage those states, but it does not guarantee that every user will configure them correctly. Panel users should review assigned slots, supported STB model choices, media player choices, overlay settings, plan duration, code generation, and activation outcomes carefully. End users should understand that access to content or portal routing depends on panel-side approval, not just on having the application installed.
6. Credits, Plans, Pricing, and Commercial Operation
The panel may support customer pricing, reseller credit packages, commercial plans, renewals, and plan-based device lifecycle handling. Admin users may define plans or reseller packages. Resellers or sub resellers may purchase or consume credits according to the business rules configured by the administrator. Credits may be required for device creation, activation, renewal, or other workflows depending on configuration. Users acknowledge that digital credits, plan entitlements, activation rights, and similar virtual business values are operational instruments within the platform, not cash deposits or stored monetary accounts.
By using the commercial features of the panel, you agree to respect the pricing, package, eligibility, and reseller-tier rules that apply to your role. For example, a reseller may need a minimum number of credits before gaining the option to create a sub reseller. Credits may be deducted when plans are assigned or renewed. Admins may have additional rights such as credit pullback or package definition. It is your responsibility to understand the operational meaning of a plan, a renewal, a credit deduction, and an expiry date before relying on those mechanics in your own business. The platform is designed to support structured commerce, but the responsibility to use it carefully remains with the operator.
7. Acceptable Use and Prohibited Conduct
You may use the platform only for legitimate operational, reseller, support, or administrative purposes connected to the service. You may not use the panel or application to attack the system, probe for vulnerabilities without authorization, exfiltrate data, forge another user’s identity, interfere with account boundaries, overload routes intentionally, distribute malware, manipulate logs, or automate abusive activity. You may not use the site in a way that creates a denial of service, degrades the experience of other panel users, or undermines the activation and routing integrity of the platform. Respectful operation is part of using a shared business tool.
You also may not use the platform to make false claims about affiliation, ownership, or support status. If you operate as a reseller or sub reseller, you must not present yourself as the admin owner unless explicitly authorized to do so. If you expose customer data or route information that your role is not permitted to share, you may be subject to suspension. If you use the support fields, public links, or customer-facing pages in a misleading or fraudulent way, we may remove, restrict, or review that access. These limits exist because the panel is intended to help run a clean business, not to create ambiguity about who is responsible for devices or customer relationships.
8. Application License and Use of the APK
Subject to compliance with these terms, we grant a limited, non-exclusive, revocable right to use the application and associated panel workflow for legitimate operation of the platform. This is not a transfer of ownership. The application, site design, panel logic, business workflow, branding assets, remote command bridge, and user interface elements remain protected by applicable intellectual property and contractual rights. You may use the APK as intended for customer installation, activation, and controlled service access. You may not claim ownership of the underlying platform simply because you have access to it as a reseller or because you distribute the app to your own customer base.
You may not reverse engineer, strip protections from, relabel, resell as your own core product without authorization, expose hidden portal URLs, alter encoded routes, or use the app in a way that undermines the activation or panel model. Custom branding or white-label arrangements, if available through business agreement, do not erase the underlying rights of the platform owner. Attempting to bypass the activation flow, replace protected routes, disrupt gateway logic, tamper with remote command handling, or interfere with app integrity checks may result in immediate termination of access. The same applies to efforts to clone or repurpose the service in a way that breaches these terms or any separate agreement.
9. Availability, Maintenance, and Service Changes
We aim to keep the site, panel, and activation workflows available, but we do not promise uninterrupted access at all times. Maintenance, upgrades, DNS changes, security improvements, hosting issues, third-party outages, and business decisions may all affect availability. Public pages may change. Pricing may be refined. Layouts may be reorganized. Security features may be added or tightened. App behavior may improve over time as new protections or operational enhancements are rolled out. Using the service means accepting that a live platform will evolve, sometimes quickly, especially when the goal is to improve reliability or security.
Where reasonably possible, changes should be made carefully and with attention to current functionality. That said, some fixes or updates may need to be applied urgently, especially if they relate to security or operational failure. Users should keep backups of any exported information they consider important to their own business administration. Admin users are also encouraged to review panel settings, plans, and branding after major updates. The service is intended to be dependable, but dependable does not mean frozen in time. It means we continue to manage the product responsibly while retaining the right to maintain and improve it.
10. Suspensions, Termination, and Enforcement
We reserve the right to suspend, disable, or terminate access to any account, device, reseller relationship, or feature if there is a reasonable belief that the terms have been violated, that the platform is being abused, that another user’s security or operations are being threatened, or that suspension is needed to comply with legal or contractual obligations. Suspension may apply to a single device, a reseller account, a sub reseller account, or a broader portion of the system depending on the issue. Examples include repeated failed login abuse, unauthorized access attempts, non-payment in a commercial arrangement, fraudulent account activity, or deliberate interference with protected flows.
Termination or suspension does not create a duty to continue servicing a user who has materially breached the agreement. In some cases, access may be restored after review, remediation, or clarification. In other cases, termination may be final. The platform owner also retains the right to discontinue certain offerings, retire plans, or change feature availability when needed. These enforcement rights are included because the service is not purely informational. It manages live activation and operational states, and therefore needs practical tools for dealing with misuse. By using the platform, you agree that these enforcement actions may be necessary and appropriate in some circumstances.
11. Disclaimers and Limitation of Liability
The platform is provided on an as-is and as-available basis to the fullest extent permitted by applicable law. We do not guarantee that every panel deployment, DNS endpoint, customer environment, Android device, network path, or third-party service will behave perfectly. We do not guarantee uninterrupted uptime, bug-free operation, complete compatibility with every box or screen, or permanent availability of every route or integration. Panel owners and resellers should test their deployments, review their assignments, and use the available operational controls responsibly. The existence of a feature does not eliminate the need for careful human administration.
To the maximum extent permitted by law, we will not be liable for indirect, incidental, special, consequential, or punitive losses arising from use of the service, including lost business opportunity, lost profits, lost customers, misconfigured DNS routing, missed renewals, third-party outages, or account misuse that resulted from poor credential management by the user. Nothing in this section is meant to excuse deliberate wrongdoing or liability that cannot legally be excluded, but it does mean that a live operational platform cannot carry unlimited responsibility for every downstream outcome created by user decisions, customer behavior, or third-party dependencies.
12. Indemnity, Governing Use, and Contact
You agree to use the service in a way that does not expose the platform owner to avoidable legal, operational, or reputational harm caused by your own misuse, misrepresentation, or unauthorized conduct. If your actions through the panel, public site, support links, device routing workflow, or reseller relationships create claims, losses, or administrative burdens that reasonably flow from your breach of these terms, you may be required to bear responsibility for those consequences to the extent permitted by law. This indemnity concept is not meant to be dramatic. It is simply a recognition that a reseller platform depends on each operator taking responsibility for how they use their scope of control.
These terms should be read in a practical business sense and applied in good faith. If any part is found unenforceable, the remaining provisions should continue to operate as far as possible. If you have questions about these terms, business use of the platform, role permissions, reseller structure, or customer activation workflows, the best route is to contact the support path listed on the site or the owner account support contact made public by the deployment. Continuing to use the site, app, or panel after changes to these terms means you accept the updated version. If you do not accept the updated terms, you should stop using the service.