Terms of Service
These terms and conditions (“Terms”) govern all use by you (“Customer”, “You” or “Your”) of the Website (as defined below), including any content and products available on or through it, and of the Service (as defined below), and form part of the legally binding Agreement (as defined below) between Customer and Emcie Co Ltd. (“Emcie”, “Company” or “We”).
Your access to and/or use of the Service or Website are deemed Your acceptance, without modification, of all of the terms and conditions contained herein (including in the Privacy Policy, AI Terms and Data Processing Addendum), and of all of the procedures and specifications (including those set forth in the Documentation) that may be published from time to time by Company with relation to the Service or the Website (collectively, the “Agreement”).
The Agreement is between You and Company, and You are required to read and accept it before creating an Account (as defined below) and/or using the Service. By creating an Account, accessing and/or using the Service, You are accepting the Agreement on behalf of yourself (if You are an individual) or of the company or any other organization that You represent, and - as applicable - You agree to become bound by the Agreement or You represent and warrant that You have full authority to bind the company or organization that You represent to the Agreement. If You do not agree as aforesaid, or are not authorized as aforesaid, You may not access or use the Service, and You must refrain from creating an Account.
1. Definitions.
1.1 “Service” – means Company’s software-as-a-service (SaaS) business platform provided on top of the Parlant solution, that enables Customer to build, connect and host AI agents (including agents that use large language models (LLMs) and small language models (SLMs)), to observe, investigate and analyze agent Sessions (including through AI-assisted features such as Session summaries and the Coparlant assistant), and to connect source-code repositories for the deployment and inspection of managed Projects, the commercial details and other specifications of which are provided in the Agreement and/or in the Documentation. Managed hosting and the other Project types are described in Section 2.11. The Agreement covers the production services only, namely the Website, the dashboard at dashboard.parlant.io, the production application programming interfaces (APIs), and the public Lighthouse documentation assistant at lighthouse.parlant.io, including access through the command-line interface (CLI). Development and staging environments, including platform.emcie.xyz, are outside the Agreement and are not part of the Service or the Website.
1.2 “Website” – means Company’s website (at: parlant.io), which provides information about the Company and the Service, and enables customer to subscribe for the Service.
1.3 “Authorized User” – means an individual whom Customer permits to use or access the Service on its behalf, through a User Account that holds a Membership in Customer’s Workspace. What an Authorized User may do is determined by the role of its Membership, as set out in the Documentation.
1.4 “End User” – means a person who interacts with, or is served by, an agent that Customer operates or makes available using the Service (for example, a customer, prospect or other contact of Customer), but excluding an Authorized User when using the dashboard or Account of the Service on Customer’s behalf.
1.5 “Parlant” – means Company’s open-source AI engine which enables organizations to define AI agent behavior. Parlant is made available under the Apache License, Version 2.0 (in the repository at https://github.com/emcie-co/parlant, and as stated in the license that accompanies the relevant release), which is separate from the Agreement. The Agreement does not limit the rights granted to Customer under that license, and that license does not by itself grant access to or the right to use the Service or any part of Company Technology that is not licensed under it. The Parlant dashboard is proprietary; it is not provided under that license, and access to and use of the dashboard are governed by the Agreement.
1.6 “Account” – means Customer’s account for the Service, being the Workspace that Customer opens through the Website (except if rejected by Company), which owns the Plan and subscription for the Service. A reference in the Agreement to an individual’s log-in is a reference to a User Account.
1.7 “Input” – means a message and any other data, content, source code, file, configuration or activity information digitally received by Company’s systems from Customer through the Service Interface or through an integration that Company makes available and Customer connects (such as a connected code repository), with relation to and for provision of the Service thereupon, but only to the extent so received by Company.
1.8 “Output” – means a message, file or other content digitally sent or made available by Company’s systems to Customer through the Service Interface, which is the outcome of the Service provided upon the applicable Input, including content generated by AI Features.
1.9 “Service Interface” – means the interface digitally connecting between Company’s systems and Customer’s systems, through which data is transmitted between them within the Service.
1.10 “Company Technology” – means the technology owned and/or licensed by Company, upon which the Service is created and provided from time to time.
1.11 “Customer Data” – means any information and materials made available by the Customer and/or anyone on its behalf in connection with the Account and Service, or submitted by them to the Service in connection with use thereof, whether as part of an Input or otherwise. Customer Data does not include data related to Service usage, information about Company’s business contacts within Customer’s organization and information about Authorized Users. Excluding such information from Customer Data does not remove any duty that applies to it under applicable privacy and data protection laws, the Privacy Policy or the confidentiality provisions of the Agreement. Data related to Service usage means data about how the Service is used, such as counts, timings, feature use and error rates; it does not include the content of Inputs, Outputs or Sessions, or logs or feedback text that contain Customer Data, and any Customer Data contained in them remains Customer Data.
1.12 “End User Data” – means any Customer Data that originates from, was submitted by, or pertains to an End User, including content submitted as part of an Input by or on behalf of an End User.
1.13 “Intellectual Property” – means any intellectual property existing from time to time under any applicable law, rule or regulation, including any patent, patent application, work of authorship, copyright, trademark, service mark, trade secret, know-how, documentation, drawing, scheme, idea, design, concept, technique, methodology, process, invention, discovery, publicity right, privacy right, moral right, and any renewal, modification, update, derivative and variation of the foregoing, to the extent applicable.
1.14 “Documentation Portal” – means Company’s webpage containing information for customers about the Service, use thereof, access thereto and pricing therefor, located at: https://parlant.io/docs.
1.15 “Documentation” – means the information provided by Company on the Documentation Portal, which information is deemed part of the Agreement.
1.16 “Plan” – means the subscription plan (free or paid) elected by Customer for the Service, including its price, the available Billing Periods and its limits (such as Projects, Seats, Session allowances, retention and dashboard lookback), as set out in the Documentation and, where applicable, in a quote or order form confirmed by Company.
1.17 “Billing Period” – means the monthly or yearly period for which the subscription fee of a paid Plan is invoiced, and at the end of which it renews.
1.18 “Usage Cycle” – means the monthly period, determined by Company for the Workspace, at the end of which the monthly Session allowances restart. A Usage Cycle is independent of the Billing Period.
1.19 “Project” – means an agent project created by Customer in the Service. Managed and self-hosted Projects share the live-Project capacity of the Plan; local Projects are subject to separate capacity, as set out in the Documentation. Section 2.11 describes Managed, Self-hosted and Local Projects.
1.20 “Session” – means a single conversation between an agent of a Project and a person (or a simulated participant), recorded in the observability features of the Service for that Project and identified in the Service as one conversation, as further described in the Documentation. A Session consists of all the messages and other interactions of that conversation, and the Session, not the individual message, is the unit counted for the Session allowance (see Section 4.4). A test conversation marked as a simulation in the dashboard is identified as such; choosing a persona alone does not mark a Session as a simulation. A Session is identified by the application that creates it, which controls whether separate conversations have separate Session identifiers; no automatic end time or inactivity timeout is stated. A simulation on a live Project counts toward the Session allowance like any other Session, while the Sessions of a Local Project take no place in that allowance (Section 4.4); all Sessions remain subject to the retention limits in Section 4.6.
1.21 “Seat” – means one Membership place for an Authorized User in a Workspace, as limited by the Plan of that Workspace; a person who holds Memberships in several Workspaces uses a Seat in each of them. A valid pending invitation also reserves a Seat until it is accepted, revoked or expires under the invitation policy; accepting an invitation does not take a second Seat.
1.22 “Unused Time Adjustment” – means the invoice adjustment for unused paid subscription time described in Section 4.7. It is not a purchased or prepaid credit, and it is not a credit for failing to meet a service level.
1.23 “User Account” – means an individual’s personal log-in to the Service, created through the Website or any other method made available by Company, which may hold Memberships in one or more Workspaces.
1.24 “Workspace” – means the shared organizational area in the Service that owns Projects, Memberships and a Plan (including the related subscription, Billing Period and Usage Cycle). A person may be a member of more than one Workspace, and each Workspace has its own Plan, Billing Period, Usage Cycle and Seats.
1.25 “Membership” – means the association of a User Account with a Workspace under a role (as described in the Documentation) that determines the person’s permissions in that Workspace, including whether the person may manage billing.
2. Service Access and Use.
2.1 Subject to Customer’s compliance with the requirements for the Service and with the Agreement, Company grants Customer, once Customer opened an Account and for as long as the Account remains active, a non-transferable, non-exclusive, revocable right to access and use the Service pursuant and subject to the terms and conditions of the Agreement and the Documentation, for Customer’s personal or business purposes aligned with the Service capabilities as set forth in the Documentation. This right includes using the Service to build, operate and make available agents that interact with End Users, including persons outside Customer’s organization, in accordance with the Agreement and the Documentation. Making Customer’s agents available to End Users in this manner is not a sale, resale or sublicense of the Service for purposes of Section 2.4. Access to the Service itself, including the dashboard and the Account, may be provided only to Authorized Users in accordance with the Agreement, and Customer may not sell, share with any person other than Authorized Users, or transfer its Account or Seats.
2.2 Subject to Company’s specific consent, at its sole discretion, Customer’s engagement with Company for the right to access and use the Service may be pursuant to executing an order form, instead of the standard joining the Service through the Website. If such executed order form determines any term or condition that is in conflict with a term or provision of the Agreement – the applicable term or provision of the order form shall prevail.
2.3 The Service and any Input and Output may only be used in compliance with all applicable laws, rules and regulations, and for legitimate purposes.
2.4 Customer must not, and shall not allow any third party, including Authorized Users, to: (i) reproduce, duplicate, copy, sell, resell or sublicense the Service and/or Company Technology in whole or part; (ii) reverse engineer, decompile or otherwise seek to obtain the source code, object code, underlying algorithms or non-public APIs to Company Technology; (iii) violate or attempt to circumvent any security measures within the Company Technology; (iv) interfere with the Service or Company Technology in a way that could damage, disable or overburden Company’s systems, security or services; (v) introduce onto, or transmit via, the Service or Company Technology any disruptive computer program code, virus, worm, Trojan horse or the like; or (vi) use the Service, Company Technology or any Input or Output in an unlawful manner, in a manner which may damage Company or its reputation, or otherwise in breach of the Agreement. Nothing in this Section 2.4 limits any right of Customer under an open-source license that applies to Parlant or to other open-source software, or Customer’s rights in its own code, agents and configurations, including its right to build, change and operate them.
2.5 By creating an Account or a User Account and/or using the Service You represent that You are at least 18 years old, and that You are competent to enter into and accept the Agreement, either on Your own behalf or on behalf of the organization which You represent. This requirement applies to the individuals who create or use an Account or a User Account. It does not describe or limit the End Users who communicate with agents that Customer builds or operates using the Service. Customer decides who may communicate with its agents and what personal data they receive, and is responsible for the notices, lawful basis and other measures that this requires, including under laws on children’s data and on health or other sensitive or regulated data. Company does not verify or restrict the age of End Users, except as applicable law requires. Customer is responsible for ensuring that its use of the Service complies with applicable law, including any rules on collecting data from children, and on health data and other sensitive or regulated data, and for the notices, lawful basis, consents and other measures that those rules require. Company processes the personal data that Customer submits to the Service only as provided in the Data Processing Addendum. Nothing in the Agreement states that the Service is designed for, or meets the requirements for, children’s data or regulated health data, or that a business associate agreement or similar contract is available.
2.6 When creating an Account, Customer must provide information that is accurate and complete. Customer must keep the Account information and the log-in details of each User Account secure at all times, and remains solely liable for any failure to do so. Failure to comply with the foregoing constitutes a breach by Customer of the Agreement, and may result in immediate termination of the Account.
2.7 Customer acknowledges that the Service utilizes third party software, services and/or tools, including AI models, that are subject to third party terms and conditions (“Third Party Provider” and “Third Party Tools”, respectively). Customer understands and accepts that when a Third Party Tool is used, such use is deemed agreement to the applicable terms and conditions of such Third Party Provider, and that Customer’s access and/or use of a Third Party Tool are governed by this Agreement and the relevant terms and conditions of such Third Party Provider. Where Company engages a Third Party Provider as a subprocessor to process personal data on Customer’s behalf, that engagement is governed by the notice and objection process in Section 8 of the Data Processing Addendum and not by this paragraph. Where Customer connects its own account, key or tool from a Third Party Provider to its agents or Projects, Customer’s relationship with that provider, including its charges and terms, is with the provider and not with Company (see Section 2.11(f)).
2.8 Company shall not be responsible for any downtime or inoperability of the Service if such is caused due to any of the following: (i) Customer’s misuse of the Service or violation of the Agreement; (ii) failure of Customer’s internet connectivity; (iii) Customer’s failure to meet any minimum technical requirements prescribed by Company; (iv) Service failure caused by any unauthorized modification by Customer in the interfaces with the Service; or (v) failure or delay caused by any Third Party Provider.
2.9 Customer acknowledges that notices to be provided by Company to it, as required under these Terms, shall be sent to Customer’s email address (that was provided upon opening the Account, or replaced thereafter) and may in addition be sent to the email address of any Owner or Admin of the Workspace, and therefore Customer agrees to regularly review its inbox for notices from Company (and ensure such are not regarded as spam). Where Company sends an invoice or a notice about billing by email, it is sent to the billing email address saved for the Workspace, which is initially the email address of the user who set up billing for the Workspace or, if none, of an Owner, unless an Owner or Admin of the Workspace changes it in the Service. Customer is responsible for keeping that address current. Company does not undertake that every issued invoice is sent by email, or that every Member or Authorized User of a Workspace receives every invoice or notice.
2.10 Each individual accesses the Service through a User Account. A User Account gains access to an Account (a Workspace) through a Membership, and one User Account may hold Memberships in several Workspaces, with a different role in each. The Plan, Seats, Projects and permissions of one Workspace do not apply to any other Workspace. The role of each Membership determines what the individual may do in the Workspace, as set out in the Documentation. Customer is responsible for assigning roles to its Authorized Users and for removing a Membership when access should end.
2.11 A “Managed Project” is a Project whose agent is built and run through Company’s managed hosting from source code in a repository that Customer connects. A “Self-hosted Project” is a Project whose server Customer operates. A “Local Project” is a Project that connects to the Service an agent running on Customer’s own computer. The following paragraphs apply to these Projects, in addition to the other provisions of the Agreement.
(a) Permission. For a Managed Project, Customer authorizes Company, through the GitHub installation or other access that Customer grants, to access the selected repository, branch and commit, to fetch the code, to build it, to run it and to inspect it as described in paragraph (d). Customer confirms that it has the right to give this authorization, including for the code and third-party components in the repository.
(b) Deployment triggers. A deployment of a Managed Project may start when Customer starts it in the Service, or when code is pushed to the branch configured for the Project. Customer is responsible for the repository, branch, build and run commands and settings that it configures or accepts, and for what a push to that branch causes to be built and run. A push that arrives while a deployment or an inspection is running waits and does not replace the work that is running; only the newest waiting push is kept; when the running work ends, the waiting push is checked again against the saved source and the settings at that time, and it is dropped if it can never be built. The Service does not show or cancel a waiting push. A push to another branch or repository, or the deletion of a branch, does not start a deployment.
(c) No service level. The description in this Section 2.11 of how code is fetched, built and run is not a promise that a build or deployment will start or finish within any time, that a deployed agent will be available, or of any uptime or response time.
(d) Repository inspection. To suggest build and run commands and variables for a Managed Project, Company may inspect Customer’s repository at a chosen commit, including by sending repository content to an AI provider as described in the AI Terms. In the initial setup of a Managed Project, the Service may fill fields that Customer has not yet edited with the build and run commands and the variables and ordinary variable values that it detects; where Customer has already edited a field, a detected value is offered as a suggestion instead. In later checks of the deployment settings, detected values are offered as suggestions that Customer may accept or reject. Customer is responsible for reviewing all fields and suggestions before it deploys. Platform-saved secret values are not designed to be supplied to the inspection. The inspection can read the files in Customer’s repository, so Customer must not commit secrets to its repository (Section 2.11(e)). This is not a guarantee that a secret in the repository or elsewhere cannot reach the AI provider.
(e) Variables, secrets and logs. Customer provides the environment variables and secrets that its Managed Project needs. Once saved, a secret is write-only: the Service shows its name but not its value. The values of ordinary environment variables are visible in the Service to users with access to the Project, and Customer must not put secrets in ordinary variables, in the repository or in log output. Build and deployment output is shown in the Service to such users for the log-age period that the Plan gives the Project, or without an expiry where the Plan has none, as set out in the Documentation. Runtime output is shown in the Service only as a limited recent window of the running agent’s output and the Service does not offer it as an archive. Company applies measures that hide known secret patterns, credential-bearing addresses and the secret values saved for the Project in that output. These measures are protective only: they do not guarantee that a secret that has been changed, encoded, split or was not known to them is hidden. Hosting and infrastructure providers may also keep their own operational logs. The period for which the Service shows build, deployment or runtime output is a limit on what Customer can view in the Service; it does not describe how long Company keeps its own internal operational log archives. Customer is responsible for what its code writes to logs, must not write secrets to output, and is responsible for rotating and revoking its secrets and keys.
(f) Outside keys, accounts and costs. The price of a Plan does not include the charges of Third Party Providers that Customer connects to, or uses with, its agents or Projects under Customer’s own accounts or keys, such as model providers, tools, repositories, databases and other infrastructure. Customer pays those charges directly, and is responsible for those accounts and keys and for complying with the providers’ terms. The features available on the Plan that Customer selects, including managed hosting and builds and platform-provided AI features where that Plan offers them, are included in the price of the Plan within the published limits of that Plan; not every feature is available on every Plan. Company does not apply automatic overage charges. A report of model spend in the Service is not an invoice from Company.
(g) Lost access. If Customer removes or loses the GitHub installation or its access to the repository or branch, or the repository, branch or commit is no longer available, Company may be unable to fetch a new source revision, or to build or redeploy the Managed Project, and deployments from pushes may not start. Company does not promise that a Managed Project that is already running continues to run, or that it can be rebuilt or redeployed, without that access. Customer is responsible for restoring access.
(h) Runtime and backups. Customer is responsible for the code, behavior, content and lawful operation of its agents and for its End Users, and, for Self-hosted and Local Projects, for operating, securing, updating, monitoring and backing up the server and environment on which the agent runs and for its connection to the Service. Company does not promise any backup, restoration service or recovery-time target for a Managed Project, and Customer should keep its own copy of its source code, settings and data.
3. Customer Responsibilities.
3.1 Without derogating from other provisions of the Agreement, Customer is responsible for: (i) obtaining, maintaining and securing any equipment and ancillary services needed in order to connect to, access and use the Service, including hardware, software, operating systems and the like; (ii) complying with these Terms and the Agreement in full; (iii) giving all notices to, and obtaining any rights, permissions and consents from its End Users or others that are necessary for Customer’s lawful use of the Service and for the processing of Customer Data contemplated by the Agreement; (iv) responding to and resolving any dispute between Customer and an End User related to or based on Customer Data and/or processing thereof in connection with Customer’s use of the Service; (v) complying with all applicable laws and regulations; (vi) notifying Company immediately of any unauthorized use of Customer’s log-in details or Account, and of any other known or suspected security breach; and (vii) immediately reporting to Company, and using reasonable efforts to immediately stop, any prohibited use and/or action with relation to the Service. Customer is also responsible for the matters stated in Section 2.11 for Managed, Self-hosted and Local Projects, including its repository content, commands, settings, secrets, accounts and keys.
3.2 Customer is also responsible for all Inputs, and represents and warrants that it has all rights and permissions required to provide the Inputs. Customer is also responsible for all use of the Outputs and for evaluating the accuracy and appropriateness of Outputs for Customer’s uses, using checks appropriate to the use, including testing before an agent is launched to End Users, ongoing monitoring and escalation, and for the notices to End Users and the authority for actions in outside systems, as set out in Section 5(d) of the AI Terms. This does not require Customer to approve each routine response of its agents before it is given. Customer is responsible for the safeguards, oversight and other measures appropriate to its deployment, including for high-stakes uses, according to its use case and its legal obligations; tests, monitoring, escalation and human review are examples of such measures. Company does not require human review of every high-stakes Output before it is acted on, and nothing in the Agreement permits Customer to bypass a safeguard that applicable law requires.
3.3 Customer undertakes and is responsible to ensure that each Authorized User is bound by and complies with all of the applicable provisions of the Agreement. Customer will at all times be and remain liable for (i) the conduct by any Authorized User with relation to the Service and compliance with Customer’s obligations and undertakings under the Agreement; (ii) any act or omission by any Authorized User which, if performed or omitted by Customer, would be a breach of the Agreement.
4. Subscription, Billing and Usage.
4.1 Subscription and Billing Periods: Access to the Service is provided under a Plan. Paid Plans are billed in advance, monthly or yearly, as elected by Customer, and renew automatically for successive Billing Periods of the same length until cancelled or changed in accordance with this Section 4. By electing a paid Plan, Customer authorizes Company, and its payment service provider, to charge the payment method provided for each Billing Period and for any other amount due under this Section 4. Company issues an invoice for each charge. Issuing an invoice, displaying it in the Service and sending it by email are separate steps, and an invoice that is sent by email is sent only to the billing address described in Section 2.9, and Company does not promise that every issued invoice is sent by email. The free Plan is provided free of charge and is subject to the Agreement and to the limits set out in the Documentation.
4.2 Usage Entitlement:
a) The Service usage entitlements (including the number of Projects and Seats, the monthly Session allowance for each Project, retention limits and dashboard lookback) are determined by the Plan elected by Customer. Details of the offered Plans and the limits thereunder are provided in the Documentation. Session data captured under Plan terms marked not private (currently the free Starter Plan) is handled as stated in Section 9.6. That marking does not by itself give Company any broader legal right, and it gives Company no additional purpose, no right to publish or distribute the data, no right to train models and no exemption from privacy rights.
b) Company reserves the right to at any time amend the offered Plans and applicable limits, including cancellation of a Plan. Company shall notify Customer thereof as set out in the next paragraph and, where the amendment is a material modification of the Agreement, as provided in Section 19.7.
c) In case of cancellation of a Plan, or amendment thereof resulting in decreased usage entitlements, Company’s notice thereof to Customer shall be provided in advance (and, where the change is a material modification of the Agreement, at least thirty (30) days in advance by email as provided in Section 19.7), and if Customer does not update their Plan election until the date stated for the change’s entrance into effect – then Company shall at its sole discretion transfer Customer to another Plan which is nearest in similarity to the cancelled/amended model. Where the amendment to a Plan does not result in decreased usage entitlements, the amendment shall enter into effect immediately upon Company’s notice.
4.3 Prices, Taxes and Payment: Prices of Plans are as stated in the Documentation or in the quote or order form confirmed by Company, are denominated in US Dollars and are exclusive of any and all taxes, levies and duties required by applicable law (“Taxes”). Customer is responsible for paying, and will be charged on top of the prices, all Taxes associated with its subscription; the billing name and address provided for the subscription (and not the display name of the Workspace or Account) are used as the place of supply for tax purposes, and Customer is responsible for keeping them accurate. Company is solely responsible for Company’s income tax. Prices of Plans do not include the charges of Third Party Providers described in Section 2.11(f). Unless agreed otherwise, payment is made by credit card, a digital billing platform, or wire or bank transfer, as made available by Company. Proration, discounts, Taxes and account adjustments are calculated by Company’s payment service provider, and the amounts shown to Customer before a change is confirmed are those calculated by it for that change. If the calculated amount changes before payment is completed, Company may charge the amount calculated at the time of the charge, and the checkout is designed to ask Customer to review a changed quote before any charge where the billing terms have changed. Company may amend the prices of Plans for future Billing Periods by notice to Customer given at least thirty (30) days before the new price applies.
4.4 Usage Cycles: Session allowances are monthly, including under a yearly Billing Period; payment for a year does not provide one shared annual Session allowance. The Usage Cycle is determined by reference to the original UTC date and time at which it was established for the Workspace, and not by a fixed 30-day duration (where that day does not exist in a shorter month, the last day of that month applies, and the original day applies again when possible). The end of a Usage Cycle is exclusive: activity at that instant belongs to the next Usage Cycle. A change of Plan or Billing Period does not change the Usage Cycle and does not clear usage already counted. Each live Project (a managed or self-hosted Project) has its own Session allowance within the Usage Cycle; allowances are not pooled between Projects, and a Project created during a Usage Cycle starts at zero with its full allowance for the remainder of that cycle. The allowance counts Sessions, not messages. A counted Session takes the next place in its Project’s Usage Cycle: the Usage Cycle in which it was created or, where it becomes active again in a later Usage Cycle, the Usage Cycle of that new activity. A Session therefore takes one place when first recorded, and one additional place on its first new activity in each later Usage Cycle; further messages in the same Usage Cycle, a reset, a replay, a title change or a deletion do not add or refund usage. A Session is readable when its place is within the allowance of that Usage Cycle, and is otherwise locked as described in Section 4.5. The following Sessions take no place in, and are not limited by, the Session allowance, although they remain subject to the retention limits described in Section 4.6: (i) every Session of a Local Project; and (ii) the history of a live Project that was imported from before that Project’s first connection to the Service. Sessions of a live Project created after its first connection are counted as set out above.
4.5 Observability Limits: The monthly Session allowance limits Customer’s access to agent activity in the observability features of the Service. It is not a limit on the number of conversations that Customer’s agent can conduct. Where a Project’s allowance is exceeded, Sessions continue to be received but are locked: identifying information may appear in the Session list, but their content cannot be viewed or analyzed, and the agent and its connection to the Service continue to operate. A Session that is already accessible remains accessible when further activity arrives in the same Usage Cycle, even after the allowance is exhausted. The first new activity of a Session in a different Usage Cycle is assessed against that cycle’s allowance, and may result in the Session being locked. Upgrading to a larger Plan may unlock qualifying Sessions of the current Usage Cycle; a Usage Cycle reset does not unlock Sessions locked in an earlier cycle, and Sessions that were not made accessible before their Usage Cycle ended become unavailable for inspection. This Section 4.5 concerns Session and retention limits only: all other limits of the Plan continue to apply, including the number of Projects and Seats, and the hourly and monthly limits of assistive features such as Coparlant, which may refuse further assistance once its limits are reached.
4.6 Retention and Lookback: Each Plan limits how much Session history remains available in the Service for each Project, both by age and by the number of retained Sessions. A Session may expire when either limit is reached, and locked Sessions also occupy retention places. Age is measured from the Session’s original creation time, in 24-hour days; additional activity does not make an older Session new, and a Usage Cycle reset does not clear retained history or restart a Session’s age. A Plan with longer retention applies going forward only: an upgrade does not restore a Session that has already expired under a previous Plan, and reimporting, or deleting other Sessions, does not restore an expired Session. A Plan with shorter retention may make additional history unavailable when it takes effect. The dashboard lookback of a Plan is a separate limit on the historical range available in aggregated views, and is not a commitment to retain individual Sessions for that period. Deletion of a Project, or removal of a member, is not reversed by a later failed payment or a cancelled Plan change. See also Section 9.6.
4.7 Changing a Plan or a Billing Period: Changes take effect as follows, subject to the Documentation:
(a) Upgrades (a higher Plan, or a change from monthly to yearly billing at the same Plan or at a higher Plan) are charged at the time of the change and take effect only after payment is confirmed and the new terms are activated. The amount charged is the price of the new Plan or Billing Period less an adjustment for the unused paid time of the current Plan, calculated by Company’s payment service provider for the unused paid time remaining at the time of the change (the “Unused Time Adjustment”) (the provider uses its own proration method with normal rounding of currency amounts; Company applies no whole-day rounding). For an upgrade within the same Billing Period length, the amount charged is the difference between the prices of the two Plans, prorated by the payment service provider for the remainder of the paid period, and the existing renewal date is retained. A change to a lower Plan is not an upgrade, even where it is combined with a change from monthly to yearly billing; it is scheduled under paragraph (c).
(b) The Unused Time Adjustment is applied against the first invoice for the new Plan or Billing Period. It is not a refund, is not paid to Customer’s bank account or payment method, is not a purchased credit or credit pack, is not a credit for failing to meet a service level, and cannot be redeemed, transferred or exchanged for cash. Where the first invoice for the new Plan or Billing Period has nothing due after the Unused Time Adjustment, the invoice is treated as paid and the new terms activate without a charge to a payment method.
(c) Any change to a lower Plan (including a change to a lower Plan combined with a change from monthly to yearly billing, or from yearly to monthly billing), and any change from yearly to monthly billing at the same Plan, is scheduled for the end of the current paid Billing Period, with no immediate charge, refund or credit; the current Plan and its entitlements continue until then. Where a lower Plan is combined with a different Billing Period length, both changes are scheduled together and take effect together at that date. The end of the current paid Billing Period is the end date of the period actually paid for (for a yearly subscription, the end of the paid year); it is not the date on which the monthly Usage Cycle ends. Before a downgrade can be scheduled, Customer’s Projects and Seats (including Seats reserved by valid pending invitations) must fit within the capacity of the lower Plan, and Customer must delete Projects, remove members or revoke invitations as needed; the capacity of the lower Plan also limits new admissions while the current Plan remains paid. Capacity is checked again when the scheduled change is to be applied, and Company does not delete Projects or remove members to make it fit.
(d) A move from a paid Plan to the free Plan takes effect at the end of the paid Billing Period, when the paid subscription ends. The limits of the free Plan then apply, including its capacity limits (paragraph (c)). Company does not delete Projects or remove members to make them fit the free Plan. If, on that date, Customer’s Projects or Seats do not fit the free Plan, Company may keep the current Plan assignment and entitlements under an administrative hold instead of applying the free Plan, and Company does not promise that a Managed Project continues to run, or is hosted uninterrupted and without charge, on the free Plan. The move does not delete the Workspace, any Project or any Customer Data; Section 13.5 explains what ends and what remains.
(e) A change from yearly to monthly billing together with a higher Plan requires first paying the prorated upgrade to the higher Plan for the remainder of the paid year. The higher Plan takes effect only after that payment is confirmed and the new terms are activated, and monthly billing at the higher Plan then begins at the end of the paid year (the existing annual period end).
(f) When an existing monthly subscription moves to yearly billing, the yearly Billing Period is anchored to the first payment attempt, even if payment completes later. This applies to a change to yearly billing that takes effect as an upgrade under paragraph (a). Where a change to yearly billing is combined with a lower Plan, paragraph (c) applies and the yearly Billing Period starts at the end of the current paid Billing Period.
(g) A new request replaces a previously scheduled change in accordance with the rules set out in the Documentation. A paid upgrade replaces a scheduled lower Plan only once its payment succeeds; an unsuccessful payment does not cancel the scheduled change. Cancelling a scheduled lower Plan keeps the current Plan and does not cancel the subscription.
The following table summarises paragraphs (a) to (g). If the table and those paragraphs differ, the paragraphs prevail. In every row, the end of the current paid Billing Period means the end date of the period actually paid for, not the date on which the monthly Usage Cycle ends.
| Change requested | How it is handled | When it takes effect |
|---|---|---|
| Free Plan to a paid Plan | Customer pays, then the paid Plan is activated and the selected Billing Period is established | After payment is confirmed |
| Higher Plan, same Billing Period length | Charged the prorated difference for the remainder of the paid period (paragraph (a)) | After payment is confirmed; the existing paid-period end is kept |
| Same Plan or higher Plan, monthly to yearly | Upgrade under paragraph (a); the yearly Billing Period is anchored under paragraph (f) | After payment is confirmed |
| Lower Plan, same Billing Period length | Scheduled; the current Plan stays active (paragraph (c)) | At the end of the current paid Billing Period |
| Lower Plan, different Billing Period length (monthly to yearly, or yearly to monthly) | Scheduled; both changes are scheduled together (paragraph (c)); no immediate charge, refund or credit | Both changes together, at the end of the current paid Billing Period |
| Same Plan, yearly to monthly | Scheduled; the current Plan and yearly period stay active (paragraph (c)) | At the end of the current paid Billing Period |
| Higher Plan, yearly to monthly | Two stages: first the prorated upgrade to the higher Plan for the remainder of the paid year; then monthly billing is scheduled (paragraph (e)) | Higher Plan after payment is confirmed; monthly billing at the end of the paid year |
| Paid Plan to the free Plan | Scheduled (paragraph (d)) | At the end of the paid Billing Period |
4.8 Failed Payments; Overdue Invoices: If a payment is declined, abandoned (including at authentication) or still processing, Customer’s existing Plan remains active while the operation is unresolved, and a competing purchase may be blocked until it is resolved. Overdue invoices must be settled before an upgrade. Access to the Service generally continues during renewal payment retries, with the Account’s overdue standing recorded; nothing in this Section 4 limits Company’s rights under Section 13 (Term, Termination and Suspension). A change that does not complete at its intended renewal is unsuccessful, and is not moved to a later renewal.
4.9 Cancellation; No Refunds: Customer may cancel a paid Plan at any time through the Account. Cancellation takes effect at the end of the current paid Billing Period, and Customer retains access to the paid Plan until then; the Workspace then moves to the free Plan (Section 4.7(d)). Cancelling a paid Plan does not by itself delete the Workspace, any Project or any Customer Data, or close any User Account; see Section 13.5. Except where required by applicable law, to correct a billing error, expressly stated in this Section 4, or agreed in a signed order form, amounts paid are non-refundable. This includes the unused part of a paid yearly Billing Period where Customer cancels, or moves to a lower Plan, before that period ends. If Company ends a paid subscription without cause, Company will refund the unused part of the prepaid Billing Period in money, through its payment service provider, to the payment method used for the charge to the extent that the provider can refund to it, and will not deduct the provider’s fees from the refund. The time at which the refund is received depends on the payment service provider and the payment method. A refund may be pending or may fail, and a pending or failed refund does not by itself discharge Company’s obligation to make it. A cash refund, an invoice credit (such as the Unused Time Adjustment in Section 4.7) and the cancellation of a Plan are different things: cancelling a Plan, or a credit balance, is not by itself a refund of money. The right in Section 19.7 to end the Agreement without charge is a right not to be charged further; it does not by itself entitle Customer to a refund of an amount already paid, unless Section 19.7 expressly says so or applicable law requires it.
4.10 Purchases and Billing Authority: A Plan is purchased for, changed, cancelled and charged to the Workspace in which the action is taken, and the Plan of one Workspace does not apply to any other Workspace. Only Memberships whose role includes billing permissions (currently Owners and Admins, as set out in the Documentation) may purchase, change or cancel a Plan or manage billing for a Workspace; individuals holding other roles may not. A person who makes such a purchase or change confirms that he or she is authorized to do so on behalf of Customer, and Customer is responsible for charges incurred through its Workspace by anyone holding such a Membership.
5. Modification
Company may modify any feature, method and/or capability of the Service and of Company Technology at any time. Where Company determines, in its sole and reasonable discretion, that the modification is material and/or that Customer should become aware of it, Company shall notify Customer thereof and - where reasonably needed - in advance. A modification that is a material modification of the Agreement is notified as provided in Section 19.7.
6. Feedback
By submitting any feedback or suggestions regarding the Service, Customer grants Company a worldwide, non-exclusive, perpetual, irrevocable, royalty-free license (transferable only to a permitted assignee of Company) to use, copy, modify and incorporate such feedback or suggestion in order to develop, operate, improve and support the Service and Company’s other offerings, without obligation to Customer. This license covers the feedback or suggestion itself. It does not give Company any right in Customer Data, in Customer’s other Intellectual Property, or in Confidential Information of Customer or of any third party that is contained in feedback, and it does not permit Company to publish feedback in a way that identifies Customer or an individual. Feedback is stored with the identity of the person who submitted it and the context of the submission, and that information is handled under the Privacy Policy. Feedback is not anonymous, and the license above does not remove any duty that applies to the personal data in it. Company retains feedback submitted through the platform for product improvement for 24 months after the last activity in the Workspace concerned, then deletes it, and deletes it earlier on a valid request sent to [email protected]. The license above is subject to such a request: it does not require Company to keep feedback, or the personal data in it, after a valid deletion request, and it does not limit a deletion right that applies by law. Company administrators and designated support and safety staff may read feedback. Customer should not include Customer Data, personal data or third-party confidential information in free-text feedback.
7. Maintenance
7.1 The Service may be temporarily unavailable for scheduled maintenance or for unscheduled emergency maintenance, either by Company or by Third Party Providers, but Company shall use reasonable efforts to provide advance written notice of any scheduled Service disruption.
7.2 Customer grants Company the non-exclusive right to collect, aggregate and analyze data related to usage of the Service, and to use it for developing, operating and improving the Service and other Company offerings. This right applies to data about usage of the Service and does not extend to the content of Customer Data, the use of which is governed by Section 9 and, where it includes personal data, by the Data Processing Addendum. Where usage data relates to an identifiable individual, it is personal information handled under the Privacy Policy. Company does not currently de-identify usage, query or conversation records or keep a separate de-identified dataset: those raw records are stored together with identifiable data. The public Lighthouse assistant also keeps a reusable answer index, which is separate from those records. As released, the assistant rewrites a suitable answer into a general Parlant question and answer, removes request-specific details, creates embeddings and saves the result for reuse in answering other requests, and the saved item keeps a reference (a source record identifier) to the record from which it was derived. Company does not describe that index as anonymous, as unlinked from its source or as impossible to delete, and it is not the training or fine-tuning of an AI model (Section 10). Statistics are treated as anonymous only if they can no longer identify a person under applicable data protection law; combining data does not by itself make it anonymous. Analytics and session-replay tools used in the dashboard (currently including PostHog, which Company hosts on its own cloud infrastructure) record how the dashboard is used. The conversation area of the dashboard, personal data shown in it, and payment, token and secret areas are masked, so that the content of Sessions is not visible in a replay. Masking covers defined areas of the interface and is not a guarantee for every item of data, such as a secret typed into a field that is not masked. A user’s analytics choice applies to that user’s account only; it is not a Workspace instruction or the consent or authorization of the other users of the Workspace or of the people in the Sessions, and it does not waive any right of an individual or any duty that applies to Company under privacy law. Company also keeps a first-party record of the actions that users take in the dashboard and the command-line tool, as described in the Privacy Policy; a user’s analytics choice does not affect it.
8. Intellectual Property Ownership.
8.1 All rights, title, and interest in and to the Service, the Website, Company Technology and Company’s Intellectual Property are hereby reserved by Company, its affiliates or licensors, as applicable. All rights, title, and interest in and to Customer’s Intellectual Property, are hereby reserved by Customer. Nothing in the Agreement shall transfer ownership of any Intellectual Property right from one party to the other and/or from Company to any Authorized User or End User. Without derogating from the generality of the foregoing, except as expressly set forth in the Agreement, Customer retains all ownership rights in Inputs and receives the rights in Outputs.
8.2 With respect to its Intellectual Property, Customer grants Company only the limited rights that are necessary for Company to provide the Service and enforce the Agreement and, as regards Customer Data, only the license in Section 9.4. This limited permission extends also to Third Party Providers, including subprocessors, only to the extent necessary for those purposes and as provided in Section 9.7.
8.3 Customer acknowledges that given the nature of the Service and of artificial intelligence and machine learning technologies (used for provision of the Service) generally, an Output may not be unique, and other users may receive similar content from Company’s services.
9. Customer Data; Data processing.
9.1 As between Customer and Company, Customer owns all right, title, and interest in and to the Customer Data, subject to Company’s rights under the Agreement.
9.2 Company shall implement and maintain technical, organizational and physical measures to protect the confidentiality and integrity of Customer Data when in Company’s possession, custody or control.
9.3 Customer acknowledges and agrees that when Customer Data includes personal data, the terms of Company’s Data Processing Addendum, which is incorporated by reference into the Agreement, shall apply with respect to processing thereof.
9.4 Customer grants Company a worldwide, royalty-free, non-sublicensable, non-transferrable (except to a permitted assignee of Company), non-exclusive license, for the term of the Agreement and subject to Section 9.8, to host, store, access, use, copy, process, adapt, transmit, display and export the Customer Data only (i) to provide, operate and maintain the Service for Customer, (ii) to comply with applicable laws and regulations, (iii) to perform Company’s obligations under the Agreement, and to enforce the Agreement, (iv) to prevent or address security, support and technical issues, and (v) to improve the Service, but only to the extent expressly set out in Section 7 of the AI Terms or separately approved by Customer. Where Customer Data includes personal data, this Section 9.4 applies subject to the Data Processing Addendum. This Section 9.4 is read together with Sections 9.7 and 9.8, and does not affect Customer’s ownership of the Customer Data under Section 9.1.
9.5 Company reserves the right to take appropriate action, including suspending or disabling access to the Service, if it suspects and/or receives notice of an alleged infringement or violation of applicable laws with relation to Customer Data.
9.6 Session history available in the Service is subject to the retention limits of Customer’s Plan under Section 4.6. The expiry of a Session for purposes of the Service interface does not, by itself, determine when the underlying Customer Data is deleted from Company’s systems; deletion is governed by the Data Processing Addendum. Deleting a Project does not by itself mean that every copy of the underlying data has been deleted (see Section 13.5(b)). The retention limits of a Plan govern what Customer can see in the Service; they do not guarantee physical deletion. Company retains full conversations and related logs internally, including those of Sessions that have expired from the Service and of Sessions captured under Plan terms marked not private (currently the free Starter Plan), for 24 months after the last activity in the Workspace concerned, for usability improvement and safety purposes. When that period ends, Company deletes the retained content. The retained content is not anonymized or reduced. Access to it is limited to Company administrators and designated support and safety staff. Retained content that relates to an identifiable person remains personal data; information is anonymous only if it can no longer identify a person under applicable data protection law (Section 7.2). Company will delete the retained content on a valid, explicit request for erasure sent separately to [email protected], so far as the content can be identified and without a promise that every copy is deleted (see Section 9.8); for data of a shared Workspace the request must be authorized by an Owner. The expiry of a Session or of a Plan limit, and clicking Delete project in the dashboard, are not such a request. This paragraph does not authorize the use of retained content to train models, and it creates no additional purpose, right to publish or distribute, or exemption from privacy rights. This paragraph concerns conversations and their logs; the activity and staff-access records described in the Privacy Policy are kept for the periods stated there.
9.7 Third Party Providers; no publication. Company may permit Third Party Providers, including subprocessors, to process Customer Data on Company’s behalf, but only to the extent necessary for the purposes in Section 9.4 and, where Customer Data includes personal data, in accordance with the Data Processing Addendum. This is not a sublicense, and Customer does not grant any Third Party Provider, through the Agreement, a right to use Customer Data for the Third Party Provider’s own purposes. This applies to Third Party Providers that Company engages; it does not apply to a provider whose account, key or tool Customer connects to its agents or Projects, whose terms are between Customer and that provider (Section 2.11(f)). Unless a signed order form or other signed agreement with Customer says otherwise, the Agreement does not promise that Customer Data is processed or stored in any particular country or region. The license in Section 9.4 is subject to the confidentiality provisions of the Agreement. Company will not publish Customer Data, make it publicly available or distribute it to third parties, other than to Third Party Providers as provided in this Section 9.7 and as required by applicable law. Showing Customer Data to Customer and its Authorized Users, or to other persons to whom Customer or an Authorized User chooses to give access through the Service, is not publication by Company. This Section 9 does not limit the license granted in the Feedback provision of these Terms or Company’s rights in data about usage of the Service under Section 7.2.
9.8 Effect of deletion and termination. The license in Section 9.4 continues only while Company provides the Service to Customer. After the Agreement ends, or after Customer deletes Customer Data in the Service, Company may keep and use Customer Data only (i) as required by applicable law, (ii) as needed to complete the deletion of Customer Data in accordance with the Data Processing Addendum, and (iii) as needed to establish, exercise or defend legal claims or to enforce the Agreement, and in each case only for as long as, and to the extent, necessary for that purpose and subject to the confidentiality provisions of the Agreement. Customer’s ownership of the Customer Data, and the limits in Sections 9.4 and 9.7, continue for as long as Company holds any Customer Data. Paragraphs (i) to (iii) above do not describe the internal retention of conversations and related logs stated in Section 9.6, which is governed by Section 9.6 and ends on a valid request for erasure under that Section.
10. AI Features.
10.1 Certain features within the Service use artificial intelligence and/or machine learning technologies (collectively, “AI Features”). Use of the AI Features is subject to the AI Terms, which are incorporated by reference into the Agreement. Section 7 of the AI Terms explains the purposes for which AI Input and AI Output may be used. Improvement of the Service and training of models using AI Input or AI Output are not agreed unless that Section expressly says so.
11. Privacy Policy.
11.1 Customer acknowledges and agrees that Company will use any personal information that it may collect or obtain in connection with the Service - in accordance with Company’s Privacy Policy, which is incorporated by reference into the Agreement (“Privacy Policy”).
11.2 Subject to the Privacy Policy, Company reserves the right to access, read and disclose any information it obtains in connection with the Service, as it reasonably believes necessary to: (i) satisfy any requirement by applicable law, regulation or competent authority, (ii) enforce the Agreement, (iii) detect or prevent fraud or security, (iv) respond to any support request, and/or (v) protect the rights, property or safety of Company or its customers. Company’s administrators may, for support and security, sign in to the Service as a user for a limited time and after recording a reason, within the limits described in the Privacy Policy; each such access is recorded, and the record is kept for twelve (12) months.
12. Confidentiality.
12.1 In this Section:
“Discloser” means the party providing or allowing access to its Confidential Information.
“Recipient” means the party receiving or being granted access to Discloser’s Confidential Information.
“Confidential Information” means all information and/or data of proprietary or confidential nature, whether written, oral or visual, in any form or media, that is commercial, financial or technical, including Intellectual Property, methods, ideas, algorithms, software code, forecasts and security reports, whether related to the current or future products, services, business, source code, data or configurations of Discloser or of Discloser’s customers. Confidential Information does not include any information or data that Recipient can demonstrate (i) was generally available to the public at the time of disclosure; (ii) was in its possession or known by it without restriction prior to receipt from Discloser; (iii) was rightfully disclosed to it without restriction by a third party; or (iv) was independently developed without the use of any Confidential Information of Discloser.
12.2 Except as permitted under these Terms, Recipient shall not: (i) disclose Discloser’s Confidential Information to any third party except Recipient’s employees, consultants and representatives who have a need to know it to enable Recipient to exercise its rights or perform its obligations under the Agreement, provided that they are subject to confidentiality and non-disclosure obligations no less stringent than those required hereunder, and provided that Recipient remains liable for their acts and omissions with respect to Discloser’s Confidential Information; (ii) use Discloser’s Confidential Information for any purpose other than exercising its rights or performing its obligations under the Agreement.
12.3 Notwithstanding the foregoing, Recipient may disclose Discloser’s Confidential Information to the limited extent required: (i) to comply with the order or requirement of a competent court or other governmental or regulatory body, or as otherwise necessary to comply with applicable law, provided that Recipient shall provide Discloser prompt written notice of such court order or requirement to enable Discloser to seek a protective order or otherwise prevent or restrict such disclosure, and provided that Recipient shall limit the disclosure to the minimum extent required; or (ii) to establish Recipient’s rights under the Agreement, including by making a court filing.
13. Term, Termination and Suspension.
13.1 The Agreement becomes effective upon Customer when Customer opens an Account, and remains in effect until the Account is closed or deleted in accordance with Section 13.5, or the Agreement is terminated under this Section 13. The Agreement is not ended by the cancellation of a paid Plan (the Account then continues on the free Plan), by the deletion of a Project or by the closing of a User Account, unless this Section 13 states otherwise. Customer may terminate the Agreement only by email to [email protected], sent by an Owner of the Workspace, asking for termination (see Section 13.5(c)); Company then deletes Customer’s data as provided in Section 6 of the Data Processing Addendum. If Customer stops paying but does not ask for termination, the Agreement continues and Company keeps Customer Data in case Customer resumes payment. If the Workspace has had no activity for 24 months and has no active paid Plan, Company may treat the Agreement as terminated after notice by email to Customer, and will then delete Customer Data as provided in Section 6 of the Data Processing Addendum.
13.2 Company may terminate or suspend Customer’s use of the Service and/or Account at any time if Company believes, in its sole and absolute discretion, that Customer is using the Service in a manner that may cause harm to Company or that is in breach of the Agreement. Company will use reasonable efforts to notify Customer before such suspension but may do so without prior notice to the extent reasonably necessary. After such suspension, Company will cooperate with Customer to promptly restore access to the Service once it verifies Customer has resolved the condition requiring suspension.
13.3 Company may terminate the Service and/or Account at any time, without prior notice or liability, if Company is required to do so by law.
13.4 Provisions of the Agreement which by their nature should survive termination thereof shall survive termination, including ownership provisions, Sections 9.7 and 9.8 (for as long as Company holds any Customer Data), warranty disclaimers, indemnity and limitations of liability.
13.5 Ending a Plan, a Project, a Workspace or a User Account. Cancelling a paid Plan, deleting a Project, deleting a Workspace and closing a User Account are separate actions with different effects, and none of them replaces another. The following paragraphs apply. A paid Plan is cancelled or changed in the Service by a Membership with billing permissions (Section 4), and a Project is deleted in the Service as described in paragraph (b). Deleting a Workspace is carried out by Company through an internal operations process and is not an action that a role can take directly in the Service (paragraph (c)). A request to delete a Workspace, and a request to close a User Account, are made to Company by email to [email protected] (paragraphs (c) and (d)).
(a) Ending a paid Plan. Cancelling a paid Plan under Section 4.9, or moving to the free Plan, ends paid access and billing for the Workspace at the end of the paid Billing Period, as provided in Section 4. It does not delete the Workspace or any Project, and does not close any User Account.
(b) Deleting a Project. Deleting a Project removes that Project from Customer’s use of the Service and starts the cleanup of its data; that does not by itself mean that every copy of that data has been deleted. It does not cancel or change the Plan, and does not stop billing for the Workspace. Sessions, traces and logs are removed in separate cleanup stages, so data of a deleted Project may remain in Company’s systems for a period after deletion, and a deleted Project is not made available to Customer in the Service. Clicking Delete project is not a request for erasure of content that Company retains internally under Section 9.6, which is requested separately at [email protected]. Session data captured under Plan terms marked not private (currently the free Starter Plan) is likewise kept when a Project is deleted until a valid request for erasure is made or the period in Section 9.6 ends. A Project is deleted in the Service by a Membership whose role includes the permission to delete Projects, as set out in the Documentation. Only the Owner role may delete a Project; the Admin, Builder and Viewer roles may not.
(c) Deleting a Workspace. Deleting a Workspace is carried out by Company through an internal operations process and is not an action that a role can take directly in the Service. It is a process with several stages, not an immediate action. It coordinates the cleanup of the Workspace’s Projects and the closing of the Workspace’s subscription with the payment service provider before the Workspace is finally removed. A request to delete a Workspace is made to Company by email to [email protected], which Company administrators monitor. Only an Owner of the Workspace may authorize Company to delete the shared Workspace data, which is separate from the permission to delete a Project in the Service. Company applies identity and authority checks appropriate to the request and communicates its completion to the requester. Company deletes the Workspace’s data from its active systems within ninety (90) days after a verified request to terminate the Agreement or to delete the Workspace; copies in backups and in provider systems are dealt with as stated in Section 6 of the Data Processing Addendum. The records of staff access described in the Privacy Policy, which Company keeps for twelve (12) months for security and accountability, are not deleted earlier by this process. The Owner requirement concerns the authorization of deletion of shared Workspace data; it does not prevent an individual from making a request about his or her own personal information, which is handled under the Privacy Policy. A waiting period in the process is not intended to allow subscription billing to continue unchecked. If a stage cannot be completed, for example because a dependency is unavailable or cleanup cannot be confirmed, the process is retried or blocked and the Workspace may remain in the Service until it completes. Deleting a Workspace does not close any User Account.
(d) Closing a User Account. Closing or deleting a User Account ends that individual’s log-in. It does not by itself cancel a Plan, delete a Workspace or a Project, or end the subscription of a Workspace of which the individual is or was a member. A request to close a User Account is made to Company by email to [email protected], which Company administrators monitor. Requests about the individual’s personal information are handled under the Privacy Policy.
(e) Export. The Service currently lets a person whose Membership allows reading Sessions export one Session at a time: a ZIP file with the Session details, its events and its logs as CSV files, and a JSON file of the Session’s raw logs. These exports cover one Session. They are not a complete export of a Workspace or a Project, this Section does not state that they include agent configurations, and Company does not promise that expired, locked or deleted Sessions can be exported with them. Company does not promise a complete historical return, export or recovery of Customer Data, and cannot promise that the full dataset is still retained or recoverable; data that Company no longer retains, including expired, locked or deleted Sessions, cannot be returned or restored. That is different from the duty under Section 6 of the Data Processing Addendum to delete personal data that Company still holds on Customer’s behalf when the Agreement ends, which this paragraph does not remove or reduce. A request for removal of data is made through the privacy-request channel at [email protected]. Nothing in this paragraph removes any right of access, portability or other right of an individual that applies by law. Company does not return personal data on termination or on request; Section 6 of the Data Processing Addendum provides for deletion.
(f) What continues. The duties that continue after the Agreement ends, or after a deletion, are those in Section 13.4, including Sections 9.7 and 9.8 for as long as Company holds any Customer Data.
14. No Warranties.
14.1 THE SERVICE IS PROVIDED ON AN “AS IS” BASIS, AND WITHOUT WARRANTIES OF ANY KIND EITHER EXPRESS OR IMPLIED. CUSTOMER ASSUMES ALL RESPONSIBILITY FOR ACCESSING AND USING THE SERVICE. EXCEPT AS OTHERWISE EXPRESSLY PROVIDED IN THE AGREEMENT, COMPANY HEREBY DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY OF AND FITNESS FOR A PARTICULAR PURPOSE.
14.2 COMPANY, ITS AFFILIATES AND ITS THIRD PARTY PROVIDERS SHALL NOT BE HELD LIABLE FOR: (I) THE ACCURACY OF THE OUTPUTS AND/OR ANY DATA CONTAINED THEREIN OR OMITTED THEREFROM, AND (II) ANY BUSINESS CONDUCTED OR LOST, OR ANY OTHER ACTION OR INACTION BY CUSTOMER, ITS CUSTOMERS OR OTHER PARTIES WITH WHOM CUSTOMER DOES BUSINESS, EVEN IF IN RELATION TO OR RELIANCE UPON, IN WHOLE OR IN PART, THE SERVICE.
14.3 THOUGH COMPANY USES COMMERCIALLY REASONABLE EFFORTS TO MAINTAIN A HIGH LEVEL OF SERVICE AVAILABILITY, IT DOES NOT WARRANT THAT THE SERVICE OR WEBSITE WILL OPERATE IN AN UNINTERRUPTED OR ERROR-FREE MANNER, THAT THEY WILL BE CONSTANTLY ACCESSIBLE OR THAT DEFECTS WILL BE CORRECTED. COMPANY ALSO DOES NOT WARRANT THAT THE SERVICE OR WEBSITE, INCLUDING INFORMATION TRANSMITTED THEREUNDER, WILL BE FREE FROM VIRUSES OR OTHER HARMFUL CODE OR INTRUSIONS. No service-level commitment, uptime target, response time or credit remedy applies to the Service unless it is stated in a signed order form or in a separate written support or service-level agreement.
14.4 NO WARRANTY IS GIVEN REGARDING THE RELIABILITY OF THE PERFORMANCE OF THE SERVICE OR OF THE OUTPUTS.
15. Limitation of Liability.
15.1 TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW, COMPANY SHALL NOT, UNDER ANY LEGAL OR EQUITABLE THEORY, INCLUDING BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, OR OTHERWISE, BE LIABLE FOR ANY CONSEQUENTIAL, EXEMPLARY, SPECIAL, INDIRECT, INCIDENTAL OR PUNITIVE DAMAGES OF ANY KIND OR NATURE, INCLUDING LOST REVENUE OR PROFITS, BUSINESS INTERRUPTION, LOSS OF DATA, GOODWILL, REPUTATION OR BUSINESS OPPORTUNITY, ARISING FROM OR RELATING TO THE AGREEMENT, THE SERVICE OR THE WEBSITE, REGARDLESS OF WHETHER COMPANY WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR COULD HAVE FORESEEN THEM.
15.2 IN NO EVENT SHALL COMPANY’S TOTAL, AGGREGATE LIABILITY FOR DAMAGES ARISING OUT OF OR IN ANY MANNER RELATING TO THE AGREEMENT, NOTWITHSTANDING THE FORM IN WHICH ANY ACTION IS BROUGHT, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHER THEORY OF LIABILITY, EXCEED, IN THE AGGREGATE, AN AMOUNT EQUAL TO THE FEES ACTUALLY PAID BY CUSTOMER TO COMPANY UNDER THE AGREEMENT IN THE TWELVE (12) MONTHS PRIOR TO THE DATE THE LIABILITY FIRST AROSE OR A SUM OF 1,000 (ONE THOUSAND) USD – WHICHEVER IS LOWER.
15.3 IN NO EVENT WILL ANY ACTION BE BROUGHT AGAINST COMPANY MORE THAN TWELVE (12) MONTHS AFTER THE CAUSE OF ACTION HAS OCCURRED.
15.4 Nothing in this Section 15 limits or excludes any liability or right that cannot be limited or excluded under applicable law, including mandatory data-protection law and any standard contractual clauses incorporated into the Agreement, and the order of precedence in the Agreement continues to apply. The limits in this Section 15 apply to Company’s liability only; they do not limit Customer’s liability, including under Section 16.
16. Indemnification.
Customer agrees to indemnify, defend and hold Company and its affiliates and Third Party Providers harmless from and against any liabilities, damages and costs (including reasonable attorneys’ and other professional advisors’ fees) payable to a third party arising out of legal proceedings filed by a third party and related to: (a) use of the Service and/or Website in violation of the Agreement or applicable law; and/or (b) Customer Data.
17. Governing Law; Exclusive Jurisdiction.
The Agreement shall be governed and construed in accordance with the laws of the State of Israel, without regard to its conflict of law provisions. The courts of Tel-Aviv, Israel shall have exclusive jurisdiction over all disputes and proceedings arising from or related to the Agreement and the use of the Service and/or Website.
18. Customer Reference.
Customer hereby permits Company to use Customer’s name and logo in order to identify Customer as Company’s customer and/or as a subscriber of the Service, on the Website, marketing materials, PR announcements and otherwise. This permission is subject to any contrary provision of a signed order form or confidentiality agreement with Customer. Company does not require Customer’s separate approval before it first uses Customer’s name and logo once Customer is using the Service. Customer may ask Company to stop further use by email to [email protected], and Company will then stop new uses once it has processed the request. Company does not undertake to remove or withdraw uses that were already published or distributed before then, including on the Website, in marketing materials and in announcements.
19. General.
19.1 Entire agreement: The Agreement constitutes the entire and exclusive agreement between Company and Customer regarding access to and use of the Service and the Website.
19.2 No waiver: No delay or failure by Company to enforce any right or power under the Agreement will be considered a waiver thereof.
19.3 Severability: Unenforceable provisions will be modified to make them enforceable, reflecting to the nearest extent possible the original intention, and the remaining provisions of the Agreement will remain in full effect.
19.4 Assignment: The Agreement and any right granted to Customer pursuant to it may not be assigned by Customer without Company’s prior written consent. Company may, without notice or Customer consent, assign the Agreement to any entity controlled by, controlling or under same control as Company, or to a purchaser of its assets or activity. The Agreement is binding upon the parties and their respective successors and permitted assigns.
19.5 Independent contractors: Company and Customer are not legal partners, but independent contractors.
19.6 Force Majeure: In no event shall Company be liable to Customer, or be deemed to have breached the Agreement, for failure or delay in performing any of its obligations under the Agreement, if and to the extent caused by any circumstance beyond Company’s reasonable control, including: acts of God, epidemic, war, terror threat or act, riot or other civil unrest, government action, national or regional emergency, strike or other industrial disturbance.
19.7 Modification: These Terms, as well as any other document constituting part of the Agreement, may be modified by Company from time to time, in whole or in part, by posting an updated version of the relevant document/s on the Website. Customer is responsible for regularly reviewing the most current version of the documents constituting part of the Agreement. When any such document is modified - Company will update the “Last Updated” date stated on it. By continuing to use the Service after the effective date of any modification to any document constituting part of the Agreement, Customer will be deemed to have accepted such modification. A modification of the Data Processing Addendum does not reduce the subprocessor notice and objection rights in Section 8.3 of that Addendum. Company gives at least thirty (30) days’ advance notice by email of material modifications, and Customer may end the Agreement without charge before they take effect (for amounts already paid, see Section 4.9). A signed order form is not modified by this paragraph and may be changed only as it provides.
19.8 No third party rights: Except if otherwise expressly stated, the Agreement does not confer any right or benefit on any third party.
19.9 When used in these Terms, the word “including” is construed to mean without limitation or a list that is not limited to what is listed, unless otherwise expressly stated.
19.10 Order of precedence: If there is a conflict between documents that form part of the Agreement, the following order applies. (a) A signed order form prevails over these Terms, to the extent that it expressly states a different term (Section 2.2). (b) The Data Processing Addendum prevails over these Terms and over the AI Terms as to the processing of personal data on Customer’s behalf. (c) The AI Terms prevail over these Terms solely as to AI Features. (d) In all other cases, these Terms apply. A signed order form prevails over the Data Processing Addendum or the AI Terms only where it expressly refers to that document and states a different term. No order form or other document overrides any standard contractual clauses incorporated under the Data Processing Addendum, or limits a right that cannot be limited under applicable law.
If You have any questions about the Agreement, please contact us at: [email protected]
Last Updated: November 6, 2026