Data Processing Addendum
Data Processing Addendum (DPA)
Last Updated: November 21st, 2026
Version: 2026.11.21.1
Effective Date: November 21st, 2026
This Data Processing Addendum (“DPA”) forms part of the Terms of Service, subscription agreement, order form, or other agreement governing Customer's use of the Countercyclical Services (collectively, the “Agreement”) between Countercyclical LLC, a Delaware limited liability company (“Provider,” “Countercyclical,” “we,” or “us”) and the individual or legal entity identified as the customer in the Agreement (“Customer”).
This DPA governs Provider's Processing of Customer Personal Data on behalf of Customer in connection with the Services.
Customer accepts this DPA through the applicable signup, clickwrap, or other designated acceptance process. A person accepting this DPA on behalf of an organization represents that they are authorized to bind that organization. Provider may retain the applicable DPA version, Customer and workspace identity, accepting person's identity, acceptance method, and acceptance timestamp as evidence of acceptance.
Capitalized terms not defined in this DPA have the meanings given to them in the Agreement. If a term is defined differently in this DPA and the Agreement, the definition in this DPA controls solely for purposes of Provider's Processing of Customer Personal Data under this DPA.
1. Definitions
For purposes of this DPA:
1.1. “Applicable Privacy Laws” means applicable U.S. federal and state privacy and data protection laws governing the Processing of Personal Data, including applicable state comprehensive privacy laws and their implementing regulations, as amended.
1.2. “Customer Personal Data” means Personal Data that Provider Processes on behalf of Customer in connection with the Services. Customer Personal Data may be included in or overlap with Customer Content, Account Data, Operational Metadata, or other information protected under the Agreement. Classification as metadata or another category does not remove protections that otherwise apply to Personal Data or Confidential Information.
1.3. “Data Subject” means an identified or identifiable natural person to whom Personal Data relates.
1.4. “Personal Data” means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked to an identified or identifiable natural person, as defined under Applicable Privacy Laws.
1.5. “Processing” means any operation performed on Personal Data, including collection, recording, organization, structuring, storage, alteration, retrieval, consultation, use, disclosure, transmission, restriction, deletion, or destruction.
1.6. “Security Incident” means a breach of Provider's security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data in Provider's possession or control. A Security Incident may occur in Provider's systems or in systems operated by a Subprocessor. A security event that does not result in such compromise, including an unsuccessful attack or routine security alert, is not by itself a Security Incident.
1.7. “Subprocessor” means a third party engaged by Provider to Process Customer Personal Data on Provider's behalf in connection with the Services.
1.8. “U.S. State Privacy Laws” means applicable state privacy and data protection statutes and regulations, including the California Consumer Privacy Act, as amended by the California Privacy Rights Act, and similar laws in other U.S. states.
2. Scope and Roles
2.1. Roles of the Parties.
For purposes of Applicable Privacy Laws, Customer acts as the business, controller, or other equivalent entity determining the purposes and means of Processing Customer Personal Data. Provider acts as the service provider, processor, contractor, or other equivalent entity Processing Customer Personal Data on behalf of Customer.
The Parties' roles may differ where Provider Processes Personal Data for its own independent business purposes, as described in Section 3.4. This DPA applies to Processing performed by Provider on behalf of Customer and does not convert Provider's independent business Processing into Processing on Customer's behalf.
2.2. Scope of Processing.
Provider will Process Customer Personal Data only as necessary to provide the Services and perform the activities permitted by this DPA, the Agreement, and Customer's documented instructions, subject to Applicable Privacy Laws.
2.3. Processing Details.
The subject matter, duration, nature, purposes, categories of Data Subjects, and categories of Personal Data are described in Schedule 1.
2.4. Customer Responsibilities.
Customer is responsible for:
(a) ensuring it has a lawful basis and all required rights, permissions, notices, and consents for Processing Customer Personal Data and providing it to Provider;
(b) ensuring its instructions to Provider comply with Applicable Privacy Laws;
(c) responding to Data Subject requests except to the extent Provider is required to assist under this DPA;
(d) ensuring that Customer Personal Data submitted to the Services is appropriate for Customer's intended use; and
(e) configuring and using the Services in compliance with the Agreement and Applicable Privacy Laws.
3. Customer Instructions and Permitted Processing
3.1. Documented Instructions.
The Agreement, this DPA, Customer's use and configuration of the Services, and Customer's written instructions constitute Customer's documented instructions to Provider.
Provider will notify Customer if Provider reasonably believes that a documented instruction violates Applicable Privacy Laws. Provider is not required to follow an instruction that Provider reasonably believes would violate Applicable Privacy Laws.
3.2. Permitted Purposes.
Provider may Process Customer Personal Data as reasonably necessary to:
(a) provide the Services and their features requested or used by Customer;
(b) host, store, retrieve, transmit, organize, and display Customer Personal Data;
(c) provide customer support and respond to Customer instructions;
(d) perform authentication, authorization, access management, and account administration in connection with the Services;
(e) provide AI-powered features and integrations when enabled or authorized by Customer, subject to this DPA and the AI Addendum where applicable;
(f) monitor, maintain, troubleshoot, and secure the functionality, reliability, and operation of the Services, subject to the use restrictions in the Agreement;
(g) detect, prevent, and investigate fraud, abuse, security incidents, and violations of the Agreement;
(h) perform usage metering and other service-administration activities necessary to provide the Services;
(i) comply with applicable legal obligations; and
(j) perform other Processing activities expressly authorized by Customer in documented instructions.
Provider's permission to Process Customer Personal Data under this Section does not independently authorize Provider to use Customer Content, Customer Personal Data, AI Inputs, AI Outputs, prompts, instructions, uploads, conversation histories, or Customer-specific Feedback for model Training or for unrelated commercial purposes. The restrictions in the Agreement and AI Addendum continue to apply.
3.3. Restrictions on Processing.
To the extent required by Applicable Privacy Laws, Provider will:
(a) Process Customer Personal Data only for the limited and specified purposes described in this DPA, the Agreement, and Customer's documented instructions;
(b) not sell or share Customer Personal Data as those terms are defined under applicable U.S. State Privacy Laws;
(c) not retain, use, or disclose Customer Personal Data outside the direct business relationship between Provider and Customer, except as permitted by Applicable Privacy Laws;
(d) not use Customer Personal Data for targeted advertising or cross-context behavioral advertising;
(e) not combine Customer Personal Data with Personal Data obtained from other sources except as permitted by Applicable Privacy Laws; and
(f) notify Customer if Provider determines that it can no longer meet its obligations under Applicable Privacy Laws.
Provider will not use this DPA or the distinction between Customer-directed Processing and Provider's independent business Processing to avoid restrictions imposed by Applicable Privacy Laws or the Agreement.
3.4. Provider's Independent Business Purposes.
Nothing in this DPA prevents Provider from Processing Personal Data as an independent business or controller where permitted by Applicable Privacy Laws, including for:
(a) account registration and administration;
(b) billing, invoicing, payment processing, and tax and accounting records;
(c) security, fraud prevention, abuse detection, and protection of the Services;
(d) compliance with legal obligations;
(e) enforcing the Agreement; and
(f) maintaining appropriate business, operational, and audit records.
(g) measuring attribution and the effectiveness of Provider's own customer acquisition and marketing campaigns, including through the use or disclosure of limited Account Data, Operational Metadata, and purchase or subscription conversion information to advertising and measurement providers, subject to the Privacy Policy and applicable privacy choices and permissions.
This paragraph applies only to Processing undertaken by Provider in its independent business capacity and does not authorize Provider to use or disclose Customer Personal Data Processed on behalf of Customer under this DPA for advertising or marketing purposes. It also does not authorize the use or disclosure of Customer Content, confidential workspace information, or other information Processed on behalf of Customer for targeted advertising or cross-context behavioral advertising. Any permitted attribution or conversion measurement under this paragraph is limited to information Provider Processes in its independent business capacity and remains subject to Applicable Privacy Laws and the applicable privacy choices and permissions described in Provider's Privacy Policy.
Provider will describe its independent Processing practices in its Privacy Policy or other applicable privacy disclosures and will comply with Applicable Privacy Laws governing that Processing.
Provider will not characterize Processing performed on behalf of Customer as independent business Processing merely to avoid its obligations under this DPA. Information that identifies Customer or an individual, reveals Customer Content, or otherwise constitutes Personal Data or Confidential Information remains subject to the protections applicable to that information, regardless of its label.
4. Confidentiality and Personnel
4.1. Confidentiality.
Provider will ensure that persons authorized to Process Customer Personal Data are subject to appropriate confidentiality obligations, whether contractual, statutory, or otherwise legally binding.
4.2. Access Restrictions.
Provider will restrict access to Customer Personal Data to persons who require access to perform their responsibilities in connection with the Services.
4.3. Personnel Access.
As of the Effective Date, Provider has a single individual with administrative access to its production infrastructure and Customer Personal Data. Provider will maintain reasonable access restrictions as its personnel and operations evolve.
5. Security Measures
5.1. Security Obligations.
Provider will implement and maintain reasonable administrative, technical, and organizational safeguards designed to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access.
5.2. Security Measures.
Provider's current general categories of technical and organizational safeguards are described in Schedule 2.
Provider may update its security measures from time to time, provided that the changes do not materially reduce the overall level of protection afforded to Customer Personal Data.
5.3. No Absolute Guarantee.
Provider does not warrant that its safeguards will prevent every Security Incident, unauthorized access attempt, service interruption, or loss of data.
5.4. Customer Responsibilities.
Customer remains responsible for maintaining the security of its own systems, credentials, devices, users, and integrations, and for configuring the Services appropriately.
6. Subprocessors
6.1. General Authorization.
Customer provides Provider with general authorization to engage Subprocessors to Process Customer Personal Data in connection with the Services, subject to this Section 6 and Applicable Privacy Laws.
6.2. Subprocessor Obligations and Responsibility.
Provider will enter into written agreements with Subprocessors that impose data protection obligations appropriate to the Processing performed by those Subprocessors, including obligations relating to confidentiality, security, incident notification, assistance, and deletion or return of Customer Personal Data, as applicable to the Subprocessor's role and Processing.
Provider remains responsible for the performance of its Subprocessors to the extent they perform Processing obligations delegated by Provider under this DPA, subject to the Agreement's applicable limitations and exclusions of liability.
6.3. Subprocessor and Authorized Customer Content Recipient Register.
Provider maintains a public register identifying its current Subprocessors and other third-party providers engaged by Provider and authorized to receive Customer Content in connection with the Services.
The register is available at:
https://security.countercyclical.io?itemUid=e3fae2ca-94a9-416b-b577-5c90e382df57
The register is incorporated by reference into this DPA and is the authoritative and definitive register of Provider's Subprocessors and other authorized Customer Content recipients. Schedule 3 describes the register and its operation; it does not create a separate or competing static list.
The register identifies the role and relevant service or purpose of each listed provider. A provider listed solely as an authorized recipient of Customer Content does not become a Subprocessor under this DPA merely by being listed. The obligations applicable to Subprocessors under this DPA apply to a listed provider only to the extent that the provider Processes Customer Personal Data on Provider's behalf.
If a descriptive summary elsewhere is inconsistent with the register, the register controls as to the identity and authorized role of Provider's listed providers, subject to the applicable notice and objection rights.
6.4. Notice of New Subprocessors.
Provider will provide at least fifteen (15) days' advance notice before authorizing a new Subprocessor to Process Customer Personal Data or a new third-party provider to receive Customer Content in connection with the Services, or materially changing an existing provider's relevant Processing activities or authorized access to Customer Content.
Notice may be provided through the Subprocessor register, email, or another reasonable electronic communication method. Provider will use the notice method identified in the Agreement or otherwise reasonably available for communicating material Subprocessor changes to Customer.
Where a Subprocessor must be engaged or replaced urgently to maintain the security, availability, or continuity of the Services, Provider may provide shorter notice where reasonably necessary, subject to Applicable Privacy Laws. Provider will provide notice of the urgent engagement or replacement as soon as reasonably practicable.
6.5. Objections.
Customer may object to a newly appointed Subprocessor or newly authorized Customer Content recipient within ten (10) days after receiving notice, provided that the objection is based on reasonable and documented data protection or security concerns relating to the proposed Subprocessor.
The Parties will work in good faith to resolve the objection. Provider will consider the documented concern and whether reasonable alternative arrangements are available.
If Provider cannot reasonably accommodate the objection, Provider may:
(a) refrain from using the proposed Subprocessor for the affected Processing;
(b) implement commercially reasonable alternative measures that address the documented concern; or
(c) discontinue the affected functionality or portion of the Services if no reasonable alternative is available, with a pro-rata refund of prepaid fees attributable to the discontinued portion, where applicable.
Provider will not use a newly appointed Subprocessor to Process the affected Customer Personal Data, or permit a newly authorized third-party provider to receive the affected Customer Content, before the applicable notice and objection period has elapsed and any timely objection has been addressed, except where an urgent engagement or replacement is reasonably necessary under Section 6.4 or otherwise permitted by Applicable Privacy Laws.
Customer's objection does not automatically entitle Customer to terminate unaffected portions of the Services or receive a refund of unrelated fees.
6.6. Existing Providers.
Subprocessors and other third-party providers identified in the register as of the Effective Date are authorized for the roles and activities identified in the register, subject to this DPA and the Agreement. Their inclusion does not alter the distinction between Subprocessors and other authorized Customer Content recipients.
7. Data Subject Requests
7.1. Assistance.
Taking into account the nature of the Processing, Provider will provide reasonable assistance to Customer, through appropriate technical and organizational measures where reasonably available, to enable Customer to respond to requests from Data Subjects exercising their rights under Applicable Privacy Laws.
7.2. Direct Requests.
If Provider receives a request directly from a Data Subject concerning Customer Personal Data, Provider will, where reasonably practicable and legally permitted, direct the Data Subject to Customer.
Provider will not independently respond to such requests except as required by law or authorized by Customer.
7.3. Customer Responsibility.
Customer remains responsible for determining whether and how to respond to Data Subject requests.
8. Security Incidents
8.1. Notification.
Provider will notify Customer without undue delay after becoming aware of a Security Incident affecting Customer Personal Data in Provider's possession or control.
This obligation includes a Security Incident involving a Subprocessor to the extent Provider becomes aware of the incident through its own investigation or notification from the Subprocessor. Provider will not delay initial notification solely because its investigation or assessment is incomplete.
8.2. Initial Incident Information.
To the extent reasonably available at the time of initial notification, Provider's notification will include:
(a) a description of the nature of the Security Incident;
(b) the categories of Customer Personal Data affected or reasonably believed to be affected;
(c) the approximate categories and number of affected individuals or records, if known;
(d) the likely consequences of the Security Incident, if known;
(e) the measures taken or proposed to address and mitigate the Security Incident, to the extent known; and
(f) a contact point for further information.
Provider may provide an initial notification with the information then reasonably available even if some details remain unknown.
8.3. Phased Notifications and Updates.
Provider may provide information in phases as it becomes available, where a complete investigation or assessment cannot reasonably be completed before initial notification.
Provider will provide material updates as reasonably available, including relevant information obtained from an affected Subprocessor. Provider is not required to provide information that is not reasonably available to Provider or that would compromise the security of its systems, another customer's information, or an ongoing investigation, provided that Provider will reasonably cooperate with Customer as described in this Section.
8.4. Cooperation.
Provider will take reasonable steps to investigate, contain, mitigate, and remediate a Security Incident within its control and will reasonably cooperate with Customer's investigation and legally required notification obligations, taking into account the nature of the Processing and information available to Provider.
8.5. Customer Notifications.
Customer remains responsible for determining whether notifications to Data Subjects, regulators, or other third parties are required, except where Applicable Privacy Laws impose a direct obligation on Provider.
8.6. No Admission.
Notification of a Security Incident does not constitute an admission of fault or liability.
8.7. Applicable Legal Requirements.
Provider will comply with legal notification obligations directly applicable to Provider. Nothing in this DPA establishes a separate universal seventy-two (72) hour notification deadline or expands a statutory notification obligation beyond its applicable scope. The notification obligation in Section 8.1 remains subject to any non-waivable requirements of Applicable Privacy Laws.
9. Regulatory and Customer Assistance
9.1. Reasonable Assistance.
Taking into account the nature of the Processing and information available to Provider, Provider will provide reasonable assistance to Customer with:
(a) security obligations relating to Customer Personal Data;
(b) Security Incident investigations and notifications;
(c) Data Subject requests;
(d) data protection impact assessments or equivalent risk assessments, where required by Applicable Privacy Laws; and
(e) reasonable regulatory inquiries relating to Provider's Processing of Customer Personal Data.
9.2. Limitations.
Provider's assistance is subject to reasonable confidentiality, security, operational, and resource limitations.
Provider is not required to disclose information relating to other customers or compromise the security of its systems.
9.3. Costs.
Unless otherwise required by law or expressly provided in the Agreement, Provider may charge reasonable fees for assistance that is materially beyond its ordinary obligations under this DPA.
10. Audits and Compliance Information
10.1. Information.
Upon reasonable written request, Provider will make available information reasonably necessary to demonstrate its compliance with this DPA.
Such information may include relevant security documentation, policies, descriptions of safeguards, and available third-party certifications or assessments.
10.2. Audits.
If the information provided under Section 10.1 is insufficient to demonstrate compliance with applicable data protection obligations, Customer may request a reasonable audit of Provider's relevant Processing activities.
10.3. Audit Conditions.
Any audit must:
(a) be requested at least thirty (30) days in advance;
(b) occur no more than once in any twelve-month period, except where required by Applicable Privacy Laws or following a Security Incident or credible evidence of material noncompliance;
(c) be conducted during normal business hours;
(d) be limited to systems and information relevant to Customer Personal Data;
(e) avoid unreasonable disruption to Provider's operations;
(f) protect Provider's confidential information and other customers' data; and
(g) be conducted by Customer or an independent auditor bound by appropriate confidentiality obligations.
10.4. Alternative Evidence.
Provider may satisfy reasonable audit requests by providing relevant documentation, questionnaires, third-party assessments, or other appropriate evidence where those materials reasonably address the subject of the request.
10.5. No Certification Requirement.
Nothing in this DPA requires Provider to obtain or maintain SOC 2, ISO 27001, or another particular certification.
11. Retention, Return, and Deletion
11.1. Customer-Initiated Deletion.
Customer may initiate account or workspace deletion through the applicable functionality made available in the Services.
Customer is encouraged to export Customer Personal Data before confirming deletion. Customer's failure to export data does not delay or condition the deletion process.
11.2. Active Application Systems.
Following a valid account or workspace deletion request, Provider initiates deletion of associated Customer Personal Data from its active application systems through its deletion workflow.
Different categories of data and systems may be subject to separate deletion mechanisms. Provider does not represent that all Customer Personal Data is deleted simultaneously when an account or workspace deletion is initiated.
11.3. Uploaded Attachments and Specific Derived Files.
Uploaded attachments stored in Cloudflare R2, together with specific derived attachment files covered by the applicable cleanup process, are subject to a separate background cleanup process.
Deletion requests are submitted asynchronously rather than directly during the account or workspace deletion request.
The cleanup process automatically retries failed deletion requests. However, the application does not currently maintain a definitive success or failure status for each individual deletion.
The R2 cleanup process covers uploaded attachments and specific derived attachment files. It does not necessarily cover every extracted text record, preview, thumbnail, AI projection, generated resource, or other derivative or copy maintained in a separate system or through a separate process. Such information may be subject to separate deletion mechanisms and retention practices.
Accordingly, Provider does not represent that every uploaded attachment or covered derived attachment file is deleted instantaneously or that the application can independently certify completion of each individual R2 deletion.
11.4. Other Generated and Synchronized Data.
Customer Personal Data maintained in other application systems, AI-related systems, integrations, or third-party services may be subject to separate deletion mechanisms, provider configurations, and retention practices.
Provider will manage such Processing and deletion in accordance with the Agreement, this DPA, applicable Subprocessor obligations, and Applicable Privacy Laws.
Deleting an original file or record does not necessarily delete a separately retained excerpt, generated resource, synchronized copy, or other independently maintained information. Such information remains subject to applicable authorization, confidentiality, retention, and deletion obligations.
11.5. AI Provider Retention.
Provider currently relies on the applicable configurations, retention policies, and contractual commitments of its AI Subprocessors for retention and deletion of data submitted to those providers.
The AI Addendum supplements this DPA and governs AI-specific Processing details to the extent consistent with this DPA and the Agreement. The AI Addendum does not override or reduce the protections or obligations in this DPA concerning Customer Personal Data. Where an AI-specific provision concerns Processing of Customer Personal Data and conflicts with this DPA, this DPA controls unless the Parties expressly agree otherwise in a written amendment that identifies the provision being modified and is permitted by Applicable Privacy Laws.
11.6. Database Backups.
Provider maintains production database backups that are performed before deployments and periodically. These backups are encrypted and access-restricted.
The backup process is not fully automated. Provider has not established a fixed backup-retention period or tested production database restoration from those backups as of the Effective Date. Provider does not promise a specific recovery time objective (RTO) or recovery point objective (RPO).
Provider may retain residual copies of Customer Personal Data in backups until those copies are overwritten, deleted, or otherwise removed through the applicable backup lifecycle. Such residual copies are not intended for ordinary use and remain subject to applicable confidentiality, security, and data protection obligations.
11.7. Object Storage.
Customer-uploaded attachments are stored in Cloudflare R2. Provider relies on the storage provider's durability and redundancy mechanisms and does not maintain an independent backup process for those files.
11.8. Records Retained for Business and Legal Purposes.
Notwithstanding account or workspace deletion, Provider may retain limited information where reasonably necessary for:
(a) billing and payment transaction records;
(b) invoices and tax and accounting records;
(c) security logs and audit trails;
(d) account registration and subscription history;
(e) legal compliance;
(f) enforcing the Agreement; and
(g) establishing, exercising, or defending legal claims.
Such records may be maintained through Provider's systems and third-party service providers, including Stripe, Metronome, and Better Stack, in accordance with applicable retention requirements, configurations, and contractual commitments.
Provider will limit retained information to what is reasonably necessary for the applicable purpose and will continue to protect retained Customer Personal Data in accordance with Applicable Privacy Laws.
11.9. Deletion by Subprocessors.
Provider's Subprocessors may maintain Customer Personal Data subject to their own technical deletion processes, retention configurations, backup practices, and contractual commitments.
Provider will impose appropriate contractual data protection and deletion obligations on its Subprocessors and will manage their Processing in accordance with this DPA and Applicable Privacy Laws.
Provider does not guarantee that every Subprocessor will immediately remove all residual copies from backups or other systems upon Customer's account or workspace deletion.
11.10. Legal Retention.
Provider may retain Customer Personal Data to the extent required by applicable law, provided that such information remains protected and is not Processed for other purposes except as permitted by law.
11.11. Deletion Confirmation.
Upon reasonable written request, Provider will provide confirmation of the deletion actions it has performed to the extent reasonably ascertainable from its systems and records. Provider is not required to certify deletion from systems for which it does not maintain definitive deletion-status information.
12. Sensitive and Regulated Information
12.1. Restricted Information.
The Services are not designed or intended to require the Processing of sensitive personal information or special-category Personal Data, including government identification numbers, health or medical information, biometric information, or information revealing racial or ethnic origin, religious beliefs, political opinions, or sexual orientation.
This restriction does not prohibit ordinary business contact information, account information, authentication information, payment transaction information, or other information intentionally collected through supported account, security, or payment functionality, where such Processing is otherwise permitted under the Agreement and Applicable Privacy Laws.
12.2. Customer Responsibility.
Customer must not intentionally submit restricted information described in Section 12.1 to the Services unless the Parties have entered into a separate written agreement expressly authorizing the relevant Processing.
12.3. Regulated Services.
The Services do not constitute a HIPAA business associate service, and this DPA does not constitute a Business Associate Agreement.
Provider does not agree to act as a payment-card processor under a separate regulated payment-card processing agreement through this DPA.
Any such arrangements require a separate written agreement.
13. Processing Locations and Data Residency
13.1. U.S. Infrastructure Regions.
Provider configures its infrastructure and Subprocessors to host and process Customer Personal Data in United States regions, where regional configuration is available.
The Subprocessor register identifies the listed processing locations for the relevant Subprocessors. This commitment is subject to the availability and configuration of regional Processing by the applicable infrastructure or Subprocessor service.
13.2. Personnel Access.
U.S. infrastructure-region configuration does not mean that every employee, contractor, support engineer, or technical operator of Provider or a Subprocessor is physically located in the United States.
Authorized personnel may potentially access Customer Personal Data remotely from other countries, subject to applicable security controls, access restrictions, and contractual commitments.
13.3. No Guarantee of Exclusive U.S. Personnel Access.
Provider does not represent that all personnel with authorized access to Customer Personal Data are located exclusively in the United States.
13.4. Changes.
Provider will update its Subprocessor register as appropriate when relevant Subprocessor Processing locations change and will provide notice of material changes in accordance with Section 6.
14. Term and Termination
14.1. Term.
This DPA remains effective for as long as Provider Processes Customer Personal Data on behalf of Customer under the Agreement.
14.2. Return and Deletion at Termination.
Before expiration or termination of the Agreement, Customer may use the self-service export functionality made available through the Services to obtain an export of Customer Personal Data and other Customer Content made available through that functionality. Customer acknowledges that the available export may not include every category of information, every underlying data structure, or every provider-side record, intermediate artifact, or operational record.
Expiration or termination of the Agreement constitutes a deletion trigger for purposes of this Section. A separate account or workspace deletion request is not required for Provider's obligations under this Section to apply.
Following expiration or termination, Provider will delete Customer Personal Data processed on behalf of Customer in accordance with Section 11 of this DPA, subject to applicable legal retention obligations, permitted residual records, backup limitations, and the other deletion qualifications set forth in this DPA. Customer Personal Data retained after termination remains subject to this DPA for as long as Provider retains or Processes it on Customer's behalf.
14.3. Continuing Obligations.
Sections concerning confidentiality, security, retention, deletion, liability, and other obligations that by their nature should survive will survive termination to the extent applicable. Customer Personal Data retained after termination remains subject to this DPA and Applicable Privacy Laws for as long as Provider retains or Processes it on Customer's behalf.
15. Relationship to Other Agreements
15.1. Agreement.
This DPA supplements and forms part of the Agreement.
15.2. Precedence.
In the event of a conflict among the Agreement and its incorporated documents:
(a) mandatory requirements of Applicable Privacy Laws control to the extent they cannot lawfully be varied by agreement;
(b) this DPA controls with respect to Provider's obligations as a processor, service provider, or contractor concerning Customer Personal Data;
(c) the AI Addendum supplements this DPA and governs AI-specific matters only to the extent that its provisions are consistent with this DPA and do not reduce the protections or obligations applicable to Customer Personal Data under this DPA;
(d) the Terms of Service control with respect to commercial terms, fees, payment obligations, intellectual property, indemnification, disclaimers, warranties, limitations of liability, remedies, and general contractual matters, subject to the express obligations in this DPA and any specific written amendment that expressly overrides an identified provision; and
(e) the Privacy Policy describes Provider's general privacy practices and individual privacy rights and does not independently amend this DPA, expand the rights granted under the Agreement, or reduce Provider's contractual obligations.
A separately signed Order Form or amendment controls over the Agreement only with respect to a specific provision that it expressly identifies as being overridden.
15.3. Liability.
Liability arising out of or relating to this DPA is subject to the limitations, exclusions, and liability caps set forth in the Terms of Service, except to the extent such limitations are prohibited by Applicable Privacy Laws.
Nothing in this DPA creates a separate or additional liability cap, a per-incident cap, or a right to stack or multiply liability caps. The applicable general or enhanced cap, as defined in the Terms of Service, will govern according to the claim and the terms of the Agreement.
16. General Provisions
16.1. Amendments.
Provider may update this DPA in accordance with the amendment provisions of the Agreement and Applicable Privacy Laws.
Material changes will be communicated through the Services, email, or another reasonable electronic notice method. Where the Agreement or Applicable Privacy Laws require affirmative acceptance or advance notice for a material change, Provider will follow those requirements.
16.2. Assignment.
Neither Party may assign this DPA except as permitted under the Agreement.
16.3. Severability.
If any provision of this DPA is held unenforceable, the remaining provisions will remain in effect.
16.4. No Third-Party Beneficiaries.
Except as expressly required by Applicable Privacy Laws, this DPA does not create third-party beneficiary rights.
16.5. Governing Law.
This DPA is governed by the laws specified in the Agreement, without regard to conflict-of-law principles, subject to any non-waivable requirements of Applicable Privacy Laws.
16.6. Notices.
Notices to Provider concerning this DPA may be sent to:
Countercyclical LLC
Email: privacy@countercyclical.io
Security-related reports may also be sent to:
Email: security@countercyclical.io
16.7. Entire Agreement.
This DPA, together with the Agreement and any applicable AI Addendum, constitutes the agreement between the Parties concerning Provider's Processing of Customer Personal Data on behalf of Customer. It supersedes prior data processing terms between the Parties concerning the same subject matter, except for any separately signed data processing agreement or amendment that expressly replaces or modifies this DPA.
SCHEDULE 1
DETAILS OF PROCESSING
1. Subject Matter
The Processing of Personal Data in connection with Countercyclical's investment research, market intelligence, due diligence, workflow management, collaboration, analytics, and related software services.
2. Duration
Processing will continue for the duration of the Agreement and any applicable post-termination period during which Provider retains Customer Personal Data in accordance with the Agreement, this DPA, applicable law, and applicable retention practices.
3. Nature and Purpose of Processing
Processing may include:
Collection, receipt, and storage of Customer Personal Data.
Account registration, authentication, and access management.
Workspace and organization management.
Research, market intelligence, and due diligence workflows.
Uploading, storing, retrieving, and processing documents and attachments.
Search, indexing, extraction, and organization of information.
AI-assisted Processing, including prompts, instructions, conversation histories, and generated outputs, where enabled or authorized by Customer.
Customer-authorized integrations and synchronization of third-party information.
Notifications, communications, and collaboration.
Usage metering and service administration.
Security monitoring, logging, troubleshooting, and abuse prevention.
Customer support and technical maintenance.
Deletion, retention, and backup operations.
Compliance with applicable legal obligations.
4. Categories of Data Subjects
Depending on Customer's use of the Services, Data Subjects may include:
Customer employees and personnel.
Customer contractors and authorized users.
Customer representatives and administrators.
Investment professionals and financial industry participants.
Company executives and officers.
Business contacts and counterparties.
Individuals identified in Customer-uploaded documents or research materials.
Individuals whose contact information is imported through Customer-authorized integrations.
Other individuals whose Personal Data Customer submits to or makes available through the Services.
5. Categories of Personal Data
Depending on Customer's use of the Services, Personal Data may include:
Names and business contact information.
Email addresses and telephone numbers.
Professional titles, roles, and organizational affiliations.
Account identifiers, user identifiers, and workspace identifiers.
Authentication and access-related information.
Activity records, audit events, and usage information.
Communications and collaboration records.
Personal Data contained in uploaded files, attachments, documents, and research materials.
Personal Data contained in prompts, instructions, AI conversation histories, and AI-generated outputs.
Personal Data imported through Customer-authorized integrations, including contact records.
Technical identifiers, device information, IP addresses, and related operational information.
Other Personal Data Customer chooses to submit to the Services.
6. Sensitive Personal Data
The Services are not designed or intended to require the Processing of sensitive personal information or special-category Personal Data.
Such information is excluded unless separately authorized through a written agreement between the Parties.
7. Frequency of Processing
Processing may occur continuously or periodically throughout Customer's use of the Services, depending on Customer activity, configurations, integrations, and enabled functionality.
8. Processing Locations
Provider configures its infrastructure and Subprocessors to host and process Customer Personal Data in United States regions, where regional configuration is available. Authorized personnel of Provider or Subprocessors may access Customer Personal Data remotely from other countries, subject to Section 13 of this DPA.
SCHEDULE 2
TECHNICAL AND ORGANIZATIONAL SECURITY MEASURES
Provider maintains the following security measures as of the Effective Date.
These measures describe Provider's current practices and are not a representation that Provider maintains a particular certification, formal security framework, or enterprise security program.
1. Access Control and Authentication
Provider restricts administrative access to production infrastructure and Customer Personal Data to authorized personnel.
As of the Effective Date:
Provider has a single individual with administrative access to production infrastructure and Customer Personal Data.
Multi-factor authentication is required for production administrative access.
Access is limited according to operational requirements.
Provider uses authentication and authorization controls within the Services and supporting infrastructure.
2. Encryption and Data Protection
Provider uses encryption designed to protect Customer Personal Data:
In transit across relevant connections, including through TLS/HTTPS connections where applicable.
At rest in relevant systems storing Customer Personal Data, including production database, object-storage, logging, and backup systems.
In production database backups.
Production database backups are access-restricted to authorized personnel.
3. Application and Infrastructure Security
Provider uses application and infrastructure security measures appropriate to the Services, which may include:
Authentication and authorization controls.
Access restrictions.
Application security controls.
Infrastructure configuration controls.
Secrets management.
Network and platform security capabilities provided by infrastructure providers.
Security capabilities made available through relevant Subprocessors.
4. Logging and Monitoring
Provider maintains centralized application and infrastructure logging and monitoring designed to support:
Detection of application errors.
Monitoring of system and service health.
Identification of unusual activity.
Troubleshooting and operational investigation.
Identification and investigation of potential security incidents.
5. Incident Reporting and Security Communications
Provider maintains a Responsible Disclosure program and accepts security-related communications at:
Provider does not currently represent that it maintains a formally documented incident-response plan or a certified incident-response framework.
Provider will nevertheless investigate, contain, mitigate, and notify Customer of qualifying Security Incidents in accordance with the DPA and Applicable Privacy Laws. Initial notification may be based on information reasonably available at the time, with additional information provided as it becomes available under Section 8.
6. Backup and Recovery
Provider performs production database backups before deployments and periodically.
Current backup practices include:
Backups are not fully automated.
Production database backups are encrypted.
Access to backups is restricted to authorized personnel.
No fixed backup-retention period has been established.
Restoration of production database backups has not been tested as of the Effective Date.
No specific recovery time objective (RTO) or recovery point objective (RPO) is promised.
For customer-uploaded attachments and other applicable object-storage data, Provider relies on Cloudflare R2's durability and redundancy mechanisms rather than maintaining an independent backup process.
7. File Deletion Controls
Customer-uploaded attachments stored in Cloudflare R2 are subject to a separate background cleanup process following account or workspace deletion.
The cleanup process:
Submits deletion requests asynchronously.
Automatically retries failed deletion requests.
Covers uploaded attachments and specific derived attachment files.
Does not currently maintain definitive success or failure status for each individual deletion.
The R2 cleanup process does not necessarily cover all extracted text, previews, thumbnails, AI projections, generated resources, or other separately maintained records. Those records may be subject to separate deletion mechanisms and retention practices.
8. Personnel Confidentiality
Persons authorized to access Customer Personal Data are subject to appropriate confidentiality obligations.
Provider restricts access to Customer Personal Data according to operational necessity.
9. Subprocessor Security
Provider evaluates Subprocessors primarily by reviewing their:
Published security documentation.
Available security certifications and assessments.
Contractual security and data protection commitments.
Published information concerning their security practices.
Provider does not currently represent that it performs formal recurring audits of every Subprocessor.
10. Security Review and Maintenance
Provider reviews and maintains its application and infrastructure security practices as reasonably necessary for the operation and protection of the Services.
Provider may update its technical and organizational measures over time, provided that such updates do not materially reduce the overall level of protection afforded to Customer Personal Data.
SCHEDULE 3
AUTHORIZED SUBPROCESSORS AND CUSTOMER CONTENT RECIPIENTS
1. Authoritative Provider Register
Provider maintains its current register of Subprocessors and other third-party providers authorized to receive Customer Content at:
The register is publicly accessible and identifies Provider's current Subprocessors and other authorized Customer Content recipients, together with their relevant services, roles, and listed processing locations.
The public register is the definitive and authoritative record of both categories of providers. No separate static provider list in this Schedule is intended to supplement, replace, or contradict the register.
2. Scope of the Register
The register identifies:
(a) third parties engaged by Provider to Process Customer Personal Data on Provider's behalf in connection with the Services; and
(b) other third-party providers engaged by Provider and authorized to receive Customer Content in connection with the Services, including where the relevant Customer Content does not contain Customer Personal Data.
The register identifies the relevant role, service or purpose, and listed processing locations for each provider. Inclusion as an authorized Customer Content recipient does not, by itself, make a provider a Subprocessor under this DPA.
A third party's involvement in Provider's general business operations, marketing, website, or other independent business activities does not by itself authorize that third party to receive Customer Content. Likewise, a third-party service selected or connected independently by Customer is not a Provider Subprocessor or authorized Customer Content recipient solely because Customer uses it with the Services.
3. Register Updates and Notice
Provider will update the register as appropriate when Subprocessors or other authorized Customer Content recipients are added, removed, or materially changed.
Provider will provide at least fifteen (15) days' advance notice before authorizing a new Subprocessor to Process Customer Personal Data, authorizing a new third-party provider to receive Customer Content, or materially changing an existing provider's relevant Processing activities or authorized access to Customer Content, subject to the urgent-engagement exception in Section 6.4 of the DPA.
Customer may object within ten (10) days after receiving notice, in accordance with Section 6.5 of the DPA.
4. Processing Locations
The register identifies the listed processing locations for the relevant Subprocessors. Provider configures its infrastructure and Subprocessors to host and process Customer Personal Data in United States regions, where regional configuration is available.
The listed infrastructure regions do not represent that every authorized person with access to Customer Personal Data is physically located in the United States. Remote personnel access may occur from other countries as described in Section 13.
5. Existing Providers
The Subprocessors and other authorized Customer Content recipients identified in the public register as of the Effective Date are authorized for the roles and activities identified in the register, subject to this DPA and the Agreement. The register, together with the notice and objection procedure in Section 6, governs subsequent additions, removals, and material changes.

