Terms of Service

Notice — Business Product, Not a Consumer Product: Kubian Integrity / Kubian, operated by Static Labs LLC, is not a consumer-facing product and should not be purchased unless needed. Kubian Integrity is a B2B / B2S / B2D offering (Business-to-Business, Business-to-Studio, Business-to-Developer), designed for games and applications looking for a proven security solution. If you are an individual end user rather than a business, studio, or developer integrating Kubian into a game or application, this product is not intended for you.

1. Acceptance of Terms

By registering, accessing, or using the Kubian platform and related APIs provided by Static Labs LLC, you agree to these Terms of Service. If you do not agree with these terms, do not use our platform.

2. Corporate Identity & Legal Entity

Kubian is a software platform and service operated exclusively by Static Labs LLC and is not a standalone corporation, partnership, or independent legal entity. All platform features, subscriptions, payments, documentation, APIs, and these Terms of Service bind you directly to Static Labs LLC.

3. Developer Conduct & Acceptable Use

Kubian is an anti-cheat and platform integrity service designed to safeguard applications. You agree to use Kubian exclusively for lawful security purposes. You agree not to attempt to reverse engineer, disrupt, or exploit the Kubian security infrastructure or third-party client integrations.

4. Reverse Engineering & Security Research

Static Labs LLC as Contractual Security Contact: Static Labs LLC is the principal contractual entity for Kubian and is the primary point of contact for authorized testing, security research, vulnerability disclosure, and other technical evaluation of Kubian. Where a party intends to conduct a thorough or dedicated security assessment of Kubian itself, including reverse engineering, decompilation, disassembly, binary analysis, API analysis, or analysis of Kubian's security mechanisms, that testing must be authorized by Static Labs LLC in writing and must comply with any scope, rules, and time limits communicated by Static Labs LLC.

Authorized Testing of Live Production Games: Reverse engineering or security testing of Kubian and/or an underlying game or application used in a live production environment may be permitted where the testing is conducted with the knowledge and authorization of the developers or operators of the applicable live production game or application. Such authorization does not, by itself, authorize access to or testing of Kubian's internal systems outside the approved scope. Researchers must remain within the permissions and technical scope granted by the applicable game developer or operator and must not intentionally cause disruption, unauthorized access, data loss, service degradation, or other harm.

Game Studio Security Testing: A game studio or authorized developer may probe, test, analyze, and evaluate Kubian as it relates to the studio's own game or application for the purpose of identifying security issues, vulnerabilities, compatibility problems, or other defects. Authorized findings may be reported directly to Kubian or to the Static Labs (LLC) Internal Development Team (SLIDT) for investigation and remediation. Such testing must remain limited to systems, applications, accounts, environments, and data for which the reporting party has authorization to test.

Coordinated Vulnerability Disclosure: Security researchers and authorized developers should promptly report suspected vulnerabilities, exploits, proof-of-concept material, and material security findings to Static Labs LLC through an authorized reporting channel. Unless otherwise authorized in writing, researchers must not publicly disclose, distribute, sell, or intentionally provide exploit material to unauthorized parties before Static Labs LLC has had a reasonable opportunity to investigate and address the issue.

Scope, Authorization & Expiration: Any authorization from Static Labs LLC, a game developer, or another authorized system owner is limited to the specific systems, applications, accounts, environments, purposes, and duration for which permission was granted. Authorization may be conditioned on additional written requirements. When an authorization expires or is revoked, all testing activities covered solely by that authorization must cease promptly.

Unauthorized Activity & Responsibility: Nothing in this Section authorizes malicious activity, unauthorized access, intentional service disruption, theft or destruction of data, deployment of malware, or attacks against systems outside the approved scope. You are responsible for your own conduct and for any unauthorized activity that you knowingly undertake, direct, materially assist, or facilitate, to the extent permitted by applicable law. Nothing in these Terms creates liability for conduct or damages that are not legally attributable to you.

Protective Suspension & Security Enforcement: Static Labs LLC, including its Static Labs (LLC) Internal Development Team ("SLIDT"), may temporarily restrict, suspend, disable, or terminate access to Kubian, Kubian Global Network Security ("KGNS"), Kubian Integrity, associated APIs, developer dashboards, protected environments, or other Kubian-controlled systems when Static Labs LLC reasonably determines that such action is necessary to protect the security, integrity, availability, or lawful operation of the service, its customers, integrated applications, or other users.

Where reasonably necessary to prevent ongoing or reasonably suspected abuse, exploitation, circumvention, unauthorized testing, fraud, security compromise, or other material risk, Static Labs LLC may impose a security restriction on an account, project, device, application identity, credential, integration, or other technical identifier associated with the activity. Such restrictions may remain in effect for as long as Static Labs LLC reasonably determines that the underlying security risk continues, including indefinitely where the circumstances reasonably warrant continued restriction.

