Data Processing Addendum
Version 2026-11
This Data Processing Addendum (“DPA”) supplements the Master Services Agreement or other written or online terms governing Customer’s use of the Services, together with applicable Orders (the “Agreement”), between Coreplane Labs, Inc., a Delaware corporation (“Company” or “Coreplane”), and the customer identified in the Agreement (“Customer”) (each a “Party” and together, the “Parties”). This DPA applies to Company’s processing of Personal Data on Customer’s behalf in providing the Services. This DPA incorporates the terms of the Agreement, subject to its order-of-precedence provisions below. Capitalized terms not defined in this DPA have the meanings given in the Agreement.
1. Definitions
1.1 “Authorized Subprocessor” means a third-party entity engaged by Company to process Personal Data in order to provide the Services and that has been approved by Customer in accordance with Section 6.
1.2 “Company Account Data” means personal data concerning Customer’s business relationship with Company, such as business contact details, contracting and billing contacts, and billing records, processed by Company for the independent purposes described under Company’s Role as a Controller below. It excludes connected Customer content and records processed solely to administer Customer’s workspace on Customer’s behalf.
1.3 “Company Usage Data” means limited personal data about access to and use of the Services, such as account-level service events, device information and security logs, processed for the independent purposes described under Company’s Role as a Controller below. It excludes Customer’s connected telemetry, source code, prompts, outputs, investigation content and other Personal Data processed on Customer’s behalf. Company Usage Data is distinct from the non-identifying “Usage Data” defined in the Agreement.
1.4 “Data Privacy Framework” means, as applicable, the EU-U.S. Data Privacy Framework, the UK Extension to the EU-U.S. Data Privacy Framework, and/or the Swiss-U.S. Data Privacy Framework.
1.5 “Data Subject” means a natural person whose Personal Data is protected by Privacy Laws. For the avoidance of doubt, “Data Subject” includes the term “Consumer” under Privacy Laws.
1.6 “Data Subject Request” means a request from a Data Subject to exercise their rights over Personal Data afforded pursuant to Privacy Laws.
1.7 “EU SCCs” means standard contractual clauses approved by the European Commission in Commission Decision 2021/914 dated 4 June 2021, for transfers of personal data to countries not otherwise recognized as offering an adequate level of protection for personal data by the European Commission (as amended and updated from time to time), as modified by Section 9 of this DPA.
1.8 “ex-EEA Transfer” means the transfer of Personal Data subject to the GDPR from the European Economic Area (the “EEA”), to a country where the transfer is not governed by an adequacy decision made by the European Commission in accordance with the relevant provisions of the GDPR.
1.9 “ex-UK Transfer” means a transfer of Personal Data subject to Chapter V of the UK GDPR from the United Kingdom (“UK”) to a country not covered by applicable UK adequacy regulations.
1.10 “Personal Data” means information constituting personal data, personal information or an equivalent term under Privacy Laws that Company processes on Customer’s behalf in connection with the Services, including information provided by or for Customer, accessed or collected from Customer-connected systems, or generated or derived in providing the Services. Personal Data includes personal data in prompts, telemetry, investigation records, outputs and intermediate artifacts. It excludes Company Account Data and Company Usage Data only to the extent processed for the independent purposes expressly described in this DPA.
1.11 “Privacy Laws” means any applicable laws and regulations in any relevant jurisdiction relating to the processing of Personal Data including, each to the extent applicable: (i) the General Data Protection Regulation (Regulation (EU) 2016/679) (“EU GDPR”) and the EU GDPR as it forms part of the law of England and Wales by virtue of section 3 of the European Union (Withdrawal) Act 2018 (the “UK GDPR”) (together, collectively, the “GDPR”), (ii) the Swiss Federal Act on Data Protection, (iii) the UK Data Protection Act 2018, (iv) the Privacy and Electronic Communications (EC Directive) Regulations 2003, (v) U.S. state comprehensive privacy laws, such as the California Consumer Privacy Act, as amended by the California Privacy Rights Act of 2020 (the “CCPA”), and (vi) U.S. consumer health data privacy laws, such as the Washington My Health My Data Act (“MHMDA”); in each case, as updated, amended or replaced from time to time. The terms “affiliates,” “business purpose,” “Controller,” “Personal Data Breach,” “Processor,” “process” or “processing,” “sell,” “share,” or “supervisory authority,” shall have the meanings set forth for those or equivalent terms under Privacy Laws. For the avoidance of doubt, the terms “Controller” and “Processor” include “Business” and “Service Provider,” respectively, as defined in the CCPA.
1.12 “Standard Contractual Clauses” means, as applicable, the EU SCCs and the UK SCCs.
1.13 “UK Addendum” means the template International Data Transfer Addendum issued by the Information Commissioner and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022 (as may be amended from time to time), as completed by Exhibit D.
1.14 “UK SCCs” means the EU SCCs, as amended by the UK Addendum.
2. Role of the Parties; Description of Processing
2.1 With respect to Personal Data, Customer is the Controller and Company is a Processor, or, where Customer processes Personal Data for another Controller, Customer is a Processor and Company is a subprocessor. Customer shall ensure that it has the relevant Controller’s authorization for its instructions and Company’s appointment. The independent processing described under Company’s Role as a Controller below is separate from this processor relationship.
2.2 Company shall process Personal Data only on Customer’s documented instructions to provide the Services, including as described in the Agreement, this DPA, applicable Orders and Customer’s configuration of integrations, model routing, permissions and enabled remediation features, or as required by applicable law. Collection of records to improve Company’s models is controlled by the Privacy Mode setting described below. Where legally permitted, Company shall inform Customer of a legal requirement before such processing. Additional instructions outside the agreed Services require written agreement, including any applicable charges. Instructions do not authorize access beyond Customer-granted permissions. Exhibit A describes the subject matter, nature, purpose and duration of processing, the types of Personal Data and the categories of Data Subjects.
2.3 Privacy Mode and Model Improvement. Notwithstanding the Training License or any other permission in the Agreement, the following applies to Personal Data. (a) Each workspace has a Privacy Mode setting on every plan. A workspace administrator may turn Privacy Mode on or off at any time, and Company records each change with the administrator and the time. Privacy Mode is off by default on self-serve plans and on by default on Enterprise plans. (b) When Privacy Mode is on, Company does not collect Customer Data from that workspace to train or improve its models. Turning Privacy Mode on stops new collection and does not affect records collected before. (c) When Privacy Mode is off, Company may use code changes and their metadata, outputs of the Services and feedback on them to improve its models. (d) When a workspace is deleted, its model-improvement records are deleted under the Return or Destruction of Personal Data provisions. (e) Company may use de-identified or aggregated data that is not Personal Data to improve the Services and shall not attempt to re-identify it. (f) Company does not permit third-party model providers to train their models on Customer Data.
2.4 AI Providers. A model or other provider engaged by Company to process Personal Data on Customer’s behalf is an Authorized Subprocessor subject to this DPA. Company shall ensure that Authorized Subprocessors that provide AI model inference are bound by terms that prevent them from using Customer Data to train their models.
3. Customer’s Obligations
Customer shall comply with Privacy Laws in using the Services and issuing instructions, and shall obtain the rights, notices, consents and other lawful bases required to provide Personal Data, authorize access to connected systems and permit the processing contemplated by this DPA. Customer is responsible for the accuracy, quality and legality of Personal Data it supplies, the means of its collection, and its instructions. Customer shall configure access on a least-privilege basis and shall not provide Personal Data contrary to the Agreement or the agreed scope in Exhibit A. The Agreement governs any indemnification obligations relating to Customer Data or Customer’s instructions; this DPA creates no separate indemnity. Company shall immediately inform Customer if, in Company’s opinion, an instruction infringes Privacy Laws and may suspend the affected processing until the Parties resolve the issue.
4. Use of Personal Data
Each Party shall comply with Privacy Laws applicable to its performance under this DPA. Where Company acts as a service provider or contractor under the CCPA, Company shall not (i) sell or share Personal Data; (ii) retain, use or disclose Personal Data for purposes other than the specific business purposes of providing the Services described in Exhibit A, or outside its direct business relationship with Customer, except as permitted by the CCPA; or (iii) combine Personal Data with personal information received from another person or collected through Company’s own interactions with a consumer, except as permitted by the CCPA. Company shall provide the level of privacy protection required by the CCPA, notify Customer if it determines that it can no longer meet its obligations, and permit Customer to take reasonable and appropriate steps to verify compliance and stop and remediate unauthorized processing in accordance with this DPA. Company certifies that it understands and will comply with these restrictions. Customer’s configuration or acceptance of the Agreement does not authorize processing prohibited by applicable Privacy Laws.
5. Audit
5.1 Company shall maintain and make available information reasonably necessary to demonstrate compliance with this DPA. Subject to reasonable confidentiality protections, Company shall first provide available independent audit reports, certifications or other relevant compliance documentation. If these are insufficient to satisfy Customer’s obligations under Privacy Laws, Company shall allow and contribute to an audit, including an inspection, by Customer or an independent auditor mandated by Customer and reasonably acceptable to Company. Audits shall ordinarily occur on reasonable prior notice, during business hours, no more than once annually, with minimal disruption and limited to relevant processing; they shall not expose other customers’ data or permit intrusive testing without Company’s prior written consent. These procedural limits do not restrict audits required by Privacy Laws, a competent authority or the Standard Contractual Clauses, or additional audits reasonably necessary following a Personal Data Breach or credible evidence of material noncompliance. Customer shall bear reasonable audit costs, including Company’s reasonable assistance costs agreed in advance, except to the extent prohibited by Privacy Laws. The audit procedures also apply to audits under the Standard Contractual Clauses without limiting rights under them.
5.2 To the extent permitted under Privacy Laws, if Customer determines that Company is processing Personal Data in an unauthorized manner, Customer may, taking into account the nature of Company’s processing and the nature of the Personal Data processed by Company on behalf of Customer, and upon providing prior written notice, take commercially reasonable and appropriate steps to stop and remediate such unauthorized processing as set forth in this DPA.
6. Authorized Subprocessors
6.1 Customer grants general written authorization for Company to engage the Authorized Subprocessors identified in Exhibit B, including affiliates identified there, to process Personal Data as necessary to provide the Services. Additional or replacement subprocessors are subject to the notice and objection procedure below. A provider engaged by Company to process Personal Data on Customer’s behalf, including a managed AI inference provider, is subject to these requirements regardless of how it is described in the Agreement.
6.2 Company shall maintain a current List of Authorized Subprocessors at polylane.com/subprocessors/ and the completed details in Exhibit B. At least thirty (30) days before an additional or replacement subprocessor first processes Personal Data, Company shall notify Customer by direct email to its designated account or privacy contact, describing the provider, processing and locations and identifying the proposed start date. Customer may object in writing within that notice period on reasonable data-protection grounds. Absent a timely objection, the provider is authorized. The Parties shall work in good faith to resolve a timely objection through a commercially reasonable alternative before the proposed start date. Company is not required to maintain customer-specific model routing while resolving an objection. If the objection cannot be resolved, either Party may terminate only the affected Service by written notice effective before the new provider first processes the affected Personal Data. Customer shall pay accrued fees and fees for unaffected Services; Company shall refund prepaid fees attributable to the terminated portion for periods after termination. Company shall implement any such termination before the new provider receives the affected Personal Data. Customer shall keep its notice details current; publication of a revised List alone does not replace the required direct notice. Objections and subprocessor-list questions may be sent to privacy@polylane.com. This procedure governs Personal Data notwithstanding any approval-by-use or non-refundable-fee provision of the Agreement.
6.3 Company shall enter into a written agreement with each Authorized Subprocessor imposing data-protection obligations no less protective than those imposed on Company under this DPA for the processing delegated to it, including confidentiality, security, assistance and deletion obligations. Company remains responsible to Customer for the Authorized Subprocessor’s performance of those obligations, subject to the liability provisions applicable under this DPA. The Agreement’s Third-Party AI Model disclaimers do not excuse these obligations for providers acting as Company’s Authorized Subprocessors.
6.4 If Customer and Company have entered into Standard Contractual Clauses as described in Section 9 (Transfers of Personal Data), (i) the above authorizations will constitute Customer’s prior written consent to the subcontracting by Company of the processing of Personal Data if such consent is required under the Standard Contractual Clauses, and (ii) the parties agree that the copies of the agreements with Authorized Subprocessors that must be provided by Company to Customer pursuant to Clause 9(c) of the EU SCCs may have commercial information, or information unrelated to the Standard Contractual Clauses or their equivalent, removed by Company beforehand, and that such copies will be provided by Company only upon request by Customer.
7. Confidentiality; Security of Personal Data
7.1 Company shall ensure that persons authorized to process Personal Data are bound by confidentiality commitments or appropriate statutory duties of confidentiality and access Personal Data only as necessary for their authorized functions. Disclosure to advisers or auditors shall be limited to what is necessary and subject to appropriate confidentiality protections. Any third party engaged to process Personal Data on Customer’s behalf remains subject to the Authorized Subprocessor requirements; this provision grants no separate right to disclose Personal Data for unrelated purposes.
7.2 Taking into account the state of the art, implementation costs, the nature, scope, context and purposes of processing, and risks to individuals, Company shall maintain appropriate technical and organizational measures to protect Personal Data, including the safeguards in the Agreement and the completed Exhibit C. Company may update those measures provided it does not materially diminish the overall protection of Personal Data during the applicable Services term.
8. Personal Data Breach
8.1 Company shall notify Customer without undue delay after becoming aware of a Personal Data Breach affecting Personal Data processed on Customer’s behalf. Company shall take reasonable steps to contain, investigate and remediate the breach within its control. Notification shall be sent to Customer’s designated security or privacy contact, or otherwise its account contact, and shall describe, to the extent then known, the nature of the breach, affected categories and approximate numbers of Data Subjects and records, likely consequences, response measures and a contact for further information. Company may provide information in phases without undue further delay; an initial notice need not await a completed investigation.
8.2 In the event of a Personal Data Breach, Company shall, taking into account the nature of the processing and the information available to Company, provide Customer with reasonable cooperation and assistance necessary for Customer to comply with its obligations under Privacy Laws with respect to notifying (i) the relevant supervisory authority or regulatory agency and (ii) Data Subjects affected by such Personal Data Breach without undue delay.
8.3 Company’s notification and assistance obligations apply regardless of whether Customer’s acts or omissions contributed to a Personal Data Breach. Providing notice or assistance is not an admission of fault or liability. Customer remains responsible for determining and making notifications to authorities and Data Subjects, except where Company is independently required by law to notify them. Company shall not identify Customer in such a notification without prior consultation where legally permitted.
9. Transfers of Personal Data
9.1 Company may process Personal Data in the United States and other countries identified in the completed Exhibit B as necessary to provide the Services, subject to Privacy Laws and the safeguards in this DPA. This DPA does not itself promise exclusive storage or access in any particular country. Company shall implement a valid transfer mechanism where required, including for onward transfers and remote access by Authorized Subprocessors.
9.2 Ex-EEA Transfers. For ex-EEA Transfers from Customer to Company, the EU SCCs are incorporated into this DPA and deemed entered into between Customer as data exporter and Company as data importer, using the applicable module specified below. Company does not represent in this DPA that it is certified under the Data Privacy Framework.
9.2.1 Module One (Controller to Controller) is not incorporated by this processor-form DPA. If a transfer of Company Account Data or Company Usage Data requires separate controller-to-controller safeguards, the Parties shall document the relevant transfer and safeguards separately before it occurs.
9.2.2 Module Two (Controller to Processor) of the EU SCCs applies when Customer is a controller and Company is a processor of Personal Data in accordance with Section 2 of this DPA.
9.2.3 Module Three (Processor to Subprocessor) of the EU SCCs applies when Customer is a processor and Company is a subprocessor of Personal Data in accordance with Section 2 of this DPA.
9.2.4 Module Four (Processor to Controller) is not incorporated by this DPA. Any transfer requiring that module must be separately documented before it occurs.
9.3 For each module, where applicable the following applies:
9.3.1 The optional docking clause in Clause 7 does not apply.
9.3.2 In Clause 9, Option 2 (general written authorization) applies, and the minimum time period for prior notice of subprocessor changes shall be as set forth in Section 6.2 of this DPA.
9.3.3 In Clause 11, the optional language does not apply.
9.3.4 All square brackets in Clause 13 are hereby removed.
9.3.5 In Clause 17, Option 1 applies and the EU SCCs are governed by Irish law.
9.3.6 In Clause 18(b), disputes shall be resolved before the courts of Ireland without limiting Data Subjects’ rights under the EU SCCs.
9.3.7 Exhibit B to this DPA contains the information required in Annex I of the EU SCCs.
9.3.8 Exhibit C contains the information required in Annex II of the EU SCCs.
9.3.9 By entering into this DPA, the Parties are deemed to have signed the EU SCCs incorporated herein, including their Annexes.
9.4 Ex-UK Transfers. For ex-UK Transfers from Customer to Company, the UK SCCs are incorporated and deemed entered into, as completed in Exhibit D. The Mandatory Clauses of the UK Addendum govern its interpretation and precedence. The applicable law and courts are England and Wales in accordance with those Mandatory Clauses.
9.5 Transfers from Switzerland. To the extent Customer transfers Personal Data to Company subject to Swiss transfer restrictions, the EU SCCs apply with the following modifications:
9.5.1 References in the EU SCCs to the GDPR include the Swiss Federal Act on Data Protection of 25 September 2020, as amended (“FADP”), to the extent the transfer is governed by the FADP.
9.5.2 Clause 13 of the EU SCCs is modified to provide that the Federal Data Protection and Information Commissioner (“FDPIC”) of Switzerland shall have authority over data transfers governed by the FADP and the appropriate EU supervisory authority shall have authority over data transfers governed by the GDPR. Subject to the foregoing, all other requirements of Clause 13 shall be observed.
9.5.3 The term “EU Member State” as utilized in the EU SCCs shall not be interpreted in such a way as to exclude Data Subjects in Switzerland from exercising their rights in their place of habitual residence in accordance with Clause 18(c) of the EU SCCs.
9.6 Supplementary Measures. In respect of any transfer of Personal Data made pursuant to the Standard Contractual Clauses, the following supplementary measures shall apply:
9.6.1 “Government Agency Request” means a legally binding request from a public authority for access to Personal Data processed under this DPA.
9.6.2 If Company receives a Government Agency Request, it shall, where legally permitted, promptly notify Customer and seek to redirect the requesting authority to Customer. Company shall review the request’s legality and challenge it where there are reasonable grounds to consider it unlawful, seek available interim measures where appropriate, and disclose only the minimum Personal Data legally required. If notification is prohibited, Company shall use reasonable efforts to obtain a waiver and document those efforts. Company shall comply with its applicable obligations under the Standard Contractual Clauses, including suspension where required.
9.6.3 The Parties will confer as appropriate to consider whether: (i) the protection afforded by the laws of the country of Company to data subjects whose Personal Data is being transferred is sufficient to provide broadly equivalent protection to that afforded in the EEA or the UK, as applicable; (ii) additional measures are reasonably necessary for the transfer to comply with Privacy Laws; and (iii) it is still appropriate for Personal Data to be transferred to Company, taking into account all relevant information available, including guidance by supervisory authorities, to the Parties.
9.6.4 If either (i) any of the means of legitimizing a transfer cease to be valid or (ii) any supervisory authority requires transfers of Personal Data pursuant to those means to be suspended, the Parties agree to amend the means of legitimizing transfers in accordance with Privacy Laws. To the extent necessary to ensure the enforceability of the Standard Contractual Clauses, the Parties shall execute the Standard Contractual Clauses as a separate agreement.
10. Data Protection Assessments
Taking into account the nature of processing and information available to Company, Company shall provide reasonable assistance with Customer’s legally required data protection impact assessments and prior consultations with supervisory authorities relating to the Services. Company shall provide relevant information Customer cannot reasonably obtain otherwise, subject to appropriate confidentiality protections. Each Party remains responsible for its own obligations. To the extent legally permitted, Customer shall reimburse reasonable assistance costs agreed in advance, except to the extent assistance is required because of Company’s breach of this DPA.
11. Data Subject Request
11.1 Company shall promptly notify Customer of a Data Subject Request relating to Personal Data, where legally permitted, and shall not respond substantively except on Customer’s documented instructions or as required by law. Company may direct the requester to Customer. Customer is responsible for assessing and responding to requests, using available Service functionality where appropriate, and for maintaining any legally required records of consent.
11.2 Company shall, at the request of Customer, and taking into account the nature of the processing applicable to any Data Subject Request, apply appropriate technical and organizational measures to assist Customer in complying with Customer’s obligation to respond to such Data Subject Request and/or in demonstrating such compliance, where possible, provided that (i) Customer is itself unable to respond without Company’s assistance and (ii) Company is able to do so in accordance with all applicable laws, rules, and regulations. Customer shall be responsible to the extent legally permitted for any costs and expenses arising from any such assistance by Company.
12. Return or Destruction of Personal Data
Upon expiration or termination of the Agreement or the applicable Order, Customer may elect return or deletion of the affected Personal Data. Unless Customer requests earlier deletion, Company shall retain that data in a restricted quarantine state for the Agreement’s sixty (60)-day Post-Termination Period solely for protection, export and deletion; Company shall provide the then-standard export without additional charge and thereafter delete remaining active copies and require Authorized Subprocessors to do the same. This obligation covers all copies of the affected Personal Data held by Company and its Authorized Subprocessors. Company may retain data only to the extent required by applicable law, with processing limited to that requirement, or in isolated backups for no more than thirty-one (31) days after deletion from active systems, protected against further use except restoration for disaster recovery, after which the deletion requirement shall be reapplied. Company shall certify deletion upon request. This DPA continues to protect retained Personal Data until deletion. Company may keep records from which it has removed names, contact details, IP addresses, account identifiers of individuals and credentials. These records contain internal identifiers, usage metrics, technical context and operational content.
13. Company’s Role as a Controller
Company acts as an independent controller, not a joint controller with Customer, for Company Account Data and Company Usage Data only to manage the commercial relationship, billing and accounting, protect its accounts and Services against fraud and abuse, and comply with its legal obligations. Company shall process that data in accordance with Privacy Laws and its applicable privacy notice. These purposes do not authorize independent use of Customer-connected content, prompts, outputs or telemetry for model training or general product development. The Privacy Mode and Model Improvement provisions govern the use of Customer Data to improve Company’s models. Data qualifies as Aggregated Anonymous Data or non-identifying Usage Data under the Agreement only if it is not personal data under applicable Privacy Laws; aggregation or pseudonymization alone does not establish this. Company shall not attempt to re-identify such data and shall maintain any legally required de-identification safeguards. Any processing used to create anonymous data must itself comply with this DPA.
14. Miscellaneous
For processing of Personal Data, conflicts are resolved in the following order: (1) applicable Standard Contractual Clauses, including the UK Addendum where applicable; (2) this DPA; and (3) the Agreement, including Orders. An Order may vary this DPA only by expressly identifying the provision varied in a writing agreed by both Parties, and may not reduce mandatory protections. A privacy policy does not expand rights to use Personal Data contrary to this DPA. Subject to Privacy Laws and the Standard Contractual Clauses, the Agreement’s exclusions, limitations of liability, indemnification procedures and governing-law provisions apply to this DPA; liability under the Agreement and this DPA is aggregated, not subject to separate cumulative caps. Nothing restricts Data Subjects’ rights or a Party’s obligations under the Standard Contractual Clauses. This DPA survives for as long as Company or its Authorized Subprocessors retain Personal Data.
15. Execution of this DPA
Customer enters into this DPA by accepting an Agreement or Order that expressly incorporates this DPA by reference, including by reference to this version of the DPA at polylane.com/legal/dpa/2026-11. This DPA takes effect upon Customer’s acceptance of such an Agreement or Order (the “DPA Effective Date”). By making this DPA available for incorporation into the Agreement or an Order, Company agrees to be bound by this DPA upon Customer’s acceptance of that Agreement or Order. Such acceptance constitutes both Parties’ execution of this DPA and signature of the incorporated Standard Contractual Clauses and UK Addendum, where applicable, as of the DPA Effective Date; no separate signature of this DPA or its Exhibits is required. This DPA applies only as issued by Company, and any change Customer makes to it is not binding unless agreed in a separate writing signed by both Parties. This DPA binds only the Customer entity that is party to the Agreement. Customer’s identity and contact details for Exhibit B are those set out in the Agreement, the applicable Order or Customer’s account records, including any data protection officer or representative details provided by Customer. Customer shall ensure that those details are accurate, complete and kept current. The person accepting the Agreement or Order on Customer’s behalf represents that it is authorized to bind Customer. The version of this DPA incorporated into the Agreement or Order when Customer enters into this DPA continues to apply to Customer unless the Parties agree otherwise in writing, subject to updates to Exhibit B under Section 6 (Authorized Subprocessors) and to Exhibit C under Section 7.2.
Exhibit A
Details of Processing
Subject Matter, Nature and Purpose of Processing: Provision of the Polylane Services selected in the applicable Order, including connection to Customer-authorized repositories, cloud infrastructure, observability and collaboration systems; monitoring and correlation of operational information; investigation of incidents and code changes; and AI inference to generate explanations, reports, recommendations, videos and proposed code or configuration changes. Processing includes retrieval, collection, recording, organization, storage, querying, analysis, correlation, generation, disclosure to authorized recipients, protection, export and deletion, according to Customer’s permissions and configuration. This includes actions in connected systems that Customer authorizes through its configuration. Use of Customer Data to improve Company’s models is governed by the Privacy Mode and Model Improvement provisions.
Stored and Transient Processing: Company stores the content needed to provide the Services, including investigation records, reports, proposed changes and data received from systems Customer connects, until deletion under the Return or Destruction of Personal Data provisions. Model prompts and responses are kept for no more than thirty days for operations and support. Company Usage Data exclude names, contact details, IP addresses, account identifiers of individuals and credentials.
Support Access and Customer-Directed Sharing: Authorized personnel access Customer Data only as needed to provide support, keep the Services secure or comply with law, and such access is logged. Customer controls the sharing features of the Services and the permissions of its users.
Model-Improvement Records: When Privacy Mode is off, Company may use code changes and their metadata, outputs of the Services and feedback on them to improve its models. These records are kept by workspace and deleted when the workspace is deleted.
Duration of Processing: For the applicable Services term and the restricted export and deletion period described under Return or Destruction of Personal Data, including any legally required retention or confirmed backup cycle. Independent Company Account Data and Company Usage Data are outside this processor schedule.
Categories of Data Subjects: As determined by Customer’s use and configuration: Customer’s employees, developers, contractors, administrators and workspace users; repository contributors and commit authors; and Customer’s end users, business contacts and other persons whose information appears in connected systems, communications or telemetry.
Categories of Personal Data: Depending on Customer’s integrations and instructions: names, email addresses, usernames, commit-author information, user and account identifiers, IP addresses and device identifiers; identifiers and personal data in source code and metadata, configurations, logs, metrics, traces, alerts, deployment histories, support and collaboration messages; workspace access and integration records processed on Customer’s behalf; and personal data reproduced or inferred in prompts, responses, context graphs, investigation threads, reports, proposed fixes, action logs, indexes or caches, where used. Integration credentials and tokens may also be processed where they constitute Personal Data. Non-personal confidential Customer Data remains governed by the Agreement.
Sensitive Data or Special Categories of Data: Customer determines which systems to connect and shall not connect a system whose main purpose is processing special-category personal data without a separate written agreement addressing that processing and any additional safeguards. Connected production logs, support tools and other systems may incidentally contain health, financial, children’s or other sensitive personal data. Company applies the safeguards in Exhibit C to all Personal Data, including such incidental sensitive data.
Exhibit B
The following includes the information required by Annex I and Annex III of the EU SCCs, and Table 1, Annex 1A, and Annex 1B of the UK Addendum.
1. The Parties
Data exporter(s): Customer, as identified below and in accordance with Section 15.
Name: Customer’s full legal name as identified in the Agreement, the applicable Order or Customer’s account records.
Trading Name (if different): As identified in the Agreement, the applicable Order or Customer’s account records, if applicable.
Address: As identified in the Agreement, the applicable Order or Customer’s account records.
Official Registration Number (if any) (company number or similar identifier): As identified in the Agreement, the applicable Order or Customer’s account records, if applicable.
Contact person’s name, position and email, including privacy/security contact and, where applicable, data protection officer and/or representative: As identified in the Agreement, the applicable Order or Customer’s account records, including details provided by Customer under Section 15.
Activities relevant to the transfer: Using the Services and authorizing processing described in Exhibit A.
Signature and date: Deemed signed by Customer through its acceptance of the Agreement or Order incorporating this DPA under Section 15, effective on the DPA Effective Date; no separate signature is required.
Role: Controller (Module Two) or Processor acting for an authorized Controller (Module Three), as applicable to the transferred Personal Data.
Data importer(s): Company, as identified below.
Name: Coreplane Labs, Inc.
Trading/product name: Polylane.
Address: 2261 Market Street STE 64441, San Francisco, CA 94114, United States
Official Registration Number: N/A
Privacy contact: privacy@polylane.com. Security contact: security@coreplane.ai.
Activities relevant to the transfer: Providing the Services and processing Personal Data as described in Exhibit A.
Signature and date: Deemed signed by Company in accordance with Section 15 upon Customer’s acceptance of the Agreement or Order incorporating this DPA, effective on the DPA Effective Date; no separate signature is required.
Role: Processor (Module Two) or Subprocessor (Module Three), as applicable.
2. Description of the Transfer
| Data Subjects | As described in Exhibit A. |
| Categories of Personal Data | As described in Exhibit A. |
| Special Category Personal Data (if applicable) | As described in Exhibit A. The Exhibit C safeguards apply to all Personal Data, including incidental sensitive data; systems principally processing special-category personal data require a separate written agreement. |
| Nature of the Processing | As described in Exhibit A. |
| Purposes of Processing | As described in Exhibit A. |
| Duration of Processing and Retention (or the criteria to determine such period) | As described in Exhibit A and the Return or Destruction of Personal Data provisions. |
| Frequency of the transfer | On an ongoing basis during provision of the Services, as initiated by Customer’s use, connected systems, permissions and configuration. |
| Recipients of Personal Data Transferred to the Data Importer | Authorized Subprocessors identified in the completed list below; Customer-authorized users and destinations solely as instructed by Customer. |
3. Competent Supervisory Authority
The supervisory authority shall be the supervisory authority of the Data Exporter, as determined in accordance with Clause 13 of the EU SCCs. The supervisory authority for the purposes of the UK Addendum shall be the UK Information Commissioner’s Office.
4. List of Authorized Subprocessors
| Name of Authorized Subprocessor | Address | Contact Person Name, position, contact information | Description of processing | Country in which subprocessing will take place |
|---|---|---|---|---|
| Cloudflare, Inc. | 101 Townsend Street, San Francisco, CA 94107, USA | Data Protection Officer, dpo@cloudflare.com; privacyquestions@cloudflare.com | Cloud infrastructure: hosting, storage, email and AI model inference. | Global; storage in the United States and the European Economic Area |
| Amazon Web Services, Inc. | 410 Terry Avenue North, Seattle, WA 98109-5210, USA | Through the AWS account team; https://aws.amazon.com/privacy | Cloud infrastructure. | United States |
| Baseten Labs, Inc. | 560 Davis St., Suite 250, San Francisco, CA 94111, USA | security@baseten.co | AI model inference. | United States |
| Parasail, Inc. | 4 West 4th Avenue, San Mateo, CA 94402, USA | hello@parasail.io; legal@parasail.io | AI model inference. | United States and the European Union |
| Anthropic, PBC | 548 Market St, PMB 90375, San Francisco, CA 94104, USA | privacy@anthropic.com; Data Protection Officer, dpo@anthropic.com | AI model inference, only when Customer selects this provider. | United States |
| OpenAI OpCo, LLC | 1455 3rd Street, San Francisco, CA 94158, USA | Data Protection Officer, privacy@openai.com | AI model inference, only when Customer selects this provider. | United States |
| Pylon Labs, Inc. | 690 5th St., San Francisco, CA 94107, USA | Data Protection Officer, reng@usepylon.com; security@usepylon.com | Customer support. | United States |
Exhibit C
Description of the Technical and Organisational Security Measures implemented by the Data Importer
The following includes the information required by Annex II of the EU SCCs and Appendix II of the UK Addendum.
| Technical and Organizational Security Measure | Details |
|---|---|
| Measures of pseudonymisation and encryption of personal data | Personal Data is encrypted in transit with TLS 1.2 or higher and at rest with industry-standard encryption. Integration credentials are also encrypted at the application level. |
| Measures for ensuring ongoing confidentiality, integrity, availability and resilience of processing systems and services | Company maintains business continuity, disaster recovery and incident response plans, reviewed annually. Data is backed up daily to a second region. |
| Measures for ensuring the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident | Daily backups to a second region and point-in-time recovery of databases allow timely restoration. Business continuity and disaster recovery plans are tested annually. |
| Processes for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures in order to ensure the security of the processing | Company monitors its controls continuously through a compliance platform, reviews its security policies annually and tests its business continuity and disaster recovery plans annually. Company’s controls are audited against SOC 2 Type II by an independent auditor. |
| Measures for user identification and authorization | Access to production systems and Customer Data requires single sign-on and multi-factor authentication, follows least privilege, is limited to personnel with a business need and is logged. |
| Measures for the protection of data during transmission | Personal Data is encrypted in transit with TLS 1.2 or higher, and public endpoints use HTTP Strict Transport Security. |
| Measures for the protection of data during storage | Personal Data is encrypted at rest. Integration credentials are also encrypted at the application level. Staff devices use encrypted storage. |
| Measures for ensuring physical security of locations at which personal data are processed | Personal Data is processed in the data centers of Company’s cloud providers, which maintain physical and environmental controls audited under SOC 2 and ISO 27001. Company does not store Customer Data on office systems. |
| Measures for ensuring events logging | Company logs security events, administrative actions and access to Customer Data, including support access, and keeps operational logs for no more than thirty days. |
| Measures for ensuring system configuration, including default configuration | Company maintains operations security and secure development policies, reviewed annually, with code review and automated vulnerability scanning. Customer controls the actions that the Services may take in its connected systems through its settings. |
| Measures for internal IT and IT security governance and management | Company operates an information security program with policies approved and reviewed annually, covering information security, access control, cryptography, data management, business continuity and disaster recovery, incident response, operations security, secure development, physical security, third-party management, risk management, asset management, human resource security and code of conduct. |
| Measures for certification/assurance of processes and products | Company is audited against SOC 2 Type II by an independent auditor and provides its most recent report on request, under confidentiality. |
| Measures for ensuring data minimisation | Company reads data from connected systems when it is needed instead of copying it in bulk, keeps operational copies for short periods, and processes only the data that Customer’s permissions allow. |
| Measures for ensuring data quality | Customer is responsible for the accuracy and legality of supplied data and its instructions under this DPA. |
| Measures for ensuring limited data retention | Personal Data is kept for the Services term and deleted under the Return or Destruction of Personal Data provisions. Operational copies, such as model traces, caches and logs, are kept for no more than thirty days. Backups expire within thirty-one days of deletion from active systems. |
| Measures for ensuring accountability | Personnel undergo background checks, sign confidentiality commitments and a code of conduct, and complete security training at hire and annually. Staff devices are centrally managed. |
| Measures for allowing data portability and ensuring erasure | Customer may request export in Company’s then-standard format without additional charge during the sixty-day Post-Termination Period. Company shall apply the Return or Destruction of Personal Data provisions across all relevant stores and Authorized Subprocessors. |
| Technical and organizational measures of subprocessors | Company reviews vendors before engagement and binds each Authorized Subprocessor by a written agreement with data protection obligations no less protective than this DPA. Authorized Subprocessors that provide AI model inference are bound by terms that prevent them from using Customer Data to train their models. |
Exhibit D
UK Addendum
International Data Transfer Addendum to the EU Commission Standard Contractual Clauses
Part 1: Tables
Table 1: Parties
| Start Date | The DPA Effective Date | |
| The Parties | Exporter | Importer |
| Parties’ Details | Customer, as identified in Exhibit B. | Coreplane Labs, Inc., as identified in Exhibit B. |
| Key Contact | See Exhibit B of this DPA | See Exhibit B of this DPA |
Table 2: Selected SCCs, Modules and Selected Clauses
| EU SCCs | The Version of the Approved EU SCCs which this UK Addendum is appended to as defined in the DPA and completed by Sections 9.2 and 9.3 of the DPA. |
Table 3: Appendix Information
| Annex 1A: List of Parties | As per Table 1 above |
| Annex 1B: Description of Transfer | See Exhibit B of this DPA |
| Annex II: Technical and organisational measures including technical and organisational measures to ensure the security of the data: | See Exhibit C of this DPA |
| Annex III: List of Sub processors (Modules 2 and 3 only): | See Exhibit B of this DPA |
Table 4: Ending this UK Addendum when the Approved UK Addendum Changes
| Ending this UK Addendum when the Approved UK Addendum changes | ☒Importer |
Part 2: Mandatory Clauses
The Mandatory Clauses of the UK Addendum are incorporated herein by reference.