Contents
COR Global Ltd., a company incorporated in the State of Delaware, United States of America
COR retains the version of this Agreement applicable to the Customer, whether separately executed or incorporated by reference, and provides a copy to the Customer on written request.
The Parties#
Processor: COR Global Ltd., a company incorporated in the State of Delaware, United States of America, with its registered office at 900 Foulk Road, Suite 201, Wilmington, Delaware 19803 (“COR”).
Controller: The Customer identified in the Principal Agreement, being the counterparty to COR under the applicable Order. Where the Customer processes personal data on behalf of a third-party controller, clause 3.4 applies.
Nature and Execution#
This Agreement supplements the Principal Agreement (as defined below) and, from the Effective Date, forms an integral and inseparable part of it.
This Agreement takes effect: (a) where separately executed by the Parties, including by electronic signature, on the later of the date of the last signature and the effective date of the applicable Order; or (b) where incorporated by reference under Section 1 of the Terms, on the effective date of the applicable Order (in either case, the “Effective Date”). Where incorporated by reference, references to the Customer and the applicable Order mean the Customer and Order under the Principal Agreement, and no separate signature of this Agreement is required. A subsequently executed DPA replaces the incorporated Standard DPA from the effective date of that executed DPA.
Order of Precedence#
The order of precedence between the Standard Contractual Clauses and the other instruments in Annex 4, this Agreement and the Terms is governed by clause 19.1.
Annexes#
The following four Annexes form an integral and inseparable part of this Agreement:
| Annex | Contents |
|---|---|
| Annex 1 | Description of the Processing |
| Annex 2 | Technical and Organisational Measures |
| Annex 3 | Authorised Subprocessors |
| Annex 4 | International Transfers |
Contact#
This Agreement designates the following two contact addresses for communications under its clauses and Annexes. Every such communication addressed to COR is sent to the address corresponding to its subject matter. Notices concerning termination, breach, indemnification or other legal matters are given in accordance with Section 17.6 of the Terms.
| Designation | Address | Subject matter |
|---|---|---|
| Privacy address | legals@projectcor.com | Data protection enquiries, Data Subject requests, objections and other communications relating to this Agreement |
| Incident address | security@projectcor.com | Notification and follow-up of Security Incidents |
For the purposes of Annex I.A to the Standard Contractual Clauses and of Table 1 of the Information Commissioner’s Office Addendum, the rows corresponding to COR as data importer are completed as follows:
| Annex I.A row | Content |
|---|---|
| Name | COR Global Ltd., a company incorporated in the State of Delaware, United States of America |
| Address | 900 Foulk Road, Suite 201, Wilmington, Delaware 19803, United States of America |
| Contact person’s name, position and contact details | Jose Gettas, legals@projectcor.com |
| Activities relevant to the data transferred under these Clauses | Those described in Annex 1 |
| Signature and date | Execution of this Agreement or acceptance of the Principal Agreement incorporating this Agreement by reference constitutes execution of Annex I by COR and Customer on the Effective Date, in accordance with provision A.8 of Annex 4. |
| Role (controller/processor) | COR, processor; the Customer, controller, in accordance with clause 3.1 |
The position stated in the table above does not constitute the designation of a data protection officer under Article 37 GDPR, nor the indication of an encarregado under Article 41 of Brazilian Law No. 13,709 (COR’s encarregado in its capacity as controller is identified in its Privacy Policy), nor the appointment of a personal data protection officer under Article 50 of Chilean Law No. 19,628 as amended by Law No. 21,719. The rows corresponding to the Customer as data exporter are completed in accordance with provision A.8 of Annex 4.
Address for communications: COR Global Ltd., 900 Foulk Road, Suite 201, Wilmington, Delaware 19803, United States of America.
1. Definitions#
1.1 “Principal Agreement”: Means the Agreement as defined in COR’s Terms of Service (the “Terms”), comprising the Terms, each applicable Order and the documents incorporated into them by reference, including the AI Additional Terms, or any separately negotiated services agreement entered into by COR and the Customer under which the Customer contracts for the Services.
1.2 “Customer”: Means the natural or legal person that contracts for the Services under the Principal Agreement, in its capacity as controller, save as provided in clause 3.4.
1.3 “Services”: Means the services COR provides to the Customer under the Principal Agreement.
1.4 “Personal Data”: Means any information relating to an identified or identifiable natural person, and any information defined as personal data, personal information or an equivalent term under Data Protection Law. “Customer Personal Data”: the Personal Data COR processes on the Customer’s behalf in providing the Services, including Personal Data contained in Input and Output.
1.5 “Data Subject”: Means the natural person to whom the Customer Personal Data relates. The term includes the data owner and its equivalents, including the consumer.
1.6 “Data Protection Law”: Means the rules on the protection of personal data and privacy applicable to the processing of the Customer Personal Data.
1.7 “GDPR”: Means Regulation (EU) 2016/679 and, where applicable, its version as incorporated into the law of the United Kingdom.
1.8 “Subprocessor”: Means the third party engaged by COR that processes Customer Personal Data on COR’s behalf.
1.9 “Security Incident”: As defined in clause 8.1.
1.10 “Standard Contractual Clauses” or “SCCs”: Means the standard clauses approved by Commission Implementing Decision (EU) 2021/914, with the applicable addenda incorporated in Annex 4.
1.11 “Affiliate”, “AI Additional Terms”, “AI Features”, “Customer-Connected AI Tool”, “Fees”, “Input”, “Order”, “Output” and “Subscription Term” have the meanings given to them in the Terms or in the AI Additional Terms, as applicable.
1.12 The remaining capitalised terms have the meaning given to them by the Terms or by Data Protection Law.
2. Subject Matter and Scope#
2.1 This Agreement governs COR’s processing of Customer Personal Data in connection with the Services and, upon execution by both Parties or incorporation by reference in accordance with Section 1 of the Terms, forms part of the Principal Agreement.
2.2 The following form an integral and inseparable part of this Agreement: Annex 1 (description of the processing), Annex 2 (technical and organisational measures), Annex 3 (authorised Subprocessors) and Annex 4 (international transfers).
2.3 This Agreement applies to processing subject to the Data Protection Law of the European Union and the European Economic Area, of the United Kingdom, of Switzerland, of the United States and of Latin America.
2.4 The processing takes place in the location and on the infrastructure described in clause 11 and in Annex 1.
2.5 This Agreement does not apply to Personal Data that COR processes as an independent controller, including the contact and account details of the Customer’s representatives and Users used for account administration, billing, satisfaction surveys and the management of the commercial relationship with the Customer, and data relating to interactions with COR’s websites. COR processes that data in accordance with its Privacy Policy, as provided in Section 1 of the Terms.
3. Roles of the Parties#
3.1 Save as provided in clause 3.4, the Customer acts as controller and COR as processor in respect of the Customer Personal Data.
3.2 The Customer determines the purposes and means of the processing and represents that it has a lawful basis for the processing and for the transmission of the Customer Personal Data to COR, and that it has discharged its information duties towards Data Subjects.
3.3 Where the applicable Data Protection Law uses different terminology, including the figures of service provider under the law of California, of controlador and operador under the law of Brazil, of responsable and encargado under the law of Mexico, and of mandatario under the law of Chile, COR acts in the position equivalent to that of processor and the Customer in the position equivalent to that of controller.
3.4 Where the Customer processes the Customer Personal Data in its capacity as processor for a third-party controller, this Agreement applies with the following adaptations: the Customer represents that it has that controller’s authorisation to engage COR; references to the Customer’s instructions include those the Customer receives from that controller, for the lawfulness of which the Customer is answerable; COR acts as subprocessor and addresses to the Customer every communication provided for in this Agreement, which the Customer passes on to the controller; and Module Three of the SCCs applies in accordance with Annex 4.
3.5 Where the Principal Agreement permits use of the Services by the Customer’s Affiliates, the Customer acts towards COR in its own name and on behalf of those Affiliates, is answerable for the instructions it issues on their behalf, and is COR’s sole point of contact for the purposes of this Agreement.
3.6 COR has no obligation to monitor the Customer’s compliance with Data Protection Law. The Customer is responsible for independently assessing whether the Services, including the measures in Annex 2, meet its requirements and obligations under Data Protection Law, and for providing the notices and obtaining the consents and lawful bases required for the processing, in accordance with Section 2 of the Terms.
4. Documented Instructions#
4.1 COR processes the Customer Personal Data solely in accordance with the Customer’s documented instructions. The initial instructions consist of the Principal Agreement, this Agreement and its Annexes, and the Customer’s use of the functionality of the Services. The instructions include processing in the locations stated in clause 11 and in Annex 1.
4.2 Subsequent instructions are to be issued in writing. If an instruction exceeds the scope of the Services, COR may make it conditional on the Parties first agreeing timescales and terms.
4.3 COR will inform the Customer without undue delay if, in COR’s opinion, an instruction infringes Data Protection Law, and may suspend its performance until the Customer confirms, amends or withdraws it.
4.4 Where a legal obligation requires COR to process the Customer Personal Data otherwise than on the Customer’s instructions, COR will inform the Customer of that requirement in advance, unless the law prohibits it.
5. Prohibition of Own Use#
5.1 COR does not process the Customer Personal Data for purposes other than providing the Services, including support and the security and maintenance of the platform. In particular, COR does not sell them, does not disclose them and does not share them for behavioural or cross-context advertising purposes, and does not use them or make them available to a third party in order to train, tune, validate or improve machine learning or artificial intelligence models.
5.2 As the sole exception to clause 5.1, COR may create aggregated or de-identified information from Customer Personal Data and use it to operate, secure, analyse, improve and develop its products and services, in accordance with Section 4 of the Terms, provided that such information: (i) does not identify, and cannot reasonably be used to identify, the Customer, any Data Subject or any individual customer account; and (ii) does not include the content of Customer Data. COR maintains technical and organisational measures to keep such information de-identified, does not attempt to re-identify it, and requires any recipient to comply with the same restrictions.
5.3 COR will not publish or communicate data attributable to the Customer without its prior written consent.
6. Confidentiality of Personnel#
6.1 COR assigns access to the Customer Personal Data according to the roles necessary to provide the Services, perform this Agreement or meet a legal obligation, and reviews that assignment periodically.
6.2 COR personnel with access to the Customer Personal Data are bound by a contractual or statutory duty of confidentiality that survives the termination of the employment or contractual relationship. Those personnel process that data solely in accordance with COR’s instructions.
6.3 COR provides those personnel with periodic training in data protection and information security.
7. Security Measures#
7.1 COR implements and maintains the technical and organisational measures described in Annex 2, having regard to the state of the art, the nature of the processing and the risks to the rights and freedoms of Data Subjects.
7.2 COR maintains an information security programme aligned with ISO/IEC 27001 and subject to SOC 2 audit, and evaluates the suitability and effectiveness of the measures in accordance with that programme.
7.3 COR may update or replace the measures in Annex 2, provided that the change does not diminish the level of protection of the Customer Personal Data.
7.4 The Customer is responsible for administering its users’ accounts and the permissions it assigns to them within the Services, and for maintaining the accuracy of the data it enters into them.
8. Security Incidents#
8.1 A Security Incident means any breach of security leading to the accidental or unlawful destruction, loss or alteration of Customer Personal Data, or to the unauthorised disclosure of or access to that data, processed by COR or by a Subprocessor. A Security Incident does not include an unsuccessful attempt or activity that does not compromise the security of Customer Personal Data, including unsuccessful log-in attempts, pings, port scans, denial-of-service attacks and other network attacks on firewalls or networked systems.
8.2 COR will notify the Customer of every Security Incident without undue delay and, in any event, within seventy-two (72) hours of COR becoming aware of it.
8.3 The notification will contain, as a minimum and to the extent the information is available: the nature of the Security Incident; the categories and approximate volume of Customer Personal Data and of Data Subjects affected; the likely consequences; the measures taken and those proposed to mitigate its effects; and the position and contact details of the contact point COR designates in the contact section.
8.4 Where any of that information is not available at the time of notification, COR will provide it in phases, as it obtains it.
8.5 COR will take reasonable steps to investigate, contain, mitigate and remediate the Security Incident and will cooperate reasonably with the Customer in assessing the Security Incident and in any notifications the Customer must make to the competent supervisory authority or to Data Subjects. The Customer is responsible for complying with the notification obligations that apply to it as controller.
8.6 Notification of a Security Incident by COR does not constitute an admission of fault or of any liability.
8.7 The Customer will address the communications under this clause to the incident address stated in the contact section. COR’s notifications will be addressed to the contact the Customer has designated for security incidents or, failing that, to the contact registered in the Services.
9. Assistance to the Customer#
9.1 COR assists the Customer so that it can respond to Data Subject requests relating to their rights of access, rectification, erasure, restriction of processing, objection and portability, through the functionality of the Services available at the relevant time.
9.2 To the extent that functionality is not sufficient to respond to a request, COR will provide commercially reasonable assistance, having regard to the nature of the processing and the information available to it.
9.3 If COR receives a request relating to the Customer Personal Data directly from a Data Subject, it will not respond to it on its own account and will refer it to the Customer without undue delay, unless Data Protection Law provides otherwise.
9.4 COR provides the Customer with reasonable assistance in carrying out data protection impact assessments and in prior consultations with the competent supervisory authority, where those actions relate to the processing that is the subject of this Agreement.
9.5 The assistance provided for in clauses 7, 8 and 9 includes that required by Article 28(3)(f) GDPR in respect of the obligations in Articles 32 to 36 GDPR.
10. Subprocessors#
10.1 The Customer gives COR general authorisation to engage Subprocessors for the processing of Customer Personal Data. The authorised Subprocessors are identified in Annex 3.
10.2 COR will give notice of every addition or replacement of a Subprocessor not less than thirty (30) days in advance, by the means provided for in Annex 3.
10.3 The Customer may object to the addition or the replacement within the notice period, by written communication to the privacy address stated in the contact section, on reasonable grounds relating to data protection. The Parties will seek a solution in good faith. If the objection is not resolved within thirty (30) days of its receipt, the Customer may, by written notice to COR, terminate without penalty that part of the Services which requires the involvement of the objected Subprocessor. Termination under this clause is the Customer’s sole and exclusive remedy in respect of the objection.
10.4 COR’s engagement of Subprocessors will be governed by binding written terms addressing the processing and protection of Customer Personal Data, which may include the Subprocessor’s standard terms and data processing addendum. The technical and organisational measures applicable to each Subprocessor may differ from those implemented by COR and from those described in Annex 2, subject to applicable Data Protection Law and any applicable Standard Contractual Clauses.
10.5 Where Chilean law applies, the authorisation of each Subprocessor is governed by provision D.1 of Annex 4.
10.6 COR will ensure that any transfer of Customer Personal Data to a Subprocessor complies with applicable Data Protection Law, including, where required, through an applicable adequacy decision, Standard Contractual Clauses or another valid transfer mechanism. COR will not make a transfer where no lawful transfer mechanism is available. Nothing in this clause requires COR to engage an alternative Subprocessor or provide alternative functionality, except as expressly agreed by the Parties or required by applicable Data Protection Law.
11. International Transfers#
11.1 The Customer Personal Data is hosted in the United States, on COR’s Amazon Web Services infrastructure, with us-east-1 and us-east-2 as principal regions and other regions of the same provider for ancillary services and content delivery. COR’s Subprocessors identified in Annex 3 may access Customer Personal Data from outside the United States to support, maintain and operate the Services, subject to clause 10 and Annex 4.
11.2 Transfers of Customer Personal Data from the European Union and the European Economic Area, the United Kingdom and Switzerland are governed by the mechanisms identified in Annex 4, including the SCCs.
11.3 Subprocessors may process Customer Personal Data outside the United States, subject to the restriction in clause 10.6. COR will enter into with each of them the transfer instrument that corresponds under Annex 4.
11.4 If COR receives a binding request from a public or judicial authority relating to the Customer Personal Data: (a) it will inform the Customer without undue delay, to the extent the law permits; (b) it will challenge requests that are manifestly unlawful, disproportionate or excessive; and (c) where it must comply, it will disclose only the minimum information legally required. Section E of Annex 4 supplements this clause.
12. Audit and Demonstration of Compliance#
12.1 COR makes available to the Customer the information reasonably necessary to demonstrate compliance with this Agreement, in accordance with Article 28(3)(h) GDPR.
12.2 Demonstration is effected, in the first instance, by the description of the measures in Annex 2, by responses to the Customer’s reasonable enquiries about them and, subject to the execution of a confidentiality agreement, by such audit reports, attestations and certifications as COR holds. On request, COR informs the Customer of the status, scope and period of the reports and certifications available at the relevant time, and of the expected schedule. The Customer may share those reports with a competent supervisory authority on its request.
12.3 The Customer may carry out an on-site audit only where: (a) the information in clause 12.2 is not sufficient to demonstrate compliance with this Agreement; (b) a confirmed Security Incident affecting the Customer Personal Data has occurred; or (c) a competent supervisory authority requires it. Insufficiency is to be established with reasons in writing, after the enquiries under clause 12.2 have been made and COR has responded.
12.4 An on-site audit may be carried out no more than once in any period of twelve (12) months, save where required by a competent supervisory authority or following a confirmed Security Incident, on a date agreed by the Parties following not less than thirty (30) days’ written notice, during business hours and by an independent third party that is not a competitor of COR or, where the SCCs or Data Protection Law confer on the Customer the right to carry it out itself, by the Customer’s own personnel. Whoever carries out the audit is bound by a duty of confidentiality. Its scope is limited to what is necessary to verify compliance with this Agreement, without undue interference with the operation of the Services, and to facilities and systems that COR controls. It does not extend to the facilities of COR’s infrastructure providers, whose certifications and reports COR makes available in accordance with clause 12.2.
12.5 No audit extends to access to the data of other COR customers or to third-party information. The findings of an audit are limited to the processing of Customer Personal Data, are COR’s Confidential Information, and the Customer will provide COR with a copy of the audit report free of charge.
12.6 The costs of the audit are borne by the Customer, save where it is carried out in the circumstances of paragraphs (b) or (c) of clause 12.3. Where applicable Data Protection Law requires COR to carry out an independent audit at its own expense, COR carries it out and makes the results available to the Customer in accordance with clause 12.2.
12.7 This clause does not limit the audit and inspection rights the SCCs confer on the Customer and on competent supervisory authorities.
13. Deletion and Return#
13.1 Upon termination of the provision of the Services and at the Customer’s election, COR will return or securely delete the Customer Personal Data as soon as reasonably practicable or in compliance with the period required by applicable law. Where the Customer elects return, COR will provide the Customer Personal Data upon written request in a structured, commonly used format, through a secure download link available for seven (7) days from delivery. COR will notify the Customer of the link’s expiration date. Following return, COR will securely delete the remaining copies, subject to clause 13.4. Any additional assistance requested by the Customer beyond the standard return process may be subject to additional Fees in accordance with Section 12 of the Terms.
13.2 If the Customer does not communicate its election within thirty (30) days of termination, COR will proceed to deletion in accordance with clause 13.1.
13.3 On the Customer’s written request, COR will issue written certification of the deletion carried out.
13.4 The following are excepted from the deletion obligation: (a) Customer Personal Data whose retention is legally required, which are retained only for the period and purpose so required; (b) copies contained in backups, which are deleted in accordance with COR’s backup retention cycles; and (c) copies contained in technical records, which cease to be accessible through the functionality of the Services. For as long as they subsist, that data remains subject to this Agreement, is not processed for any other purpose and is not made available to third parties.
14. Record of Processing Activities#
COR maintains the record of the categories of processing carried out on the Customer’s behalf that is required of it by Article 30(2) GDPR and makes it available to the competent supervisory authority and to the Customer on reasonable request.
15. Processing by Means of Artificial Intelligence Systems#
15.1 The Services include functionality assisted by language models, provided through the providers identified in Annex 3, which act as Subprocessors subject to clause 10. The Customer’s authorisation is given in respect of the set of providers identified in Annex 3; the provider that handles a given interaction may vary among them depending on model availability, subject to the restriction in clause 10.6. Where the Customer configures the credential of its own model provider, or connects a Customer-Connected AI Tool, that provider or tool is not a Subprocessor of COR and is governed by Table 2 of Annex 3 and Section 9 of the AI Additional Terms.
15.2 That functionality assists the Customer’s users, who retain control of the decisions they take on the basis of its Output. It is for the Customer, as controller, to determine whether its use of that functionality involves automated decision-making within the meaning of Article 22 GDPR and to adopt the measures that would then fall to it. Section 11 of the AI Additional Terms governs the use of AI Features in Consequential Decisions.
15.3 The restrictions on COR’s own use of Customer Personal Data and on model training established in clause 5 apply to Input and Output containing Customer Personal Data and to Customer Personal Data contained in attachments and related traces processed in connection with the AI Features. COR does not itself use such data to train, tune, validate or improve AI or machine learning models.
The use of AI Features does not, by itself, constitute an instruction or authorisation from the Customer to use Customer Personal Data for model training or other purposes outside the provision of the Services.
15.4 COR complies with the obligations that applicable artificial intelligence legislation imposes on it in respect of the assisted functionality it supplies, and assists the Customer, on reasonable request, with the information available to it about that functionality.
16. Liability#
16.1 To the fullest extent permitted by Data Protection Law, each Party’s liability arising out of or in connection with this Agreement, whether in contract, tort or under any other theory of liability, is subject to the exclusions and limitations of liability in the Terms.
16.2 Nothing in this Agreement limits the rights the SCCs confer on Data Subjects or any liability that Data Protection Law declares not to be limitable.
17. Term, Versions and Amendments#
17.1 This Agreement is in force from the Effective Date and for as long as COR processes Customer Personal Data. It survives termination of the Principal Agreement until clause 13 has been performed in full.
17.2 This Agreement may be amended only in accordance with clause 19.3, save for updates to Annex 2 in accordance with clause 7.3, to Annex 3 in accordance with clause 10, and to Annex 4 resulting from a successor instrument in accordance with that Annex. No such update reduces the level of protection of the Customer Personal Data.
17.3 COR does not unilaterally amend the SCCs or the other transfer instruments incorporated in Annex 4. Their amendment requires the agreement of the Parties or results from the instrument that approves them.
17.4 If a change in Data Protection Law, or a decision of a competent supervisory authority or court, requires an amendment to this Agreement or to the transfer instruments in Annex 4, the Parties will negotiate that amendment in good faith.
18. Governing Law and Jurisdiction#
18.1 This Agreement is governed by the laws of the State of Delaware, United States of America, and is submitted to the courts designated in the Principal Agreement.
18.2 As an express exception to clause 18.1, the SCCs incorporated in Annex 4 are governed by the law of Ireland, and their Clauses 17 and 18 are neither amended nor affected by clause 18.1, without prejudice to transfers subject to the Information Commissioner’s Office Addendum being governed by what that Addendum provides in its Mandatory Clauses.
19. General Provisions#
19.1 Precedence. In matters of data protection the following order of precedence applies: (a) the SCCs and the other transfer instruments in Annex 4; (b) this Agreement and its Annexes; (c) the AI Additional Terms; and (d) the remainder of the Terms.
19.2 Partial invalidity. A declaration that any provision is invalid, illegal or unenforceable does not affect the remaining provisions, which remain in full force. The affected provision is replaced by a valid one reflecting its purpose.
19.3 Amendments. Save as provided in clause 17.2, any amendment to this Agreement requires written form signed by both Parties.
19.4 Assignment. Neither Party may assign this Agreement without the other’s prior written consent, save for an assignment together with the Principal Agreement in accordance with Section 17.1 of the Terms.
19.5 Counterparts and electronic signature. This Agreement may be executed in counterparts and by electronic signature, each with the same validity and effect as a handwritten signature. This clause is without prejudice to the signature and date of Annex I to the SCCs, which are governed by provision A.8 of Annex 4.
19.6 Language. This Agreement is made in English, and the English text is its sole official text. COR does not maintain a translation of this Agreement, and no translation, by whomever made, forms part of it or may be relied upon to construe it. Where a mandatory rule of law requires that this Agreement, or information it contains, be made available in another language, COR complies with that requirement without the translation thereby becoming an official text, save to the extent that rule provides otherwise. Where the law applicable to a Customer denies effect to a stipulation of official language, or entitles that Customer to rely on a version in another language, this clause applies only so far as that law permits. The instruments incorporated by reference in Annex 4 are not translated by COR and govern in their own official language version, as set out in the table of incorporated instruments in that Annex.
Annex 1 - Description of the Processing#
Version [2.1.0]. Effective [●].
1. Subject Matter, Nature, Purpose and Duration#
| Item | Description |
|---|---|
| Subject matter of the processing | Processing of Customer Personal Data by COR to the extent necessary to provide the Services in accordance with the Principal Agreement and the Customer’s documented instructions. |
| Nature and purpose | Automated operations of collection, recording, organisation, storage, consultation, alteration, use, disclosure by transmission to the Customer and its authorised users, backup, deletion and return. Purpose: to operate COR’s management platform for agencies and professional services, comprising project and task management, time recording, profitability analysis and invoicing, together with support, maintenance and security of the Services. |
| Duration of the processing | The term of the Principal Agreement, plus the periods and exceptions in clause 13. |
| Retention period | For as long as the Customer keeps the data in the Services. Following deletion within the application and following termination, the data is retained for such time as it subsists in backups or in technical records, in accordance with the periods and exceptions in clause 13, without being processed for any other purpose. The Customer determines what data it keeps in the Services. |
2. Categories of Data Subjects#
| Category | Description |
|---|---|
| Customer personnel | Employees, contractors and collaborators of the Customer who access the platform or whose data the Customer records in it. |
| End-client contacts | Contact persons at the Customer’s own clients. |
3. Categories of Customer Personal Data#
| Category | Content |
|---|---|
| Identification and professional contact details | First name, surname, email address, position, area and team. |
| Employment relationship and assignment | Position, team, start and end dates, leave and absences, according to what the Customer records. |
| Time and activity records | Hours recorded, tasks, projects, comments and files attached by the Customer’s users. |
| Financial data associated with the resource | Cost and hourly rate, where the Customer records them. |
| Technical identifiers of service use | Account and user identifiers, IP address, device and browser data, and timestamps of application use. |
| Free-form content | Text that the Customer’s users write in the platform’s text fields and in the model-assisted functionality. |
| Special category data | The platform is not intended for the processing of special category data and COR does not require it. The Customer should not record such data in free-text fields; if it configures absence types that reveal data concerning health, it does so on its own responsibility. |
| National identifiers | Where the Customer records them for its own administration, for example a tax or employment identifier of the Data Subject’s country, they form part of the Customer Personal Data and are subject to this Agreement. |
The categories above describe the scope contemplated by the functionality of the Services. Their actual content depends on what each Customer decides to record in them.
4. Transfers#
| Item | Description |
|---|---|
| Frequency of the transfer | Continuous, throughout the term of the Principal Agreement, depending on the use of the Services by the Customer’s users. |
| Nature of the processing in the transfers | Hosting, storage, automated processing, backup, support and maintenance, with the measures in Annex 2. |
| Processing by Subprocessors | Subject matter and nature: those stated in Annex 3 as the purpose of each Subprocessor. Duration: for as long as COR engages that Subprocessor in accordance with clause 10, within the duration stated in section 1. |
5. Location of the Processing#
| Item | Description |
|---|---|
| Location | The Customer Personal Data is hosted in the United States, on Amazon Web Services infrastructure, with us-east-1 and us-east-2 as principal regions and other regions of the same provider for ancillary services and content delivery. COR personnel and COR Affiliates may access it remotely from the countries in which they are located, subject to clause 11 and Annex 4. |
The Subprocessors in Annex 3 may process Customer Personal Data on their own infrastructure, which may be located outside the United States. Those transfers are governed by clause 11 and by Annex 4.
Annex 2 - Technical and Organisational Measures#
Version [2.1.0]. Effective [●].
COR applies and maintains the following measures in respect of the Customer Personal Data.
| Area | Measure |
|---|---|
| Security governance and policies | COR maintains a documented information security programme, with internal policies reviewed in accordance with that programme. The programme is aligned with ISO/IEC 27001 and subject to SOC 2 audit. Such reports and certifications as COR holds are provided in accordance with clause 12, under a confidentiality agreement. |
| Access and identity management | Access to the systems that process Customer Personal Data is governed by role-based access control. Authentication of COR personnel is performed by federated authentication through the corporate identity provider. |
| Encryption at rest | On COR’s systems, the Customer Personal Data is encrypted at rest with AES-256 by means of the managed encryption of the infrastructure provider. |
| Encryption in transit | The public access points of the service support encrypted connections using TLS 1.2 or higher. |
| Segregation of data between customers | The Customer Personal Data is segregated logically by means of a customer identifier, applied at the application layer. That segregation does not entail infrastructure dedicated to each customer. |
| Network and infrastructure security | The processing takes place on managed Amazon Web Services infrastructure, in the location stated in Annex 1. Physical and environmental security of the data centres is the responsibility of that provider. |
| Vulnerability and patch management | COR runs automated vulnerability scanning over container images and infrastructure. Findings are prioritised according to their severity and their remediation is managed by updating components, dependencies or base images. |
| Logging and monitoring | COR maintains a centralised record of administrative activity over the infrastructure. The records are used for the investigation of security events. |
| Backups and recovery | COR maintains automated backups of the production databases, with point-in-time recovery on the systems that support it. The backups reside in encrypted storage of the infrastructure provider. |
| Availability and recovery | Recovery capability rests on the backups and the point-in-time recovery described in this Annex. Service availability commitments, where they exist, are governed by the Principal Agreement. |
| Data minimisation and quality | The scope of the data processed is that described in Annex 1 and COR does not require additional categories. The accuracy of the data the Customer enters into the Services is the Customer’s responsibility in accordance with clause 7.4. |
| Secure development and change management | COR applies code review before changes are merged, and those changes are recorded in version control. Deployment to production is carried out through automated pipelines. |
| Personnel security | COR personnel are bound by a duty of confidentiality and receive periodic training in information security and data protection. COR revokes access in accordance with its offboarding procedure upon the end of the employment or contractual relationship or of the assignment that justified the access. |
| Supplier management | The technical and organisational measures described in this Annex apply to systems and operations under COR’s control. Subprocessors apply their own technical and organisational measures, which may vary by provider and service. Their engagement is governed by clause 10, and they are identified in Annex 3. |
| Incident response | COR maintains a documented incident response procedure, with defined roles, escalation criteria and containment and remediation stages. Notification to the Customer is governed by clause 8. |
| Deletion of data and storage media | Deletion or return of the Customer Personal Data is carried out in accordance with clause 13, by logical erasure on the production systems. Sanitisation and destruction of storage media are the responsibility of the infrastructure provider. Corporate devices are wiped or rendered unusable before reassignment or disposal. |
These measures are updated in accordance with clause 7, without diminishing the level of protection of the Customer Personal Data.
COR answers the Customer’s enquiries about measures not described in this Annex in accordance with clause 12.2.
Annex 3 - Authorised Subprocessors#
By entering into this Agreement through execution or incorporation by reference, the Customer authorises COR to engage the Subprocessors in Table 1, which are those authorised as at the Effective Date. COR notifies updates to them in accordance with clause 10 and with the change procedure in this Annex. Providers listed below act as Subprocessors only to the extent they process Customer Personal Data on COR’s behalf in providing the Services. Processing for COR’s independent controller purposes is outside the scope of this Agreement and is described in the Privacy Policy.
Table 1 - Infrastructure and Service Subprocessors#
| Provider | Country of establishment | Purpose of the processing |
|---|---|---|
| Amazon Web Services, Inc. | United States | Hosting, compute, storage, databases, sending of the service’s transactional email, and language model inference |
| Cloudflare | United States | Network and edge execution services for the service’s access points, with the associated storage |
| OpenAI | United States | Language model inference for the assisted functionality |
| Anthropic | United States | Language model inference for the assisted functionality |
| Tavily | United States | Search and information retrieval for the assisted functionality |
| Pinecone | United States | Storage of vector representations for semantic search |
| LangChain (LangSmith) | United States | Observability and diagnostics of the model-assisted functionality, including storage of Input, Output and related traces containing Customer Personal Data, with a configured retention period of fourteen (14) days. |
| Grafana Labs | United States | Observability, metrics and application logs |
| Sentry | United States | Detection and diagnosis of application errors |
| United States | Email, communications and operational notifications, platform services for product functionality, language model inference of the Gemini family, and tag management on the service’s front end | |
| Microsoft | United States | Communications and operational notifications, and integration with the Customer’s collaboration tools |
| Zendesk | United States | Management of support requests |
| Appcues, Inc. | United States | In-app user guidance and onboarding flows, with the associated user and usage identifiers |
| Retently (Remsys, Inc.) | United States | Satisfaction surveys addressed to the Customer’s users |
| Chargebee | United States | Billing and subscription management |
| Metabase | United States | Internal analytics over operational service data |
| Amplitude, Inc. | United States | Product analytics over use of the Services, with the associated user and usage identifiers |
| HubSpot | United States | Management of the commercial relationship with the Customer |
Table 1 comprises the third parties that process Customer Personal Data on COR’s behalf. It does not comprise the suppliers COR engages for its own administration without access to Customer Personal Data, nor the third parties the Customer selects under Table 2, nor the infrastructure COR operates itself.
Tag management. COR operates a tag-management layer on the front end of the Services, through which identification and usage data of the categories described in Annex 1 is transmitted to Subprocessors identified in Table 1. COR does not enable in that layer the transmission of Customer Personal Data to any third party that is not identified in Table 1. Enabling a tag that transmits Customer Personal Data to a third party constitutes the addition of a Subprocessor and is subject to the notice and objection procedure in this Annex and in clause 10.
Model-assisted functionality. Language model inference is provided through Amazon Web Services, OpenAI, Anthropic and Google. Where a model is served through Amazon Bedrock, it runs on Amazon Web Services infrastructure and the Customer Personal Data is not disclosed to the organisation that developed the model, which is accordingly not a Subprocessor. In accordance with clause 15.1, the provider that handles a given interaction may vary among those listed depending on model availability.
The purpose stated delimits the processing authorised for each Subprocessor, which is not permitted to process Customer Personal Data for any other purpose.
The country stated is that of establishment of the entity with which COR contracts; a Subprocessor may process Customer Personal Data from another location. Those transfers are governed by clause 11 and by Annex 4.
Table 2 - Customer-Directed Integrations#
A third party that the Customer selects and enables by its own decision, by activating an integration or configuring an output destination, is not a Subprocessor of COR. COR carries out the transmission on the Customer’s instruction, and the subsequent processing by that third party is the Customer’s responsibility; the Customer acts as controller towards it and determines which integrations it enables and with what scope.
| Category of destination selected by the Customer | Examples | Subsequent processing |
|---|---|---|
| Customer management systems | Enterprise resource planning, accounting, human resources, or issue and project management systems | Customer’s responsibility |
| Automation or integration platforms contracted by the Customer | Workflow orchestration services between applications, under the account the Customer contracts | Customer’s responsibility |
| Customer productivity and communication tools | The Customer’s email, calendar and corporate messaging services | Customer’s responsibility |
| Model providers configured by the Customer | Inference services for which the Customer supplies the credential | Customer’s responsibility |
| Customer-Connected AI Tools | Third-party AI applications, assistants, models or agents that the Customer connects through COR’s APIs, MCP servers or connectors (Section 9 of the AI Additional Terms) | Customer’s responsibility |
| Output destinations configured by the Customer | Access points designated by the Customer to receive service data | Customer’s responsibility |
Change Procedure#
COR will give notice of every addition or replacement of a Subprocessor not less than thirty (30) days in advance. COR sends the notice by email to the privacy contact the Customer has designated and, failing that, to the contact registered in the Services. The Customer may designate or change that contact, and indicate additional destination addresses, by communication to the privacy address stated in the contact section. That contact is also the one that completes, in accordance with provision A.8 of Annex 4, the data exporter’s contact person row in Annex I.A to the SCCs.
The Customer may object to the change with reasons within the notice period, with the effects provided for in clause 10. This procedure applies to the enabling of a tag in the tag-management layer on the same terms as to any other addition of a Subprocessor.
For a Customer subject to Chilean law, the authorisation of each Subprocessor is governed by provision D.1 of Annex 4.
Annex 4 - International Transfers#
Version [2.1.0]. Effective [●].
Incorporated Instruments#
The instruments listed below are incorporated by reference. COR does not translate them: each governs in its own official language version. The Appendix Information to those instruments is drafted by COR and is printed in English, the language of this Agreement; the row labels of each appendix are reproduced literally from the official text of the incorporated version and are not translated.
| Instrument | Identifier and official version | Governing language | Where published | Appendices | Subscription and succession |
|---|---|---|---|---|---|
| Standard Contractual Clauses | Commission Implementing Decision (EU) 2021/914, Official Journal L 199 of 7 June 2021, Modules Two and Three | The official version of the language of the data exporter’s place of establishment and, failing that, the English version. For transfers subject to the Information Commissioner’s Office Addendum, the English version, without option, because that Addendum amends a text of the Clauses | eur-lex.europa.eu | Drafted by COR, printed in English, row labels reproduced from the official version incorporated | Entered into upon execution or incorporation by reference to this Agreement, in accordance with A.2 and A.8 |
| International Data Transfer Addendum to the EU Commission Standard Contractual Clauses | Version B1.0, with its Mandatory Clauses | English. No official version exists in any other language, and a translation is not the Approved Addendum | ico.org.uk | Tables completed by COR, printed in English | Entered into upon execution or incorporation by reference to this Agreement, in accordance with A.2 and A.8 |
| ANPD Standard Contractual Clauses | Annex II to ANPD Resolution CD/ANPD No. 19/2024, as rectified | Portuguese | gov.br/anpd | Information and elections completed by reference. | Entered into upon execution or incorporation by reference to this Agreement. |
Where the authority that issues an instrument replaces it with a successor instrument, the successor applies from the date that authority sets, and COR notifies the Customer of the updated Annex in accordance with clause 17.2.
Section A - European Union and European Economic Area#
A.1 For transfers subject to Chapter V of Regulation (EU) 2016/679, the Standard Contractual Clauses approved by Implementing Decision (EU) 2021/914 (the SCCs) are incorporated by reference, in full and without amendment.
A.2 The SCCs are entered into upon execution of this Agreement or its incorporation by reference in accordance with Section 1 of the Terms, with the Customer acting as data exporter and COR as data importer.
A.3 The Parties resolve the options as follows.
| Item | Election |
|---|---|
| Module | Two where the Customer is a controller; Three where it is a processor for a third-party controller under clause 3.4 |
| Clause 7 | Docking clause included, on the terms of provision A.8 |
| Clause 9(a) | Option 2, general written authorisation, with thirty (30) days’ prior notice |
| Clause 11(a) | No independent dispute resolution body |
| Clause 17 | Law of Ireland |
| Clause 18(b) | Courts of Ireland |
A.4 The Annexes to the SCCs are completed by reference: Annex I.A, by the section “The Parties”, by the contact section and by provision A.8, the role of each Party, as controller or as processor, being that which results from clauses 3.1 and 3.4, and the activities relevant to the data transferred being those described in Annex 1; Annex I.B, by Annex 1; Annex II, by Annex 2; and Annex III, by Annex 3.
A.5 The competent supervisory authority for the purposes of Annex I.C is the one that corresponds under Clause 13. COR submits to its jurisdiction.
A.6 The SCCs prevail over this Agreement, its Annexes and the Principal Agreement; any provision that contradicts them or detracts from the rights of Data Subjects is deemed not written to that extent.
A.7 Onward transfers to Subprocessors are governed by Clause 8.8 of the SCCs, by clause 10.4 and by the restriction in clause 10.6. COR will enter into with each Subprocessor the transfer instrument that corresponds. The instruments COR enters into with its Subprocessors may be governed by a law and submitted to a forum different from those elected in clause 18.2; that circumstance does not affect the rights the SCCs confer on the Customer and on Data Subjects as against COR.
A.8 Signature and date of Annex I. The Parties’ execution of this Agreement or acceptance of the Principal Agreement incorporating this Agreement by reference constitutes their execution of Annex I to the SCCs, with the Customer as data exporter and COR as data importer, on the Effective Date. No separate signature of Annex I is required in either case. Updates to the appendix information made in accordance with clause 17.2 are made on the terms of Clause 2(a) of the SCCs, without a fresh signature of Annex I being necessary.
Each Party consents to the subscription, the signature and the date provided for in A.2 and in this provision, and to communications relating to the SCCs, being given in electronic form. That consent is given, among other effects, for the purposes of sections 12 and 13 of the Electronic Commerce Act 2000 of Ireland, whose law governs the SCCs under their Clause 17 and under clause 18.2, and extends to the retention of Annex I in electronic form, a copy of which COR provides to the Customer on request.
As regards the data exporter, the name, position and contact details of its contact person are those of the privacy contact the Customer has designated under the change procedure in Annex 3 and, failing that, those of the contact registered in the Services. Where the Customer has a data protection officer or a representative in the European Union, their details are those the Customer communicates through that same channel.
The accession of an entity that is not a Party, under Clause 7 of the SCCs, requires that entity to complete the appendix and sign Annex I.
A.9 Copies and summaries for Data Subjects. Clause 8.2 of the SCCs entitles a Data Subject, on request, to a copy of the SCCs including the Appendix as completed by the Parties. COR makes that copy available free of charge on request addressed to the privacy address. This Agreement, including the Appendix Information, is made in English. Where a Data Subject would otherwise not be able to understand its content or exercise their rights, COR provides, free of charge and without undue delay, a meaningful summary of the SCCs and of the Appendix Information in a language the Data Subject understands, and informs the Data Subject of the right to obtain it. COR redacts the Appendix Information only to the extent necessary to protect business secrets or other confidential information, including personal data, and gives the reasons for the redactions to the extent possible without revealing the redacted information.
Section B - United Kingdom and Switzerland#
B.1 United Kingdom. The International Data Transfer Addendum to the EU Commission Standard Contractual Clauses of the Information Commissioner’s Office, version B1.0, with its Mandatory Clauses, which amends the SCCs for the United Kingdom regime, is incorporated by reference. Its four Tables are completed by reference: Table 1, by the section “The Parties” and by the contact section, from which the name of each Party, its address and the position and contact details of its principal contact point result, and whose signature box is completed in accordance with provision A.8; Table 2, by the SCCs and the elections in A.3; Table 3, by the Annexes in A.4; and Table 4, by the selection that neither Party may terminate it upon a revision of the Approved Addendum. The competent authority is the Information Commissioner.
B.2 Switzerland. For transfers subject to Swiss federal data protection legislation, the SCCs are read with the following adaptations: references to the Regulation are to be understood as references to that legislation; the competent authority is the Federal Data Protection and Information Commissioner; references to Member States do not deprive Data Subjects in Switzerland of exercising their rights or of bringing a claim in their place of habitual residence; and references to Personal Data and to Data Subjects extend to the data of legal persons for as long as that legislation protects them.
Section C - United States#
C.1 COR processes the Customer Personal Data as a service provider within the meaning of California privacy legislation and as a processor within the meaning of applicable state privacy legislation. It does not sell or share them and receives no consideration for them.
C.2 COR: (a) processes them only to provide the Services and for the purposes documented in this Agreement; (b) does not retain, use or disclose them for any other purpose, nor combine them with data from another source save as legally permitted; (c) does not use them for its own purposes or to train, tune, validate or improve models, in accordance with clause 5; (d) will impose equivalent obligations on its Subprocessors, in accordance with clause 10.4; (e) assists the Customer with consumer requests and with the assessments the law imposes on it; (f) notifies the Customer if it can no longer meet these obligations; and (g) permits the reasonable verification in clause 12 and the Customer’s reasonable steps to stop and remediate any unauthorised processing.
C.3 Where the Customer so instructs as a consequence of a verified consumer request, COR provides the assistance in clauses 9.1 and 9.2 for the cessation of processing, deletion or correction, and communicates the instruction to the Subprocessors that process that data.
Section D - Latin America#
D.1 Chile. In respect of Personal Data subject to Chilean legislation: (a) the delegation of processing requires the Customer’s specific written authorisation, given by execution of this Agreement or its incorporation by reference in accordance with Section 1 of the Terms, in respect of the Subprocessors in Annex 3; (b) every subsequent addition or replacement requires specific, prior and written authorisation, and silence does not constitute authorisation; (c) COR reports security breaches to the Customer, as controller, within the periods in clause 8; (d) COR and its personnel owe secrecy in respect of that data, a duty that survives termination; and (e) these provisions apply from the time Chilean legislation becomes enforceable.
For as long as the Customer has not given the authorisation in paragraph (b), COR will not engage the new Subprocessor in respect of Personal Data subject to Chilean legislation or, if that is not technically possible, will inform the Customer, which may terminate without penalty the part of the Services affected, in accordance with clause 10.3.
D.2 Brazil. Where the Parties rely on the standard contractual clauses approved by the Autoridade Nacional de Proteção de Dados (“ANPD”) for international transfers of Customer Personal Data from Brazil, those clauses, as set out in Annex II to ANPD Resolution CD/ANPD No. 19/2024, are incorporated by reference in full and without alteration, in their official Portuguese version, with the Customer as exporter and COR as importer. The information required by those clauses is completed by reference to the section “The Parties”, the contact section and Annexes 1 and 2, and the clauses are entered into upon execution of this Agreement or its incorporation by reference in accordance with Section 1 of the Terms. No separate transfer addendum is required. In the event of a conflict, those clauses prevail with respect to the transfers they govern.
D.3 Mexico. In respect of Customer Personal Data subject to Mexican law:
(a) COR acts as encargado and the Customer as responsable within the meaning of the Federal Law on the Protection of Personal Data Held by Private Parties published in the Diario Oficial de la Federación on 20 March 2025.
(b) The transmission of Customer Personal Data by the Customer to COR is a remisión and not a transferencia. COR is not a recipient distinct from the responsable for that purpose, and that transmission does not of itself require separate consent from the Data Subject.
(c) COR processes the Customer Personal Data solely on the Customer’s documented instructions and in accordance with clauses 4, 5, 6, 7, 10 and 13, which implement the duties owed by an encargado: processing confined to instructions, confidentiality of personnel, security measures, restrictions on Subprocessors, and deletion or return on termination.
(d) Where Mexican law prescribes minimum content for the instrument between responsable and encargado, this Agreement is that instrument, and COR will execute any additional instrument required to satisfy that content.
(e) The competent authority for matters governed by Mexican law is the Secretaría de Anticorrupción y Buen Gobierno, which assumed the functions previously exercised by the Instituto Nacional de Transparencia, Acceso a la Información y Protección de Datos Personales. COR submits to its jurisdiction in respect of the processing governed by this Agreement.
(f) COR does not make, on the Customer’s behalf, the designation of the person or department responsible for personal data that Mexican law may require of the responsable; that designation falls to the Customer. This is without prejudice to the contact point COR designates in the contact section.
(g) Onward transfers by COR to Subprocessors are governed by clauses 10.4 and 10.6 and by Annex 3.
D.4 Other instruments. Where the legislation of a country in the region requires a particular international transfer instrument, the Parties will subscribe it. Until then, the obligations in this Agreement apply as a minimum contractual standard.
Section E - Authority Requests and Assistance#
E.1 COR notifies the Customer, without undue delay, of every binding request from a public or judicial authority relating to the Customer Personal Data and of every direct access of which it becomes aware, with the identity of the authority, the basis invoked and the response given, to the extent it holds that information and the law permits. If the law prohibits notification, COR requests a waiver and communicates to the Customer as much information as possible at the earliest opportunity.
E.2 COR reviews the lawfulness of each request and exhausts the avenues of challenge reasonably available, including, where appropriate, interim measures, where there are reasonable grounds to consider the request manifestly unlawful, disproportionate or excessive. It does not disclose that data before it is obliged to do so under the applicable procedural rules and limits any disclosure to the minimum reasonably necessary.
E.3 COR assists the Customer, with the information reasonably available, in the transfer assessment the Customer must carry out, and informs it without undue delay if it has reason to believe it is subject to legislation or practice incompatible with the instruments in this Annex.
Questions about this document?
Write to legals@projectcor.com. COR Global Ltd., 900 Foulk Road, Suite 201, Wilmington, DE 19803, United States.
