# Data Processing Agreement

Last updated November 19, 2026

## 1\. Parties and application

1.1 This Data Processing Agreement ("DPA") is between Cayzu Inc., a corporation incorporated under the laws of Canada, located at 280-13300 Tecumseh Rd. E., Suite 369, Tecumseh, Ontario N8N 4R8 ("Cayzu"), and the organization that subscribes to the Cayzu service ("Customer").

1.2 This DPA forms part of the Cayzu Terms of Use or other written agreement governing the Customer's use of the service ("Agreement"). It applies whenever Cayzu processes Personal Information on the Customer's behalf.

1.3 If this DPA conflicts with the Agreement concerning the processing of Personal Information, this DPA governs. The transfer terms in Schedule D prevail over conflicting terms of this DPA to the extent required by those transfer terms.

1.4 This DPA becomes effective when it is incorporated into an Agreement accepted by both parties, including through electronic acceptance of an Agreement that incorporates this DPA. A signed copy is available on request at [privacy@cayzu.com](mailto:privacy@cayzu.com). Publication of an updated version does not, by itself, replace an existing Customer's agreed terms; section 11.3 governs updates.

## 2\. Definitions

2.1 "Personal Information" means information about an identified or identifiable individual that Cayzu processes on the Customer's behalf through the service, as described in Schedule A. It includes "personal data" and "personal information" under applicable Privacy Laws.

2.2 "Customer Data" means information submitted to or generated through the service on the Customer's behalf, including tickets, messages, attachments, contacts, help articles, account settings and related service records. It excludes information Cayzu processes solely for its own purposes under section 3.3.

2.3 "Privacy Laws" means privacy and data protection laws applicable to the relevant processing under the Agreement. Depending on the circumstances, these may include Canada's Personal Information Protection and Electronic Documents Act ("PIPEDA"), applicable provincial privacy laws, Quebec's private sector privacy legislation as amended by Law 25, applicable US state privacy laws, the EU General Data Protection Regulation ("EU GDPR"), and the UK General Data Protection Regulation and Data Protection Act 2018 ("UK GDPR").

2.4 "Subprocessor" means an outside company Cayzu engages to process Personal Information on the Customer's behalf in providing the service.

2.5 "Confidentiality Incident" means unauthorized access to, use of, or disclosure of Personal Information, loss of Personal Information, or another breach of its protection. It includes a personal data breach under the GDPR, a breach of security safeguards under PIPEDA, and a confidentiality incident under applicable Quebec privacy legislation.

2.6 "Staff" means Cayzu employees and individual contractors.

2.7 "Process" and "processing" include collecting, accessing, using, storing, disclosing, transferring, returning and deleting information.

2.8 Unless expressly stated otherwise, Cayzu's contractual obligations concerning confidentiality, security, Subprocessors, incidents, return and deletion apply to all Customer Data, including the Personal Information within it.

## 3\. Roles and responsibilities

3.1 The Customer determines the purposes for which Personal Information is processed through the service and the information submitted to it. The Customer is responsible for lawful instructions, required notices, and any consent or other legal authority needed for its use of the service.

3.2 Cayzu acts as the Customer's service provider or processor. Where the Customer processes Personal Information on another organization's behalf, Cayzu acts as its subprocessor, and the Customer is responsible for obtaining the authorization needed to engage Cayzu.

