Data Processing Agreement
This Data Processing Agreement (“DPA”) forms an integral part of the Terms of Service between the party named as “Customer” in the Agreement (“Customer”) and Pylon Labs, Inc. (“Pylon”) involving the provision of Pylon’s Services or other agreement between Customer and Pylon governing Customer’s use of Pylon’s Services (as applicable, the “Agreement”) and is hereby incorporated by reference into the Agreement. All capitalized terms not otherwise defined in this DPA will have the meaning given to them in the Agreement.
The parties hereby agree as follows:
- Definitions and Interpretation
- Unless otherwise defined herein, capitalized terms and expressions used in this DPA shall have the following meanings:
- “Customer Personal Data” means any Personal Data subject to Data Protection Laws contained in Customer Data that Customer provides or makes available to Pylon and is Processed on behalf of Customer in the course of providing the Services;
- “Data Protection Laws” means any applicable laws and regulations in any relevant jurisdiction where Services are provided relating to the use or processing of Personal Data, which may include depending on the circumstances (but is not limited to): (i) the California Consumer Privacy Act (Cal. Civ. Code §§ 1798.100 et seq.), as amended by the California Privacy Rights Act of 2020 (“CCPA”); (ii) the General Data Protection Regulation (Regulation (EU) 2016/679) (“EU GDPR”); (iii) the UK Data Protection Act 2018 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 with the EU GDPR, collectively, the “GDPR”); and (iv) the Swiss Federal Act on Data Protection (“FADP”); in each case, as updated, amended or replaced from time to time;
- “Data Subject” means an identified or identifiable natural person to whom Personal Data relates.
- “EEA” means the European Economic Area;
- “EU SCCs” means the 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).
- “ex-EEA Transfer” means the transfer of Customer Personal Data, which is processed in accordance with the EU GDPR, from the Data Exporter to the Data Importer (or its premises) outside the EEA, and such transfer is not governed by an adequacy decision made by the European Commission in accordance with the relevant provisions of the EU GDPR.
- “ex-UK Transfer” means the transfer of Customer Personal Data covered by Chapter V of the UK GDPR, which is processed in accordance with the UK GDPR and the Data Protection Act 2018, from the Data Exporter to the Data Importer (or its premises) outside the United Kingdom (the “UK”), and such transfer is not governed by an adequacy decision made by the Secretary of State in accordance with the relevant provisions of the UK GDPR and the Data Protection Act 2018.
- “Personal Data” means “personal data” or “personal information” as defined under Data Protection Laws.
- “Personal Data Breach” means a breach of security of Pylon or its Subprocessors leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data in Pylon’s possession, custody or control. Personal Data Breaches do not include unsuccessful attempts or activities that do not compromise the security of Customer Personal Data, including unsuccessful log-in attempts, pings, port scans, denial of service attacks, or other network attacks on firewalls or networked systems.
- “Process” or “Processed” means any operation or set of operations which is performed on Personal Data or on sets of 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;
- “Services” means those services and activities to be supplied to or carried out by or on behalf of Pylon for Customer pursuant to the Agreement.
- “Standard Contractual Clauses” means the EU SCCs and the UK SCCs.
- “Subprocessor” means any person appointed by or on behalf of Pylon to process Customer Personal Data on behalf of the Customer in connection with the DPA.
- “UK SCCs” means the EU SCCs, as amended by the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses of 21 March 2022 issued under Section 119A of the UK Data Protection Act 2018, available at https://ico.org.uk/media/for-organisations/documents/4019539/international-data-transfer-addendum.pdf (the “UK Addendum”) and incorporated by reference to this DPA.
- As used in this DPA, the terms, “Controller”, “Member State”, “Processor”, and “Supervisory Authority” shall be interpreted in accordance with the GDPR.
- As used in this DPA, the terms “Business”, “Business Purpose”, “Sell”, “Share” and “Service Provider” shall be interpreted in accordance with the CCPA.
- Unless otherwise defined herein, capitalized terms and expressions used in this DPA shall have the following meanings:
- Scope; Role of the Parties
- This DPA applies to the Processing of Customer Personal Data by Pylon.
- With respect to Customer Personal Data, the parties agree that Pylon is a data Processor (or, for CCPA purposes, a Service Provider) and Customer is a data Controller (or, for CCPA purposes, a Business). Each party is responsible for complying with Data Protection Laws as applicable to such party in its respective role.
- Processing of Customer Personal Data
- Pylon shall not Process Customer Personal Data other than on Customer’s documented instructions, including as documented in the Agreement and this DPA as well as through Customer’s use of the Services unless applicable laws require otherwise. If Pylon is required by applicable laws to otherwise Process Customer Personal Data, Pylon shall inform Customer of that legal requirement before Processing, unless that law prohibits such information on important grounds of public interest.
- Customer instructs Pylon to process Customer Personal Data to provide the Services to Customer and its Authorized Users. The subject matter, nature, purpose, and duration of this processing, as well as the types of Customer Personal Data collected and categories of Data Subjects, are described in Exhibit A to this DPA.
- Pylon shall ensure that its personnel authorized to Process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
- Customer shall, in its use of the Services, at all times Process Customer Personal Data, and provide instructions for the Processing of Customer Personal Data, in compliance with Data Protection Laws. Customer shall ensure that the Processing of Customer Personal Data in accordance with Customer’s instructions will not cause Pylon to be in breach of Data Protection Laws. Customer is solely responsible for the accuracy, quality, and legality of (i) the Customer Personal Data provided to Pylon by or on behalf of Customer, (ii) the means by which Customer acquired any Customer Personal Data, and (iii) the instructions it provides to Pylon regarding the Processing of Customer Personal Data.
- Pylon is prohibited from (i) Selling or Sharing Customer Personal Data; (ii) retaining, using, or disclosing Customer Personal Data for any commercial purpose other than the Business Purposes specified in this DPA and the Agreement; (iii) retaining, using, or disclosing Customer Personal Data outside the direct business relationship between Customer and Pylon; and (iv) combining Customer Personal Data with Personal Data obtained from, or on behalf of, sources other than Customer except as permitted under Data Protection Laws.
- Pylon shall notify Customer after Pylon determines that it can no longer meet its obligations under Data Protection Laws. If Customer reasonably believes that Pylon’s Processing of Customer Personal Data is not consistent with the requirements of the CCPA and upon Customer’s reasonable notification of the same to Pylon, Customer and Pylon will work together in good faith to remedy the issue, or, if after working together Customer reasonably determines that the issue cannot be remedied, Pylon will stop Processing the affected Customer Personal Data upon written instruction from Customer.
- Security
- Pylon shall implement and maintain technical and organizational measures in relation to Customer Personal Data designed to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure of or access, and at a minimum such measures as are compliant with Data Protection Laws. Pylon’s security measures with respect to Customer Data as of the effective date of this DPA are set forth in Exhibit C. Pylon may update such security measures from time to time, provided the updated measures do not materially decrease the overall protection of Customer Personal Data.
- Subprocessing
- Customer hereby grants its general authorization and consent for Pylon to engage its Affiliates as well as the Subprocessors on the List (defined below) to Process Customer Personal Data in connection with the Services.
- A list of Pylon’s current Subprocessors (the “List”) is available to Customer at usepylon.com/subprocessors. Such List may be updated by Pylon from time to time. Pylon will provide a mechanism to subscribe to notifications (which may include but are not limited to email notifications) of new Subprocessors and Customer, if it wishes, will subscribe to such notifications where available. If Customer does not subscribe to such notifications, Customer waives any right it may have to receive prior notice of changes to Subprocessors. If Customer subscribes to such notifications, Pylon will, at least ten (10) days before allowing new third-party Subprocessors to Process Customer Personal Data, add such third party to the List and notify Customer via the aforementioned notification mechanism. Customer may object to such an engagement by informing Pylon in writing within ten (10) days of receipt of the aforementioned notice by Customer, provided such objection is in writing and based on reasonable grounds relating to data protection. Customer acknowledges that certain Subprocessors are essential to providing the Services and that objecting to the use of a Subprocessor may prevent Pylon from providing the Services to Customer.
- If Customer objects to an engagement in accordance with the preceding section, Pylon may cure the objection through one of the following options: (i) Pylon will cancel its plans to use the new Subprocessor with regards to processing Customer Personal Data or will offer an alternative to provide the Services without such Subprocessor; (ii) Pylon will take the corrective steps requested by Customer in Customer’s objection notice and proceed to use the Subprocessor; or (iii) Customer may cease providing Customer Personal Data to Pylon for processing involving such Subprocessor. If the objection(s) have not been resolved to the reasonable satisfaction of the parties within thirty (30) days of Pylon’s receipt of Customer’s objection notice, then either party may terminate the Agreement with respect to the Services that cannot be provided without the use of the new Subprocessor and in such case, Customer will be refunded any pre-paid fees for the applicable subscriptions to the extent they cover periods or terms following the date of such termination. Such termination right is Customer’s sole and exclusive remedy if Customer objects to any new Subprocessor.
- Pylon will enter into a written agreement with each Subprocessor imposing on the Subprocessor data protection obligations comparable to those imposed on Pylon under this DPA with respect to the protection of Customer Personal Data. Pylon agrees to be liable for the acts and omissions of its Subprocessors to the same extent Pylon would be liable under the terms of the DPA if it performed such acts or omissions itself.
- With respect to Standard Contractual Clauses as described in this DPA, (i) the above authorizations will constitute Customer’s prior written consent to the subcontracting by Pylon of the Processing of Customer Personal Data if such consent is required under the Standard Contractual Clauses, and (ii) the parties agree that the copies of the agreements with Subprocessors that must be provided by Pylon 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 Pylon beforehand, and that such copies will be provided by Pylon only upon request by Customer.
- Data Subject Rights
- Taking into account the nature of the Processing, Pylon shall assist Customer by implementing appropriate technical and organizational measures, insofar as this is possible, for the fulfillment of the Customer obligations, as reasonably understood by Customer, to respond to requests to exercise Data Subject rights under Data Protection Laws with respect to Customer Personal Data.
- Pylon shall:
- To the extent Pylon is able to verify that a Data Subject is associated with Customer, promptly notify Customer if it receives a request from a Data Subject under any Data Protection Law in respect of Customer Personal Data; and
- other than to confirm receipt, ensure that it does not respond to that request except on the documented instructions of Customer or as required by Applicable Laws to which Pylon is subject, in which case Pylon shall to the extent permitted by Applicable Laws inform Customer of that legal requirement before Pylon responds to the request. In the absence of Customer’s instructions to the contrary, Pylon may inform the Data Subject that the request cannot be acted upon because the request has been sent to a data Processor or Service Provider.
- Personal Data Breach
- Pylon shall notify Customer without undue delay upon Pylon becoming aware of a Personal Data Breach affecting Customer Personal Data, providing Customer with information to allow the Customer to meet any obligations to report or inform Data Subjects or regulatory authorities of the Personal Data Breach under Data Protection Laws. Pylon’s notification of or response to a Personal Data Breach will not be construed as Pylon’s acknowledgement of any fault or liability with respect to the Personal Data Breach.
- Pylon shall reasonably cooperate with Customer and take reasonable commercial steps as are requested by Customer to assist in the investigation, mitigation and remediation of each such Personal Data Breach.
- Data Protection Impact Assessment and Prior Consultation
- Pylon shall provide reasonable assistance to Customer with any data protection impact assessments, and prior consultations with Supervisory Authorities or other competent data privacy authorities, which Customer reasonably considers to be required by article 35 or 36 of the EU GDPR or equivalent provisions of any other Data Protection Law, in each case solely in relation to Processing of Customer Personal Data by, and taking into account the nature of the Processing and information available to, Pylon.
- Audit rights
- Pylon uses external auditors to assess the adequacy of its security measures with respect to Customer Personal Data. Such audits are performed at least once annually at Pylon’s expense by independent third-party security professionals at Pylon’s selection and result in the generation of a confidential audit report (“Audit Report”). Upon Customer’s written request, Pylon will provide Customer with a copy of its latest Audit Report at no cost to Customer, up to once per year. To the extent permitted by Data Protection Laws, such Audit Reports will be Pylon’s Confidential Information under the confidentiality provisions of the Agreement. To the extent permitted by Data Protection Laws, Customer agrees that the Audit Reports will be used to satisfy any audit or inspection request by or on behalf of Customer in relation to Data Protection Laws, this DPA, and/or the Agreement.
- To the extent Data Protection Laws require audits beyond the Audit Reports, Customer and Pylon may mutually agree to an audit plan that: (a) ensures the use of an independent third party; (b) provides notice to Pylon in a timely fashion, but at a minimum 30 days’ notice; (c) requests access only during business hours; (d) is performed at Customer’s sole cost and expense; (e) occurs no more than once annually; and (f) restricts findings to only Customer Personal Data relevant to Customer. To the extent permitted by Data Protection Laws, all information collected in connection with such audits will be Pylon’s Confidential Information under the confidentiality provisions of the Agreement.
- Data Transfer
- The parties agree that Pylon may transfer Customer Personal Data Processed under this DPA outside the EEA, the UK, or Switzerland. Customer acknowledges that Pylon’s primary Processing operations take place in the United States. If Pylon transfers Customer Personal Data Processed under this DPA to a jurisdiction for which the European Commission has not issued an adequacy decision, Pylon will ensure that appropriate safeguards have been implemented for the transfer of Customer Personal Data in accordance with the GDPR.
- Ex-EEA Transfers. The parties agree that ex-EEA Transfers are made pursuant to the EU SCCs, which are deemed entered into (and incorporated into this DPA by this reference) and completed as follows:
- Module Two (Controller to Processor) of the EU SCCs apply when Customer is a Controller and Pylon is Processing Customer Personal Data on behalf of Customer as a Processor.
- Module Three (Processor to Subprocessors) of the EU SCCs apply when Customer is a Processor and Pylon is Processing Customer Personal Data on behalf of Customer as a subprocessor.
- For each module of the EU SCCs, where applicable the following applies:
- The optional docking clause in Clause 7 does not apply.
- In Clause 9, Option 2 (general written authorization) applies;
- In Clause 11, the optional language does not apply;
- All square brackets in Clause 13 are hereby removed;
- In Clause 17 (Option 1), the EU SCCs will be governed by Ireland law.
- In Clause 18(b), disputes will be resolved before the courts of Ireland;
- Exhibit B to this DPA contains the information required in Annex I and Annex III of the EU SCCs;
- Exhibit C to this DPA contains the information required in Annex II of the EU SCCs; and
- By entering into this DPA, the parties are deemed to have signed the EU SCCs incorporated herein, including their Annexes.
- Ex-UK Transfers. The parties agree that ex-UK Transfers are made pursuant to the UK SCCs, which are deemed entered into and incorporated into this DPA by reference, and amended and completed in accordance with the UK Addendum, which is incorporated herein as Exhibit D of this DPA.
- Transfers from Switzerland. The parties agree that transfers of Customer Personal Data from Switzerland are made pursuant to the EU SCCs with the following modifications:
- The terms “General Data Protection Regulation” or “Regulation (EU) 2016/679” as utilized in the EU SCCs shall be interpreted as references to the FADP.
- 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 EU GDPR. Subject to the foregoing, all other requirements of Clause 13 shall be observed.
- 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.
- If either (i) any of the means of legitimizing transfers of Customer Personal Data outside of the EEA or UK set forth in this DPA cease to be valid or (ii) any supervisory authority requires transfers of Customer Personal Data pursuant to those means to be suspended, then Data Importer may by notice to the Data Exporter, with effect from the date set out in such notice, amend or put in place alternative arrangements in respect of such transfers, as required by Data Protection Laws.
- In the event of inconsistencies between the provisions of the Standard Contractual Clauses and this DPA or the Agreement, the Standard Contractual Clauses shall take precedence. The terms of this DPA shall not vary the Standard Contractual Clauses in any way.
- Term; Data Return and Destruction
- This DPA will remain in full force and effect so long as the Agreement remains in effect or Pylon retains Customer Personal Data in its possession or control.
- On termination of the Agreement for any reason or expiry of its term, and within 30 days of Customer’s request, Pylon will securely delete or destroy or, if directed in writing by Customer, return as specified in the Agreement, Customer Personal Data in its possession or control. Notwithstanding the foregoing, Pylon may retain Customer Personal Data in its ordinary course archival backups provided that: (i) Pylon operates and complies with a reasonable data archive and retention policy with a schedule for deletion and (ii) this DPA will continue to apply to Customer Personal Data until it is so deleted. If Customer and Pylon have entered into Standard Contractual Clauses as described in this DPA, the parties agree that the certification of deletion of Personal Data that is described in Clause 8.1(d) and Clause 8.5 of the EU SCCs (as applicable) shall be provided by Pylon to Customer only upon Customer’s request.
- General Terms
- This DPA forms part of the Agreement and is without prejudice to the rights and obligations of the parties under the Agreement which shall continue to have full force and effect. In the event of any conflict between the terms of this DPA and the terms of the Agreement, the terms of this DPA shall prevail so far as the subject matter concerns the processing of Customer Personal Data.
- To the maximum extent permitted by law, Pylon’s liability under or in connection with this DPA (including under the SCCs) is subject to the exclusions and limitations on liability contained in the Agreement. The foregoing shall not limit the rights of data subjects pursuant to Data Protection Laws.
- Except where and to the extent required as a matter of Data Protection Laws, this DPA does not confer any third-party beneficiary rights; it is intended for the benefit of the parties hereto and their respective permitted successors and assigns only, and is not for the benefit of, nor may any provision hereof be enforced by, any other person.
- This DPA and any action related thereto shall be governed by and construed in accordance with the laws as specified in the Agreement, without giving effect to any conflicts of laws principles. The parties consent to the personal jurisdiction of, and venue in, the courts specified in the Agreement.
- If any provision of this DPA is, for any reason, held to be invalid or unenforceable, the other provisions of the DPA will remain enforceable.
- No modification of, amendment to, or waiver of any rights under the DPA will be effective unless in writing and signed by an authorized signatory of each party. This DPA may be executed in counterparts, each of which shall be deemed to be an original, but all of which, taken together, shall constitute one and the same agreement. Each party warrants to the other that the execution and delivery of this DPA, and the performance of such party’s obligations hereunder, have been duly authorized and that this DPA is a valid and legally binding agreement on each such party, enforceable in accordance with its terms.
EXHIBIT A
Details of Processing
Nature and Purpose of Processing: Pylon will Process Customer Personal Data as necessary to provide the Services under the Agreement, for the purposes specified in the Agreement and this DPA, and in accordance with Customer’s instructions as set forth in this DPA. The nature of Processing includes, without limitation:
- Receiving data, including collection, accessing, retrieval, recording, and data entry
- Protecting data, including restricting, encrypting, and security testing
- Holding data, including storage, organization, and structuring
- Erasing data, including destruction and deletion
- Analyzing data, including product usage assessment
- Sharing data, including disclosure to subprocessors as permitted in this DPA
Categories of Data Subjects: Data Subjects include the individuals whose Customer Personal Data is provided to Pylon through the Services by or at the direction of Customer or by any employee or end user of Customer which may include, but is not limited to Personal Data relating to users, employees, contractors, agents, vendors, customers, visitors, and such other individuals whose Personal Data may be submitted to the Services; the extent of which is determined and controlled by Customer in its sole discretion depending on its use of the Services.
Categories of Personal Data: Personal Data relating to individuals provided to Pylon via the Services, by or at the direction of Customer which may include, but is not limited to the following categories of Personal Data: name, email, job title, Slack username, and communication data; the extent of which is determined and controlled by Customer in its sole discretion depending on its use of the Services.
The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis): Pylon will Process Customer Personal Data on an ongoing basis to provide the Services to the Customer in accordance with, and as otherwise permitted by, the Agreement, and for any disclosures compelled by law.
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period: The term of the Agreement plus the period from the expiry or termination of the Agreement until deletion of all Customer Personal Data by Pylon in accordance with the Agreement.
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 SCCs.
- The Parties
Data exporter(s):
Name: The party named as “Customer” in the Agreement.
Address: The address for Customer associated with its Pylon account or as otherwise specified in the Order Form or Agreement.
Contact person’s name, position and contact details: The contact details for Customer associated with its Pylon account or as otherwise specified in the Order Form or Agreement.
Activities relevant to the data transferred under these Clauses: As described in Section 2 of the DPA.
Signature and date: By using the Services to transfer Customer Personal Data to Pylon located in a non-adequate country, the data exporter will be deemed to have signed this Exhibit B.
Role (controller/processor): Controller
Data importer(s):
Name: Pylon Labs, Inc.
Address and contact information: 690 5th Street, San Francisco, CA 94107; security@usepylon.com
Activities relevant to the data transferred under these Clauses: As described in Section 2 of the DPA.
Signature and date: By transferring Customer Personal Data to a non-adequate country on Customer’s instructions, the data importer will be deemed to have signed this Exhibit B.
Role (controller/processor): Processor