Last Revised: August 17, 2026
These Terms of Service (“Terms”) govern your access to and use of the Gimbl platform and any related content, features, tools, or services that you order, access, or use (collectively, the “Services”), as made available by Precision Infinity, Inc., a Florida corporation (“Gimbl,” “we,” “us,” or “our”). If you are using the Services on behalf of a company or other legal entity (“Organization”), then (a) “you” includes that Organization, (b) you represent and warrant that you have authority to bind the Organization to these Terms, and (c) the Organization is responsible for all use of the Services under its Account(s).
Please read these Terms carefully as they constitute a legal agreement between you and Gimbl.
By accessing or using the Services, you confirm your agreement to be bound by these Terms and our Privacy Policy, located at https://gimbl.dev/privacy. If you do not agree to these Terms, you may not access or use the Services. These Terms supersede any and all prior agreements or arrangements with you regarding the use of the Services.
When used in these Terms, the following terms shall have the meanings set out below:
Agentic Artificial Intelligence (“AI”)
AI that operates autonomously to carry out multi-step analysis and testing tasks without manual approval at each step.
Artifacts
Diagnostic and testing byproducts generated in the course of providing the Services, such as screenshots, DOM snapshots, metadata, event logs, performance traces, and similar technical records.
Beta Services
Any Services or features identified as alpha, beta, preview, early access, invite-only, or not generally available.
Credits
Any prepaid usage units, quotas, or consumption-based entitlements that may be used to access certain features of the Services.
End-User Data
Anything you input into the Services, including data within an End-User System. It excludes Outputs and Usage Data.
End-User System
Any website, application, repository, or codebase you submit for analysis or testing.
Non-Production Environment
An instance of an End-User System that (a) does not serve active end users, (b) does not contain production data, real personal data, or other data whose loss, alteration, or exposure would cause harm to you or any third party, and (c) is not connected to live external services in a way that could cause real-world consequences unless those connections have been sandboxed, disabled, or otherwise safeguarded. Examples include staging, test, and preview deployments, as well as deployed systems that have not yet launched to real users.
Open-Source Components
Software libraries or code available under open-source licenses (such as MIT, BSD, Apache, or GPL) that we may identify within your End-User System.
Outputs
Reports, findings, and recommendations the Services generate. They are informational only and not professional advice of any kind.
Production Credentials
Credentials that provide access to a production environment serving active end users, to real personal or customer data, or to an account used by an actual person in an End-User System. Credentials for dedicated test accounts on a Non-Production Environment are not Production Credentials. Source-control tokens supplied through designated repository-connection fields are governed by Section 6(d).
Security Emergency
Circumstances in which Gimbl reasonably concludes that a run or an Account is being used without authorization, is harming or likely to harm an End-User System or any third party, is illegal, or presents a security or liability risk.
Services
The Gimbl platform and all related features, tools, and support we make available to you.
Source Code
The code of an End-User System that you choose to share with us for deeper analysis.
Subscription
A recurring paid plan that provides access to the Services for a stated term, which may renew automatically as described in Section 16.
Third-Party AI Providers
The external AI services we use, currently including Anthropic (Claude), OpenAI, Google Gemini, and xAI (Grok).
Third-Party Service Providers
Third-party vendors and infrastructure providers used by Gimbl to host, operate, secure, support, or deliver the Services, including cloud hosting providers, payment processors, analytics providers, communications providers, and other operational service providers.
Usage Data
Technical data about how you use the Services, such as logs and metrics, excluding End-User Data or personal information.
The Services are currently invite-only and in active development. Certain features may be paused, amended, or discontinued at any time without notice. Section 15 sets out the terms applicable to Beta Services.
Gimbl is a software testing and validation platform that combines AI and engineering principles to analyze existing code and applications. An End-User submits a website or application for analysis, and Gimbl produces an Output detailing functionality, scalability, potential security issues, and common risks associated with AI-generated code. The Output summarizes key findings and recommendations. The Services may operate as long-running, autonomous analysis and testing workflows that use project context to identify, prioritize, and explain areas of the End-User System that may require review.
With respect to Source Code and connected repositories, Gimbl operates strictly read-only: it retrieves file listings and file content for analysis only, and will not commit, push, or otherwise modify repository content, write data into your systems, or deploy code.
With respect to a website or application you submit for testing, the Services are designed not to make destructive or lasting changes. By submitting an End-User System and initiating analysis or testing, you authorize the Services to interact with it autonomously, without manual approval at each step; such interaction may include signing in with the test credentials you provide, exercising user workflows, and submitting forms. The Services may interact with an End-User System by sending automated requests, navigating user flows, and performing ongoing or scheduled checks (for example, monitors or “signals”). You acknowledge that such interactions may generate Artifacts and may result in traffic to the End-User System. Section 5 describes the practical consequences in detail. All findings are communicated through Outputs only.
Upon receiving an invitation to Gimbl, you will be prompted to register an account (“Account”). You must be at least 18 years of age (or the age of legal majority in your jurisdiction if different) to obtain an Account. You cannot register for or maintain an Account if you have previously been banned from accessing or using the Services, or if you have breached these Terms at any time.
Account registration requires you to submit certain personal information, such as your name and email address (and, optionally, a phone number). For more information regarding Gimbl’s use of your personal information, please see our Privacy Policy at https://gimbl.dev/privacy. You are responsible for maintaining accurate and up-to-date Account information at all times. You are responsible for all activity that occurs under your Account and must maintain the security and secrecy of your Account credentials. Unless otherwise permitted by Gimbl in writing, you may only possess one Account. If an Account is created using an email address associated with an Organization, or if the Services are purchased on behalf of an Organization, Gimbl may treat that Account as associated with the Organization. The Organization may be responsible for managing access to such Accounts and for all activities conducted through them, subject to the functionality made available by the Services.
In order to submit an End-User System to the Services, you confirm that (with Section 4 governing authorization in detail):
Each time you submit an End-User System or connect a repository, you represent and warrant that you own it or hold permission from its owner, covering all actions the Services will perform: accessing it, signing in, navigating it, submitting data to it, and reading its contents. This representation is made afresh on each submission and applies to every run, every target, and every repository for as long as you use the Services. Any permission relied upon must be current, documented in writing, and granted by a person with authority to give it.
By submitting an End-User System and initiating a run, you authorize Gimbl, including its automated browser, its hosting infrastructure, and the Third-Party AI Providers, to access and interact with that system on your behalf. You agree that this authorization is intended to constitute authorized access under the Computer Fraud and Abuse Act and any similar applicable law, and that you have the authority to grant such access.
Automated testing traffic, including sign-ins, rapid navigation, form submissions, and requests originating from cloud infrastructure, may resemble malicious activity to firewalls, intrusion detection systems, and security personnel. You acknowledge this and agree not to bring any claim against Gimbl arising from access performed as part of a run you authorized, except in cases of Gimbl’s gross negligence or willful misconduct. If your security tooling, or that of your hosting provider, is likely to flag or block automated traffic, you are responsible for allowlisting the Services or notifying the appropriate personnel before initiating a run.
Gimbl may require proof of ownership of, or authorization for, any End-User System or repository at any time, before or during a run. Gimbl may pause or suspend a run pending receipt of such proof, without liability for the resulting delay.
A run covers only the specific End-User System you submitted, and not other systems, other domains, or destinations reached by redirect. The Services are designed not to follow redirects to unverified hosts, and you must not use redirects or similar techniques to bring unauthorized systems within the scope of a run.
Automated testing involves real traffic and real interactions with the End-User System, including signing in, navigating user flows, and submitting forms. Although the Services are designed not to make destructive or lasting changes, it is communicated at the outset that the following may occur during testing:
Authenticated and other interactive testing of a website or application must be directed at a Non-Production Environment, where the effects described above carry no consequences for real users or real data. You should back up any data of value before initiating a run. An environment containing users or data of value should not be submitted for testing.
Certain effects of testing may extend beyond the End-User System itself. Where an End-User System is connected to live external services, an automated run may:
Before submitting an End-User System, you must identify any connection to live external services, including payment processors, transactional email and SMS, webhooks, and notifications to real users, and disable, sandbox, or otherwise safeguard those connections. The Services must not be directed at a live contact form, checkout flow, or notification pipeline connected to real recipients or real payment infrastructure.
The following allocation applies:
You may be required to provide access materials through designated fields, including test account credentials for authenticated testing, request headers or bypass secrets for protected staging environments, and source-control tokens for connected repositories. This Section governs such materials. The prohibition on submitting Production Credentials in Section 8 continues to apply, and nothing in this Section overrides it.
By supplying any credential, header, secret, or token, you represent and warrant that:
You remain responsible for all activity performed by the Services using the access you supplied, and for keeping your own copies of such materials secure.
Where the Services permit you to supply a bypass mechanism, such as a custom request header or an access-protection secret, you may only direct the agent through an access control which you are authorized to bypass. Using the Services to circumvent authentication or access controls on any system you do not control, or are not permitted to bypass, is prohibited, and the general prohibition on circumventing security in Section 12 applies.
A source-control access token supplied through the designated repository-connection fields is permitted notwithstanding that the connected repository may contain production code. Such tokens must be scoped to the minimum access necessary: read-only where the platform supports it, and limited to the specific repository being analyzed.
If you lose the right to use any credential you have supplied, whether through departure from an Organization, withdrawal of authorization, or closure of the underlying account, you must remove it from the Services and discontinue any runs that depend on it. Continued testing using access you no longer legitimately hold is a breach of this Section and of Section 4.
By connecting a repository, you represent and warrant that you have the right to share its entire contents with Gimbl and its service providers, including Third-Party AI Providers, for analysis. This includes third-party code. If a repository contains proprietary code, licensed components, or other material that you are contractually not permitted to disclose to outside services, you must not connect the repository, or must exclude that material before connecting.
Repositories frequently contain embedded credentials, API keys, access tokens, private certificates, and personal data that were not intended to be committed. Connecting a repository transmits its contents through the analysis pipeline, including to Third-Party AI Providers.
Before connecting a repository, you must remove, or rotate so that they no longer function, any live credentials, keys, or secrets embedded in it, and take reasonable steps to remove personal data that does not belong there.
Gimbl is not responsible for secrets, credentials, or personal data left in a connected repository, or for their exposure through the routing described above. Any live secret discovered to have been transmitted should be rotated immediately and treated as compromised.
As reiterated above, nothing in this Section conflicts with the commitments in Section 8(b): Source Code will not be used to train AI models, will be retained only in accordance with Gimbl’s retention policy, and will be treated as confidential in accordance with Section 14.
By using the Services, you confirm that you have the rights to submit your End-User Data and that doing so is not in contravention of any existing laws or agreements. You are solely responsible for the information you submit.
Do not submit Production Credentials. Where the Services request credentials through designated credential fields (for example, to sign in to your End-User System for authenticated testing, to access a protected staging environment, or to connect a source-code repository), supply test credentials for dedicated test accounts on Non-Production Environments wherever possible, and in all cases use credentials scoped to the minimum access necessary. Section 6 governs supplied credentials in detail. Do not submit any data that you are prohibited by law, contract, or policy from disclosing to Gimbl.
Unless expressly authorized by Gimbl in writing, you must also not submit protected health information, payment card data, financial account access credentials, government ID numbers, biometric data, or personal data belonging to children under 13. If Gimbl becomes aware that prohibited or restricted data has been submitted in violation of these Terms, Gimbl may remove, quarantine, or delete that data, suspend related access, and disclose or report the matter to the extent required by applicable law or reasonably necessary to protect the Services, Gimbl, its users, or third parties. You must use reasonable efforts to avoid unnecessary sensitive or regulated data, to minimize the personal data made available to the Services, and to use Non-Production Environments as required by Section 5(b).
If you submit sensitive or restricted data in violation of these Terms, that is your risk, and Gimbl is not liable for any consequences arising therefrom.
If you choose to share Source Code with the Services for further analysis, Gimbl commits to the following: (i) your Source Code will not be used to train any AI model; (ii) it will be accessed, processed, and retained only as reasonably necessary to provide the Services for your project, perform analysis you request, maintain project context, troubleshoot issues, investigate misuse or security concerns, and support the Services; and (iii) it will be treated as confidential in accordance with Section 14 of these Terms. Gimbl may use run logs, diagnostics, Artifacts, and operational telemetry related to Source Code to secure, debug, maintain, and improve the Services, provided that Gimbl will not use your Source Code to train AI models without your explicit consent. Limited copies may persist in encrypted backups for a reasonable period consistent with Gimbl’s backup, security, and retention practices. Section 7 sets out your responsibilities when connecting a repository.
Gimbl will delete or de-identify End-User Data in accordance with its data retention policy as in effect from time to time, except to the extent it retains limited End-User Data, Artifacts, project context, or run history as reasonably necessary to: (i) provide the Services and maintain your Outputs, (ii) support ongoing monitoring or project functionality, (iii) prevent fraud or misuse, (iv) comply with law, or (v) establish, exercise, or defend legal claims. If no specific retention period is stated for a category of data, Gimbl may retain that data for as long as reasonably necessary to provide, secure, support, improve, and document the Services, comply with law, prevent misuse, resolve disputes, and enforce these Terms. Outputs will remain accessible in your Account for the applicable retention period (or until you delete them, if that functionality is made available). You may request deletion of your End-User Data by contacting support. Gimbl may retain de-identified or aggregated Usage Data for an indefinite period.
To the extent End-User Data includes personal data that is subject to applicable privacy laws, you are responsible for determining the purposes and means of processing and for providing required notices and obtaining required rights and consents. Where applicable, Gimbl will process such data only as a service provider or processor on your behalf to provide the Services. If Gimbl offers or requires a data processing addendum (“DPA”), subprocessor list, or similar data-processing terms for business customers, those terms will apply to the extent stated therein.
All rights in and to the End-User Data, End-User System, and Source Code are retained by you. By submitting them to the Services, you grant Gimbl a limited, non-exclusive, non-transferable licence to access and analyze that material solely in order to provide the Services and generate Outputs. This licence terminates upon deletion of your data.
As between you and Gimbl, you retain ownership of End-User Data and the End-User System, and Gimbl (or its licensors) retains ownership of the Services and the Output templates, presentation, and underlying technology used to generate Outputs. Subject to your compliance with these Terms, Gimbl grants you a non-exclusive, worldwide license to use, reproduce, and internally share Outputs for your business or development purposes, including sharing with your contractors and professional advisors who are bound by confidentiality obligations. You may not publicly publish or market Outputs as an endorsement or certification by Gimbl without Gimbl’s prior written consent.
Your End-User Data, End-User Systems, Source Code, and related project context will not be used for any purpose other than providing, securing, supporting, debugging, maintaining, and improving the Services, unless you expressly consent otherwise. They will not be sold, made available to other customers, or used to train generalized AI models. Gimbl will not use customer code or customer project data to train AI models without your explicit consent. Human personnel may access run logs, diagnostics, Artifacts, and project context solely as reasonably necessary to provide support, troubleshoot issues, investigate misuse, improve service reliability, and develop or improve the Services. Gimbl may also use automated operational systems to host, secure, monitor, debug, and improve the reliability and performance of the Services, provided that such use does not train AI models on your customer code or customer project data without your explicit consent. Where feasible, Gimbl will use aggregated, de-identified, or operational telemetry for generalized product improvement.
Subject to your compliance with these Terms, Gimbl grants you a limited, personal, non-exclusive, non-sublicensable, revocable, and non-transferable licence to access and use the Services solely for your internal business or development purposes. Any rights not expressly granted herein are reserved by Gimbl. Neither these Terms nor your use of the Services convey or grant to you any rights of ownership in or to the Services or any underlying technology.
You may not: (i) copy, resell, distribute, sublicense, or otherwise exploit the Services or any Gimbl materials; (ii) reverse engineer, decompile, or otherwise attempt to extract the underlying technology or architecture of the Services; (iii) bypass or circumvent any security controls or access restrictions; (iv) use the Services to develop a competing product or service; or (v) remove any ownership or proprietary notices from the Services or Outputs.
Where Gimbl identifies Open-Source Components within your End-User System, that analysis is informational only and does not constitute legal advice. You are responsible for ensuring that your use of any open-source software complies with all applicable licence terms.
Any suggestions or feedback you provide are voluntary and non-confidential, and you grant Gimbl a perpetual, irrevocable, worldwide, royalty-free license to use, disclose, reproduce, modify, and otherwise exploit that feedback without restriction or compensation.
In the provision of the Services, Gimbl currently utilizes the Third-Party AI Providers. Gimbl may add or change providers over time, and this list will be updated accordingly. You acknowledge and accept that certain End-User Data may be processed by a Third-Party AI Provider in the course of delivering the Services. Third-Party AI Providers operate under their own terms and privacy practices, and Gimbl’s use of them is subject to those providers’ policies and any applicable subprocessor terms described in our Privacy Policy and/or DPA (if applicable). Gimbl does not control Third-Party AI Providers and cannot guarantee their availability or accuracy. You acknowledge and accept that Gimbl is not liable for any failures or errors on the part of any Third-Party AI Provider. The Services also depend on Third-Party Service Providers, including cloud hosting and infrastructure providers. These providers are not Third-Party AI Providers unless they provide AI model services, but their availability, performance, security, and service changes may affect the Services.
Certain features of the Services utilize Agentic AI. Agentic AI autonomously performs multi-step analysis and testing, taking only the categories of actions described in Section 3(b) within the End-User System you submit for testing. Although the Services are designed not to make destructive or lasting changes, Agentic AI may create test data, trigger side effects, consume resources, or otherwise affect an End-User System as described in Section 5. The Output limitations set out in Section 11 remain applicable to all Outputs generated through Agentic AI.
Gimbl does not knowingly use AI models or services developed or operated by entities based in or subject to the jurisdiction of the People’s Republic of China to process End-User Data. Gimbl may update its providers and subprocessors over time; any material changes will be reflected through updates to these Terms, our Privacy Policy, and/or applicable subprocessor lists, as appropriate.
All Outputs produced by the Services are strictly informational. They do not constitute legal, engineering, security, or compliance advice and should not be treated as certifications or audit opinions. Gimbl cannot guarantee the completeness or accuracy of any Output, as Outputs are produced in part by Third-Party AI Providers and may therefore contain errors or omissions, including false positives (reported issues that are not real) and false negatives (real issues that go unreported). Gimbl is not liable for either. All Outputs should be independently verified by a qualified expert in the relevant field before being relied upon, and you must apply qualified human review before acting on any finding.
Gimbl is not liable for any loss or damage incurred as a result of relying on Outputs without independent verification.
A clean Output does not necessarily mean that a system is without fault. The absence of reported issues is not a representation that the system is secure, scalable, or fault-free. The Services are a tool to assist in identifying potential issues but are not a substitute for professional review or independent audit. For clarity, the Services are not a penetration testing service, bug bounty program, or formal security audit, and do not provide any certification of security posture or compliance.
The Services must be used in compliance with applicable law and in accordance with these Terms. Without limiting the foregoing, you may not, and may not permit any third party to:
Because Outputs may enumerate potential security issues in a live system, you must also protect the confidentiality and security of your Outputs and restrict access to them as you would any sensitive security material.
Gimbl may investigate suspected violations of this Section and may suspend, terminate, block, remove, or report related Accounts, End-User Systems, End-User Data, or activity to the extent reasonably necessary to enforce these Terms or comply with applicable law.
Where a Security Emergency arises, Gimbl may immediately throttle, pause, deprioritize, suspend, or terminate the affected run or Account, without prior notice and without liability to you or any third party for doing so. The exercise of these controls does not constitute a breach of these Terms. Where practical, Gimbl will inform you of the action taken and the reasons for it.
Gimbl controls the pacing of its own testing, including crawl rates, concurrency, and request frequency, and may set, publish, change, and enforce usage limits (including limits on targets, runs, pages, frequency, and concurrent runs against the same target) at any time, including limits designed to protect fragile targets. Nothing in these Terms obligates Gimbl to run tests at any particular speed, volume, or intensity against any target, and no configuration you select can require Gimbl to exceed limits it has set.
The Services exist to test your systems, not Gimbl’s. You may not use the Services, or any other tool, to probe, scan, load-test, penetration-test, or otherwise test the security or performance of the Gimbl platform or its infrastructure, or circumvent its technical limits, without Gimbl’s prior written consent.
If you discover a security vulnerability in the Services, sign in to your Gimbl Account and report it privately through the in-platform Request Support option, allowing Gimbl a reasonable opportunity to remediate it. You must not exploit the vulnerability, use it to access any data, or disclose it publicly before remediation. Gimbl will not pursue claims in respect of good-faith reports made in compliance with this paragraph.
Do not submit any End-User System or page that you know or suspect contains malicious content. You represent and warrant that no End-User System you submit is designed to attack, exploit, or compromise Gimbl’s browser, infrastructure, or providers. If hostile content is detected during a run, Gimbl may abort or suspend the run immediately under (a). Submitting such a target is a material breach of these Terms and of Section 12.
Both parties undertake to keep each other’s confidential information private. For purposes of these Terms, End-User Data, Source Code, non-public Artifacts, and non-public Outputs are your confidential information, subject to Gimbl’s rights to process and use them as expressly permitted by these Terms. Confidential information may be shared with employees, contractors, or advisors where operationally necessary, provided that equivalent confidentiality obligations are in place. These obligations do not apply to information that is in the public domain, was already known to the receiving party without restriction, or was independently developed without reference to the other party’s confidential information. Where disclosure is legally required, both parties undertake to provide notice where possible and to limit disclosure to what is strictly required.
Gimbl has implemented reasonable security measures to protect End-User Data. However, no system is entirely secure and Gimbl cannot guarantee absolute security. You remain responsible for maintaining the security of your Account and ensuring that your End-User System does not contain sensitive data. Should Gimbl determine that a security incident materially affecting your End-User Data has occurred, Gimbl will notify you without undue delay, consistent with applicable law and its incident response procedures. If either party breaches this Section, the non-breaching party may seek injunctive relief without the requirement of posting bond.
The Services are currently offered on an invite-only, early access basis. Beta Services are provided “as is,” without service level commitments, uptime guarantees, support obligations, or warranties or indemnities beyond those expressly stated in these Terms. Features may be modified, suspended, or discontinued at any time, with or without notice, and the pacing, limits, and behavior of the testing engine may change between runs.
For any free access, Gimbl makes no commitment to data retention or continuity, and you should download any Outputs you wish to retain. Gimbl may end the early access program, transition it to paid plans, or discontinue the Services in their entirety, at any time.
Certain features of the Services require payment, which may be offered via Subscription plans, Credits, or both. Your plan details (including pricing, included usage, and renewal term) will be presented at checkout or in an order page within the Services.
Subscriptions renew automatically at the end of each billing period unless you cancel before the renewal date through your Account settings or another cancellation method we make available. If you cancel, you will continue to have access through the end of your then-current billing period, and your Subscription will not renew. We do not provide refunds or credits for partial billing periods except where required by applicable law or expressly stated at the time of purchase.
You authorize Gimbl (and our payment processors) to charge your provided payment method for recurring Subscription fees, usage-based fees, Credits, applicable taxes, and other charges you incur in connection with the Services. You are responsible for maintaining current payment information.
Fees are exclusive of taxes unless stated otherwise. You are responsible for all applicable taxes, duties, and similar governmental assessments, except for taxes on Gimbl’s net income.
Credits, if offered, are usage-based entitlements that may be used to access or consume specified Services, features, runs, signals, AI usage, or other functionality as described at purchase or in the Services. Credits have no cash value, are non-transferable, and are not redeemable for cash. Credits may be included with a Subscription, purchased separately, or granted on a promotional or beta basis. Gimbl may establish expiration dates, rollover rules, usage priority, and consumption rates for Credits, which will be disclosed at purchase or in the Services. Unless otherwise stated or required by law, unused Credits expire at the end of the applicable billing period or expiration date and are not refundable.
We may change fees and pricing at any time. For active Subscriptions, we will provide notice of material price increases in advance, and the change will take effect at the next renewal unless you cancel prior to renewal.
If you believe you were billed in error, you must notify us in writing within thirty (30) days of the charge. Unjustified chargebacks may result in suspension or termination of your Account.
During invite-only or Beta Services periods, some features may be provided free of charge or at promotional rates, and Gimbl may modify or discontinue such offers at any time.
You may close your Account by contacting support or, if made available, through your Account settings. No fees paid will be refunded upon closure.
Gimbl may suspend or terminate your access to the Services immediately where: (i) you have violated these Terms; (ii) your use poses a risk to Gimbl, other End-Users, or third parties; (iii) applicable fees remain unpaid; or (iv) Gimbl is required to do so by law. Gimbl may also terminate access for convenience on reasonable notice. Section 13 separately governs immediate operational action in a Security Emergency.
Upon closure of your Account: (i) your access to the Services ends immediately; (ii) your End User Data and Source Code will be handled in accordance with the retention, deletion, and de-identification provisions in Section 8; (iii) your Outputs will no longer be accessible, and you are responsible for downloading anything you wish to retain beforehand; and (iv) any amounts owing to Gimbl remain due. Sections 4 through 14, 16 (as to accrued amounts), 18 through 21, and 23 survive termination.
The Services and all Outputs are provided “as is” and “as available.” Gimbl disclaims all representations and warranties, express, implied, or statutory, not expressly set out in these Terms, including the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. Gimbl does not warrant that the Services will be uninterrupted or error-free, or that Outputs will be accurate, complete, or suitable for any particular purpose.
Gimbl is not responsible for the availability or performance of any Third-Party AI Provider or Third-Party Service Provider. Gimbl’s core functions depend on third-party AI and cloud infrastructure; delays, interruptions, degraded output, model changes or deprecations, security failures, or a provider suspending or terminating Gimbl’s access are not a breach of these Terms by Gimbl, and Gimbl may suspend or modify affected features when an upstream provider’s actions require it, without liability. During the invite-only early access period, no service level commitments apply. The entire risk arising out of your use of the Services remains with you, to the maximum extent permitted by applicable law.
Gimbl shall not be liable for any indirect, incidental, special, exemplary, punitive, or consequential damages, including lost profits, lost data, or business interruption, arising out of or in connection with your use of or inability to use the Services or any Outputs, regardless of whether Gimbl has been advised of the possibility of such damages.
Gimbl’s total liability for any claim arising out of or relating to these Terms or the Services shall not exceed: (a) where you have paid fees, the total amount paid by you to Gimbl in the twelve (12) months preceding the event giving rise to the claim; or (b) where no fees have been paid, one hundred U.S. dollars (US$100).
The above limitations do not apply to: (i) your indemnification obligations under Section 20; (ii) breaches of the sensitive data prohibition in Section 8; (iii) breaches of Section 12; (iv) breaches of confidentiality under Section 14; or (v) liability that cannot be excluded or limited under applicable law.
For clarity, the caps above limit Gimbl’s liability to you. They do not limit your liability to Gimbl or to third parties arising from your breach of Sections 4 through 7, Section 12, or Section 13(e), or from your indemnification obligations.
You agree to indemnify, hold harmless, and defend Gimbl and its affiliates, officers, directors, employees, and agents from and against any claim, action, investigation, loss, damage, liability, cost, or expense (including reasonable attorneys’ fees) arising out of or relating to:
Gimbl will notify you promptly of any indemnifiable claim. You may assume control of the defense of any such claim, provided that you may not settle any claim that imposes obligations or liability on Gimbl without Gimbl’s prior written consent.
These Terms and any disputes arising hereunder shall be governed by and construed in accordance with the laws of the State of Florida, without regard to its conflict of law principles.
In the event of a dispute, the parties agree to first attempt resolution in good faith by way of written notice setting out the nature of the dispute and the relief sought. If the dispute is not resolved within thirty (30) days of such notice, either party may proceed to arbitration. This does not prevent either party from seeking emergency injunctive relief where necessary.
Any unresolved dispute shall be referred to and finally determined by binding arbitration in the State of Florida, administered under the rules of the American Arbitration Association (“AAA”) by a single arbitrator. The arbitrator’s decision shall be final and binding and may be entered as a judgment in any court of competent jurisdiction. Either party may bring an individual action in small claims court in lieu of arbitration, so long as the action remains in small claims court and proceeds only on an individual basis.
If you are an individual consumer, you may opt out of arbitration and the class action waiver by sending written notice to Gimbl at the address in Section 23(h) within thirty (30) days of first accepting these Terms. Your notice must include your name, email address, and a clear statement that you wish to opt out of arbitration.
All disputes must be brought on an individual basis. You waive any right to participate in a class action or class-wide arbitration against Gimbl.
Gimbl may update these Terms from time to time. If we make material changes, we will provide notice by email, through the Services, by requiring re-acceptance within the Services, or by other reasonable means at least fourteen (14) days before the changes take effect, unless a shorter period is required for legal, security, or operational reasons. Non-material changes may take effect upon posting or as otherwise indicated.
The “Last Revised” date at the top of these Terms will reflect the effective date of the most recent update. By continuing to access or use the Services after updated Terms take effect, or by clicking to accept or re-accept the updated Terms within the Services, you agree to be bound by the revised Terms. If you do not agree to the updated Terms, you must stop using the Services before the updated Terms take effect. Gimbl may require you to accept or re-accept the then-current Terms before continuing to access the Services. If you do not accept the updated Terms when prompted, you may not continue using the Services.
These Terms, together with the Gimbl Privacy Policy, constitute the entire agreement between you and Gimbl with respect to the Services and supersede all prior agreements and understandings, whether written or oral, relating to the subject matter hereof.
If any provision of these Terms is held to be invalid or unenforceable, that provision shall be modified to the minimum extent necessary to make it enforceable, and the remaining provisions shall continue in full force and effect. Gimbl’s failure to enforce any right or provision shall not constitute a waiver of that right or provision.
You may not assign or transfer your rights or obligations under these Terms without Gimbl’s prior written consent. Gimbl may assign these Terms freely, including in connection with a merger, acquisition, or sale of assets.
Gimbl shall not be liable for any delay or failure to perform its obligations under these Terms to the extent caused by circumstances beyond its reasonable control, including natural disasters, pandemics, government action, or third-party service outages.
The parties are independent contractors. Nothing in these Terms creates a partnership, joint venture, employment, or agency relationship between you and Gimbl.
You agree to comply with all applicable United States export control laws and sanctions regulations, including those administered by OFAC. You confirm that you are not located in or acting on behalf of any person or entity in a sanctioned country or territory.
Upon logging in to the Services, and at other points in the user workflow as determined by Gimbl, you may be presented with compliance reminders or acknowledgments regarding Gimbl’s key restrictions, including the prohibition on the submission of Production Credentials, sensitive data, and unauthorized systems. Such reminders do not modify or replace these Terms.
All legal notices to Gimbl under these Terms must be provided in writing and delivered to:
Precision Infinity, Inc.
3801 Avalon Park East Blvd, Suite 320
Orlando, Florida 32828, United States
Gimbl will contact you via your registered email address or through an in-platform notification. For customer support inquiries (not legal notices), sign in to your Gimbl Account and submit a request through the in-platform Request Support option.
Last Revised: August 17, 2026