Reverse

Terms and Conditions

Last revised September 16, 2026 · Effective September 21, 2026

These Terms and Conditions (the "Terms") govern your access to and use of Reverse, a visual editor over your codebase. Reverse connects to your GitHub repositories and uses artificial intelligence to parse a codebase into a visual workflow graph, answer questions about it through an AI advisor, autonomously draft and propose code changes through an AI coding agent, and generate documentation. Reverse is accessed through your browser. Additional information about the Service is available in our documentation at reverse.dev.

Reverse is a new and experimental product. Certain features are provided on a beta, proof-of-concept basis and may change, be interrupted, or be discontinued at any time.

Please read these Terms carefully before using the Service. These Terms include, and incorporate by reference, our Privacy Policy. If you do not agree to these Terms, you must not access or use the Service.

BY CREATING AN ACCOUNT OR USING THE SERVICE, YOU ACKNOWLEDGE THAT YOU HAVE READ AND AGREE TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS, YOU MUST NOT ACCESS OR USE THE SERVICE.

1. INTRODUCTION

  • a. Agreement. These Terms and Conditions (the "Terms") form a legal agreement between you and Bubble Group, Inc. ("Reverse," "we," "us," or "our"), the company that operates the Reverse product and the website at reverse.dev (the "Site"). These Terms govern your access to and use of the Site and the Reverse service (together, the "Service"). Our Privacy Policy is incorporated by reference into these Terms.
  • b. Eligibility and age. TO USE THE SERVICE, YOU MUST BE AT LEAST 16 YEARS OLD (or the age of majority in the jurisdiction from which you access the Service). If you are under the age of majority, you represent that you have your parent or guardian's consent to use the Service. The Service is not intended for, and may not be used by, anyone under 16.
  • c. Authority. By accessing or using the Service, you represent and warrant that you have the legal right and capacity to enter into these Terms — either for yourself or on behalf of the entity you represent. If you accept these Terms on behalf of an entity, you represent that you are authorized to bind that entity, and "you" refers to that entity. If you create or join a Workspace on behalf of an entity, you likewise represent and warrant that you are authorized to bind that entity, and references in these Terms to "you" are to that entity. YOU ARE REQUIRED TO AFFIRMATIVELY ACCEPT THESE TERMS WHEN YOU SIGN UP TO ACCESS THE SERVICE, WHETHER YOU SIGN UP WITH GITHUB OR WITH AN EMAIL ADDRESS.
  • d. Third-party services. These Terms do not apply to third-party websites, services, or applications you access through the Service, including the third-party AI services described in Section 10. We are not responsible for their content or practices. Review the terms of any third-party service you use.
  • e. Arbitration notice. SECTION 16 REQUIRES THE USE OF ARBITRATION ON AN INDIVIDUAL BASIS TO RESOLVE DISPUTES, RATHER THAN JURY TRIALS OR CLASS ACTIONS, AND LIMITS THE REMEDIES AVAILABLE TO YOU.
  • f. Changes. We may change these Terms at any time. When we do, we will post the updated Terms on the Site and, where material, notify you through the Service or by email. Changes are effective immediately for new users and five (5) days after posting for existing users. The current version and its effective date will always appear at the top of these Terms.
  • g. Contact. You may contact us with questions about these Terms at support@reverse.dev, or in writing at Bubble Group, Inc., 22 West 21st Street, 2nd Floor, New York, NY 10010, ATTN: Reverse Legal.

2. DEFINITIONS

"Account" means an account created to access the Service.

"Advisor" means the AI chat assistant that answers questions about a Connected Repository.

"Coding Agent" means the AI agent that autonomously drafts and proposes code changes, including by opening branches and committing changes to them.

"Connected Repository" means a GitHub repository you connect to the Service.

"Credits" means the prepaid units used to access metered features of the Service, as described in Section 11.

"Editor" means a Workspace Member holding the Editor role.

"Feedback" means any feedback, comments, or suggestions you provide about us or the Service.

"GitHub App" means the Reverse GitHub application you install to grant the Service access to a Connected Repository.

"Input" means the prompts, instructions, code, and other content you provide to the Reverse AI Tools.

"Marks" means trademarks, service marks, logos, names, branding, and equivalent identifiers.

"OSS" means "open source" or "free software" licenses.

"Output" means the code, answers, documentation, and other outputs generated by the Reverse AI Tools in response to your Input.

