Data Processing Addendum
Last updated: November 14, 2026
This DPA applies automatically to every proto[docs] customer, with no signature needed. Customers who need a signed copy can request one at help@prototypd.dev. This Data Processing Addendum (including its annexes, this "DPA") is between the customer that accepts the proto[docs] Terms of Service or signs an Order Form ("Customer") and prototypd LLC, a Kansas limited liability company ("Provider") (each a "Party" and together the "Parties"). It forms part of the proto[docs] Terms of Service, or the signed agreement that incorporates them (the "Agreement"), and takes effect when the Agreement does.
1. Definitions
The following terms have the meanings set out below for purposes of this DPA. Any capitalized terms not defined in this DPA have the meanings given in the Agreement.
Affiliate means any entity that directly or indirectly controls, is controlled by, or is under common control with the subject entity, where "control" refers to the power to direct or cause the direction of the subject entity, whether through ownership of voting securities, by contract or otherwise.
Applicable Data Protection Laws means the privacy, data protection and data security laws and regulations applicable to Provider's Processing of Personal Data under the Agreement, including, the State Privacy Laws.
Controller means the entity that, alone or jointly with others, determines the purposes and means of the Processing of Personal Data, including, as applicable, any "business" or "controller" as such term is defined by the California Consumer Privacy Act (the "CCPA") or other State Privacy Laws.
Customer Data means information provided or otherwise made available by or on behalf of Customer to Provider for Processing on Customer's behalf to perform the Services, including Customer Content as defined in the Agreement.
Data Subject means the identified or identifiable natural person to whom Personal Data relates.
Information Security Incident means a breach of Provider's security resulting in the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data in Provider's possession, custody or control. Information Security Incidents do not include unsuccessful attempts or activities that do not compromise the security of Personal Data, including unsuccessful log-in attempts, pings, port scans, denial of service attacks, or other network attacks on firewalls or networked systems.
Personal Data means Customer Data that constitutes "personal data," "personal information," or "personally identifiable information" as defined in Applicable Data Protection Laws, or information of a similar character regulated by them. Personal Data does not include information about Customer's personnel who are business contacts of Provider, or information Provider collects independently of the Services, which Provider handles under its Privacy Policy.
Process or Processing means any operation or set of operations performed by Provider (or on Provider's behalf) for Customer under the Agreement on Personal Data, whether or not by automated means, such as collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.
Processor means the entity that Processes Personal Data on behalf of the Controller, including, as applicable, any "service provider" or "contractor" as those terms are defined by the CCPA.
Security Measures has the meaning given in Section 4(a) (Provider Security Measures).
Services means the proto[docs] Cloud Service and related services provided under the Agreement.
State Privacy Laws means the comprehensive U.S. state data privacy laws (and any implementing regulations) in effect and applicable to Provider's Processing of Personal Data under the Agreement.
Subprocessors means Provider's Affiliates and third parties that Provider engages to Process Personal Data in relation to the Services.
Supervisory Authority means any entity with the authority to enforce Applicable Data Protection Laws, including a state attorney general.
2. Duration and scope of this DPA
(a) This DPA remains in effect for as long as Provider Processes Personal Data, even after the Agreement expires or ends.
(b) Processing of Personal Data subject to the State Privacy Laws is also subject to Annex 2 (State Privacy Laws Annex).
3. Customer instructions
Provider will Process Personal Data only in accordance with Customer's documented instructions, including as set out in this DPA, the Agreement, any Order Form, the Connected Sources and AI Services Customer turns on in the Services, and any other written instructions from Customer that are consistent with the Agreement and this DPA. If Customer requests instructions outside the scope of the Services, or that would require Provider to materially change the Services, the Parties will agree to them in writing first. By entering into this DPA, Customer instructs Provider to Process Personal Data to provide the Services and to perform its other obligations and exercise its rights under the Agreement. The details of the Processing, including the roles of the Parties, are described in Annex 1 (Data Processing Details).
4. Security
(a) Provider Security Measures. Provider will implement and maintain technical and organizational measures designed to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data, as described in Annex 3 (the "Security Measures"), taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of Processing, and the risks to Data Subjects. Provider may update the Security Measures from time to time, so long as the updated measures do not materially decrease the overall protection of Personal Data.
(b) Security compliance by Provider staff. Provider will require that its personnel who are authorized to access Personal Data are subject to appropriate confidentiality obligations.
(c) Information Security Incidents. Provider will notify Customer without undue delay, and in any event no later than 72 hours after confirming an Information Security Incident. The notice will describe, to the extent then known, the details of the Information Security Incident, the steps taken to mitigate the risks, and the steps Provider recommends Customer take. Provider's notification of or response to an Information Security Incident is not an acknowledgement of fault or liability. Provider will reasonably cooperate with Customer and take commercially reasonable steps, within Provider's control, as Customer reasonably requests and the Parties agree in good faith, to assist in the investigation of the Information Security Incident. Customer is responsible for complying with notification laws that apply to Customer and for any third-party notifications. If Customer determines that an Information Security Incident must be notified to a Supervisory Authority, Data Subjects, the public or others, and the notice refers to or identifies Provider, Customer will, where permitted by law, (i) notify Provider in advance, and (ii) in good faith consult with Provider and consider any clarifications or corrections Provider reasonably requests about Provider's involvement, consistent with applicable law.
5. Customer's security responsibilities and assessment
(a) Customer's security responsibilities. Without limiting Provider's obligations under Section 4 (Security), Customer is responsible for its use of the Services, including (i) using the Services to ensure a level of security appropriate to the risk to the Personal Data; (ii) securing the account credentials, systems and devices Customer uses to access the Services; (iii) granting only the access to Connected Sources that Customer intends to share, and securing those Connected Sources; and (iv) backing up Personal Data, as applicable.
(b) Customer's security assessment. Customer acknowledges that it has evaluated the Services, the Security Measures and Provider's commitments under this DPA, and has determined, based on information Provider made available, that they meet Customer's needs and provide a level of security appropriate to the risk to the Personal Data.
6. Data Subject rights
(a) Data Subject request assistance. Taking into account the nature of the Processing, Provider will provide Customer with assistance reasonably necessary and technically feasible for Customer to fulfill requests by Data Subjects to exercise their rights under Applicable Data Protection Laws ("Data Subject Requests") with respect to Personal Data in Provider's possession or control. If that assistance requires work beyond the Services, Customer will pay for it at Provider's then-current professional services rates, and Provider will give a good-faith estimate on request.
(b) Customer's responsibility for requests. If Provider receives a Data Subject Request, Provider will (i) promptly notify Customer, unless prohibited by law; and (ii) advise the Data Subject to submit the request to Customer. Customer is responsible for responding to the request, unless applicable law requires otherwise.
7. Customer responsibilities
(a) Customer is responsible for providing all notices to, and obtaining all consents and permissions from, third parties (including Data Subjects), as required under Applicable Data Protection Laws for Provider to Process Personal Data as contemplated by the Agreement.
(b) Customer represents and warrants that Customer Data does not and will not contain any of the following ("Restricted Data"): social security numbers or other government-issued identification numbers; protected health information subject to HIPAA or other information about an individual's medical history, condition, treatment or diagnosis; health insurance information; biometric information; passwords or other credentials for individuals' personal online accounts; credentials to any financial accounts; tax return data; payment card information subject to PCI DSS; personal data of children under 16; or any other special categories of data as defined in Applicable Data Protection Laws. Credentials, keys and app installations Customer provides to connect Connected Sources under the Agreement are not Restricted Data.
(c) Customer will ensure there is, throughout the term of the Agreement, a valid legal basis for Provider's Processing of Personal Data under this DPA and the Agreement, as required by Applicable Data Protection Laws.
(d) Customer will ensure that all Data Subjects have (i) received all required notices; and (ii) given all required consents, in each case relating to Provider's Processing of Personal Data.
8. Subprocessors
(a) Consent to Subprocessor engagement. Customer specifically authorizes Provider to engage its Affiliates as Subprocessors and generally authorizes Provider to engage third parties as Subprocessors in accordance with this Section 8.
(b) Information about Subprocessors. Information about Subprocessors, including their functions and locations, is available at https://prototypd.dev/legal/subprocessors (the "Subprocessor Site"). Provider may continue to use the Subprocessors engaged as of the effective date of this DPA.
(c) Requirements for Subprocessor engagement. When engaging a Subprocessor, Provider will enter into a written contract with it containing data protection obligations no less protective than those in this DPA, to the extent applicable to the nature of its services. Provider remains responsible for all obligations it subcontracts to a Subprocessor and is liable for the Subprocessor's acts and omissions as if they were Provider's own.
(d) Opportunity to object. When Provider engages a new Subprocessor, Provider will update the Subprocessor Site at least 30 days before the Subprocessor begins Processing Personal Data, naming the Subprocessor, its location and its activities. If Customer objects by emailing help@prototypd.dev before the Subprocessor begins Processing Personal Data on reasonable grounds relating to the protection of Personal Data, the Parties will work together in good faith to resolve the objection. If they cannot do so within a reasonable time, Customer may, as its sole and exclusive remedy, terminate the Agreement by written notice. Provider will then refund any prepaid Fees for the remainder of the Subscription Period, and Customer will pay all amounts due up to the date of termination.
9. Audits
Customer may audit Provider's compliance with this DPA once per year, and at other times only if Applicable Data Protection Laws or a competent Supervisory Authority require it, by written request with reasonable detail and supporting documentation of the requirement. Provider will contribute to audits by providing the information and assistance reasonably necessary to conduct them. Provider may object to a third-party auditor that is, in Provider's reasonable opinion, not independent, a competitor of Provider, or otherwise manifestly unsuitable, in which case Customer will appoint another auditor or conduct the audit itself. To request an audit, Customer must submit a proposed audit plan at least two weeks before the proposed audit date, describing its scope, duration and start date. Any third-party auditor must sign a customary non-disclosure agreement reasonably acceptable to both Parties. Provider will review the plan, raise any concerns (for example, a request that could compromise Provider's security, privacy or employment policies), and work with Customer to agree a final plan. Nothing in this Section 9 requires Provider to breach a duty of confidentiality. Audits must take place during regular business hours, follow the final audit plan and Provider's safety and security policies, and not unreasonably interfere with Provider's business. Customer will promptly notify Provider of any non-compliance found and share any audit report with Provider, unless prohibited by law, and may use audit reports only to meet its regulatory audit requirements or confirm compliance with this DPA. Audits are at Customer's expense, including any auditor's fees, and Customer will reimburse Provider's reasonable, documented costs, including internal time at Provider's then-current professional services rates.
10. Return and deletion
(a) Subject to Sections 10(b) and 10(c), when the Services involving Processing of Personal Data end (the "Cessation Date"), Provider will promptly stop Processing Personal Data for any purpose other than storage and the Processing needed to return, delete or anonymize it, or as otherwise permitted or required by this DPA or applicable law.
(b) Customer may export Personal Data from the Services at any time before the Cessation Date. Subject to Section 10(c), Provider will delete all Personal Data in its possession, custody or control within 30 days after the Cessation Date.
(c) Provider may retain Personal Data to the extent applicable law permits or requires, for no longer than that law requires, provided that Provider will (i) keep it confidential and protect it in accordance with the Security Measures; (ii) Process it only for the purpose the law specifies; and (iii) delete or anonymize it once retention is no longer permitted or required.
11. Artificial intelligence and automated processing
(a) Provider will not use Personal Data to train, fine-tune, develop or improve any artificial intelligence or machine learning model, whether Provider's own or a third party's, unless Customer expressly authorizes it in writing.
(b) Provider will prohibit its Subprocessors, including AI model providers, from using Personal Data for their own model training, fine-tuning, development or improvement, except as Customer expressly authorizes in writing.
(c) When Customer connects its own AI model provider under the AI Terms, Provider sends Personal Data to that provider on Customer's instructions. That provider is engaged by Customer, not Provider, and is not Provider's Subprocessor.
(d) The Services do not make automated decisions that produce legal or similarly significant effects on Data Subjects. If that changes, Provider will (i) disclose the processing to Customer; (ii) provide meaningful information about the logic involved, to the extent reasonably available and without disclosing trade secrets; and (iii) reasonably cooperate with Customer, as Applicable Data Protection Laws require, so Data Subjects can exercise their rights.
12. Miscellaneous
(a) Except as modified by this DPA, the Agreement remains in full force and effect. The Parties agree that Provider's access to Personal Data is not part of the consideration exchanged under the Agreement. Provider may give notices under this DPA (i) under the notice clause of the Agreement; (ii) to Customer's data protection contact in Annex 1; (iii) to Provider's primary points of contact at Customer; or (iv) to any email address Customer designates for Services-related communications. Customer is responsible for keeping those addresses valid.
(b) Provider will cooperate in good faith with Customer to consider amendments reasonably necessary for compliance with Applicable Data Protection Laws.
(c) Provider may, on written notice, vary this DPA only to the extent necessary to maintain compliance with Applicable Data Protection Laws, provided that the variation does not materially reduce the protections for Personal Data or materially increase Customer's obligations without Customer's written agreement.
(d) To the extent permitted by Applicable Data Protection Laws, each Party's total aggregate liability under or in connection with this DPA is subject to the limitations, caps and exclusions of liability in the Agreement.
(e) If this DPA conflicts with the Agreement, this DPA prevails.
(f) This DPA is governed by the laws of the State of Kansas, and the Parties submit to the exclusive jurisdiction of the courts located in Johnson County, Kansas.
Annex 1: Data processing details
| Item | Details |
|---|---|
| Provider | prototypd LLC, a Kansas limited liability company, 7306 Reeds Road, Overland Park, KS 66204, USA. Data protection contact: help@prototypd.dev. Provides proto[docs], a hosted service that discovers and documents software architecture. Role: Processor (or Subprocessor, as applicable) |
| Customer | The entity that is a party to the Agreement, at the address and data protection contact on its account or Order Form. Uses the Services as part of its business operations. Role: Controller or Processor, as applicable |
| Categories of Data Subjects | Customer's personnel and contractors who use the Services or whose names appear in Connected Sources (for example as code authors, committers, repository owners or deployment approvers); and individuals whose identifiers appear in telemetry Customer sends |
| Categories of Personal Data | Personal details, such as names, usernames and email addresses in repository metadata, commit history, code, cloud resource tags and deployment records. Authentication details, such as account identifiers and access tokens for the Services. Technical details, such as IP addresses, user and session identifiers and other attributes Customer's telemetry contains |
| Sensitive data | None. Restricted Data must not be submitted to the Services (Section 7(b)) |
| Frequency of transfer | Continuous, as Customer connects sources and runs discovery |
| Nature of the Processing | Reading Connected Sources and telemetry; storing, classifying and analyzing them, including with AI models; building and displaying the architecture model and diagrams; hosting, backup and support |
| Purpose of the Processing | To provide the Services as Customer uses them, and to follow Customer's documented instructions under this DPA and the Agreement |
| Duration and retention | For the term of the Agreement and then as described in Section 10. Raw telemetry and repository contents fetched for analysis are kept for the historical-diffs window of Customer's plan: 30 days on Basic, 90 days on Plus, 12 months on Pro, and as agreed in the Order Form on Enterprise |
| Transfers to Subprocessors | As described on the Subprocessor Site |
Annex 2: State Privacy Laws Annex
- For this Annex 2, the terms "business," "controller," "processor," "commercial purpose," "sell," "share," "service provider" and "contractor" have the meanings given in the applicable State Privacy Laws, and "personal information" means Personal Data to the extent it is "personal information" or "personal data" (or a similar term) governed by the State Privacy Laws.
- The Parties intend that, for any personal information, Provider is a service provider, contractor and/or processor, as applicable. Provider (a) acknowledges that Customer discloses personal information only for the limited and specified purposes described in the Agreement; (b) will comply with its obligations under the State Privacy Laws and provide the level of privacy protection they require; (c) agrees that Customer may take reasonable and appropriate steps to ensure that Provider's Processing is consistent with Customer's obligations under the State Privacy Laws; (d) will notify Customer in writing if it determines it can no longer meet its obligations under the State Privacy Laws; and (e) agrees that Customer may, on reasonable notice, take reasonable and appropriate steps to stop and remediate unauthorized use of personal information.
- Provider will not (a) sell or share any personal information; (b) retain, use or disclose personal information for any purpose other than providing the Services, including for a commercial purpose other than providing the Services, or as otherwise permitted by the State Privacy Laws; (c) retain, use or disclose personal information outside the direct business relationship between Provider and Customer; or (d) combine personal information received under the Agreement with personal information received from or on behalf of another person, or collected from Provider's own interactions with the Data Subject, except as permitted by the State Privacy Laws and necessary to provide the Services. Provider certifies that it understands and will comply with these obligations.
- Notice of Subprocessor engagements under Section 8 of this DPA satisfies Provider's obligation under the State Privacy Laws to give notice of, and an opportunity to object to, those engagements.
- Customer may conduct audits under Section 9 of this DPA to help ensure that Provider's use of personal information is consistent with its obligations under the State Privacy Laws.
- The Parties acknowledge that Provider's retention, use and disclosure of personal information as authorized by Customer's instructions in the Agreement and this DPA are integral to providing the Services and to the business relationship between the Parties.
Annex 3: Security Measures
- Hosting. The Services are hosted in Microsoft Azure, in the Central US region.
- Encryption at rest. Azure SQL transparent data encryption and Azure storage encryption protect Customer Data at rest.
- Encryption in transit. Customer Data is encrypted in transit with TLS 1.2 or higher.
- Connected Source credentials and customer AI keys. These are encrypted at the application level with AES-256-GCM before they are stored, so they are unreadable to anyone with database access or a database backup, and are never sent to AI models.
- Key management. Database and storage encryption keys are managed in Azure (Azure-managed keys). The application-level encryption key is held in Azure App Service configuration, separate from the database and its backups.
- Secrets exclusion. Files that look like secrets are excluded before any content reaches an AI model.
- Production access. Access to production systems is limited to Provider's owner, who uses multi-factor authentication.
Annex 4: Subprocessors
The current list of Subprocessors, their locations and the processing they perform is published on the Subprocessor Site at https://prototypd.dev/legal/subprocessors. Customer approves the Subprocessors listed there on the effective date of this DPA.
Adapted from a template by General Legal, PC, released under CC0. General Legal has not reviewed these changes.