This Evergreen Data Processing Addendum (this “DPA”) is part of the Evergreen Terms of Service (the “Terms”) between eShares, Inc. DBA Carta, Inc. (“Carta”) and Customer. It applies automatically when Customer accepts the Terms, and no signature is required. Capitalized terms not defined in this DPA have the meanings given in the Terms.
1Scope and Precedence
#1.1Scope
#This DPA applies only to Carta’s processing of Customer Personal Data on Customer’s behalf in providing Evergreen. It does not apply to the Other Carta Services.
1.2Precedence
#If this DPA conflicts with the Terms regarding the processing of Customer Personal Data, this DPA controls. If the Standard Contractual Clauses conflict with this DPA, the Standard Contractual Clauses control.
2Definitions
#- Account Data
- means personal data Carta collects to create and administer Accounts, process payments, provide support, and communicate with Customer and its Authorized Users.
- Customer Personal Data
- means personal data contained in Customer Content that Carta processes on Customer’s behalf. It excludes Account Data and Usage Data.
- Data Protection Laws
- means all data protection and privacy laws that apply to the processing of Customer Personal Data under the Terms, including, as applicable, the California Consumer Privacy Act as amended (the “CCPA”) and other U.S. state privacy laws, the EU General Data Protection Regulation 2016/679 (the “GDPR”), the UK GDPR and UK Data Protection Act 2018, and the Swiss Federal Act on Data Protection.
- Personal Data Breach
- means a confirmed breach of Carta’s security leading to the accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of, or access to, Customer Personal Data in Carta’s possession. It excludes unsuccessful attempts and activities that do not compromise the security of Customer Personal Data, such as pings, port scans, and failed log-in attempts.
- Standard Contractual Clauses
- means the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914, as completed under Section 11.
- Subprocessor
- means a third party, including a Carta affiliate, that Carta engages to process Customer Personal Data on Carta’s behalf in providing Evergreen.
- UK Addendum
- means the International Data Transfer Addendum to the Standard Contractual Clauses issued by the UK Information Commissioner, version B1.0.
Terms such as “controller,” “processor,” “service provider,” “data subject,” “personal data,” “processing,” “sell,” and “share” have the meanings given in the applicable Data Protection Laws.
3Roles of the Parties
#3.1Carta as Processor
#As between the parties, Customer is the controller of Customer Personal Data, or a processor acting for a third-party controller. Carta is a processor or subprocessor and, for purposes of the CCPA, a service provider.
3.2Carta as Independent Controller
#Carta processes Account Data and Usage Data as an independent controller under the Evergreen Privacy Notice. Carta uses that data to operate, bill for, secure, support, and improve Evergreen, to prevent fraud and abuse, and to comply with law. This DPA does not apply to that processing.
3.3Third-Party Controller
#If Customer acts as a processor for a third-party controller, Customer is Carta’s sole point of contact and gives all instructions on that controller’s behalf. Customer warrants that the controller has authorized those instructions and Carta’s engagement.
4Customer Instructions and Responsibilities
#4.1Instructions
#The Terms, this DPA, and Customer’s configuration and use of Evergreen, including instructions given to Agents by Customer and its Authorized Users, are Customer’s complete instructions to Carta. Additional instructions require Carta’s written agreement and may be subject to additional fees.
4.2Customer Responsibilities
#Customer is solely responsible for (a) the accuracy, quality, and legality of Customer Personal Data and how Customer obtained it, (b) providing all required notices and obtaining all required consents and other legal bases for the processing, and (c) ensuring that its instructions comply with Data Protection Laws and will not cause Carta to violate them.
4.3Restricted Data
#Customer will not submit any data prohibited by Section 9.5 of the Terms or any special categories of personal data. If Customer does so, Customer is solely responsible for that submission, and Carta assumes no obligations for that data beyond those in this DPA.
4.4Customer-Directed Third Parties
#When Customer or its Authorized Users direct Evergreen to send Customer Personal Data to a Third-Party Service, including a Model Provider accessed with BYOK Credentials, a code host, or another integration Customer connects, that third party is not Carta’s Subprocessor. The transfer is made on Customer’s instruction under Section 8.3 of the Terms, and Customer’s agreement with that third party governs its processing.
5Carta Obligations
#5.1Purpose Limitation
#Carta will process Customer Personal Data only to provide Evergreen under Customer’s instructions, to secure Evergreen and enforce the Terms, and as Data Protection Laws require. If law requires other processing, Carta will notify Customer before processing unless the law prohibits notice.
5.2CCPA Commitments
#Carta will not (a) sell or share Customer Personal Data, (b) retain, use, or disclose Customer Personal Data for any purpose other than the business purposes in the Terms, or outside the direct business relationship between Carta and Customer, or (c) combine Customer Personal Data with personal data Carta receives from other sources, except as the CCPA permits. Carta will notify Customer if it determines it can no longer meet its obligations under the CCPA. Customer may then take reasonable steps to stop and remediate unauthorized use of Customer Personal Data.
5.3No Model Training
#Carta will not use Customer Personal Data to train or fine-tune AI models, consistent with Section 9.3 of the Terms. For Carta-Provided Models, Carta will maintain contractual terms or configurations with the applicable Model Provider that prohibit it from using Customer Personal Data to train its models.
5.4De-Identified Data
#If Carta de-identifies Customer Personal Data as the Data Protection Laws permit, Carta will take reasonable measures to prevent re-identification, will not attempt to re-identify the data, and will contractually require any recipient to do the same.
5.5Personnel
#Carta will ensure that personnel authorized to process Customer Personal Data are bound by confidentiality obligations.
5.6Unlawful Instructions
#Carta will inform Customer if, in Carta’s opinion, an instruction violates Data Protection Laws. Carta may suspend processing under that instruction without liability.
6Subprocessors
#6.1Authorization
#Customer gives Carta general authorization to engage Subprocessors, including Carta’s affiliates, its hosting providers, and the Model Providers for Carta-Provided Models. Carta’s current Subprocessors for Evergreen are listed at evergreen.carta.com/subprocessors (the “Subprocessor List”).
6.2Subprocessor Obligations
#Carta will enter into a written agreement with each Subprocessor imposing data protection obligations no less protective of Customer Personal Data than those in this DPA, to the extent applicable to the Subprocessor’s services. Subject to Section 13, Carta remains responsible for each Subprocessor’s performance of those obligations.
6.3Changes
#Carta will update the Subprocessor List at least 7 days before a new Subprocessor begins processing Customer Personal Data. Customer may subscribe to updates at evergreen.carta.com/subprocessors, and Customer is responsible for subscribing.
6.4Objections
#Customer may object to a new Subprocessor in writing within 7 days after the update, on reasonable grounds relating to data protection. The parties will discuss the objection in good faith. If they cannot resolve it within a reasonable time, Customer’s sole and exclusive remedy is to stop using the affected part of Evergreen or to close its Account under Section 15.2 of the Terms. Customer remains responsible for Fees incurred before that time, and Section 6.6 of the Terms applies to unused Credits. If Customer does not object in time, it is deemed to have approved the Subprocessor.
6.5Emergency Model Changes
#Section 3.3 of the Terms permits Carta to add, change, or remove Models. If an emergency replacement of a Carta-Provided Model is needed for security, availability, or legal reasons, Carta may engage the replacement Model Provider immediately and will update the Subprocessor List promptly afterward.
7Security
#7.1Security Measures
#Carta will maintain the technical and organizational measures described in Annex II. Carta may update them, provided the updates do not materially reduce the overall protection of Customer Personal Data. Section 11.1 of the Terms continues to apply to Carta’s responsibility for unauthorized access to Customer Personal Data, subject to Section 13.
7.2Customer Security Responsibilities
#Customer is responsible for its own security decisions, including its Account credentials, the access, credentials, and permissions it gives Agents under Section 5 of the Terms, its Collaborator permissions, and the security of its Customer Repositories and systems. Customer acknowledges that Annex II provides appropriate security for its intended processing.
8Personal Data Breaches
#8.1Notice
#Carta will notify Customer without undue delay after becoming aware of a Personal Data Breach. Carta will send notice to the email address on the Account.
8.2Information and Assistance
#Carta will provide information reasonably available to it about the Personal Data Breach, including, where known, the categories of data and data subjects affected. Carta will take steps it considers reasonable to contain and remediate the Personal Data Breach, and will give reasonable assistance to help Customer meet its own notification obligations.
8.3No Admission
#Carta’s notice of or response to a Personal Data Breach is not an acknowledgment of fault or liability.
9Data Subject Requests and Assistance
#9.1Data Subject Requests
#If Carta receives a request from a data subject about Customer Personal Data, Carta will direct the data subject to Customer and, where lawful and the request identifies Customer, notify Customer. Carta will not otherwise respond unless law requires. Customer is responsible for responding, including by using Evergreen’s functionality.
9.2Assistance
#If Customer cannot respond to a request, or cannot meet its obligations to conduct data protection impact assessments or consult supervisory authorities, using the information available to it, Carta will give reasonable assistance, taking into account the nature of the processing. Customer will reimburse Carta’s reasonable costs of that assistance to the extent law permits.
10Audits
#10.1Reports
#On Customer’s written request, no more than once every 12 months, Carta will provide information reasonably needed to demonstrate its compliance with this DPA. That information may consist of summaries of third-party audit reports or certifications, security questionnaire responses, or similar documentation.
10.2Audits
#If Data Protection Laws require more, and the information under Section 10.1 is not reasonably sufficient, Customer may engage an independent auditor, bound by confidentiality obligations and reasonably acceptable to Carta, to audit Carta’s compliance with this DPA. Any audit (a) requires at least 30 days’ written notice, (b) will follow a scope, time, and duration the parties agree on, (c) will occur during business hours and minimize disruption to Carta, (d) will occur no more than once every 12 months, unless a supervisory authority requires it or it follows a Personal Data Breach, and (e) is at Customer’s sole expense, including reimbursement of Carta’s reasonable costs.
11International Transfers
#11.1Location
#Customer acknowledges that Carta and its Subprocessors process Customer Personal Data primarily in the United States, and authorizes those transfers.
11.2EEA Transfers
#For transfers of Customer Personal Data subject to the GDPR to a country without an adequacy decision, the parties enter into the Standard Contractual Clauses, which are incorporated by reference and completed as follows: (a) Module Two applies where Customer is a controller, and Module Three applies where Customer is a processor; (b) Clause 7 does not apply; (c) in Clause 9, Option 2 applies, with the notice period in Section 6.3 of this DPA; (d) in Clause 11, the optional language does not apply; (e) in Clause 17, Option 1 applies, and the governing law is Irish law; (f) in Clause 18(b), disputes will be resolved by the courts of Ireland; and (g) Annexes I, II, and III of this DPA complete the corresponding Annexes of the Standard Contractual Clauses.
11.3UK Transfers
#For transfers subject to the UK GDPR, the UK Addendum applies and is incorporated by reference. Tables 1 through 3 are completed with the information in Section 11.2 and the Annexes, and in Table 4, either party may end the UK Addendum as permitted by its Section 19.
11.4Swiss Transfers
#For transfers subject to the Swiss Federal Act on Data Protection, the Standard Contractual Clauses apply with these changes: references to the GDPR include that Act, the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for those transfers, and the term “member state” does not prevent data subjects in Switzerland from bringing claims in their place of habitual residence.
12Government Requests
#If a government authority requests Customer Personal Data, Carta will first try to redirect the authority to Customer, and may give the authority Customer’s basic contact information for that purpose. If Carta is compelled to disclose Customer Personal Data, Carta will give Customer reasonable notice so Customer can seek a protective order, unless law prohibits notice. Carta will disclose only the data it determines in good faith that law requires.
13Liability
#Each party’s liability arising out of or relating to this DPA, including the Standard Contractual Clauses, is subject to the exclusions and limitations of liability in Section 17 of the Terms, as they apply to that party. Carta’s liability counts toward, and does not add to, the cap in Section 17.2 of the Terms. This Section does not limit either party’s liability to data subjects under the Standard Contractual Clauses to the extent that limitation is not permitted.
14Return and Deletion
#On termination of the Terms, Customer may export Customer Content as Section 15.5 of the Terms provides. After the export period, Carta will delete Customer Personal Data within a reasonable time, subject to its standard backup and retention practices. Carta may retain Customer Personal Data that law requires it to keep, will keep that data confidential, and will process it only for the purpose requiring its retention. Carta will provide a certification of deletion only on Customer’s written request.
15Term and Changes
#This DPA remains in effect as long as Carta processes Customer Personal Data. Carta may update this DPA under Section 20.2 of the Terms, or at any time to comply with Data Protection Laws or the requirements of a supervisory authority, provided the update does not materially reduce the protection of Customer Personal Data.
Annex I: Description of Processing
#- A.
Parties. Data exporter: Customer, as identified in its Account, acting as controller or as processor for a third-party controller. Contact: the email address on the Account. Data importer: eShares, Inc. DBA Carta, Inc., 333 Bush Street, Floor 23, Suite 2300, San Francisco, CA 94104, acting as processor. Contact: privacy@carta.com. Each party is deemed to have signed this Annex when Customer accepts the Terms.
- B.
Categories of Data Subjects. Individuals whose personal data Customer or its Authorized Users include in Customer Content. These may include Customer’s employees, contractors, Authorized Users, and Collaborators, and individuals whose personal data appears in Customer Repositories, code, files, or prompts.
- C.
Categories of Personal Data. As determined by Customer. Typically names, usernames, email addresses, and other identifiers or contact information contained in code, commit history, comments, configuration files, logs, test data, prompts, and Outputs.
- D.
Sensitive Data. None. Customer will not submit sensitive data or special categories of personal data under Section 4.3.
- E.
Frequency of Transfer. Continuous for the duration of the Terms.
- F.
Nature and Purpose of Processing. Hosting, storage, transmission, and processing of Customer Content to run Agents and Sessions, send Inputs to and receive Outputs from Carta-Provided Models, enable collaboration in Workspaces, provide support, secure Evergreen, and enforce the Terms.
- G.
Duration and Retention. For the Term, plus the export and deletion period in Section 14 of this DPA.
- H.
Subprocessor Transfers. Same subject matter, nature, and duration as above, limited to each Subprocessor’s services.
- I.
Competent Supervisory Authority. For EEA transfers, the Irish Data Protection Commission, unless Clause 13 of the Standard Contractual Clauses requires otherwise. For UK transfers, the UK Information Commissioner. For Swiss transfers, the Swiss Federal Data Protection and Information Commissioner.
Annex II: Technical and Organizational Security Measures
#Carta maintains the following measures for Evergreen, which Carta may update under Section 7.1.
- Access Control. Role-based access to production systems on a least-privilege basis, multi-factor authentication for personnel, periodic access reviews, and prompt removal of access when personnel leave.
- Encryption. Encryption of Customer Content in transit using TLS 1.2 or higher. TLS 1.1 and lower are rejected. Encrypted storage of BYOK Credentials and customer-supplied secrets, with keys managed through AWS Postgres Database (encrypted).
- Agent Isolation. Execution of each Session in an isolated environment segregated from other customers’ Sessions.
- Network and Infrastructure Security. Separate production and non-production environments, firewalls and network access controls, and vulnerability management and patching.
- Logging and Monitoring. Security logging and monitoring of production systems, with alerting for anomalous activity.
- Incident Response. A documented incident response plan, with a channel for reporting and triaging security incidents.
- Personnel. Background checks where lawful, confidentiality obligations, and security training at hire and at least annually.
- Vendor Management. Security review of Subprocessors before engagement, and written data protection terms.
- Business Continuity. Backups and disaster recovery procedures for Evergreen systems.
Annex III: Subprocessors
#Carta’s current Subprocessors for Evergreen are listed at evergreen.carta.com/subprocessors; and Carta’s affiliates as needed to provide Evergreen. Carta’s payment processor receives only Account Data and is not a Subprocessor. Model Providers and other Third-Party Services Customer accesses with BYOK Credentials or connects at its direction are not Subprocessors under Section 4.4.