3.3 Cayzu separately processes account owner and administrator contact details, billing information, and information reasonably necessary to manage its own business relationship, prevent fraud and meet legal obligations. To the extent Cayzu determines the purposes and means of that processing independently, it is governed by the Cayzu Privacy Policy at [https://www.cayzu.com/privacy](https://www.cayzu.com/privacy/). This exception does not permit Cayzu to use ticket content or other information processed on the Customer's behalf for its own unrelated purposes.

3.4 For Customers subject to Quebec's private sector privacy legislation, this DPA establishes the written confidentiality and processing conditions required by section 18.3 of that legislation.

## 4\. Cayzu's processing commitments

4.1 **Documented instructions.** Cayzu will process Personal Information only on the Customer's documented instructions, including instructions concerning transfers, unless applicable law requires otherwise. The Agreement, this DPA, and the Customer's authorized settings and use of the service constitute those instructions. Cayzu will inform the Customer promptly if it believes an instruction infringes applicable Privacy Laws.

4.2 **Required processing.** If applicable law requires processing outside the Customer's instructions, Cayzu will notify the Customer before that processing unless the law prohibits notice. Any processing involving EU or UK Personal Information remains subject to the applicable requirements of section 13 and Schedule D.

4.3 **Purpose limitation.** Cayzu will process Personal Information only to provide, secure, maintain and support the service as described in the Agreement and this DPA. Cayzu will not sell Personal Information, use it for its own marketing or targeted advertising, or disclose it except as authorized by this DPA or required by applicable law.

4.4 **Staff confidentiality.** Access to Customer Data is limited to Staff who need it to perform their duties. Staff may access tickets and attachments when necessary to operate or support the service. Staff with access are bound by written confidentiality obligations and receive privacy and security training annually.

4.5 **Cayzu AI features.** Cayzu's suggested answer and message quarantine features run on Cayzu controlled systems in the account's hosting country: Canada for Canadian hosted accounts and the United States for US hosted accounts. Cayzu does not send Customer Data to an outside AI provider for these features and does not use Customer Data to train AI models. These features do not retain a separate copy of the input or suggested output after processing. An answer becomes part of the ticket record when a user chooses to use it.

4.5A **Optional AI features.** Some Cayzu AI features, such as AI drafted replies, are off until an account administrator agrees to them and turns them on. When one is on, Cayzu sends the information that feature needs, such as ticket text, to Amazon Bedrock, an AWS service, for processing in the United States, and stores the result in the account's hosting country. Cayzu uses the United States for these features so that Customers have access to AI models that are not yet, or not ever, offered in Canada. Depending on the AI model, AWS may retain that information within AWS for a limited period (currently up to 30 days) for abuse detection, and AWS personnel may review content flagged for abuse. Under AWS's terms, Amazon Bedrock does not share those inputs or outputs with the companies that make the AI models and does not use them to train models. Turning a feature on is the Customer's documented instruction under section 4.1 for that processing. Turning it off stops new processing.

4.6 **Customer connected tools.** If the Customer connects an external AI assistant or other application through Cayzu's API, MCP server or another integration, Cayzu will transmit information as directed by the Customer's authorized configuration and use. A provider independently selected and engaged by the Customer is not a Cayzu Subprocessor solely because it receives information through that connection. If Cayzu independently engages a provider to process Personal Information on the Customer's behalf, section 6 applies.

4.7 **Legal demands.** Where legally permitted, Cayzu will direct demands for Customer Data to the Customer and notify the Customer before disclosure. Cayzu will review the demand and disclose only information it is legally required to disclose. Schedule D governs any additional duties applicable to restricted transfers.

## 5\. Data locations and access

5.1 **Hosting region.** Accounts created on the new Cayzu platform use Amazon Web Services hosting in Canada. Legacy accounts created before that platform launched use Amazon Web Services hosting in the United States and cannot currently be migrated to Canada.

5.2 **Account identification.** Cayzu will confirm the Customer's applicable platform and primary hosting country on request at [privacy@cayzu.com](mailto:privacy@cayzu.com). Any hosting region expressly agreed in the Customer's order form or signed schedule governs that account.

5.3 **Primary storage, AI and backups.** Primary databases, file storage, database replicas, backups and Cayzu AI processing remain in the account's hosting country, except processing under section 4.5A. Cayzu may replicate these systems across AWS locations within that country for reliability.

5.4 **Other processing locations.** The hosting commitment in section 5.3 does not exclude the limited processing by providers identified in Schedule B. For example, outgoing email content may be processed in the United States by Postmark. Optional AI features under section 4.5A are processed in the United States through Amazon Bedrock.

5.5 **Staff access.** Staff access the service's back end only from within Canada, including when working remotely or travelling. Access is limited to the task, protected through multiple security layers and logged. Staff are not permitted to download or retain Customer Data on their devices outside approved service systems.

5.6 **Assessments.** Cayzu will provide information reasonably needed for the Customer's assessment of processing outside its jurisdiction, including an assessment required before Personal Information is communicated outside Quebec. The Customer remains responsible for determining whether its own legal requirements permit the proposed processing.

5.7 **Changes.** Cayzu will not change an expressly agreed primary hosting country without the Customer's prior written authorization. Changes to Subprocessors are governed by section 6, and changes to this DPA are governed by section 11.3.

## 6\. Subprocessors

6.1 **Authorization.** The Customer authorizes the Subprocessors identified in Schedule B. Cayzu will maintain a current list at [https://www.cayzu.com/subprocessors](https://www.cayzu.com/subprocessors/) identifying each Subprocessor's function, relevant information and processing locations.

6.2 **Contractual protection.** Cayzu will bind each Subprocessor by a written agreement imposing data protection obligations appropriate to its processing and no less protective than the applicable obligations in this DPA. Cayzu remains responsible for the performance of those obligations by its Subprocessors.

6.3 **Notice.** Cayzu will post any new or replacement Subprocessor on its public list at least 60 days before it processes the Customer's Personal Information. Customers who want these notices by email can ask at [privacy@cayzu.com](mailto:privacy@cayzu.com), and Cayzu will email them when the list is updated. The Customer is responsible for checking the list or requesting email notices.

6.4 **Objections.** The Customer may object within the notice period on reasonable grounds relating to data protection. Cayzu will work with the Customer to address the objection, including through an alternative provider or reasonable service configuration where available. If no reasonable solution is available, the Customer may terminate the affected service before the change takes effect and receive a prorated refund of prepaid fees for the unused period.

6.5 **Urgent replacements.** Where a replacement is urgently necessary to address a material security risk or an unexpected interruption of a provider's service, Cayzu will give as much advance notice as reasonably possible and explain the reason for the shortened period. Cayzu will complete appropriate diligence and contractual safeguards before the replacement processes Personal Information. The Customer retains its objection and termination rights under section 6.4. This provision does not override stricter authorization requirements imposed by applicable law or Schedule D.

6.6 **List corrections.** If Cayzu discovers that its public list omitted an existing Subprocessor, it will promptly correct the list, notify affected Customers and address any failure to obtain required authorization. A correction does not retroactively satisfy an unmet authorization or notice requirement.

## 7\. Security and confidentiality incidents

7.1 **Safeguards.** Cayzu will maintain the technical and organizational measures in Schedule C while it holds Customer Data. Cayzu may update those measures provided the changes do not materially reduce the overall protection of Customer Data.

7.2 **Incident notice.** Cayzu will notify the Customer without undue delay after becoming aware of a Confidentiality Incident affecting its Personal Information and, in any event, within 72 hours. A shorter period required by applicable law or a signed customer schedule will apply.

7.3 **Quebec confidentiality obligations.** Where section 18.3 of Quebec's private sector privacy legislation applies, Cayzu will notify the Customer's person responsible for the protection of Personal Information without delay of any violation or attempted violation of an obligation concerning the confidentiality of the Personal Information communicated to Cayzu. This obligation is not limited to confirmed Confidentiality Incidents and is not subject to the 72 hour period.

7.4 **Notice contents.** To the extent known, the notice will describe the nature of the incident, the categories and approximate numbers of affected individuals and records, likely consequences, containment and remediation measures, and a contact for further information. Cayzu will provide an initial notice with available information and supplement it without undue delay as further details become available.

7.5 **Response and assistance.** Cayzu will promptly investigate, contain and remediate the incident and reasonably assist the Customer with risk assessments, legally required notices and regulatory inquiries. Cayzu will maintain incident records required by applicable law and provide relevant information to the Customer on request.

7.6 **External communications.** Cayzu will not notify individuals or regulators on the Customer's behalf without the Customer's instructions unless applicable law requires Cayzu to do so. Where legally permitted, Cayzu will coordinate required notices with the Customer.

## 8\. Assistance with requests and assessments

8.1 **Individual requests.** Cayzu will promptly forward requests it receives concerning Personal Information processed on the Customer's behalf. It will not substantively respond except on the Customer's instructions or as required by law.

8.2 **Service controls.** The service provides tools to locate, export, correct and delete records, including tickets, contacts and attachments. Customer administrators control their users' permissions. Taking account of the nature of the processing, Cayzu will provide reasonable assistance where those tools do not enable the Customer to meet an applicable obligation.

8.3 **Portability.** On request, Cayzu will provide relevant Personal Information in a structured, commonly used and machine readable format to assist the Customer with applicable portability requirements.

8.4 **Security and assessments.** Taking account of the nature of the processing and the information available to it, Cayzu will assist the Customer with applicable security obligations, breach notifications, privacy or data protection impact assessments, and prior consultation with regulators. This includes providing relevant information for assessments of processing outside Quebec.

8.5 **Public bodies.** Cayzu will cooperate with obligations that applicable public sector privacy legislation places on its service providers. Additional customer specific requirements, including restrictions on location or access, must be documented in a signed schedule before the affected processing begins.

8.6 **Charges.** Routine assistance is included in the subscription. If a request requires substantial additional work, Cayzu may propose a reasonable fee and obtain the Customer's agreement before starting that additional work. Charges will not excuse Cayzu from performing its own legal obligations or delay assistance needed to meet a mandatory legal deadline.

## 9\. Return, deletion and retention

9.1 **Customer choice.** When the service ends, the Customer may instruct Cayzu to return or delete its Personal Information. If the Customer chooses return, Cayzu will provide an export and then delete remaining copies in accordance with this section.

9.2 **Export.** The Customer may export its Customer Data, including attachments, during the subscription. Requests for assistance with return should be made before the last paid period ends. If a return request remains outstanding at termination, Cayzu will provide the requested export before deleting the relevant information.

9.3 **Paid accounts.** Subject to sections 9.2 and 9.6, Cayzu will permanently delete Customer Data from its active systems, attachments, replicas and service logs containing Customer Data 90 days after the Customer's last paid period ends. Cayzu will email the Customer's account administrator before deletion. Remaining backup copies are deleted within a further 30 days. If retention is necessary to complete a timely return request, Cayzu will isolate the retained information, use it only for that return and delete it promptly afterwards.

9.4 **Trial accounts.** Subject to section 9.6, trial accounts that do not become paid subscriptions are deleted from active systems, attachments, replicas and service logs 30 days after the trial expires. Cayzu will email the trial account's administrator before deletion. Remaining backup copies are deleted within a further 30 days. A Customer may request earlier return or deletion where required by applicable Privacy Laws.

9.5 **Subprocessors.** Cayzu will instruct relevant Subprocessors to return or delete Customer Data within the applicable periods in this section and ensure its arrangements with them support those obligations.

9.6 **Legally required retention.** Cayzu may retain information only to the extent and for the period required by applicable law. It will identify the legal requirement to the Customer unless prohibited, restrict access, maintain applicable safeguards, use the retained information only for the required purpose and delete it when the requirement ends. For EU or UK Personal Information, any retention exception must satisfy the applicable GDPR and transfer terms. Cayzu's independently controlled billing records are governed by section 3.3.

9.7 **Backup restrictions.** Until deletion, backup data is protected and unavailable for ordinary business use. If a backup is restored for disaster recovery, Cayzu will reapply applicable deletion instructions.

9.8 **Confirmation.** On written request, Cayzu will confirm completion of deletion and identify any information retained under section 9.6 and the applicable retention basis.

## 10\. Information and audits

10.1 **Information.** Cayzu will provide information reasonably necessary to demonstrate compliance with this DPA, including responses to reasonable security questionnaires and available relevant documentation.

10.2 **Audits.** Cayzu will allow and contribute to audits, including inspections, by the Customer or an independent auditor it appoints. The parties will first consider whether documentation, a questionnaire or an independent report adequately addresses the concern. Such materials do not replace an audit where further verification is reasonably necessary or legally required.

10.3 **Arrangements.** Routine audits will ordinarily take place no more than once annually, on 30 days' notice, during business hours and under appropriate confidentiality obligations. These limits do not restrict audits required by applicable law, a regulator, a Confidentiality Incident, or reasonable evidence of material noncompliance. The parties will agree on practical arrangements that protect security and other customers' information without preventing meaningful verification.

10.4 **Costs.** The Customer bears its own routine audit costs. Any charges for Cayzu's substantial additional assistance must be reasonable and agreed in advance and must not prevent an audit required by applicable law.

10.5 **Quebec verification.** Where section 18.3 of Quebec's private sector privacy legislation applies, Cayzu will allow the Customer's person responsible for the protection of Personal Information to conduct verification relating to confidentiality requirements.

10.6 **Hosting reports.** Cayzu may make relevant AWS security reports available where permitted by AWS. Those reports describe AWS's controls and do not, by themselves, establish independent certification of Cayzu's own operations.

## 11\. General terms

11.1 **Duration.** This DPA remains in effect for as long as Cayzu or its Subprocessors hold Customer Data on the Customer's behalf. Applicable confidentiality, security, restricted use, audit and deletion obligations survive termination until that information has been returned or deleted, including information retained under section 9.6.

11.2 **Liability.** Subject to applicable law and Schedule D, liability between the parties is governed by the Agreement. Nothing in the Agreement or this DPA limits an individual's rights, a regulator's powers or liability that cannot lawfully be limited. Cayzu maintains cyber and privacy breach insurance and will provide evidence of coverage on request.

11.3 **Changes.** Cayzu may propose updates to this DPA to reflect changes in law or the service by giving at least 30 days' advance notice by email to the Customer's designated contact or account administrator. Updates will not materially reduce protection of Customer Data or override mandatory transfer terms. A Customer that objects to a material update may terminate the affected service before it takes effect and receive a prorated refund of prepaid fees for the unused period. Where applicable law or the Agreement requires express acceptance, Cayzu will obtain that acceptance.

11.4 **Governing law.** Except as provided in Schedule D or required by applicable law, this DPA is governed by the laws of Ontario and the federal laws of Canada applicable there.

11.5 **Contacts.** Cayzu's privacy officer is Adam Schentag, reachable at [privacy@cayzu.com](mailto:privacy@cayzu.com). The Customer's privacy contact is the contact designated in its order form or account records, or its account administrator if no separate contact has been designated.

## 12\. US state privacy laws and school data

12.1 **Service provider and processor obligations.** Where applicable US state privacy laws treat Cayzu as a service provider, contractor or processor, Cayzu will process Personal Information only for the specific purposes described in the Agreement and Schedule A and on the Customer's documented instructions.

12.2 **Restrictions.** Cayzu will not sell or share Personal Information, use it for targeted or cross context behavioural advertising, or retain, use or disclose it outside the specified purposes or the direct business relationship with the Customer, except as permitted by applicable law. Cayzu will not combine that information with information received from another person or collected through its own interactions with individuals except to the extent expressly permitted by applicable law.

12.3 **Compliance and oversight.** Cayzu will provide the level of privacy protection required by applicable law, notify the Customer if it determines that it can no longer meet its obligations, and permit reasonable steps to verify compliance and stop and remediate unauthorized processing. Cayzu certifies that it understands and will comply with the restrictions applicable to its role. Subprocessors will be subject to equivalent applicable requirements.

12.4 **New York education records.** Where Cayzu receives student data or protected teacher or principal data from a New York educational agency, it will process that information only for authorized educational purposes, restrict access to authorized personnel, apply appropriate safeguards, including encryption in transit and at rest, and prohibit sale or use for marketing or commercial purposes unrelated to the authorized service.

12.5 **Education data incidents.** Cayzu will notify the educational agency in the most expedient way possible and without unreasonable delay after discovery of a breach or unauthorized release, within the shorter period required by section 7.2 or applicable law. Cayzu will cooperate with investigation, remediation and legally required notices.

12.6 **Required school schedule.** Before processing information subject to New York Education Law § 2-d, the parties will complete a written education data protection schedule and any required data security and privacy plan. These documents will address required matters, including exclusive purposes, protected information, subcontractor obligations, storage locations, safeguards, applicable parents' bill of rights, training, incident procedures, and return or destruction at the end of the engagement. This DPA alone does not replace those customer specific documents.

## 13\. EU and UK Personal Information

13.1 **Roles.** Where the EU GDPR or UK GDPR applies, the Customer acts as controller or processor, as applicable, and Cayzu acts as its processor or subprocessor. This DPA establishes the processing terms required by Article 28.

13.2 **Processing details.** Schedule A describes the subject matter, duration, nature and purposes of processing, categories of individuals and types of Personal Information. The Customer's rights and obligations are set out in this DPA and the Agreement.

13.3 **Assistance and accountability.** Cayzu will comply with the applicable requirements of Articles 28 and 32 through 36 concerning instructions, confidentiality, security, Subprocessors, individual rights, incidents, assessments, regulatory consultation, return or deletion, and compliance information and audits.

13.4 **Transfers.** Cayzu will ensure that transfers requiring safeguards under Chapter V of the applicable GDPR are covered by a valid adequacy decision or another lawful transfer mechanism. Canadian adequacy may be relied on only to the extent it covers the recipient and processing concerned.

13.5 **US recipients.** Reliance on the EU US Data Privacy Framework, its UK Extension or another adequacy arrangement requires verification that the recipient has an active certification or other applicable coverage extending to the relevant information and transfer. A recipient's US location alone does not establish coverage.

13.6 **Contractual safeguards.** Where no applicable adequacy decision covers a restricted transfer between the Customer and Cayzu, Schedule D applies. Cayzu will separately ensure that restricted onward transfers to its Subprocessors are supported by an appropriate mechanism binding the relevant recipients. Incorporating clauses between the Customer and Cayzu does not, by itself, bind an outside recipient.

13.7 **Transfer assessments.** Where required, Cayzu will carry out or assist with transfer assessments and implement necessary supplementary measures. If a transfer cannot lawfully continue, Cayzu will suspend it and work with the Customer on a lawful alternative, return or deletion.

## Schedule A: Description of processing

| Item | Details |
| --- | --- |
| A.1 Subject matter | Processing Customer Data in connection with the Cayzu help desk service. |
| A.2 Nature and purposes | Receiving, recording, organizing, storing, retrieving, routing and transmitting support tickets, messages and attachments; maintaining contacts, customer portals and knowledge bases; generating reports; providing configured AI suggested answers and message quarantine, and optional AI features under section 4.5A where the Customer turns them on; providing technical support; securing and maintaining the service; and returning or deleting information on the Customer's instructions. |
| A.3 Categories of individuals | The Customer's agents and administrators; individuals requesting support; portal users; and other individuals whose information is included in tickets, messages, attachments or other Customer Data. |
| A.4 Types of Personal Information | Names, email addresses, phone numbers, company details, ticket and message content, attachments, portal account and authentication information, IP addresses, device and browser information, usage records and agent time records. |
| A.5 Sensitive information | The service is not designed specifically to host health, financial or other sensitive information. The Customer controls submitted content and is responsible for determining whether the service is suitable for its intended information. Before intentionally submitting information requiring additional safeguards or a separate regulated agreement, the Customer must contact Cayzu to agree on any necessary conditions. The presence of sensitive information does not remove Cayzu's obligations concerning information it processes. |
| A.6 Frequency | Continuous or recurring processing during the Customer's use of the service, with individual operations occurring on the Customer's instructions and as necessary to provide the service. |
| A.7 Duration | The subscription or trial period and the applicable return, deletion or legally required retention periods in section 9. |
| A.8 Locations | Primary hosting and Cayzu AI processing in Canada or the United States according to the Customer's account; Staff access from Canada; optional AI features under section 4.5A processed in the United States through Amazon Bedrock; and other provider processing as described in Schedule B. |
| A.9 Subprocessor activities | Hosting, storage and backups throughout the service and deletion period; email delivery as messages are sent; analytics processing where enabled and performed on the Customer's behalf; and AI processing through Amazon Bedrock while optional AI features are turned on. |

## Schedule B: Subprocessors and other providers

| Provider | Role | Services | Information | Location |
| --- | --- | --- | --- | --- |
| Amazon Web Services | Subprocessor | Hosting, databases, file storage, replicas and backups; Amazon Bedrock for optional AI features | Customer Data hosted in the service | Canada for Canadian hosted accounts; United States for legacy US hosted accounts. Primary storage, replicas and backups stay in the account's hosting country. Optional AI features under section 4.5A are processed in the United States through Amazon Bedrock. Results are stored in the account's hosting country. |
| Postmark, provided by ActiveCampaign, LLC | Subprocessor | Delivery of transactional email, ticket replies and notifications | Recipient and sender email addresses, names, outgoing email content, attachments in those emails, and delivery records | United States |
| Google Analytics, provided by Google LLC | Subprocessor to the extent Cayzu configures analytics to process portal or application usage on the Customer's behalf | Usage measurement for websites, applications and customer portals where enabled | Device and browser information, IP address information to the extent processed, online identifiers and usage events. Ticket content and attachments are not authorized inputs. | Determined by Google. Cayzu does not control where Google processes Analytics data. See Google's privacy policy and the Google Analytics terms. |
| Stripe Payments Canada, Ltd. | Provider for Cayzu's own billing; not a Subprocessor for ticket processing | Subscription billing and payment processing | Billing contact, transaction and payment information. No ticket content or attachments. | United States, with any other locations disclosed in the applicable billing privacy information |

B.1 **Google Analytics conditions.** Processing for Cayzu's own website measurement is addressed in the Cayzu Privacy Policy. Analytics must be configured and used consistently with the Customer's instructions, applicable consent requirements and section 12, and must not be used to get around this DPA's advertising or disclosure restrictions. Cayzu will identify applicable locations and contractual safeguards before authorizing processing not covered by the existing authorization.

B.2 **Stripe.** Section 3.3 and the applicable privacy notices govern independently controlled billing processing.

B.3 **List maintenance.** Cayzu's public list at [https://www.cayzu.com/subprocessors](https://www.cayzu.com/subprocessors/) will distinguish Subprocessors from providers used solely for Cayzu's independent business purposes. Subprocessor changes remain subject to section 6.

## Schedule C: Technical and organizational security measures

These measures apply to all accounts, including those not yet moved to the new Cayzu platform.

| Area | Measure |
| --- | --- |
| C.1 Encryption | Customer Data is encrypted at rest in service storage and backups. Web and API traffic uses HTTPS with TLS. Connections used to submit email to Postmark use TLS. Internet email delivery is not end to end encrypted; recipient delivery protection depends on the receiving system and delivery configuration. |
| C.2 Hosting and resilience | The service uses AWS data centres. Core databases are replicated across AWS locations within the account's hosting country for reliability. Backups are protected against unauthorized access and remain in that country. |
| C.3 Customer authentication | SAML 2.0 single sign on is available on Pro and Enterprise plans and supports compatible providers, including Okta, Microsoft Entra and Google Workspace. Agent multifactor authentication is available on all plans, with or without single sign on. |
| C.4 Network restrictions | Enterprise customers may configure trusted IP allow lists for agents, portal users or both. |
| C.5 Staff access | Back end access is restricted to authorized Staff with a business need, takes place from Canada, passes through multiple security layers and is logged. Access permissions are reviewed and removed when no longer required. Customer Data must remain within approved service systems. |
| C.6 Confidentiality and training | Staff with access to Customer Data are bound by written confidentiality obligations and receive annual privacy and security training. |
| C.7 Software changes | Code changes undergo automated unit and integration testing before release. Releases pass through a separate staging environment before production deployment. |
| C.8 AI processing | Suggested answer and message quarantine features process information on Cayzu controlled systems in the account's hosting country. Customer Data is not provided to outside AI providers for those features or used to train AI models. Optional AI features under section 4.5A are processed through Amazon Bedrock as described in that section. Separate input and suggested output copies are not retained after processing, as described in section 4.5. |
| C.9 Backups and deletion | Backups are retained for up to 30 days, subject to the account deletion deadlines in section 9. Deletion procedures cover active storage, attachments, replicas, logs containing Customer Data, backups and relevant copies held by Subprocessors. |
| C.10 Incident response | Cayzu maintains a written incident response plan assigning responsibilities for investigation, containment, recovery, documentation and customer notification. |
| C.11 Review | Cayzu reviews safeguards in light of relevant risks, changes to the service and incidents, and maintains appropriate measures to protect confidentiality, integrity, availability and resilience. |

## Schedule D: International transfer terms

D.1 **Application.** This Schedule applies where a transfer of Personal Information between the Customer and Cayzu requires contractual safeguards under the EU GDPR or UK GDPR and is not covered by an applicable adequacy decision.

D.2 **EU Standard Contractual Clauses.** The Standard Contractual Clauses adopted by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021 ("SCCs") are incorporated by reference without modification except for the selections and completion information permitted by the SCCs and set out below. The official text is available at [https://eur-lex.europa.eu/eli/dec\_impl/2021/914/oj](https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj).

D.3 **Modules and selections.** Module Two applies where the Customer is a controller and Cayzu is its processor. Module Three applies where the Customer is a processor and Cayzu is its subprocessor. Clause 7, the optional docking clause, applies. For Clause 9(a), Option 2, general written authorization, applies, with an advance notice period of 60 days; any urgent replacement must remain consistent with the SCCs' authorization requirements. The optional wording in Clause 11 does not apply. For Clause 17, Option 1 applies and the SCCs are governed by Irish law. For Clause 18(b), disputes are subject to the courts of Ireland, without limiting any rights granted to individuals by the SCCs.

D.4 **Annex I.A: Parties.** Data exporter: the Customer, identified by its full legal name and address in the Agreement, order form or accepted account registration records; its contact is its designated privacy contact or account administrator; its activity is use of the Cayzu service for the processing in Schedule A; its role is controller under Module Two or processor under Module Three. Data importer: Cayzu Inc., 280-13300 Tecumseh Rd. E., Suite 369, Tecumseh, Ontario N8N 4R8, Canada; contact Adam Schentag, Privacy Officer, [privacy@cayzu.com](mailto:privacy@cayzu.com); activity is provision of the Cayzu service as described in Schedule A; role is processor under Module Two or subprocessor under Module Three. Each party's binding acceptance of the Agreement incorporating this DPA constitutes its acceptance of the SCCs, on the date recorded in the Agreement or electronic acceptance records.

D.5 **Annex I.B: Transfer description.** The categories of individuals, types of Personal Information, processing purposes, nature of processing, frequency and retention periods are those in Schedule A and section 9. Sensitive information, if present, is subject to section A.5 and the safeguards in Schedule C. Any additional safeguards required for the Customer's intended sensitive information must be agreed before that processing begins. Transfers to Subprocessors concern the activities and durations in Schedules A and B.

D.6 **Annex I.C: Supervisory authority.** The competent supervisory authority is determined under Clause 13 of the SCCs. Where the Customer is established in an EU member state, the authority responsible for its compliance with the EU GDPR is competent. Where the Customer is subject to Article 3(2) and has appointed an EU representative, the authority for the member state where that representative is established is competent. Where the Customer is subject to Article 3(2) but is not required to appoint a representative, the authority is that of a member state where affected individuals are located, as identified by the Customer before the relevant transfer. The Customer will provide the information needed to identify the competent authority before a transfer relying on the SCCs begins.

D.7 **Annex II: Security measures.** Schedule C specifies the technical and organizational measures applicable to the transfer. Sections 6 through 10 describe additional controls concerning Subprocessors, incidents, assistance, deletion and verification. Any additional transfer specific measures identified by a required assessment will be documented before the affected transfer begins.

D.8 **Onward transfers.** Cayzu will comply with the SCC requirements for onward transfers and ensure that each restricted transfer to a Subprocessor is covered by an appropriate legally binding mechanism. Where separate clauses are required with a Subprocessor, Cayzu will execute and complete them for that transfer.

D.9 **UK Addendum.** For restricted transfers subject to the UK GDPR, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner, version B1.0 in force from 21 March 2022, is incorporated by reference, including Part 2, Mandatory Clauses, as revised in accordance with those Mandatory Clauses. The official Addendum is available at [https://ico.org.uk/media/for-organisations/documents/4019539/international-data-transfer-addendum.pdf](https://ico.org.uk/media/for-organisations/documents/4019539/international-data-transfer-addendum.pdf). For Table 1, the parties, contacts, roles and acceptance details are those in section D.4, and the start date is the date the Addendum becomes binding through acceptance of the Agreement. For Table 2, the selected EU SCCs are those in sections D.2 and D.3. For Table 3, the appendix information is provided by sections D.4 through D.7 and Schedules A, B and C. For Table 4, both the exporter and the importer may end the Addendum under section 19 of its Mandatory Clauses. The Mandatory Clauses determine the applicable UK adaptations, governing law and jurisdiction.

D.10 **Priority and mandatory rights.** The SCCs and UK Addendum prevail over conflicting provisions of the Agreement or this DPA to the extent required by their terms. No commercial liability limit, audit restriction, fee or termination provision may restrict mandatory rights or obligations under those instruments.

D.11 **Completion before transfer.** The parties will ensure that the incorporated account and Agreement records identify the Customer and required transfer particulars before relying on this Schedule. If a transfer requires information, safeguards or a recipient agreement not supplied by this DPA and those records, the parties will complete them before that transfer begins.

---

The web page: https://www.cayzu.com/dpa/
