Skip to main content

Data Processing Agreement

How Productmind processes personal data on your behalf as a processor under the GDPR - instructions, security, breaches, subprocessors, international transfers, deletion and audits.

Type
Data protection
Effective
Last updated

This Data Processing Agreement (the "DPA") forms part of the Agreement between Architected B.V., trading as Productmind ("Productmind"), and the Customer, and applies whenever Productmind processes Customer Personal Data. It is accepted together with the General Terms and needs no separate signature; a countersigned copy is available on request at legal@productmind.ai. Capitalized terms are defined in the Definitions.

1. Scope and roles

1.1 The terms "controller", "processor", "data subject", "personal data breach", "processing" and "supervisory authority" have the meanings given to them in the GDPR. "Standard Contractual Clauses" means the clauses annexed to Commission Implementing Decision (EU) 2021/914, and "UK Addendum" means the International Data Transfer Addendum issued by the UK Information Commissioner.

1.2 For Customer Personal Data, the Customer is the controller and Productmind is its processor. Where the Customer itself processes the data as a processor for its own customers, Productmind is its subprocessor, and the Customer confirms that its controller has authorized the processing under this DPA, including Productmind's Subprocessors.

1.3 Productmind processes the Personal Data it needs to run the Customer's account, billing, security and communications, and Usage Data, as a controller. That processing is described in the Privacy Notice and is not governed by this DPA.

1.4 Annex 1 describes the processing: its subject matter, nature, purpose and duration, and the categories of data and data subjects.

2. Instructions

2.1 Productmind processes Customer Personal Data only on the Customer's documented instructions. The Customer instructs Productmind to process it to provide the Service in accordance with the Agreement, including as the Customer configures and uses the Service: the Workspaces it creates, the agents and Coding Sessions it runs, and the Integrations it connects, which Productmind exchanges data with on the Customer's behalf. Further instructions must be agreed in writing.

2.2 Productmind informs the Customer without undue delay if, in its opinion, an instruction infringes Applicable Data Protection Law, and may suspend that processing until the instruction is confirmed or changed.

2.3 Where Union or Member State law requires Productmind to process Customer Personal Data otherwise, Productmind informs the Customer of that requirement before processing, unless the law prohibits it.

3. The Customer's obligations

3.1 The Customer is responsible for the lawfulness of the processing it instructs, including having a lawful basis, informing data subjects, and obtaining any consent required, in particular for recording meetings and calls, running interviews, and collecting feedback through the feedback widget.

3.2 The Customer does not submit special categories of Personal Data, or data relating to criminal convictions and offences, unless permitted under the Acceptable Use Rules.

3.3 The Customer is responsible for the settings it controls: who it admits to its Organization and with which role, its sign-in requirements, the Integrations and model keys it connects, and the data it configures for Coding Sessions.

4. Confidentiality

Productmind ensures that every person it authorizes to process Customer Personal Data is bound by an obligation of confidentiality, contractual or statutory, and processes the data only as needed to provide the Service.

5. Security

5.1 Taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing and its risks, Productmind implements and maintains the technical and organizational measures described in Annex 2 to ensure a level of security appropriate to the risk.

5.2 Productmind may update these measures as technology and risks evolve, provided that the overall level of security is not reduced.

6. Personal data breaches

6.1 Productmind notifies the Customer of a personal data breach affecting Customer Personal Data without undue delay, and in any event within 48 hours, after becoming aware of it.

6.2 The notification describes, as far as then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, its likely consequences, the measures taken or proposed, and a contact point. Where not all information is available at once, Productmind provides it in phases without undue delay.

6.3 Productmind takes reasonable steps to contain and remedy the breach, and assists the Customer in meeting its obligations to notify the supervisory authority and data subjects. Notifying a breach is not an acknowledgement of fault or liability.

7. Subprocessors

7.1 The Customer gives Productmind general written authorization to engage Subprocessors. The current Subprocessors, with their purpose and location, are listed on the Subprocessors page.

7.2 Productmind notifies the Customer of an intended addition or replacement of a Subprocessor at least 30 days before it starts processing Customer Personal Data, by email to the Organization's Owners and by updating the Subprocessors page.

7.3 The Customer may object to the change in writing to legal@productmind.ai within 30 days of the notice, on reasonable grounds relating to data protection. The parties will discuss the objection in good faith. If they cannot resolve it, the Customer may terminate the affected Plan before the change takes effect, and receive a pro rata refund of prepaid Fees for the period after termination and of its unused prepaid Wallet credit.