A restriction under this Section may prevent or limit access to Kubian or participation in applications that use Kubian-controlled integrity or security services. Static Labs LLC does not guarantee that a restricted account, device, application, integration, or other identifier will be restored, reinstated, or permitted to access the service in the future. Static Labs LLC may consider the nature and severity of the conduct, the likelihood of recurrence, the security impact, prior enforcement history, and other reasonably relevant circumstances when determining the scope and duration of a restriction.

Liability Limitations for Security Enforcement: To the maximum extent permitted by applicable law, Static Labs LLC is not responsible for losses, disruption, access restrictions, compatibility issues, or other consequences resulting from a good-faith security restriction, suspension, investigation, or enforcement action taken under these Terms, including where the action is based on reasonably suspected security abuse or where the restriction is later determined to have been unnecessary. Nothing in this paragraph excludes liability that cannot lawfully be excluded or limited.

5. Service Tiers & Managed Subscriptions

Kubian operates on a paid tier model:

Subscriptions and project onboarding are managed directly via ticket requests in our official Discord server.

Project Scoping & Application Certificate Locking: Each active subscription seat is strictly tied to a single, unique application identity (Package Name and Application SHA-256 certificate hash). Upon initial registration or uploaded binary binding, the project certificate is permanently locked and cannot be swapped, transferred, or re-assigned to a different game or application title. Managing multiple applications or changing target titles requires provisioning an additional subscription seat.

Project Revisioning: Project Revisioning is mandatory when a Developer intends to move an active subscription seat from an existing game or application to a completely different game or application title. The determination is based on the underlying application itself, rather than solely on its package name, signing certificate, app store listing, or other application-store information.

New Application Title (Mandatory Project Revisioning): If the Developer is moving their subscription seat to a completely different game or application, a formal Project-Revisioning Request must be submitted to and verified by Kubian staff before the subscription seat may be rebound to the new title. Upon verified processing, all existing project keys, hardware attestation records, logs, and associated project metadata for the prior application will be purged from active systems and unavailable through routine recovery, subject to the limited retention exceptions described in Section 7 of these Terms and Privacy Policy Sections 6 and 9. The subscription seat will then be unlocked to allow binding to the new application.

App Store Migrations & Certificate Swaps (Same Application): Project Revisioning is not required when the Developer is continuing to operate the same game or application but is relocating it to a different app store, publishing the same game under a new store page, or changing/swapping the signing certificate used for the same game or application. These changes do not constitute a new application title solely because the package name, certificate, store listing, or other app-store information has changed.

For an App Store Migration or Certificate Swap involving the same underlying game or application, project data is not deleted, purged, or reset. Existing project analytics, historical settings, logs, hardware attestation records, project metadata, and other applicable project data remain intact. Only the stored application-specific APK binary data and application identity information required to support the new store listing or certificate binding may be purged, replaced, or updated. This limited update is performed solely to allow the same existing game or application to be rebound to its new app-store or certificate information.

If a requested change is determined by Kubian staff to constitute a move to a genuinely different game or application, the change will instead be treated as a New Application Title and full Project Revisioning will be required.

Self-service project resets within the dashboard are not supported.

6. Service Availability & Limitations

While we strive for high availability and continuous security protection, Kubian is provided on an "as is" and "as available" basis. Security signals and attestation results are designed to assist developers in protecting their software; developers remain responsible for their overall application security architecture.

7. Account & Project Termination

We reserve the right to suspend or terminate service for projects or accounts that engage in infrastructure abuse, unpaid balances past due, or intentional misuse of the API.

24-Hour Data Retention & Reinstatement Window (Manual Cancellation / Deletion / Stop Only): When you manually cancel your subscription, delete your project, or stop your project (each subscription seat is tied to a single project), your project data is not deleted immediately. Instead, all associated project data — including project keys, IDs, settings, logs, hardware attestation records, and metadata — is retained in active systems for a 24-hour (1 calendar day) grace period measured from the moment of your manual cancellation, deletion, or stop. This window exists so developers can keep their project data and reinstate a manually cancelled, deleted, or stopped application if they act within the time window.

Scope limitation — manual actions only: The 24-hour reinstatement window applies only where you manually deleted, cancelled, or stopped your project through your own action (including a manual project deletion, a manual subscription cancellation, or a manual project stop). It does not apply to automatic termination caused by missing payment due dates or unpaid balances past due (see Section 9), nor to suspensions or terminations for infrastructure abuse, security enforcement under Section 4, or intentional misuse of the API. Automatically terminated projects are not granted a reinstatement window.

