Skip to main content

Product Terms

How the Productmind service works under the agreement - plans and usage, coding sessions on your repositories, AI output, integrations, acceptable use, support, and your data when you leave.

Type
Service agreement
Effective
Last updated

These Product Terms form part of the Agreement between Productmind and the Customer and complement the General Terms. Capitalized terms are defined in the Definitions.

1. Scope

1.1 These Product Terms describe how the Service is provided and the rules for using it. They apply to every Plan, including the free Plan, unless an Order Form states otherwise.

1.2 Where the Documentation describes how a feature works, that description applies together with these Product Terms. It describes features; it does not add commitments beyond those in the Agreement.

2. The Service

2.1 The Service helps teams gather product knowledge and requirements, turn them into specifications, tasks and releases, and run AI agents that work on the Customer's code. Depending on the Plan, it includes:

  1. product management: features, specifications, tasks, bug reports, feature requests, notes, decisions, releases and a knowledge base;
  2. customer research and feedback: customer interactions, meeting notes, an embeddable feedback widget, and AI-led interviews by email, voice or a meeting notetaker;
  3. AI assistants that read and write in the Customer's Workspaces;
  4. Coding Sessions, live previews, scans of the Customer's applications, and pull requests on the Customer's repositories; and
  5. access through the web application, the API, the MCP server, the command-line agent, the browser extension and the mobile application.

2.2 Which features, limits and allowances apply to the Customer's Organization depends on its Plan, as set out on the Pricing Page or in an Order Form.

3. Organizations, Workspaces and Seats

3.1 The Customer's Organization is administered by its Owners and administrators, who decide who becomes a member, what role each member has, which Workspaces exist, and which Integrations are connected. The Customer is responsible for those choices.

3.2 On a Plan priced per user, every active member counts as a Seat. A member added during a Billing Period is charged pro rata from the day they are added. The Plan may cap the number of members.

3.3 The Customer can require single sign-on and multi-factor authentication for its Organization where its Plan includes them, and is responsible for the security of its own identity provider.

4. Plans, usage and the Wallet

4.1 A Plan may include allowances per Billing Period (such as AI Credits, Sandbox hours or interview minutes) and may meter some usage from the first unit. Usage beyond an allowance, or metered usage, is charged at the rates of the Customer's Plan on the Pricing Page or in its Order Form. The usage-based Fees include:

  1. AI Credits consumed by the Service's agents and by Coding Sessions on Productmind's runners;
  2. a fee per Coding Session run on a machine of the Customer;
  3. Sandbox hours, by Sandbox size;
  4. voice interview and meeting notetaker minutes; and
  5. Productmind Architect review time, quoted and accepted per request.

4.2 Usage-based Fees are debited from the Organization's Wallet as the usage is recorded, unless an Order Form provides for invoicing. The Customer tops up the Wallet with a payment, and may switch on automatic top-ups at a threshold and an amount it chooses. The Service shows the Wallet balance and the usage that drew on it.

4.3 The Service may require a payment method to be added before usage that would be charged starts. It refuses or stops usage that would be charged when the Wallet does not cover it, when the Customer has paused spending, or when a Plan limit is reached. A Coding Session stopped for this reason saves its work in progress to its branch where it can, and can be continued once the Wallet is topped up.

4.4 The Service measures usage, including AI Credits, with its own meters. The Customer can review its usage in the Service, and may contest a charge as provided in clause 5.10 of the General Terms.

4.5 Where the Customer connects its own AI model key and its Plan allows it, the model provider bills the Customer directly for that use, and the AI Credits the Service records for it are not charged.

5. Coding Sessions and your repositories

5.1 To run Coding Sessions, the Customer connects its repositories through its git provider and authorizes the access the Service needs: to read the code, to create branches, to push commits and to open, update and merge pull requests. The Service acts on a repository only within the access the Customer and its Authorized Users grant, and opens pull requests through the git connection of the person who started the work, or the Workspace's connection otherwise.

5.2 A Coding Session runs either on Productmind's cloud runners, in an isolated container per session, or on a machine of the Customer through the command-line agent. On the Customer's machine, the agent uses the Customer's own AI coding tools and their providers' terms apply to that use.

5.3 A Coding Session may run the commands, tests and services of the Customer's application, and may use the environment variables and secrets the Customer configures for its Sandbox. The Customer decides what it configures there, and should configure only what a session needs.

5.4 Merging a pull request, deploying, and releasing remain the Customer's decision. The Service can merge, tag and release on the instruction of an Authorized User, through the access the Customer has granted. The Customer is responsible for reviewing changes before they reach its production systems.

5.5 Where the Customer starts an application from a Productmind template, the Service creates its repository as a private repository in an organization Productmind controls on GitHub, and connects it to the Customer's Workspace. The code in that repository is Customer Data. Before the application, its Workspace or the Organization is deleted, the Customer may ask Productmind at legal@productmind.ai to transfer the repository to a GitHub organization the Customer controls, or to provide a copy of it.