7.4 Where a Subprocessor must be replaced urgently, for example because it ceases its service or for security reasons, Productmind notifies the Customer as soon as possible, and the Customer's right to object applies from that notice.

7.5 Productmind imposes on each Subprocessor, by written contract, data protection obligations that offer at least the same level of protection as this DPA, and remains liable to the Customer for its Subprocessors' performance of those obligations.

8. International transfers

8.1 Productmind stores Customer Personal Data in the European Union, in Amazon Web Services' Frankfurt region. Some Subprocessors, including AI model providers, process it in countries outside the European Economic Area when the Service uses them. The Subprocessors page lists where each one processes data.

8.2 Productmind transfers Customer Personal Data outside the European Economic Area only where the recipient is in a country covered by an adequacy decision, including a recipient certified under the EU-U.S. Data Privacy Framework, or under appropriate safeguards, such as the Standard Contractual Clauses (Module Three, processor to processor) concluded with the Subprocessor, together with any supplementary measures a transfer impact assessment shows to be needed.

8.3 Where the Customer is established outside the European Economic Area in a country without an adequacy decision, and the law requires it, the Standard Contractual Clauses (Module Four, processor to controller) apply to Productmind's transfers to the Customer and are incorporated by reference, with the Netherlands as the governing law and the courts of Amsterdam as the competent courts.

8.4 For Personal Data subject to the UK GDPR, the UK Addendum applies to those transfers. For Personal Data subject to the Swiss Federal Act on Data Protection, references to the GDPR are read as references to that Act and the Swiss Federal Data Protection and Information Commissioner is the competent authority.

8.5 If a public authority requests access to Customer Personal Data, Productmind notifies the Customer unless the law prohibits it, assesses the lawfulness of the request and challenges it where there are reasonable grounds, and discloses no more than the request strictly requires.

9. Assistance

9.1 Productmind forwards to the Customer any request from a data subject concerning Customer Personal Data and does not answer it itself, except to refer the data subject to the Customer. Taking into account the nature of the processing, Productmind assists the Customer with appropriate technical and organizational measures in responding to such requests, primarily through the features of the Service that let the Customer find, correct, export and delete data.

9.2 Productmind provides the Customer with reasonable assistance, using the information available to it, with data protection impact assessments and prior consultations with a supervisory authority concerning the Service. Productmind may charge its reasonable costs for assistance beyond providing its standard documentation.

10. Return and deletion

10.1 During the Subscription Term, the Customer can retrieve Customer Personal Data through the Service, its API and its MCP server.

10.2 When the Customer deletes a Workspace, it is no longer accessible. Its knowledge-base files and its assistant conversation data are erased 30 days after the deletion, and its remaining records are erased when the Organization is deleted, or earlier at the Customer's written request.

10.3 When the Organization is deleted at the end of the Agreement, as described in section 9 of the Product Terms, Productmind deletes Customer Personal Data from its production systems after the grace period of 30 days. Copies in backups are overwritten as the backups expire, within 35 days of that deletion. Coding Session transcripts expire 60 days after they are written in any case.

10.4 Productmind may keep Customer Personal Data only where Union or Member State law requires it to, such as the invoicing records Dutch tax law requires it to keep, and the audit records of destructive changes, for the period that obligation or purpose lasts, and protects it as this DPA requires during that period.

10.5 On request, Productmind confirms the deletion in writing.

11. Audits and information

11.1 Productmind makes available to the Customer the information necessary to demonstrate compliance with Article 28 GDPR and this DPA, including its security documentation and its answers to reasonable security questionnaires, subject to confidentiality.

11.2 Where that information does not reasonably suffice, or a supervisory authority requires it, the Customer may audit Productmind's compliance with this DPA, itself or through an independent auditor bound by confidentiality who is not a competitor of Productmind, no more than once in any twelve months (except after a personal data breach, or where a supervisory authority requires it), on at least 30 days' written notice, during Business Days, and within a scope agreed in advance that does not compromise other customers' data or Productmind's security. The Customer bears its own costs and reimburses Productmind's reasonable costs for time beyond one Business Day.

11.3 Productmind cooperates with a supervisory authority in the performance of its tasks.

12. AI models

12.1 Productmind does not use Customer Personal Data to train or fine-tune AI models.

12.2 The AI model providers the Service uses are Subprocessors, engaged and listed in accordance with section 7. They receive Customer Personal Data only as part of the requests the Service makes to generate AI Output for the Customer, under commercial terms that do not permit them to use it to train their models.