During the 24-hour window the manually deleted project remains visible in your dashboard in a greyed-out, read-only state. Opening it shows the project dashboard greyed out with a live countdown timer and a Reinstate Project button, alongside a Back to Dashboard button that returns you to the home screen at any time. Reinstating within the window fully restores the project and all of its data with no loss. Deleting a project returns you to the home screen; the greyed-out entry can be re-opened at any time before expiry.

Automatic & Immediate Purge After 24 Hours: Once the 24-hour window has passed, all associated project data (including project keys, IDs, settings, logs, and metadata) is immediately and permanently purged from active systems and routine recovery via standard systems is not possible, except for the limited records Kubian must retain as described in Privacy Policy Sections 3, 6, and 9 (active restriction enforcement, security investigations, fraud prevention, and legal compliance), which are held in isolated security repositories and are not restored to active use.

Immediate Deletion on Request (Waiver of the 24-Hour Window): As an alternative to the standard 24-hour process above, you may elect to delete your project immediately through the dashboard's Delete Immediately option (available in the Delete section and on the pending-deletion banner). Choosing immediate deletion explicitly waives the 24-hour reinstatement window for that project: the project and all associated data — including project keys, IDs, settings, logs, hardware attestation records, and metadata — are immediately and permanently purged at the moment you confirm, with no countdown, no reinstatement, and no recovery of any kind. This action is irreversible. The limited records described in Privacy Policy Sections 3, 6, and 9 are unaffected and remain retained as stated there.

8. DMCA & Intellectual Property

For copyright claims or intellectual property notices, please refer to our dedicated DMCA Policy. Formal notices sent to [email protected] are reviewed within 1-2 weeks (7-14 business days).

9. Billing, Payments & Service Suspension

Subscriptions are billed monthly on a recurring basis. Account management and billing requests are handled via our official support channels and Discord ticket system.

Grace Period & Payment Failures: If a subscription renewal payment fails or is missed, a seven (7) calendar day grace period will automatically begin. Your Kubian API access and security protection will remain fully active during this 7-day window to allow time to update payment details.

Late Penalties & Service Suspension: If an account remains past due after the 7-day grace period:

Project Termination for Non-Payment (No Reinstatement Window): If an outstanding balance is not paid within fourteen (14) calendar days of the original due date, the associated project will be automatically terminated for missing the payment due date. Automatic termination for non-payment is final and immediate: all project keys, hardware attestation records, logs, and metadata are immediately and permanently purged from active systems at the moment of termination, with no 24-hour reinstatement window and no reinstatement available. The 24-hour reinstatement window described in Section 7 applies only to manual deletions, cancellations, or stops initiated by you, and does not apply to automatic termination caused by missing payment due dates. A terminated-for-non-payment project cannot be restored; continued use requires provisioning a new subscription seat.

Extended Payment Date Change Fee & 2-Cycle Settlement Period: If you wish to change your recurring payment due day (for example, moving your billing date from the 21st to the 27th), a flat $3.00 extended / retracted payment fee applies per change. The fee is identical whether the date is extended forward or retracted backward — e.g., changing from the 21st to the 27th incurs a flat $3.00 fee to extend the payment date, which is added to that month's invoice (e.g., a Kubian Max subscription bills $83.00 for the month in which the change is made). Each additional date-change request incurs a separate $3.00 fee, and the fee is non-refundable.

Change Frequency Limit (2 Monthly Billing Cycles): A payment due day may only be changed after the current payment day has settled for two (2) full monthly billing cycles (2 months) following the most recent change. For example, if you change your payment day from the 7th to the 19th and pay the $3.00 fee for that initial change, you cannot change the payment day again until 2 months / 2 monthly billing cycles have passed since that change. Requests submitted inside the settlement period will be rejected until the period elapses. This limit exists to prevent developers from repeatedly shifting the payment day and racking up unpaid or overlapping payment obligations. The new due day takes effect for the next billing cycle once the fee is settled.

Refund Policy: Refund requests are subject to the following limits:

10. Limitation of Liability & Warranty Disclaimer

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, KUBIAN AND ALL RELATED SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, OR THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR FREE FROM VULNERABILITIES.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, STATIC LABS LLC, ITS OFFICERS, DIRECTORS, EMPLOYEES, CONTRACTORS, AGENTS, AND SERVICE PROVIDERS SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS OPPORTUNITY, DATA, APPLICATION AVAILABILITY, IN-GAME ECONOMY, VIRTUAL ITEMS, PLAYER DATA, OR APPLICATION INTEGRITY, ARISING OUT OF OR RELATING TO THESE TERMS, THE KUBIAN SERVICE, SECURITY ENFORCEMENT ACTIONS, SERVICE INTERRUPTION, SECURITY RESEARCH, TESTING, OR THE USE OR INABILITY TO USE THE SERVICE, EVEN IF STATIC LABS LLC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, STATIC LABS LLC'S TOTAL AGGREGATE LIABILITY FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THESE TERMS OR THE KUBIAN SERVICE SHALL NOT EXCEED THE GREATER OF (A) THE TOTAL FEES ACTUALLY PAID BY YOU TO STATIC LABS LLC FOR THE KUBIAN SERVICE DURING THE ONE (1) MONTH IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM, OR (B) THE MINIMUM AMOUNT REQUIRED BY APPLICABLE LAW.