"Owner" means a Workspace Member holding the Owner role. The Owner role is the only role that may remove a Workspace Member, change a Workspace Member's role, and configure Project Settings.

"Payment Provider" means a valid credit card or other payment method that we accept.

"Platform Fee" means the one-time fee for the bring-your-own-key access option described in Section 11.

"Project Settings" means the project-level settings that only an Owner may configure, namely whether agent runs are permitted and whether pull requests may be merged from within the Service. Each of these settings is on by default for every project and remains on unless an Owner turns it off. Project Settings do not include project configuration that an Editor may change.

"Reverse AI Tools" means the AI features of the Service, including the Advisor, the Coding Agent, and documentation generation.

"Third Party AI Services" means third-party large language models and artificial-intelligence platforms used to provide the Reverse AI Tools, including Anthropic (Claude) and OpenAI.

"Third Party Services" means any third-party websites, services, and applications you may access or connect through the Service, including GitHub, Third Party AI Services, any bring-your-own infrastructure such as Supabase, and collaboration tools you connect to the Service, such as Slack.

"Update" means any change to the Service made available to all users at no additional cost.

"Usage Information" means data regarding installation, registration, use, and performance of the Service, including response times, activity logs, and usage and cost metering.

"User Content" means all content you or your collaborators provide, connect, upload, or generate through the Service, including the contents of Connected Repositories, your Inputs, and Outputs.

"Viewer" means a Workspace Member holding the Viewer role.

"Workspace" means a shared environment in the Service through which one or more users collaborate on Connected Repositories.

"Workspace Member" means any user with access to a Workspace, whatever their role.

3. LICENSE TO USE THE SERVICE

  • a. License. Subject to these Terms, we grant you a non-exclusive, non-transferable, non-sublicensable, limited, and revocable license to access and use the Service to understand, navigate, document, and edit codebases you are authorized to work with, and to use any Updates at no additional cost.
  • b. Restrictions. Except as expressly permitted, you may not, directly or indirectly: (i) modify or create derivative works of the Service; (ii) decompile, reverse engineer, or attempt to derive the source code, models, or techniques of the Service (except to the extent applicable law expressly permits); (iii) rent, lease, resell, or distribute the Service to any third party, including on a service-bureau basis; (iv) remove or alter proprietary notices; (v) circumvent or disable the Service's security, rate limits, token metering, or usage restrictions; (vi) interfere with the Service's operation; (vii) use the Service to violate the law or the rights of others; or (viii) attempt to do any of the foregoing. We may take any action we deem reasonable, including suspending or terminating your access, for any breach of this Section 3.

