Standard Contractual Clauses (SCCs)

Effective date: June 22, 2026

These Standard Contractual Clauses are incorporated by reference into the Excede Data Security Addendum (DSA) pursuant to DSA Section 11.4, and govern international transfers of personal data from the EU/EEA to the United States.

STANDARD CONTRACTUAL CLAUSES

Controller to Processor

Section I

Clause 1 – Purpose and scope

(a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation)^[1] for the transfer of data to a third country.

(b) The Parties:

(i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter 'entity/ies') transferring the personal data, as listed in Annex I.A (hereinafter each 'data exporter'), and

(ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each 'data importer')

have agreed to these standard contractual clauses (hereinafter: 'Clauses').

(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2 – Effect and invariability of the Clauses

(a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.

(b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3 – Third-party beneficiaries

(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

(i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;

(ii) Clause 8.1(b), 8.9(a), (c), (d) and (e);

(iii) Clause 9(a), (c), (d) and (e);

(iv) Clause 12(a), (d) and (f);

(v) Clause 13;

(vi) Clause 15.1(c), (d) and (e);

(vii) Clause 16(e);

(viii) Clause 18(a) and (b).

(b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4 – Interpretation

(a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.

(b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.

(c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5 – Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 6 – Description of the transfer(s)

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

Clause 7 – Docking clause

(a) An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.

(b) Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.

(c) The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.

Section II – Obligations of the Parties

Clause 8 – Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1 Instructions

(a) The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.

(b) The data importer shall immediately inform the data exporter if it is unable to follow those instructions.

8.2 Purpose limitation

The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter.

8.3 Transparency

On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.

8.4 Accuracy

If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data.

8.5 Duration of processing and erasure or return of data

Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).

8.6 Security of processing

(a) The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter 'personal data breach'). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.

(b) The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

(c) In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

(d) The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.

8.7 Sensitive data

Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person's sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter 'sensitive data'), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

8.8 Onward transfers

The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union^[2](in the same country as the data importer or in another third country, hereinafter 'onward transfer') if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:

(i) the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;

(ii) the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;

(iii) the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or

(iv) the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.

8.9 Documentation and compliance

(a) The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.

(b) The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.

(c) The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter's request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.

(d) The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.

(e) The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.

Clause 9 – Use of sub-processors

(a) GENERAL WRITTEN AUTHORISATIONThe data importer has the data exporter's general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 30 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.

(b) Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.^[3] The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.

(c) The data importer shall provide, at the data exporter's request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.

(d) The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor's obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.

(e) The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

Clause 10 – Data subject rights

(a) The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.

(b) The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects' requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.

(c) In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.

Clause 11 – Redress

(a) The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.

(b) In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.

(c) Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:

(i) lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;

(ii) refer the dispute to the competent courts within the meaning of Clause 18.

(d) The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.

(e) The data importer shall abide by a decision that is binding under the applicable EU or Member State law.

(f) The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.

Clause 12 – Liability

(a) Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.

(b) The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.

(c) Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.

(d) The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer's responsibility for the damage.

(e) Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.

(f) The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.

(g) The data importer may not invoke the conduct of a sub-processor to avoid its own liability.

Clause 13 – Supervision

(a) Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679: The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

(b) The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.

Section III – Local Laws and Obligations in Case of Access by Public Authorities

Clause 14 – Local laws and practices affecting compliance with the Clauses

(a) The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.

(b) The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:

(i) the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;

(ii) the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards^[4];

(iii) any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.

(c) The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.

(d) The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.

(e) The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).

(f) Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.

Clause 15 – Obligations of the data importer in case of access by public authorities

15.1 Notification

(a) The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:

(i) receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or

(ii) becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.

(b) If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.

(c) Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).

(d) The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.

(e) Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2 Review of legality and data minimisation

(a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

(b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.

(c) The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

Section IV – Final Provisions

Clause 16 – Non-compliance with the Clauses and termination

(a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.

(b) In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).

(c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

(i) the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;

(ii) the data importer is in substantial or persistent breach of these Clauses; or

(iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

(d) Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.

(e) Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.

Clause 17 – Governing law

These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland.

Clause 18 – Choice of forum and jurisdiction

(a) Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.

(b) The Parties agree that those shall be the courts of Ireland.

(c) A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.

(d) The Parties agree to submit themselves to the jurisdiction of such courts.

Appendix

EXPLANATORY NOTE: It must be possible to clearly distinguish the information applicable to each transfer or category of transfers and, in this regard, to determine the respective role(s) of the Parties as data exporter(s) and/or data importer(s). This does not necessarily require completing and signing separate appendices for each transfer/category of transfers and/or contractual relationship, where this transparency can achieved through one appendix. However, where necessary to ensure sufficient clarity, separate appendices should be used.

Annex I

A. List of Parties

I.A — Data Exporter

Field	Value
Name	The Customer entity as identified in the Service account and/or applicable Order Form
Address	As registered in the Customer's Service account or Order Form
Contact person's name, position, contact details	[As designated by Customer in writing to privacy@excede.ai]
Activities relevant to the data transferred under these Clauses	Use of the Excede Unified Platform (Growth, Execution, and Finance modules) for business development, resource planning, and financial analytics in connection with Customer's architecture, engineering, or construction (AEC) business operations
Role (controller/processor)	Controller
Signature and date	Executed on behalf of Excede, Inc. by its authorized representative

I.B — Data Importer

Field	Value
Name	Excede, Inc.
Address	1654 Calle Tulipan Suite 100, San Juan, Puerto Rico 00927-6242
Contact person's name, position, contact details	Privacy Officer, dpo@excede.ai, (201) 824-2307
Activities relevant to the data transferred under these Clauses	Provision of a cloud-based AI operating platform for AEC firms, comprising Growth, Execution, and Finance modules, including hosting, processing, AI-assisted analytics, and related support services, as further described in the MSA and DSA
Role (controller/processor)	Processor
Signature and date	[Per execution of DSA / MSA]

I.C – Competent Supervisory Authority

The competent supervisory authority is the authority of the EU Member State in which the Customer's EU data subjects whose personal data is transferred are predominantly located. Customers must notify Excede of the applicable supervisory authority in writing at privacy@excede.ai upon entering into this DSA or upon request.

Annex II

Categories of data subjects whose personal data is transferred

Customer's employees
Customer's contractors and consultants
Customer's clients and project stakeholders
Other individuals whose personal data Customer or its users enter into the Service

Categories of personal data transferred

Company and contact information (names, email addresses, phone numbers)
Employee/project team information (names, email addresses, roles)
Project information (project names, timelines, budgets, resource allocations)
Financial data (revenue figures, cost data, margin information)
System usage data (login information, activity logs)
Any other personal data Customer inputs into the Service

Sensitive data transferred (if applicable) and restrictions or safeguards

None by design. The Service is not designed to process special category data (e.g., health data, racial or ethnic origin, religious beliefs, biometric data) as a core function.

Frequency of the transfer

Continuous / on a rolling basis for the duration of the MSA, as Customer and its users interact with the Service.

Nature of the processing

Hosting, storage, and processing for SaaS delivery; AI-assisted analytics, lead scoring, and draft generation (per DSA Section 2.1 and Privacy Policy Section 3a); backup and disaster recovery; security monitoring and logging.

Purpose(s) of the data transfer and further processing

Providing the Services (Growth, Execution, Finance modules)
Operating and maintaining the Services (security, updates, support)
Complying with legal obligations
Creating anonymized, aggregated reports (with identifiers removed)

Period for which the personal data will be retained, or the criteria used to determine that period

For the duration of the MSA. Upon termination, per DSA Section 10: data export available for 30 days, deletion completed within 90 days, subject to limited legal-hold retention as described in the Data Retention & Deletion Schedule (v3.0).

For transfers to (sub-)processors, also specify subject matter, nature, and duration of the processing

Subject matter, nature, and duration of processing by Excede's sub-processors are as set out in the Sub-Processor List (https://www.excede.ai/subprocessors), incorporated by reference.

Annex III

Technical and Organisational Measures (Including Technical and Organisational Measures to Ensure the Security of the Data)

Reformatted from DSA Section 4 (Excede Security Obligations) into the standard SCC Annex III categories.

Measures of pseudonymisation and encryption of personal data

Data in transit: TLS 1.2 or higher (minimum AES-128)
Data at rest: AES-256 encryption for sensitive data
Encryption keys managed by Excede; documented key management procedures, reviewed regularly

Measures for ensuring ongoing confidentiality, integrity, availability, and resilience of processing systems and services

Role-based access control (RBAC) limiting access to authorized personnel
Multi-factor authentication (MFA) required for all user accounts
Principle of least privilege
Quarterly access reviews; immediate deprovisioning of terminated employees
Firewalls, intrusion detection/prevention systems, DDoS protection and monitoring
Critical security patches applied within 7 days
VPN required for remote access; secure, authenticated API endpoints
Logical separation of Customer Data in a multi-tenant architecture, with database-level access controls

Measures for ensuring the ability to restore availability and access to personal data in a timely manner in the event of a physical or technical incident

Daily encrypted backups
Quarterly backup restoration testing
Documented incident response plan; designated security incident coordinator; 24/7 incident reporting capability; incident response procedures tested annually; post-incident reviews and remediation

Processes for regularly testing, assessing, and evaluating the effectiveness of technical and organisational measures

Quarterly vulnerability assessments
Annual penetration testing by a qualified third party
Vulnerability remediation timelines: critical within 7 days, high within 30 days
Annual independent security assessment (interim measure pending formal certification — see certifications note below)

Measures for user identification and authorisation

MFA required for all accounts
RBAC tied to job function
Automatic session timeouts after 15 minutes of inactivity

Measures for the protection of data during transmission

TLS 1.2+ enforced for all data in transit

Measures for the protection of data during storage

AES-256 encryption at rest
Database-level access controls and logical tenant isolation

Measures for ensuring physical security of locations at which personal data are processed

Excede does not maintain its own data centers; physical security is provided by underlying infrastructure sub-processors (Supabase / AWS) under their respective security certifications and DPAs. Reference: Sub-Processor List.

Measures for ensuring events logging

Logging of all access to personal data (logs retained for a minimum of 1 year)
Monitoring for suspicious activity
Monthly review of access logs

Measures for ensuring system configuration, including default configuration

Background checks for personnel handling personal data
Mandatory data protection and security training for all employees, with annual refresher training
Written confidentiality agreements with all employees
Disciplinary procedures for unauthorized access

Measures for internal IT and IT security governance and management

Excede maintains (or is pursuing) SOC 2 Type II and ISO 27001 certifications; current target timelines and interim assessment practices are documented in DSA Section 4.3.
Alignment with NIST Cybersecurity Framework, CIS Top 20 Critical Controls, OWASP Top 10, and PCI DSS (where applicable)

Measures for certification/assurance of processes and products

See certifications note above; interim independent security assessments provided to Customer upon request pending formal certification

Measures for ensuring data minimisation

Customer Data is processed solely to provide, secure, and monitor the Service as instructed by Customer; not used, disclosed, sold, or retained for any other commercial purpose (DSA Section 2.1)

Measures for ensuring data quality

Customer is responsible for the accuracy of data it inputs (DSA Section 3.3); Excede provides correction mechanisms upon Customer instruction

Measures for ensuring limited data retention

Per the Data Retention & Deletion Schedule (v3.0) and DSA Section 10

Measures for ensuring accountability

Records of processing activities maintained per GDPR Article 28
Audit rights and documentation provided to Customer per DSA Section 9

Measures for allowing data portability and ensuring erasure

Data export available in standard formats (CSV, JSON, SQL dump, PDF) within 15 days of request; deletion completed within 90 days of termination, per DSA Section 10

For transfers to (sub-)processors, also describe the specific technical and organisational measures to be taken by the (sub-)processor to be able to provide assistance to the controller

Sub-processors are bound by data processing agreements requiring obligations equivalent to GDPR Articles 28–32, per DSA Section 7.3. Current sub-processor DPA execution status is maintained in the Sub-Processor List.

Standard Contractual Clauses

Processor to Processor

SECTION I

Clause 1

Purpose and scope

(b) The Parties:

have agreed to these standard contractual clauses (hereinafter: 'Clauses').

(d) The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2

Effect and invariability of the Clauses

(b) These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3

Third-party beneficiaries

(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

(i) Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;

(ii) Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g);

(iii) Clause 9(a), (c), (d) and (e);

(iv) Clause 12(a), (d) and (f);

(v) Clause 13;

(vi) Clause 15.1(c), (d) and (e);

(vii) Clause 16(e);

(viii) Clause 18(a) and (b).

(b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4

Interpretation

(a) Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.

(b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.

(c) These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5

Hierarchy

Clause 6

Description of the transfer(s)

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

Clause 7

Docking clause

(c) The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.

SECTION II – OBLIGATIONS OF THE PARTIES

Clause 8

Data protection safeguards

8.1 Instructions

(a) The data exporter has informed the data importer that it acts as processor under the instructions of its controller(s), which the data exporter shall make available to the data importer prior to processing.

(b) The data importer shall process the personal data only on documented instructions from the controller, as communicated to the data importer by the data exporter, and any additional documented instructions from the data exporter. Such additional instructions shall not conflict with the instructions from the controller. The controller or data exporter may give further documented instructions regarding the data processing throughout the duration of the contract.

(c) The data importer shall immediately inform the data exporter if it is unable to follow those instructions. Where the data importer is unable to follow the instructions from the controller, the data exporter shall immediately notify the controller.

(d) The data exporter warrants that it has imposed the same data protection obligations on the data importer as set out in the contract or other legal act under Union or Member State law between the controller and the data exporter.

8.2 Purpose limitation

The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B., unless on further instructions from the controller, as communicated to the data importer by the data exporter, or from the data exporter.

8.3 Transparency

On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including personal data, the data exporter may redact part of the text of the Appendix prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information.

8.4 Accuracy

8.5 Duration of processing and erasure or return of data

Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the controller and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).

8.6 Security of processing

(a) The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter 'personal data breach'). In assessing the appropriate level of security, they shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subject. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter or the controller. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.

(b) The data importer shall grant access to the data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

(c) In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify, without undue delay, the data exporter and, where appropriate and feasible, the controller after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the data breach, including measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

(d) The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify its controller so that the latter may in turn notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.

8.7 Sensitive data

8.8 Onward transfers

The data importer shall only disclose the personal data to a third party on documented instructions from the controller, as communicated to the data importer by the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (in the same country as the data importer or in another third country, hereinafter 'onward transfer') if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:

(i) the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;

(ii) the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 of Regulation (EU) 2016/679;

(iii) the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or

(iv) the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.

8.9 Documentation and compliance

(a) The data importer shall promptly and adequately deal with enquiries from the data exporter or the controller that relate to the processing under these Clauses.

(c) The data importer shall make all information necessary to demonstrate compliance with the obligations set out in these Clauses available to the data exporter, which shall provide it to the controller.

(d) The data importer shall allow for and contribute to audits by the data exporter of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. The same shall apply where the data exporter requests an audit on instructions of the controller. In deciding on an audit, the data exporter may take into account relevant certifications held by the data importer.

(e) Where the audit is carried out on the instructions of the controller, the data exporter shall make the results available to the controller.

(f) The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.

(g) The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.

Clause 9

Use of sub-processors

(a) GENERAL WRITTEN AUTHORISATION The data importer has the controller's general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the controller in writing of any intended changes to that list through the addition or replacement of sub-processors at least 30 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the controller with the information necessary to enable the controller to exercise its right to object. The data importer shall inform the data exporter of the engagement of the sub-processor(s).

(b) Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the controller), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.

(c) The data importer shall provide, at the data exporter's or controller's request, a copy of such a sub-processor agreement and any subsequent amendments. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.

Clause 10

Data subject rights

(a) The data importer shall promptly notify the data exporter and, where appropriate, the controller of any request it has received from a data subject, without responding to that request unless it has been authorised to do so by the controller.

(b) The data importer shall assist, where appropriate in cooperation with the data exporter, the controller in fulfilling its obligations to respond to data subjects' requests for the exercise of their rights under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.

(c) In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the controller, as communicated by the data exporter.

Clause 11

Redress

(c) Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:

(i) lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;

(ii) refer the dispute to the competent courts within the meaning of Clause 18.

(d) The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.

(e) The data importer shall abide by a decision that is binding under the applicable EU or Member State law.

(f) The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.

Clause 12

Liability

(a) Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.

(g) The data importer may not invoke the conduct of a sub-processor to avoid its own liability.

Clause 13

Supervision

SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES

Clause 14

Local laws and practices affecting compliance with the Clauses

(b) The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:

(ii) the laws and practices of the third country of destination – including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards;

(d) The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.

(f) Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation, if appropriate in consultation with the controller. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the controller or the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.

Clause 15

Obligations of the data importer in case of access by public authorities

15.1 Notification

(a) The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:

The data exporter shall forward the notification to the controller.

(d) The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.

15.2 Review of legality and data minimization

(c) The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV – FINAL PROVISIONS

Clause 16

Non-compliance with the Clauses and termination

(a) The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.

(c) The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

(ii) the data importer is in substantial or persistent breach of these Clauses; or

(iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority and the controller of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

Clause 17

Governing law

These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland.

Clause 18

Choice of forum and jurisdiction

(a) Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.

(b) The Parties agree that those shall be the courts of Ireland.

(c) A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.

(d) The Parties agree to submit themselves to the jurisdiction of such courts.

APPENDIX

ANNEX I

I.A — Parties

Data Exporter

Field	Value
Name	Excede, Inc.
Address	1654 Calle Tulipan Suite 100, San Juan, Puerto Rico 00927-6242
Contact person	Privacy Officer, dpo@excede.ai, (201) 824-2307
Activities	Provision of a cloud-based AI operating platform for AEC firms (Growth, Execution, and Finance modules), including hosting, AI-assisted analytics, email processing, lead scoring, and related services, as a Processor acting on documented instructions from its Customers (the Controllers)
Role	Processor (acting on behalf of its Customers as Controllers)
Signature and date	Executed on behalf of Excede, Inc. by its authorized representative

Data Importers

The following sub-processors act as data importers under these Clauses. Each sub-processor processes only the categories and purposes specified in its corresponding row in Annex I.B. For sub-processors certified under the EU-US Data Privacy Framework (DPF), Excede relies on DPF as the transfer mechanism in lieu of these Clauses. The current list of Excede's DPF-covered sub-processors is maintained at excede.ai/subprocessors.

#	Sub-Processor Name	Address	Contact / DPA Reference	Role
1	Supabase, Inc.	San Francisco, CA, USA	privacy@supabase.io / supabase.com/privacy	Sub-processor: database hosting, authentication, storage, real-time, edge functions
2	Axiom, Inc.	USA	legal@axiom.co / axiom.co/privacy	Sub-processor: log management and analytics
3	GitLab Inc.	San Francisco, CA, USA	privacy@gitlab.com / about.gitlab.com/privacy	Sub-processor: source code repository, version control (backup mirror)
4	Zoho Corporation Pvt. Ltd.	Austin, TX, USA (India parent entity)	privacy@zohocorp.com / zoho.com/privacy.html	Sub-processor: CRM integration (Zoho CRM), accounting integration (Zoho Books)
5	Better Stack Inc.	USA	betterstack.com/privacy	Sub-processor: uptime monitoring, incident alerting
6	Verne Nemo, LLC dba Ottomatik	12600 Triskett Road, Cleveland, OH 44111, USA	support@ottomatik.io / ottomatik.io	Sub-processor: automated encrypted database backup and recovery

I.C — Competent Supervisory Authority

The competent supervisory authority is the authority of the EU Member State in which the data subjects whose personal data is transferred are predominantly located, as determined by reference to the Customer Controller's establishment or the location of the data subjects in question.

ANNEX II

DESCRIPTION OF THE TRANSFER

In Module 3, this Annex describes the transfer from Excede (as Processor/Exporter) to each sub-processor (as Importer). The categories of data and purposes below reflect what each sub-processor actually receives – not the full scope of data Excede holds.

Categories of data subjects whose personal data is transferred to sub-processors

Customer's employees and project team members
Customer's clients and project stakeholders
Customer's contacts (leads, prospects in CRM-integrated workflows)
Other individuals whose personal data is contained in Customer's data processed by Excede on behalf of the Customer

Categories of personal data transferred (overall)

Identifiers: names, email addresses, phone numbers, user IDs
Professional data: job titles, roles, organizational affiliations
Project and financial data: project names, budgets, hours, revenue figures
Communications data: email content, subject lines, sender/recipient metadata (for email-processing sub-processors only)
Technical and behavioral data: IP addresses, session identifiers, error context, log metadata, usage events
AI-derived data: lead scores, classifications, draft content (generated from above inputs)

Per-sub-processor data categories and purposes

Sub-Processor	Data Categories Received	Purpose of Transfer	Retention at Importer
Supabase	All categories above (primary database)	Hosting and storage of all Customer data; authentication; real-time data sync; file storage	Per Supabase DPA; data deleted upon account closure per Excede instructions
Vercel	IP addresses, request metadata, function inputs/outputs, error context	Application hosting and serverless compute; request routing	Per Vercel DPA; log retention ~90 days
Sentry	Error context (may include user IDs, email addresses, stack traces, request params)	Error monitoring and performance tracking	Per Sentry DPA; typically 90 days
Axiom	Application logs (may include user IDs, org IDs, request metadata)	Log management and analytics	Per Axiom DPA; configurable; typically 90 days
Resend	Email addresses, names, email content (transactional emails only)	Transactional email delivery (platform notifications, invitations, alerts)	Per Resend DPA; delivery logs ~1 year
Cloudflare	IP addresses, request metadata, DNS queries, traffic data	CDN, DDoS protection, WAF, DNS	Per Cloudflare DPA; typically 30 days
Google LLC (Vertex AI / Gemini)	Email content, document text, contact data (as inputs to AI prompts)	AI inference for email classification, lead scoring, draft generation, company research	Per Google Cloud DPA; not used for model training without separate opt-in
Google LLC (Workspace)	Email metadata, calendar data (for integration features)	Email/calendar sync for growth features	Per Google Workspace DPA
Stripe	Billing contact info, payment card data (via Stripe-hosted fields, not seen by Excede), subscription metadata	Payment processing, subscription management	Per Stripe DPA; financial records per PCI-DSS and Stripe retention policy
GitHub / Microsoft	Source code (may contain sample/test data referencing individuals – should not; see security controls)	Version control, CI/CD (primary)	Per GitHub/Microsoft DPA; indefinite as development artifact; PI must be removed on identification
GitLab	Source code (same constraint as GitHub row above)	Version control (backup mirror)	Per GitLab DPA; indefinite as development artifact; PI must be removed on identification
Zoho Corporation	Contact names, email addresses, company names, deal data, financial transaction records	CRM data sync (Zoho CRM); accounting data sync (Zoho Books)	Per Zoho DPA
Upstash / QStash	Session tokens, rate-limit counters, job queue payloads (may include user IDs, org IDs)	Cache, rate limiting, async job processing	TTL-enforced; 1–30 minutes for session/cache; queue messages deleted after delivery
Ottomatik	Full database backup (all data categories above)	Automated encrypted database backup and recovery	30-day rolling backup retention

Sensitive data

None intended. See Module 2 Annex II for the same flag regarding affirmative restriction on Customer input of special category data.

Frequency of transfer

Continuous / on a rolling basis for the duration of the MSA, as Excede provides services to its Customers.

Nature of the processing

Hosting, storage, error monitoring, log analytics, email delivery, AI inference, payment processing, version control, backup, caching and queueing – each limited to the purpose described per sub-processor.

Period for which personal data is retained at the sub-processor level

Per each sub-processor's DPA and the per-processor table above. Excede's deletion obligations upon Customer account closure (per DSA Section 10 and Data Retention Schedule v3.0) are passed down to sub-processors through their DPAs and Excede's deletion instructions.

ANNEX III

TECHNICAL AND ORGANISATIONAL MEASURES OF THE DATA IMPORTERS (SUB-PROCESSORS)

In Module 3, this Annex describes the TOMs of the data importers (sub-processors), not of Excede. Excede's own TOMs are covered in the Module 2 Annex II.

Excede warrants that it has conducted reasonable diligence on each sub-processor's security posture before engagement, and that each sub-processor is bound by a DPA requiring GDPR Article 28-equivalent obligations.

Minimum baseline required of all sub-processors (enforced via their DPAs):

Encryption of personal data in transit using TLS 1.2 or higher
Encryption of personal data at rest using AES-256 or equivalent
Role-based access controls limiting personnel access to minimum necessary
Multi-factor authentication for sub-processor personnel accessing customer data systems
Incident notification to Excede without undue delay (and no later than 72 hours where feasible) upon discovery of a personal data breach
Cooperation with and assistance to Excede in fulfilling data subject rights requests under GDPR/CCPA, including deletion upon documented instruction
Prohibition on sub-processor engaging its own sub-sub-processors to process Excede Customer data without Excede's prior written authorization

Per-sub-processor security certification and documentation references:

Sub-Processor	Security Certifications / DPA Reference	Notes
Supabase	SOC 2 Type II; ISO 27001; supabase.com/security	Primary database – highest criticality; verify current SOC 2 report
Vercel	SOC 2 Type II; vercel.com/security	Application hosting
Sentry	SOC 2 Type II; sentry.io/security	Error monitoring
Axiom	SOC 2 Type II (in progress per public disclosures – verify); axiom.co/security	Log analytics
Resend	resend.com/security; DPA at resend.com/legal/dpa	Email delivery
Cloudflare	SOC 2 Type II; ISO 27001; PCI DSS Level 1; cloudflare.com/trust-hub	CDN/WAF
Google LLC	ISO 27001; SOC 2 Type II; SOC 3; PCI DSS; cloud.google.com/security	AI inference and Workspace
Stripe	SOC 2 Type II; PCI DSS Level 1; stripe.com/docs/security	Payment processing
GitHub / Microsoft	SOC 2 Type II; ISO 27001	Source code
GitLab	SOC 2 Type II; about.gitlab.com/security	Source code backup
Zoho	ISO 27001; SOC 2 Type II; zoho.com/privacy/security.html	CRM / accounting
Upstash	SOC 2 Type II; upstash.com/trust	Cache / queue
Ottomatik	SOC 2 certification; ottomatik.io	Automated encrypted database backup