THE LIMITATIONS AND EXCLUSIONS IN THIS SECTION APPLY REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, STATUTE, OR OTHERWISE, AND APPLY EVEN IF ANY LIMITED REMEDY PROVIDED UNDER THESE TERMS FAILS OF ITS ESSENTIAL PURPOSE.

NOTHING IN THESE TERMS EXCLUDES OR LIMITS LIABILITY TO THE EXTENT THAT SUCH LIABILITY CANNOT LAWFULLY BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW.

YOU ACKNOWLEDGE THAT KUBIAN IS A SECURITY AND INTEGRITY SERVICE AND IS NOT A GUARANTEE THAT AN APPLICATION, GAME, DEVICE, ACCOUNT, OR SYSTEM WILL BE FREE FROM CHEATING, EXPLOITATION, COMPROMISE, UNAUTHORIZED ACCESS, OR OTHER SECURITY INCIDENTS. YOU REMAIN RESPONSIBLE FOR MAINTAINING APPROPRIATE BACKUPS, SECURITY CONTROLS, ACCESS CONTROLS, AND OTHER SAFEGUARDS FOR YOUR APPLICATION, SYSTEMS, AND DATA.

11. Governing Law & Jurisdiction

These Terms of Service and any dispute or claim arising out of or in connection with them shall be governed by and construed in accordance with the laws of the State of Oregon, United States, without giving effect to any choice or conflict of law provisions. You agree to submit to the exclusive personal jurisdiction of the state and federal courts located within Oregon for the resolution of any legal proceedings arising under these Terms.

12. Modifications to Terms

Kubian reserves the right to modify or update these Terms of Service at any time. Changes will become effective immediately upon posting to our platform. Your continued access to or use of Kubian services, SDKs, or APIs after such changes are posted constitutes your explicit acceptance of the revised Terms.

13. Survival Clause

Any provisions of these Terms of Service which by their nature should survive termination or expiration of your access to the service shall survive, including but not limited to Section 3 (Developer Conduct & Acceptable Use), Section 4 (Reverse Engineering & Security Research Restrictions), Section 8 (DMCA & Intellectual Property), Section 10 (Limitation of Liability & Warranty Disclaimer), Section 11 (Governing Law & Jurisdiction), Section 14 (Data Protection Roles: Data Collector & Data Processor), and any accrued payment or indemnification obligations.

14. Data Protection Roles: Data Collector & Data Processor

You act solely as the authoritative Data Collector. By integrating Kubian into your game or application, you — the game studio, developer, or buyer — are the authoritative Data Collector for all data collected while your game or application is running. Kubian, operated by Static Labs LLC, acts solely as the authoritative Data Processor: we only process the data provided to us, which in most cases requires you to initialize Kubian's system to collect and process data upon request.

In practical terms: Kubian will not, and will never, act on, collect, or store data without explicit code execution from you, the Data Collector. Our internal systems will never collect data automatically until instructed by your application code. Once you execute our code, you remain the authorized authoritative Data Collector for all data collected while the game or application is running.

App-scoped identifiers; no cross-application tracking. All device identifiers processed by Kubian (including ANDROID_ID and the Widevine MediaDrm device ID) are app-scoped: the same physical device presents different values in different applications, and there is no universal device identifier. Kubian therefore cannot identify a physical device across different games, and centralized cross-application data deletion has been discontinued.

Your deletion obligations. As the authoritative Data Collector, you are fully responsible for end-user data deletion for your application, including maintaining a proper data-deletion system with adequate guardrails and notifying Kubian / Static Labs LLC about end-user data deletion requests — for example by calling the automated developer API at POST https://api.kubian.app/privacy/admin/enduser-deletion. A deletion request you forward is honored for your application only; it cannot reach data the same device generated in any other application. Records inactive in your application for sixty (60) days are automatically anonymized as described in the Privacy Policy. See the Privacy Policy (Sections 0, 3, 6, 9, and 10) for the full deletion, retention, and anonymization terms, which are incorporated here by reference.



© 2026 Static Labs LLC. All rights reserved.  ·  Oregon, USA

Return to Dashboard Privacy Policy End-User Privacy Terms of Service DMCA Copyright Policy