4. ACCOUNTS, GITHUB CONNECTION & ACCEPTABLE USE

  • a. Accounts. To use the Service you must create an Account, which you may do with GitHub or with an email address and password. You agree to provide accurate, current, and complete information, to keep it up to date, and to accept these Terms at sign-up. All personal data we collect in relation to your Account is handled under our Privacy Policy.
  • b. Account security. You are responsible for maintaining the confidentiality of your credentials and for all activity that occurs under your Account, including the acts of your Workspace Members and of anyone else you allow to access the Service on your behalf. You must notify us immediately at support@reverse.dev of any suspected unauthorized use. We are not liable for any loss arising from your failure to safeguard your credentials.
  • c. Workspaces and roles. The Service is organized around Workspaces. A Workspace Member's access is determined by that Workspace Member's role and by the Project Settings an Owner configures. A Viewer may use the Advisor and view the documentation and other Workspace content made available to Workspace Members, but may not start agent runs or open or merge pull requests. An Editor may start agent runs and open pull requests unless an Owner has turned off agent runs for the project, and may merge pull requests from within the Service unless an Owner has turned off merging from the Service. Both settings are on by default, so an Editor has these abilities unless an Owner takes them away. Opening a pull request from an agent run is also subject to the GitHub verification described in the GitHub connection and scope of access subsection below. Whatever those settings, an Editor may change project configuration, such as the application root, automatic reparsing, and documentation synchronization, and may create an invitation link through which another person may join the Workspace. An Editor who creates an invitation link selects the role the joining person receives, which may be Editor or Viewer but never Owner and never a role above the Editor's own. Only an Owner may remove a Workspace Member or change a Workspace Member's role, and only an Owner may configure Project Settings. An Owner's own access to the Workspace is not subject to these restrictions.
  • d. Authorization; responsibility for Workspace Members and others. By installing the GitHub App and connecting a Connected Repository, you authorize the Service to access that Connected Repository and to take the actions described in these Terms at the direction of Workspace Members, up to the permissions granted at installation. The person installing the GitHub App represents and warrants that they are authorized to grant that authority for the Connected Repository and its owner. Actions taken in a Connected Repository by any Workspace Member are deemed authorized by you. You further authorize the Service to make information from a Connected Repository available to any person with access to a Slack channel the Workspace maps to that Connected Repository, and to act at the direction of any AI client a Workspace Member authorizes through the Reverse MCP server. You are responsible for whom you invite to a Workspace, for the roles and Project Settings you assign, for whom you allow to access a mapped Slack channel or to connect through the Reverse MCP server, and for all acts and omissions of your Workspace Members and of those other persons.
  • e. GitHub connection and scope of access. The Service connects to your Connected Repositories through the Reverse GitHub App and GitHub authentication. The GitHub App requests read/write access to repository contents and pull requests, and read access to repository metadata, checks, commit statuses, and your email address; GitHub authentication requests your profile, email address, and organization memberships. You are responsible for ensuring that you are permitted to install the GitHub App and connect each Connected Repository. You acknowledge that installing the GitHub App on an organization's repositories generally requires organization-owner permission under GitHub's own controls. Access within the Service is controlled by Workspace roles and Project Settings. The Service does not verify any individual Workspace Member's own GitHub permissions when an agent run is started or when a pull request is merged from within the Service. The Service does verify a Workspace Member's own GitHub permissions on the Connected Repository at the moment that member attempts to open a pull request from an agent run. We intend to remove that verification, after which access within the Service will be governed solely by Workspace roles and Project Settings; we will post updated Terms and notify you as described in Section 1(f) before we do. A pull request that the Service opens in the background for documentation synchronization is not subject to that verification.
  • f. Repository rights. For each Connected Repository and all code and content you or your Workspace Members access, connect, upload, or generate through the Service, you represent and warrant that you and each of your Workspace Members have all rights and permissions necessary to do so and to grant the licenses in Section 6, and that your use, and each Workspace Member's access to and use of each Connected Repository, does not violate any agreement with, or the rights of, your employer, any organization, or any third party.
  • g. Acceptable use. You must use the Service only for lawful purposes and in compliance with these Terms and all applicable laws. Without limitation, you may not, and may not permit or encourage others to: (i) connect any repository, or access, read, or modify any codebase, that you do not have the right to connect, access, or modify; (ii) upload, generate, or deploy malicious code, malware, or other harmful code, or use the Coding Agent or any other feature of the Service to build, distribute, or facilitate harmful or illegal software; (iii) use the Service to infringe or misappropriate the intellectual property, privacy, or other rights of any person, or to engage in any illegal, fraudulent, deceptive, harassing, or abusive activity; (iv) scrape, crawl, or systematically access or copy the Service or its data other than through supported interfaces; (v) circumvent, disable, or interfere with the Service's rate limits, Credit metering, security, or other usage restrictions, or create multiple accounts to obtain free Credits or otherwise access paid features without payment; (vi) probe, scan, or test the vulnerability of, or attack, disrupt, or gain unauthorized access to, the Service or any system or network; or (vii) attempt to do any of the foregoing. We may investigate suspected violations and may suspend or terminate access, remove or disable content, or take any other action we deem appropriate.

5. OUR OBLIGATIONS

  • a. Availability. We will use commercially reasonable efforts to make the Service available, but you acknowledge that the Service — and in particular its beta and proof-of-concept features — may be unavailable, interrupted, changed, or discontinued at any time, with or without notice. We are not liable for any unavailability, including any caused by events beyond our reasonable control.
  • b. Security. We will use reasonable administrative, technical, and physical measures designed to protect the Service and User Content against unauthorized access. These include hashing of account passwords, encryption of stored credentials, secrets, and access tokens, short-lived signed image URLs, isolation of each project's code-execution environment, and verification of the email address before an Account created with an email address may direct changes to a Connected Repository other than a demonstration repository. You acknowledge that no method of transmission or storage is completely secure, particularly given the experimental nature of the Service.
  • c. Support. Support is provided primarily through our documentation and community resources. We may, but are not obligated to, provide additional support to paid users. Before contacting support, please check the documentation, as many common issues are addressed there.