12.3 Where the Customer connects its own AI model key, or runs a Coding Session on its own machine with its own AI tools, its own provider processes that data under the Customer's own terms with it, and is not Productmind's Subprocessor.

13. Liability

Each party's liability under or in connection with this DPA is subject to the limitations and exclusions in section 13 of the General Terms, to the extent Applicable Data Protection Law allows.

14. Duration and precedence

14.1 This DPA applies for as long as Productmind processes Customer Personal Data, including after the Agreement ends until the data is deleted.

14.2 On the processing of Customer Personal Data, this DPA prevails over the other documents of the Agreement, except an Order Form that expressly departs from it. Where the Standard Contractual Clauses apply, they prevail over this DPA.

14.3 This DPA is governed by the law that governs the Agreement, and disputes are resolved as provided in section 20 of the General Terms.

Annex 1: Description of the processing

The parties. The data exporter is the Customer, as controller (or as processor for its own controller), its contact being the Owners of its Organization. The data importer is Architected B.V., trading as Productmind, Amsterdam, the Netherlands, as processor, its contact being legal@productmind.ai.

Categories of data subjects.

  • The Customer's Authorized Users.
  • The Customer's own customers, prospects, users and other contacts whose data the Customer records in the Service, including participants in interviews, meetings and calls, and people who send feedback through the feedback widget.
  • People named or described in the content the Customer submits, including authors of commits in the Customer's repositories.

Categories of personal data.

  • Identification and contact details: names, email addresses, job titles, companies.
  • Content the Customer submits or connects: product and customer research content, conversations, feedback, interview answers, meeting recordings and transcripts, call audio, documents, attachments and screenshots.
  • Source code and repository metadata, such as commit authors and messages.
  • Prompts and AI Output.
  • Technical data collected by the feedback widget and the Service on the Customer's behalf, such as browser and page information.

Special categories of data. None are intended. See clause 3.2.

Nature and purpose of the processing. Hosting, storage and display of Customer Data; processing with AI models to generate, summarize, classify, search and index content; running Coding Sessions and previews on the Customer's code; exchanging data with the Integrations the Customer connects; sending notifications and interview messages the Customer initiates; and providing Support. All to provide the Service under the Agreement.

Frequency. Continuous, for as long as the Customer uses the Service.

Duration. The Subscription Term, followed by the deletion periods in section 10.

Subprocessors. As listed on the Subprocessors page, for the purposes and in the locations stated there.

Annex 2: Technical and organizational measures

Access to the Service.

  • Sign-in by password (stored only as a salted bcrypt hash), with Google, or through the Customer's single sign-on (SAML or OpenID Connect) where its Plan includes it.
  • Multi-factor authentication with an authenticator app, available on every Plan, which the Customer can require for its Organization.
  • Role-based permissions per Organization and Workspace, enforced by the API for every request; sessions and tokens that expire and can be revoked.

Separation of customers.

  • Every Workspace belongs to one Organization, and every request is scoped to a Workspace named in its path.
  • On the Early Plan, Workspaces share a database schema and are separated in every query. On the Start and Scale Plans, each Workspace has its own database schema. On the Enterprise Plan, the Organization has a dedicated database.
  • Each cloud Coding Session runs in its own container with credentials scoped to that session.

Encryption.

  • All connections to the Service use TLS, with HTTP Strict Transport Security; connections between the Service's components and its database use TLS.
  • Databases, object storage, queues and the parameter store are encrypted at rest with AES-256.
  • Credentials for the Customer's Integrations are encrypted by the application with AES-256-GCM before storage, under a key held in AWS Key Management Service with automatic rotation, and are never returned by the API.

Infrastructure.

  • Hosted on Amazon Web Services in the Frankfurt region, in private networks, with least-privilege roles for each component.
  • Security headers and a content security policy on the web application.

Logging and monitoring.

  • An audit log of changes in each Organization, kept for 730 days by default (configurable).
  • A log of every API request.
  • AWS CloudTrail and threat detection across Productmind's AWS accounts.

Availability and backups.

  • Point-in-time recovery for the primary database for 30 days, and for other databases for 35 days.
  • Deletion protection on production databases.

Data minimization.

  • Coding Session transcripts expire after 60 days.
  • Secrets configured for a Coding Session are fetched by its runner when needed and never placed on a queue.

People and processes.

  • Access to production systems is limited to authorized personnel who need it.
  • Everyone with access is bound by confidentiality.
  • The Productmind support team reaches a Customer's session only through a time-limited, recorded grant that the Customer's request creates and can revoke.
  • A documented incident response process, and a vulnerability disclosure contact at security@productmind.ai.