5.6 Productmind is not responsible for the Customer's code or for a container image the Customer supplies for a Sandbox. Their security, the dependencies they use, the secrets they contain and what they do when a Coding Session runs them are the Customer's responsibility, as are the settings of its repositories at its git provider, such as branch protection and required reviews. Productmind remains responsible for the runners it provides, as described in Annex 2 of the DPA.

6. AI Output

6.1 AI Output is generated by AI models from the Customer's instructions and Customer Data. It can be inaccurate, incomplete or inappropriate for the Customer's purpose, and similar output may be generated for others. The Customer is responsible for reviewing AI Output, including code, before relying on it, merging it or publishing it.

6.2 As provided in clause 8.2 of the General Terms, the Customer owns the AI Output generated for it, to the extent rights in it exist.

6.3 The AI models the Service uses are provided by the model providers listed on the Subprocessors page, or by the Customer's own provider where it connects its own key. Productmind may change the models it uses to provide a feature.

7. Integrations and Third-Party Services

7.1 The Customer may connect Integrations, such as its git provider, issue tracker, support desk, chat tool, CRM, MCP servers, identity provider or its own AI model key. When it does, the Customer instructs Productmind to exchange data with that Third-Party Service as the Integration requires. The Third-Party Service's own terms govern the Customer's use of it, and its provider is not Productmind's Subprocessor.

7.2 Productmind is not responsible for a Third-Party Service, for changes to its interface that affect an Integration, or for what it does with data the Customer sends it. Productmind may stop supporting an Integration if its provider changes or ends its service or no longer allows the connection.

7.3 Cloud accounts the Customer connects or has Productmind create, where its Plan includes them, are subject to the additional terms the Service presents when the account is connected or requested.

8. Acceptable use

8.1 The Customer and its Authorized Users must not use the Service to:

  1. break the law, or infringe the rights of others, including their Intellectual Property Rights and privacy;
  2. process special categories of Personal Data, or data relating to criminal convictions, unless the Customer has a lawful basis and has agreed suitable safeguards with Productmind in writing;
  3. create or spread malware, or attack, probe or test the security of any system without its owner's authorization;
  4. send spam or unsolicited communications, including through interviews or notifications, or contact people the Customer has no lawful basis to contact;
  5. generate content that is unlawful, defamatory, or that exploits or harms children;
  6. circumvent the Service's limits, metering, billing or security controls, share accounts or credentials, or access the Service by means other than its interfaces;
  7. copy, reverse engineer or resell the Service, or use it to build a competing product, except as the law allows; or
  8. use AI Output in a way that breaches the usage policies of the model providers that produced it.

8.2 The Customer may not load-test, penetration-test or scan the Service without Productmind's prior written agreement.

8.3 If the Customer embeds the feedback widget, records meetings or runs interviews, it is responsible for informing the people concerned and for having a lawful basis, including any consent required, for collecting their data and for recording them.

8.4 Productmind may act on a breach of these Acceptable Use Rules as described in section 7 of the General Terms.

9. Ending the Service and your data

9.1 During the Subscription Term, the Customer can retrieve its Customer Data through the Service, its API and its MCP server, and can export audit logs where its Plan includes them.

9.2 The Customer can delete Workspaces itself. Data in a deleted Workspace is removed as described in the DPA.

9.3 To end the Agreement entirely, an Owner asks for the deletion of the Organization by writing to legal@productmind.ai. Productmind schedules the deletion, which takes effect after a grace period of 30 days during which the Organization is suspended and the deletion can still be cancelled. After the grace period, the Organization and its Customer Data are deleted as described in the DPA.

9.4 Productmind keeps the records the law requires it to keep, such as invoices and the bookkeeping behind them, and the audit records of destructive changes, after the Organization is deleted, for as long as that obligation or purpose lasts.

10. Early Access Features

10.1 Productmind may offer Early Access Features to the Customer. Using one is optional. Early Access Features may change or be withdrawn at any time, may be less reliable, and are provided without warranty or service commitment.

10.2 Usage of an Early Access Feature may be charged as its description in the Service states. Productmind tells the Customer before it starts charging for an Early Access Feature that was free.

11. Support

11.1 Every Plan includes Support through the Support center in the Service: the Documentation, the support assistant, and requests to the Productmind support team. Productmind handles requests in a reasonable time, during Business Days, without guaranteed response times unless an Order Form sets them.

11.2 When the Customer asks for a human review of a session, the request gives the assigned Productmind Architect temporary access to that session. The access is limited to what the request needs, is recorded, and ends when it expires, when the request is closed or when the Customer revokes it. The Customer can switch this access off for its Organization.

11.3 A Productmind Architect review is quoted before it starts, and the Customer accepts the quote before any time is charged.

12. Availability

12.1 Productmind uses commercially reasonable efforts to keep the Service available and performing, and to schedule maintenance that interrupts it outside the Customer's business hours where possible.

12.2 The Service depends on hosting, AI model, payment and other providers. Productmind is not responsible for unavailability caused by them, by the public internet, or by the Customer's systems, Integrations or own providers.

12.3 No service level, availability percentage or service credit applies unless an Order Form sets one.