6. YOUR CONTENT

  • a. Responsibility for User Content. As between you and us, you are solely responsible for all User Content, including the contents of your Connected Repositories, your Inputs, and any Outputs, and for all activity conducted through your Account and your Workspace, including activity by your Workspace Members and by any other person given access under Section 4. You agree to indemnify us for any claims arising from your User Content, as set out in Section 14.
  • b. License to operate the Service. You grant us a non-exclusive, worldwide, royalty-free license to host, copy, process, transmit, display, and modify your User Content, and to share it with the Third Party Services (including Third Party AI Services) as needed, in each case solely for the purpose of operating and providing the Service to you during the term. We acquire no rights in your User Content except for this limited license.
  • c. Review and removal. We are not required to review User Content, but we may remove or disable access to any User Content, and suspend or terminate any Account, that we determine violates these Terms, or as otherwise permitted by Section 6(d). We do not guarantee the accuracy, reliability, or quality of any User Content.
  • d. Access and preservation. We may access, preserve, and disclose Account information and User Content if we believe in good faith that it is reasonably necessary to comply with law or legal process, enforce these Terms, respond to claims that content violates the rights of others, respond to your support requests, prevent fraud or security or technical issues, or protect the rights, property, or safety of Reverse, our users, or the public.

7. THE CODING AGENT & DEVELOPER TOOLS

  • a. Autonomous actions; you remain in control. The Coding Agent operates autonomously to draft and propose changes — for example, by opening a working branch, committing changes to that branch, and preparing a pull request. That branch and those commits are created in the Connected Repository before any review takes place. A change reaches the default branch of a Connected Repository only when it is merged in GitHub or, unless an Owner has turned off merging from the Service, when a Workspace Member with the necessary role merges it from within the Service. You acknowledge and agree that you and your Workspace Members are solely responsible for reviewing, testing, and approving any change before deployment or merge. We are not liable for any effect of the Coding Agent's actions on your codebase, systems, or data.
  • b. Attribution of agent actions. Actions the Coding Agent takes in a Connected Repository are performed through the Reverse GitHub App and appear in GitHub under its identity, rather than under the individual Workspace Member's GitHub account. A pull request opened from the Service at a Workspace Member's request identifies that Workspace Member.
  • c. Documentation synchronization. Documentation synchronization is off by default and is turned on for a project by an Owner or an Editor. Where it is on, the Service writes the documentation it generates into the Connected Repository as files, through a pull request that the Service opens in the background. That pull request is not opened at the request of a Workspace Member, appears in GitHub under the Reverse GitHub App's identity as the documentation synchronization action, and may be merged only in GitHub.
  • d. Bring-your-own infrastructure and tools. The Service may let you connect your own third-party infrastructure and submit code from your own local tools or agents. Any such third-party infrastructure and tools are Third Party Services that you are solely responsible for, including compliance with their terms and the security of any credentials or access tokens. You must keep any ingest, overlay, or project tokens confidential and treat them as you would a password. Where the Reverse MCP server is available to your Workspace, the AI clients you connect to it are Third Party Services that you are solely responsible for, and content from your Connected Repositories may be made available to them. A client connected through the Reverse MCP server authenticates as the Workspace Member who authorized it and may reach that Workspace Member's projects with that Workspace Member's level of access. A Workspace Member may review the applications they have connected, and revoke a connection, in their account settings.
  • e. Slack integration. Where the Slack integration is available, an Owner may connect the Workspace's own Slack workspace to the Service, and an Owner or an Editor may map Slack channels to Connected Repositories. Once a channel is mapped, a Workspace Member of any role may ask the Advisor questions in that channel. The Advisor's answer is posted in the channel, so any person with access to the channel can see content derived from the code in the mapped Connected Repository, whether or not that person is a Workspace Member. You are responsible for controlling who has access to a mapped channel. Slack is a Third Party Service, and its own terms and privacy practices govern the messages exchanged there.
  • f. Public share links. Where an Owner or an Editor enables a public share link for a project, the documentation generated for that project is available to anyone who has the link, without password, review, or expiration. That documentation routinely includes file paths, function and entity names, short excerpts of code, and the commit from which it was generated. A plain-text version of it is published at the same address with /llms.txt added to the end, and is accessible to automated crawlers. Revoking the link is the only way to withdraw access. You are responsible for deciding whether to enable a public share link and for the content it exposes.
  • g. Experimental features. You acknowledge that the Service and its features, including those identified as beta or proof-of-concept, are provided on an experimental basis, may be restructured or removed without notice, and are subject to the disclaimers in Section 14.

