Terms of Use
Last updated: November 19, 2026
These Terms of Use (the “Terms”) govern access to and use of the websites, software, hosted services, cloud execution environments, browser and computer-use agents, APIs, integrations, hosted cloud computers and persistent workspaces (including “Simular Box” or “Box”), remote desktop and shell functionality, Model Context Protocol (“MCP”) connections, and related services made available by Simular, Inc. (“Simular,” “we,” “us,” or “our”) (collectively, the “Services”).
By creating an account, clicking to accept these Terms, or accessing or using the Services, you agree to these Terms. If you use the Services on behalf of an employer or other organization, you represent that you have authority to bind that organization, and “Customer” and “you” refer to that organization. Otherwise, “Customer” and “you” refer to you individually.
1. Eligibility and Accounts
You must be at least 18 years old and legally capable of entering into a binding agreement. You are responsible for the accuracy of account information, maintaining the confidentiality of credentials, and all activity occurring through your account or Authorized Users. You must promptly notify Simular of suspected unauthorized access.
If Customer permits employees, contractors, or other personnel to access the Services (“Authorized Users”), Customer is responsible for their compliance with these Terms and for ensuring that each Authorized User has appropriate authority to access Customer systems and data.
For Box, a “Connected AI Client” means an independently operated AI agent, application, automation, or MCP client that Customer authorizes to access the Box environment. Customer is responsible for selecting trustworthy Connected AI Clients, protecting OAuth authorizations and personal access keys, reviewing active connections, and promptly revoking access that is no longer appropriate, without limiting any independent legal obligations of Simular.
2. The Services and Subscription Rights
Subject to these Terms, any applicable order form or subscription plan, and payment of applicable fees, Simular grants Customer a limited, non-exclusive, non-transferable, non-sublicensable right during the applicable subscription term to access and use the Services for Customer’s internal business or personal productivity purposes, as applicable.
The Services may include downloadable software, web applications, remote or local execution environments, workflow runners, APIs, browser automation, and AI-assisted or autonomous computer-use functionality. Features may vary by plan, deployment, geography, or technical configuration.
Box provides a hosted cloud computer that may be accessed through authorized Connected AI Clients. Available browser, desktop, file, shell, and MCP functions may differ by integration, authorization method, plan, and configuration.
Box System Updates. Simular may update, replace, or reconfigure a Box’s system image, operating system, software, or other components for security, maintenance, compatibility, operational needs, or new features. Following an update, software, packages, dependencies, or configurations installed by Customer may need to be reinstalled or reconfigured. Simular will handle Customer Content in accordance with these Terms, the Privacy Policy, and applicable service documentation, including applicable retention and deletion practices. Where reasonably practicable, Simular will provide advance notice of material changes that may affect Customer-installed software or configurations.
Using a Connected AI Client on Customer’s behalf does not, by itself, grant the third-party provider a license to resell, sublicense, or independently commercialize the Services. Any customer-facing resale, managed-service offering, or provisioning of Box for third-party end users requires authorization under an applicable order form, enterprise agreement, or written supplemental terms.
3. Autonomous Actions, Authorization, and Oversight
The Services may take actions in software interfaces, browsers, connected applications, or other systems based on Customer instructions or requests transmitted through Customer-authorized Connected AI Clients. These actions may include navigating websites, clicking controls, entering information, sending communications, creating or modifying files, calling APIs, or executing workflows.
By connecting an account, enabling an integration, granting a permission, configuring an approval setting, or instructing the Services to perform a task, Customer authorizes Simular and the Services to access and act within the scope of the permissions, settings, and instructions Customer provides. Customer is responsible for determining whether a requested action is appropriate and lawful and for configuring approvals and human review appropriate to the risk of the action.
For Box, an authorized Connected AI Client may direct browsing, file operations, command execution, or other tools within the permissions actually made available to that connection. An authenticated request may be processed through Customer’s authorized connection, but technical authentication alone does not establish that every resulting action was specifically intended by Customer. Simular retains its own obligations regarding the security and operation of the Services.
Customer should maintain meaningful human oversight over high-impact, difficult-to-reverse, financial, legal, security-sensitive, or external-facing actions. Customer is responsible for deciding which independently selected AI clients to use and for configuring any human-review or approval prompts made available by those clients. If Customer elects to pre-authorize categories of actions, or to disable or reduce approval prompts, Customer assumes responsibility for the consequences of that configuration. Except for separately available connector-tool controls described below, general Box browser, shell, and file operations are not subject to a Simular-enforced per-action approval requirement.
Box does not independently require user approval for shell commands, emails sent through a browser, file deletion, or changes to account credentials. Approval prompts offered by a Connected AI Client are controlled by that third party. Certain connector tools, if made available, may offer user-level Allow, Ask, or Off settings; an action using a connector tool set to Ask may require a single-use, action-specific approval. Such connector approvals do not govern ordinary Box browser, file, or shell operations.
Customer acknowledges that AI-generated outputs and automated actions may be incomplete, inaccurate, unexpected, delayed, or unsuccessful. Simular does not guarantee that any requested action will be initiated, completed, completed correctly, reversible, or recoverable after interruption. Customer should independently review outputs and actions before relying on them for material decisions or mission-critical processes.
4. Acceptable Use
Customer may not, and may not permit any third party to, use the Services to:
- violate applicable law, regulation, contractual obligations, or third-party rights;
- engage in phishing, malware distribution, credential theft, unauthorized surveillance, denial-of-service activity, deceptive spam, or other malicious conduct;
- gain unauthorized access to accounts, systems, networks, or data, or circumvent security controls, guardrails, sandboxing, rate limits, or access restrictions;
- use the Services to make or materially assist high-impact decisions about individuals in a manner prohibited by applicable law;
- reverse engineer, decompile, disassemble, or attempt to discover non-public source code or underlying components of the Services except to the extent such restriction is prohibited by law;
- use the Services to build or train a competing product by extracting the Services’ non-public models, logic, or system behavior, except as expressly authorized in writing by Simular;
- scan, probe, enumerate, exploit, or attempt to access another customer’s Box, workspace, virtual machine, storage, credentials, authentication tokens, or other tenant resources, except within the scope of a written security-testing authorization from Simular and the affected customer or other person legally authorized to grant access;
- compromise, exploit, disrupt, or attempt to gain unauthorized access to Simular’s MCP servers, authentication or authorization systems, administrative interfaces, host infrastructure, execution environments, control plane, or other components of the Services;
- use shell commands, scripts, Connected AI Clients, or other tools to move laterally between tenants, bypass tenant isolation, access Simular’s internal network or management services, or extract data from another user or environment;
- conduct vulnerability scans, penetration tests, port scans, or other security assessments against the Services, shared infrastructure or other users’ systems, except strictly within an advance written authorization that identifies the permitted systems, methods, duration, and testing boundaries and is issued by Simular and, where applicable, the owner or other person authorized to approve testing of an affected third-party system;
- attempt to evade or defeat abuse detection, access-token revocation, MCP restrictions, rate limits, account suspensions, or other protective measures, including by rotating credentials or changing Connected AI Clients; or
- use the Services in a manner that materially interferes with the integrity, availability, or operation of the Services or third-party services.
Customer is responsible for ensuring that its instructions to the Services and its use of third-party websites, applications, and APIs comply with the terms and policies applicable to those third-party services.
Customer must not direct or knowingly permit a Connected AI Client to access accounts, files, websites, networks, or personal information without appropriate authority. Customer will not expose access keys or tokens publicly or share them with unauthorized parties and will promptly report suspected compromised credentials or cross-tenant access to support@simular.ai.
Customer shall reasonably configure and supervise Connected AI Clients that it authorizes, use available permission and credential safeguards, and promptly revoke access and notify Simular upon becoming aware of suspected compromise or harmful activity. Customer shall reasonably cooperate in investigating and containing security incidents involving its account, credentials, or Connected AI Clients. These obligations do not require Customer to guarantee the conduct of an independent AI provider.
Fair Use. Customer may not use the Services for unauthorized cryptocurrency mining, botnet activity, abusive automated traffic, unauthorized proxying or tunneling, resource exhaustion, or other activity that unreasonably burdens shared computing, storage, or network resources. Customer may not use scripts, automated interactions, or other means to artificially keep a Box active or prevent hibernation for the purpose of circumventing plan-based sleep, inactivity, usage, or resource limits.
5. Healthcare and Protected Health Information
The general-purpose Services are not intended for processing Protected Health Information (“PHI”). Simular may designate specific deployments or service configurations for PHI use. Customer may submit or permit access to PHI only through a deployment or configuration that Simular has expressly designated in writing for that purpose and only if Customer and Simular have entered into a Business Associate Agreement (“BAA”) covering that use. A designation applies only to the identified deployment or configuration and does not extend to other Services.
Designated healthcare deployments are intended for administrative healthcare workflows. The Services are not intended to provide diagnosis, treatment recommendations, clinical decision support, or other outputs on which a healthcare professional or other person should rely to make a clinical determination regarding an individual, unless Simular expressly agrees otherwise in writing under terms specifically addressing that use.
Customer must not submit PHI to beta, development, staging, experimental, or general-purpose deployments that have not been expressly designated for PHI use. If these Terms conflict with an executed BAA regarding PHI, the BAA controls to the extent of the conflict.
6. Customer Content, Data Use, and Outputs
“Customer Content” means prompts, instructions, files, images, credentials, records, messages, data, and other content submitted to or made accessible to the Services by or for Customer. As between the parties, Customer retains its rights in Customer Content. Customer grants Simular a limited right to host, store, process, transmit, reproduce, and otherwise use Customer Content as reasonably necessary to provide, secure, support, maintain, and improve the Services as permitted by these Terms and the Privacy Policy; comply with law; and enforce applicable agreements and policies.
Customer represents that it has all rights, notices, permissions, consents, and lawful bases necessary for Simular to process Customer Content as contemplated by these Terms and Customer’s instructions, including personal information relating to third parties.
For Box, Customer Content may include information placed in or accessible from the persistent workspace, browser sessions, downloaded files, shell outputs, and content returned through MCP tool responses. Customer must obtain the permissions and provide the notices required for content that Customer or its Connected AI Clients causes Box to access, process, or disclose, including information about third parties.
Storage of Customer Content is separate from whether Customer Content is used for generalized model training. Simular may store session, conversation, workflow, and related content as part of providing and maintaining the Services as described in the Privacy Policy.
Simular does not use Customer Content, task transcripts, uploaded files, screen observations, or PHI to train or fine-tune public, third-party, or generalized cross-customer AI models unless Customer expressly opts in or otherwise authorizes such use in writing and, for PHI, such use is permitted under the applicable BAA and law. This restriction does not prevent Simular from processing Customer Content through AI models as necessary to perform the Services, performing security or debugging activities, or using information that has been lawfully de-identified or aggregated.
The restrictions on Simular’s own model training and on vendors acting for Simular do not govern a Connected AI Client independently selected by Customer after that client receives data through MCP. Such third-party AI providers may process content under their own separate terms and privacy policies. Simular remains responsible for its own handling of Customer Content and the providers it engages as required by law.
Subject to Customer’s rights in Customer Content, Simular owns the Services and all related software, models, workflows, documentation, interfaces, know-how, and intellectual property. To the extent permitted by law and subject to third-party rights, Customer may use outputs generated for Customer through the Services for its own purposes.
7. Third-Party Services and Integrations
The Services may interoperate with third-party services selected or connected by Customer, such as email, calendar, collaboration, source-code, productivity, practice-management, or other systems. Customer authorizes Simular to access and interact with those services as necessary to perform Customer-requested tasks and subject to permissions Customer grants.
For Box, Customer may authorize a Connected AI Client through supported OAuth connections or a personal access key. Subject to the actual permissions and technical controls, connected clients may use available MCP tools to view workspace information, operate applications, and return screenshots, command outputs, files, or other task-related content to the independent AI provider.
For Box, OAuth authorizations are limited to the Boxes selected during consent and have an applicable expiration period; a consent screen may initially preselect all Boxes. A personal access key may authorize access to every Box associated with the account until that key is revoked, without reliably identifying the underlying AI application. Access to a Box generally includes the available screenshot, browser, file, and shell functions rather than independently configurable permissions for each such function. Revoking an OAuth grant or personal key prevents further access using that authorization but does not necessarily stop programs or other tasks already running inside the Box. Box does not notify Customer when an additional Connected AI Client connects to an existing Box. Some clients may register themselves through dynamic client registration and are identified as unverified on the consent screen. Simular does not verify the identity, security, or data practices of any Connected AI Client, and Customer should approve only clients it trusts.
Box is designed to retain files, application state, browser sign-ins, cookies, SSH keys, and shell history between connections or idle periods. More than one authorized Connected AI Client may access the same persistent Box workspace, and a subsequently connected client may be able to use authenticated sessions or other state left by an earlier client. Connecting, disconnecting, or changing clients does not create a segregated workspace or erase existing Box data. Disconnecting all connected applications and credentials does not by itself reset the Box or remove stored website sign-ins; deleting the Box is the available full-reset mechanism.
Third-party services are governed by their own terms and privacy practices. Simular is not responsible for third-party services that Customer independently selects or contracts for, including their availability, security, or acts and omissions. Customer is responsible for selecting connected services, managing permissions, understanding applicable third-party terms, and revoking or limiting access when appropriate. This does not limit Simular’s obligations with respect to service providers or subprocessors that Simular itself engages to provide the Services.
For independently chosen Connected AI Clients, Customer is responsible for reviewing the provider’s separate terms and privacy notices, evaluating the information that may be made available to that client through MCP, and managing available permissions and credentials. A Connected AI Client may autonomously request or return information within the access afforded to it; Customer does not necessarily select each item of data transmitted in every tool response. Simular does not control how an independent provider uses or retains information after it receives the information, except to the extent that provider separately acts on Simular’s behalf. Nothing here excludes Simular’s responsibility for its own Services, acts, omissions, or engaged service providers to the extent required by applicable law.
Customer is responsible for assessing whether an independently selected Connected AI Client’s applicable terms and privacy practices, including its data retention, model-training, confidentiality, and onward-disclosure practices, are compatible with Customer’s legal obligations, contractual commitments, and privacy notices. Customer shall not make Customer Content available to that client where doing so would violate those obligations or commitments, and shall obtain necessary permissions and apply reasonable access restrictions. Customer may need to use an appropriately contracted service configuration or refrain from connecting that client. This does not limit Simular’s independent legal obligations for its own processing or security.
An independent Connected AI Client provider does not become a party to these Terms solely because Customer connects or authorizes its application. Such a provider is subject to separate developer, API, or access terms only if it independently accepts them. Simular may nevertheless exercise its access-control rights under Section 14 in relation to connections, credentials, sessions, workspaces, or accounts used to access the Services, regardless of whether that provider has a direct contractual relationship with Simular.
8. Professional and Regulated Uses
Unless Simular expressly agrees otherwise in writing, the Services and outputs are not professional legal, medical, financial, tax, psychological, or other regulated advice and are not a substitute for consultation with a qualified professional. Customer is responsible for independently reviewing outputs before using them in regulated activities or decisions.
These Terms do not create a fiduciary, professional, partnership, joint venture, employment, or other legal agency relationship between Simular and Customer. The authorization granted under Section 3 is limited to carrying out Customer instructions within the Services.
9. Privacy and Security
Simular’s Privacy Policy describes how Simular collects, uses, discloses, and protects personal information in connection with the Services. If Simular processes personal information on Customer’s behalf under a separate data processing agreement or BAA, that agreement controls to the extent of any conflict within its scope.
The Privacy Policy describes Simular’s handling of Box workspace content, credentials and authorization records, MCP data returned to Connected AI Clients, security and audit records, and persistent workspace data. Depending on the processing activity and applicable U.S. law, the parties may enter into additional enterprise, privacy, security, service-provider, or data-processing terms. These Terms do not by themselves characterize Simular as a processor or service provider for every activity.
Customer is responsible for configuring its accounts and integrations appropriately and for implementing safeguards suitable for Customer’s systems, users, and data. No service can guarantee complete security, and Customer should maintain appropriate backups, access controls, and business continuity procedures.
Customer acknowledges that Box workspace data may persist after a Connected AI Client disconnects or its OAuth authorization or personal key is revoked. Deleting a chat in a third-party AI application does not delete corresponding Box files or browser state. Box inactivity deletion varies by payment history and subscription status and is described in the Privacy Policy. Deletion of a Box, revocation of credentials, account closure, and removal of retained logs or saves are separate processes with different applicable timeframes.
For Box, the applicable inactivity-deletion period depends on payment history and subscription status: Small and Medium subscribers are not scheduled for deletion solely because of inactivity while their subscriptions remain active; users who have ever paid for a top-up or subscription are subject to deletion after 30 consecutive days in hibernation when no paid subscription is active; and users who have never paid are subject to deletion after 14 consecutive days in hibernation. If a paid subscription is cancelled, the applicable inactivity-deletion period begins no earlier than the end of the paid subscription period; following a failed payment, it begins no earlier than when payment retries have been exhausted and the subscription actually ends. The applicable rules depend on activity and payment history rather than unused credit balance. For Boxes existing when these Terms are posted on November 19, 2026, the applicable period will be measured no earlier than that date, and no such Box will be deleted for inactivity earlier than 14 days after that date. Simular will send a warning email to the email address associated with the account at least seven days before any inactivity deletion. If the warning email has not been sent at least seven days before the proposed deletion, the deletion will be postponed until that minimum notice period has elapsed after the warning is sent. Simular may also send a reminder email approximately one day before and a notification after deletion. Customer is responsible for keeping that address current, and non-receipt of a notice that Simular sent does not prevent deletion. An inactivity deletion removes the Box together with all of its saves, and deleted Boxes cannot be restored by Customer. Customer is responsible for exporting any content it wishes to keep before a Box is deleted. To the maximum extent permitted by law, Simular is not liable for loss of content resulting from a deletion carried out in accordance with these rules. Simular may change these rules prospectively in accordance with Section 18.
Simular maintains administrative, technical, and organizational safeguards designed to protect Customer Content and the Services against unauthorized access, use, disclosure, alteration, and destruction, taking into account the nature of the Services, the information processed, and applicable legal requirements. For Box, safeguards are intended to reduce the risk of unauthorized access across customer accounts and hosted environments. The availability and implementation of particular controls, including network, storage, and execution-environment isolation, depend on the deployed configuration. Nothing in these Terms limits Simular’s obligations to implement reasonable security measures as required by applicable law.
For Box, Simular may use available account and Box audit records, connector-call records (where connector tools are offered), limited server request logs, and, where reasonably necessary, Box content, as described in the Privacy Policy, to detect, investigate, prevent, or respond to suspected unauthorized access, cross-tenant activity, malicious automation, or other misuse. The scope of monitoring, detection, and response measures may vary by deployment and technical configuration.
Security Incident Notification. Where Simular becomes aware of an actual or reasonably suspected security incident involving unauthorized access to or disclosure of Customer Content, Simular will provide notice and reasonable cooperation as required by applicable law and any applicable written enterprise, security, or data-processing agreement. Such agreements may specify incident definitions, notification procedures, investigation assistance, and return or deletion of Customer Content.
10. Subscription Fees, Credits, and Billing
Paid plans, usage limits, included credits, and other commercial terms are described at the time of purchase or in an applicable order form. Unless otherwise stated, subscription fees are billed in advance and are non-refundable except as required by law or expressly provided in an applicable order form.
Usage Credits. Credits have no cash value, are non-transferable, and are not redeemable or refundable except as required by applicable law. Free sign-up credits (including the initial 5,000), invitation credits, and other gifted, KOL, or promotional credits expire 90 days after they are granted. Purchased top-up credits and top-up bonus credits expire 12 months after purchase, as disclosed at the time of purchase, subject to any longer period or different treatment required by nonwaivable applicable law. Credits included in a monthly subscription expire at the end of the applicable monthly billing period. Expired credits are forfeited and are not refunded, except as required by applicable law. Simular may modify, reduce, suspend, or discontinue free, invitation, KOL, or promotional credits and credit programs, and may otherwise revise credit terms, on a prospective basis, subject to applicable law and any required notice. Changes affecting credits already purchased remain subject to the terms disclosed at purchase and nonwaivable law.
Credit Application and Purchases. Unless otherwise stated at purchase and subject to applicable law, credits are used in the following order: (1) monthly subscription credits; (2) Free sign-up credits; (3) invitation and promotional credits; (4) top-up bonus credits; and (5) purchased top-up balance. Purchased credits, if any, are governed by disclosures presented at purchase and any applicable order form. Subscriptions may renew automatically unless cancelled before the renewal date, as disclosed at purchase. Customer authorizes Simular or its payment processor to charge applicable fees, taxes, and usage charges to the payment method on file.
Referral and Promotional Credits. An invited user receives 5,000 credits upon starting the user's first Box. The inviting user may receive 5,000 referral credits when the invited user completes the qualifying action disclosed in the applicable referral program or offer, subject to the per-code limits and other conditions disclosed with that program or offer. For a designated KOL or promotional link, the first 50 eligible sign-ups under that link receive an additional 5,000 promotional credits; subsequent eligible sign-ups receive only the standard Free sign-up credit, if eligible. Duplicate, self-referral, fictitious, fraudulent, or otherwise ineligible accounts or sign-ups do not count toward referral or promotional limits, including the first-50 sign-up limit. Simular may conduct reasonable eligibility and anti-abuse checks and, where it reasonably suspects credit farming, fraud, or other program abuse, may withhold credits or temporarily restrict account access pending review. Where Simular reasonably determines that a claim or account is ineligible or abusive, it may disqualify the claim, exclude it from program limits, void or revoke improperly obtained credits, and suspend or terminate the account, subject to applicable law. Referral and promotional credits are gifted credits subject to the 90-day expiration above. Simular may revise qualifying actions, reward amounts, limits, or other program rules prospectively, as disclosed in the applicable program or offer and subject to applicable law and any required notice.
11. Beta, Preview, and Experimental Features
Simular may make beta, preview, experimental, or pre-release features available from time to time. Those features may be changed or discontinued at any time, may be subject to additional terms, and may be less reliable or secure than generally available Services. Customer should not use such features for regulated or sensitive data, including PHI, unless Simular expressly designates the feature for that use in writing.
12. Feedback
If Customer provides suggestions, ideas, or feedback regarding the Services, Customer grants Simular a worldwide, perpetual, irrevocable, royalty-free right to use and incorporate that feedback without restriction or obligation, provided Simular does not identify Customer publicly as the source without permission.
13. Confidentiality
Simular Proprietary Information. Without limiting the foregoing, Simular's Confidential Information includes all nonpublic information concerning the Services, including source code, algorithms, proprietary models, system architecture, infrastructure, security controls and mechanisms, authentication methods, technical documentation, product roadmaps, business strategies, pricing arrangements, trade secrets, and other proprietary technical or business information disclosed or made available to Customer in connection with the Services.
Restrictions on Use and Disclosure. Customer shall not use, disclose, reproduce, distribute, or make available Simular's Confidential Information to any third party except as expressly permitted under these Terms or otherwise authorized in writing by Simular. Customer shall not use such information to reverse engineer the Services, circumvent security controls, gain unauthorized access to Simular's systems or other users' environments, develop competing products through unauthorized use of Simular's Confidential Information, or facilitate any such activities by third parties. Nothing in this Section prohibits disclosures or activities protected by applicable law, including lawful security research, vulnerability reporting, or communications with governmental or regulatory authorities.
14. Suspension, Refusal, and Termination
Simular may refuse, suspend, restrict, or terminate an action or access to the Services if reasonably necessary to address a security risk, suspected unlawful or abusive use, material violation of these Terms, nonpayment, technical or operational risk, risk to third parties, or legal or regulatory requirements. Simular is not obligated to execute an instruction that it reasonably determines should not be executed for those reasons.
For Box, Simular may, based on its reasonable security or operational judgment, proactively refuse, block, rate-limit, monitor, restrict, suspend, or revoke access associated with a Connected AI Client, MCP connection, OAuth authorization, personal access key, credential, process, session, workspace, virtual machine, or account where activity presents or may present a security, legal, abuse-prevention, or material operational risk. Simular need not establish that a breach or violation has occurred before taking a protective measure. Restrictions generally operate at the applicable credential, OAuth-grant, Box, or account level. Simular may not be able to identify which AI provider is using a shared personal key or to block only one tool or session, and a restriction may therefore affect multiple clients.
Protective measures may include blocking tool calls or further MCP requests, revoking an OAuth grant or personal access key, disabling connector tools, restricting account access, terminating processes or sessions, restricting computing or network activity, hibernating, isolating, shutting down, or deleting an affected Box, restricting inbound access to infrastructure, and temporarily suspending affected infrastructure or portions of the Services. Some process-level or outbound-network containment actions may require manual intervention by authorized infrastructure personnel and may not be immediately available. Revoking a grant or key does not necessarily stop tasks or commands already executing inside Box. Where narrower action is unavailable or inadequate, Simular may take reasonably necessary broader measures, including measures affecting other sessions, workspaces, or customers, to protect shared infrastructure or third parties, subject to applicable law.
Simular may take protective action without prior notice or Customer approval, including to prevent an anticipated threat, and may decline to execute an instruction presenting such risk. Where legally required, Simular will provide notice; otherwise it may provide notice or an opportunity for review when reasonably practicable and consistent with security, legal, and investigative needs. Simular may preserve reasonably necessary evidence in accordance with the Privacy Policy. Customer acknowledges that protective action may interrupt tasks or transactions, terminate sessions, or cause loss of unsaved work. To the maximum extent permitted by law, Simular is not liable for losses resulting solely from good-faith, commercially reasonable protective action, except to the extent arising from its gross negligence, willful misconduct, or liability that cannot lawfully be excluded.
Customer may stop using the Services at any time and may cancel a subscription in accordance with the applicable plan or order form. Simular may terminate these Terms or discontinue the Services upon reasonable notice, except where immediate termination or suspension is reasonably necessary for security, legal, abuse-prevention, or operational reasons. Provisions that by their nature should survive termination will survive.
15. Disclaimer of Warranties
TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICES AND OUTPUTS ARE PROVIDED “AS IS” AND “AS AVAILABLE.” SIMULAR DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AVAILABILITY, SECURITY, AND ANY WARRANTY THAT THE SERVICES, OUTPUTS, OR ACTIONS WILL BE ERROR-FREE, UNINTERRUPTED, COMPLETE, OR SUITABLE FOR ANY PARTICULAR USE.
16. Indemnification
To the extent permitted by law, Customer shall defend, indemnify, and hold harmless Simular and its affiliates, officers, directors, employees, and agents against third-party claims, damages, liabilities, judgments, settlements, costs, and reasonable attorneys’ fees arising out of or relating to (a) Customer Content or Customer’s use of the Services; (b) acts, omissions, commands, or other activity performed through Customer’s account, credentials, authorizations, or Connected AI Clients, including autonomous or unintended actions within access authorized by Customer; (c) unauthorized access, malicious code, network scanning, lateral movement, interference with other systems, or other security-related activity originating from such use; or (d) Customer’s violation of these Terms, applicable law, or third-party rights, including failure to safeguard credentials or reasonably cooperate in incident response.
Customer’s obligations for claims involving Connected AI Clients do not require proof that Customer specifically directed, anticipated, or knowingly approved the particular autonomous action. However, Customer need not indemnify Simular to the extent a claim results from Simular’s negligence, willful misconduct, breach of these Terms, or violation of applicable law. Simular will provide reasonably prompt notice and cooperation at Customer’s expense; Customer may control the defense with counsel reasonably acceptable to Simular, but may not settle in a manner that admits fault by, imposes non-monetary obligations on, or fails to fully release Simular without Simular’s prior written consent.
Security Incident Costs. If Customer materially breaches its security-related obligations under these Terms and that breach directly causes a security incident, Customer shall reimburse Simular for reasonable, documented, proportionate out-of-pocket costs of investigation, containment, forensic services, and remediation to the extent directly caused by such breach, excluding ordinary overhead and costs attributable to Simular’s own negligence, willful misconduct, or breach. These reimbursement obligations are subject to Section 17 unless otherwise agreed in writing.
17. Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, GOODWILL, OR DATA, ARISING OUT OF OR RELATING TO THE SERVICES OR THESE TERMS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
EXCEPT FOR AMOUNTS PAYABLE BY CUSTOMER, CUSTOMER’S INDEMNIFICATION OBLIGATIONS, OR LIABILITY THAT CANNOT LAWFULLY BE LIMITED, EACH PARTY’S AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THE SERVICES OR THESE TERMS WILL NOT EXCEED THE GREATER OF (A) THE FEES PAID OR PAYABLE BY CUSTOMER TO SIMULAR FOR THE SERVICES DURING THE TWELVE MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY OR (B) US$100 IF CUSTOMER HAS PAID NO FEES.
Any different limitation of liability in an applicable order form, enterprise agreement, DPA, or BAA will control for claims within its scope.
18. Changes to the Services and These Terms
Simular may modify the Services from time to time. Simular may also update these Terms. If a change to these Terms materially reduces Customer’s rights or materially increases Customer’s obligations, Simular will provide reasonable notice before the change becomes effective, unless a faster change is required for legal, regulatory, security, operational, or abuse-prevention reasons. Continued use of the Services after the effective date of updated Terms constitutes acceptance of the updated Terms to the extent permitted by law.
19. Governing Law and Dispute Resolution
These Terms are governed by the laws of the State of Delaware, without regard to conflict-of-laws rules. Except for claims eligible for small claims court or requests for temporary or preliminary injunctive relief, any dispute arising out of or relating to these Terms or the Services will be resolved by binding arbitration administered by the American Arbitration Association under its applicable rules. Arbitration will take place in English. EACH PARTY WAIVES ANY RIGHT TO A JURY TRIAL OR TO PARTICIPATE IN A CLASS, COLLECTIVE, OR REPRESENTATIVE ACTION TO THE MAXIMUM EXTENT PERMITTED BY LAW.
20. General
Neither party may assign these Terms without the other party’s consent, except that Simular may assign them in connection with a merger, reorganization, sale of assets, or transfer to an affiliate. If any provision is unenforceable, the remaining provisions remain in effect. Failure to enforce a provision is not a waiver. These Terms, together with any applicable order form, enterprise agreement, DPA, BAA, supplemental terms, and incorporated policies, constitute the agreement between the parties regarding the Services within their respective scope.
Contact Us
Simular, Inc.
1209 Orange Street
Wilmington, New Castle, Delaware 19801
Email: support@simular.ai