8. OWNERSHIP

  • a. The Service. Except for the limited license in Section 3, we retain all right, title, and interest in and to the Service, the Site, our documentation, and all Updates, including all related intellectual property and Marks.
  • b. Your content. Except for the limited licenses granted to us in these Terms, as between the parties you retain all right, title, and interest in and to your User Content, including your code, Inputs, and Outputs.
  • c. Usage Information. We own all Usage Information. Usage Information excludes personal data and the substance of your User Content, and may include aggregated and de-identified information used for analytics, monitoring, and improving the Service.
  • d. Marks. Each party retains all right, title, and interest in and to its Marks. You may not use the Reverse Marks without our prior written consent, except to accurately refer to the Service. If you enable any public sharing feature, you grant us a limited, non-exclusive license to display your Marks solely as needed to provide that feature.
  • e. Feedback. Any Feedback you provide is voluntary, and you grant us a perpetual, irrevocable, royalty-free license to use it in any lawful manner, without any obligation to you.

9. THIRD-PARTY MATERIAL

  • a. Third Party Services. You are responsible for complying with the terms of all Third Party Services applicable to your use of the Service, including GitHub, Third Party AI Services, and any bring-your-own infrastructure. We are not responsible for the performance of, or any act or omission of, any Third Party Service.
  • b. Third-party content. We may make third-party content available through the Service. We are not responsible for its accuracy or completeness and may remove it without notice if required or if we believe it may violate law or the rights of others.
  • c. Open-source software. Certain components provided with or accessed through the Service are subject to OSS licenses and are governed by those licenses, not these Terms, except for Section 14.

10. REVERSE AI TOOLS

  • a. Access. Subject to these Terms, we provide access to the Reverse AI Tools, including the Advisor, the Coding Agent, and documentation generation. The Reverse AI Tools use Third Party AI Services to generate Output in response to your Input. You acknowledge that we share your Input (including relevant code from your Connected Repositories) with those Third Party AI Services to generate Output.
  • b. Ownership of Input and Output. As between the parties and to the extent permitted by law, you own your Input, and we do not claim ownership of your Output. We do not represent or warrant that any Output is protectable by intellectual-property rights, or that it does not incorporate, infringe, or misappropriate the rights of any third party. Because of the nature of AI, Output may not be unique, and other users may receive similar Output.
  • c. Your responsibility. YOU ACKNOWLEDGE THAT AI OUTPUT MAY BE INACCURATE OR INCOMPLETE. WE DO NOT WARRANT THAT ANY OUTPUT WILL BE ACCURATE, COMPLETE, SECURE, NON-INFRINGING, OR FIT TO DEPLOY. YOU ARE SOLELY RESPONSIBLE FOR REVIEWING, TESTING, AND VALIDATING ALL OUTPUT BEFORE USE, AND FOR ENSURING THAT YOUR USE COMPLIES WITH APPLICABLE LAW AND THESE TERMS. WE ARE NOT LIABLE FOR ANY DECISION OR ACTION YOU TAKE BASED ON OUTPUT.
  • d. Third Party AI Services. The Reverse AI Tools are powered by Third Party AI Services, including Anthropic (Claude) and OpenAI, which are not controlled by us. When we process your Input and Output using our own accounts with these providers, they act as our service providers and do not use your data to train their models. If you choose to connect your own third-party AI account or API key (for example, under a bring-your-own-key option), or to connect an AI client to the Reverse MCP server, your use of that account or client is governed by your agreement with the relevant provider, whose terms may permit the provider to use your Input and Output, including to train its models. It is your responsibility to review and comply with those terms, and your use of such services is at your own risk.
  • e. Improvement of the Service. We do not use your Input or Output — including the contents of your Connected Repositories — to train artificial-intelligence models. We may use usage and telemetry data (such as parse times, error and failure signals, and other performance metrics), any feedback you submit, and aggregated and de-identified data, to operate, secure, evaluate, and improve the Service, in accordance with our Privacy Policy.

11. FEES & CREDITS

  • a. Fees and Credits. Every new user starts with a free allotment of Credits; no payment or key is required to use your free Credits. When your free Credits are used up, you may continue by choosing one of two options: (i) a one-time Platform Fee under which you connect your own Anthropic API key for your Workspace; or (ii) prepaid Credit bundles on a pay-as-you-go basis. Credits are held at the Workspace level as a shared pool. Any Workspace Member may consume Credits from that pool, including by using the Advisor, whatever their role and whether or not they may start agent runs. Credits are not allocated to individual Workspace Members. A question asked through the Slack integration in a mapped channel is charged as an Advisor turn against the Credits of the Workspace that owns the mapped Connected Repository, whatever the role of the Workspace Member who asks. Where a Workspace connects its own AI provider key under the Platform Fee option, the Workspace's usage under that key is billed through that key rather than drawn from its Credits. For more information on current pricing and Credit costs, please visit the pricing information or FAQ page at https://reverse.dev.
  • b. No refunds. ALL PAYMENTS FOR THE PLATFORM FEE AND FOR CREDITS ARE FINAL AND NON-REFUNDABLE, EXCEPT WHERE REQUIRED BY APPLICABLE LAW. CREDITS HAVE NO CASH VALUE AND ARE NOT REDEEMABLE FOR MONEY.
  • c. Taxes. Our prices are exclusive of taxes. You are responsible for all applicable sales, use, and similar taxes, which will be added where required by law.
  • d. Payment processing. We use Stripe to process payments. By providing payment information, you authorize us and Stripe to charge your Payment Provider for the amounts due, and you agree to Stripe's applicable terms and privacy policy. Your Payment Provider agreement governs your use of the designated payment method.
  • e. Responsibility for Workspace amounts. A Workspace Member may purchase Credits using their own payment method. The payment method saved for a Workspace is the Owner's. A one-click purchase against that saved payment method may be made only by that Owner, and an automatic top-up is charged to that Owner even where another Workspace Member's use of the Service triggers it. The Owner, or the entity on whose behalf that Owner purchases, is responsible for all amounts due for the Workspace, including amounts for Credits consumed by any Workspace Member.

12. CONFIDENTIAL INFORMATION

  • a. General. Each party may have access to the other's non-public or proprietary information that is marked or should reasonably be understood to be confidential ("Confidential Information"). Confidential Information remains the property of the disclosing party.
  • b. Use. Each party will (i) use Confidential Information only to perform under these Terms; (ii) disclose it only to personnel and advisers who need it and are bound by similar obligations; and (iii) protect it using at least a reasonable degree of care. These obligations continue for three (3) years after the term, and for trade secrets, for as long as they remain trade secrets.
  • c. Exceptions. Confidential Information does not include information that is or becomes public through no fault of the recipient, is rightfully obtained without confidentiality obligations, or is independently developed. A party may disclose Confidential Information as required by law, provided it gives reasonable prior notice where legally permitted.

13. TERM AND TERMINATION

  • a. Term. These Terms apply for as long as you access the Site or use the Service.
  • b. Termination by us. We may suspend or terminate your Account or access at any time, with or without notice, if you materially breach these Terms, if payment fails, if we reasonably believe your use poses a risk to the Service or others, or if we are required to do so by law. Because the Service is experimental, we may also discontinue the Service, in whole or in part, at any time.
  • c. Termination by you. You may terminate these Terms at any time by ceasing to use the Service and closing your Account.
  • d. Effect of termination. Upon termination, all licenses granted to you end. Sections 6 and 8 through 17 survive termination. Non-refundable amounts remain non-refundable as set out in Section 11. Where a Workspace Member other than the last remaining Owner of a Workspace closes their Account, the Workspace and its records remain available to the other Workspace Members. Where the last remaining Owner of a Workspace closes their Account, the Workspace's projects, agent runs, proposed code changes, documentation, share links, and memberships are deleted thirty (30) days later.

14. DISCLAIMER; LIMITATION OF LIABILITY; INDEMNIFICATION

  • a. WARRANTY. THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTY OF ANY KIND. WE MAKE NO WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE OR ANY OUTPUT WILL BE ERROR-FREE, SECURE, UNINTERRUPTED, ACCURATE, OR COMPLETE.
  • b. LIMITATION OF LIABILITY. EXCEPT IN THE CASE OF GROSS NEGLIGENCE, WILLFUL MISCONDUCT, OR MISAPPROPRIATION OF INTELLECTUAL PROPERTY, IN NO EVENT WILL (a) OUR TOTAL LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS EXCEED THE GREATER OF THE AMOUNTS YOU PAID US IN THE TWELVE (12) MONTHS BEFORE THE CLAIM AND ONE HUNDRED U.S. DOLLARS ($100); OR (b) EITHER PARTY BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED. THESE LIMITATIONS APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.
  • c. INDEMNIFICATION. You will indemnify, defend, and hold us harmless from any claim, action, or proceeding arising out of or related to (a) your breach of these Terms, (b) your User Content, including your Connected Repositories and your use of Output, (c) your violation of any law or the rights of any third party, or (d) the acts or omissions of your Workspace Members and of any other person given access under Section 4, and the use of the Service through your Workspace, including any change made to a Connected Repository at the direction of a Workspace Member.

15. INFRINGEMENT & TAKEDOWN

  • a. Reporting infringement. We respect the intellectual-property rights of others. If you believe content made available through the Service — including through a public share link or another publicly accessible page generated by the Service — infringes your copyright or other rights, please notify our designated agent in writing at support@reverse.dev, or at Bubble Group, Inc., 22 West 21st Street, 2nd Floor, New York, NY 10010, ATTN: Reverse Legal.
  • b. Notice requirements. A notice must include: (i) your physical or electronic signature; (ii) identification of the work claimed to be infringed; (iii) identification of the allegedly infringing material and information sufficient to locate it; (iv) your contact information; (v) a statement of your good-faith belief that the use is not authorized; and (vi) a statement, under penalty of perjury, that the information is accurate and that you are authorized to act. We may forward notices, including your contact information, to the person who provided the material.
  • c. Repeat infringers. We may remove allegedly infringing content and terminate the accounts of repeat infringers, in each case in our discretion and without prior notice.

16. DISPUTE RESOLUTION

  • a. Governing law. These Terms are governed by the laws of the State of New York, without regard to its conflict-of-laws rules.
  • b. Arbitration. Any dispute that cannot be brought in small-claims court will be resolved by binding, confidential arbitration in New York, New York, before a single commercial arbitrator of the American Arbitration Association under its Commercial Arbitration Rules.
    • (i) YOU ARE GIVING UP YOUR RIGHT TO GO TO COURT AND TO A TRIAL BY JUDGE OR JURY, EXCEPT FOR MATTERS THAT MAY BE TAKEN TO SMALL-CLAIMS COURT.
    • (ii) ANY CLAIMS MUST BE BROUGHT IN YOUR INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS OR REPRESENTATIVE PROCEEDING. THE ARBITRATOR MAY NOT CONSOLIDATE CLAIMS OR AWARD CLASS-WIDE RELIEF.
    • (iii) You may opt out of this arbitration agreement by sending written notice to support@reverse.dev, or to Bubble Group, Inc., 22 West 21st Street, 2nd Floor, New York, NY 10010, ATTN: Reverse Legal, within thirty (30) days after first becoming subject to it. Your notice must include your name, the email address associated with your Account, and a clear statement that you want to opt out.
    • (iv) Notwithstanding the above, either party may bring an individual action in small-claims court, and claims of infringement or misappropriation of intellectual property may be brought in the state or federal courts located in New York County, New York.
  • c. Severability of this Section. If the class-action waiver is found unenforceable, the remainder of this Section 16 will be null and void and disputes will be brought exclusively in the state or federal courts located in New York County, New York.

17. MISCELLANEOUS

  • a. Assignment. You may not assign these Terms without our prior written consent. We may assign these Terms in connection with a merger, acquisition, or sale of assets. These Terms bind the parties' permitted successors and assigns.
  • b. Export. You represent that you are not located in an embargoed country or on any government denied-party list, and you will not use the Service in violation of export-control laws.
  • c. Severability. If any provision is held unenforceable, the remaining provisions remain in effect.
  • d. Attribution. We may identify you as a user in reasonable marketing materials, consistent with any brand guidelines you provide.
  • e. Waiver. A waiver of any breach is not a waiver of any other breach.
  • f. Entire agreement. These Terms, together with the Privacy Policy, are the entire agreement between the parties regarding the Service and supersede prior communications. "Includes" means "includes without limitation." Headings are for reference only.
  • g. Existing users. If you accessed the Service before the effective date of these Terms, these Terms apply to your continued use of the Service from that date.
  • h. Data processing. If our provision of the Service involves processing personal data on your behalf under applicable privacy law, and we make a Data Processing Addendum available, that Data Processing Addendum will govern such processing and, once agreed, will be incorporated into these Terms.