EBM Transfer Impact Assessment (TIA)
Date: February 2026
1. Introduction and Purpose
EBM Software, LLC (“EBM”) publishes this Transfer Impact Assessment (TIA) to assist current and prospective customers — particularly those subject to the EU General Data Protection Regulation (GDPR), UK GDPR, or Swiss Federal Act on Data Protection (FADP) — in discharging their own TIA obligations when transferring personal data to EBM.
Under the Schrems II ruling (Data Protection Commissioner v. Facebook Ireland Limited, Maximillian Schrems, Case C-311/18), data exporters must assess whether the law and practice of the destination country ensures an adequate level of protection for transferred personal data before relying on Standard Contractual Clauses (SCCs) or other Article 46 GDPR transfer mechanisms.
This document represents EBM’s own assessment of the relevant legal framework of the United States, combined with specific information about our technical, organizational, and contractual safeguards. It is intended as a reference document that customers may use as a starting point or supplement for their own assessments. Customers remain responsible for conducting their own TIA based on their specific circumstances and the nature of data transferred.
2. Nature of the Data Transfer
2.1 Categories of Personal Data
Depending on how customers use the “Compass”, “Catalyst”, and “Ontario” platforms (“Platforms”) , the following categories of personal data may be transferred to EBM :
- Identification and contact data: names, job titles, business contact information of the customer’s employees or contractors.
- User account credentials: usernames and authentication data for authorized platform users.
- Business and financial data relating to individuals: payroll or compensation data, customer order or payment details, vendor contact information contained in financial records.
- Any other personal data that the customer chooses to input into the Ontario platform or provides as part of professional services.
2.2 Categories of Data Subjects
Data subjects whose personal data may be processed include:
- Customer’s employees, staff, and contractors.
- Customer’s own end-customers (where customer-related financial transactions or records contain personal identifiers).
- Customer’s business contacts, partners, or vendors.
2.3 Purposes of Processing
Personal data is processed exclusively for the following purposes:
- Providing the SaaS Platforms and their functionalities (data ingestion, transformation, analytics, and reporting).
- Delivering agreed professional services, such as data analysis support or fractional finance team support.
- Supporting platform operations including security monitoring, incident response, and system maintenance.
2.4 Frequency and Duration
Transfers occur on a continuous, on-demand basis for the duration of the Master Subscription and Services Agreement (MSSA) between EBM Software, LLC and the customer. Personal data is retained only for the duration of the MSSA and deleted or returned upon termination, subject to a maximum 12-month archival backup retention period.
2.5 Sub-Processors
EBM Software, LLC uses the following principal sub-processors in connection with the Platform. All sub-processors are subject to data processing agreements, security requirements, and obligations equivalent to those imposed on EBM under its customer contracts and the applicable SCCs:
| Sub-Processor | Role | Location |
|---|---|---|
| Microsoft Azure | Cloud hosting, infrastructure, data storage, analytics (Azure Data Lake, Azure DevOps, Entra ID, Defender) | United States (US East Region) |
| Amazon Web Services (AWS) | Supplementary cloud services | United States |
| Zendesk | Customer support ticketing | United States |
3. Legal and Regulatory Framework of the United States
This section assesses the US legal environment relevant to government access to personal data held by private companies, as required by the Schrems II framework and guidance from the European Data Protection Board (EDPB Recommendations 01/2020).
3.1 Key US Legal Instruments Relevant to Government Access
Foreign Intelligence Surveillance Act (FISA), Section 702
FISA § 702 authorizes the US government to conduct targeted surveillance of non-US persons located outside the United States, for the purpose of acquiring foreign intelligence information. Importantly:
- Section 702 collection targets specific foreign intelligence targets, not bulk collection of all data held by US companies.
- Section 702 requires prior approval by the Foreign Intelligence Surveillance Court (FISC), an independent judicial body.
- US companies are legally prohibited from disclosing whether they have received FISA orders, which limits transparency.
- The EU-US Data Privacy Framework (DPF) Adequacy Decision (adopted July 2023) and its implementing Executive Order 14086 introduced enhanced safeguards, including the Data Protection Review Court (DPRC) — a new redress mechanism for EU data subjects.
Executive Order 12333
EO 12333 authorizes broad-based foreign intelligence collection by US intelligence agencies outside the United States. Unlike FISA § 702, it operates with fewer judicial oversight mechanisms. However, Executive Order 14086 (signed October 2022) imposed proportionality and necessity requirements on signals intelligence activities conducted under EO 12333, bringing US practice closer to the EU standard.
Electronic Communications Privacy Act (ECPA) / Stored Communications Act (SCA)
The SCA governs law enforcement access to stored electronic communications. Law enforcement must obtain a court-issued warrant, subpoena, or court order to compel disclosure of customer data, depending on the type and age of the data. The warrant standard (requiring probable cause and judicial authorization) applies to the content of electronic communications.
USA PATRIOT Act / National Security Letters (NSLs)
NSLs are administrative subpoenas issued by the FBI without prior judicial approval, but they are subject to judicial review and are limited to subscriber and transactional metadata (not the content of communications). NSL recipients may seek judicial review to challenge the validity of the letter or any associated gag order.
3.2 Practical Limitations on US Government Access
Based on publicly available information and EBM ‘s own assessment of its business and operations, the following practical factors reduce the likelihood and scope of US government access to customer personal data processed by EBM :
- EBM is SaaS company providing financial analytics services. Its operations do not bring it within the typical profile of entities targeted by national security surveillance programs, which tend to focus on providers of electronic communications services with large consumer bases.
- The types of personal data processed (business financial data, employee contact information, payroll data) are predominantly commercial in nature and are not typical targets of foreign intelligence collection.
- EBM has never received a national security request, FISA order, NSL, or any government request for access to customer personal data as of the date of this assessment.
- FISA § 702 orders are targeted at specific foreign intelligence targets; they are not instruments for bulk collection of commercial business data.
- US law enforcement requests for content data require a warrant based on probable cause, subject to judicial oversight.
3.3 The EU-US Data Privacy Framework
The European Commission adopted an adequacy decision in respect of the EU-US Data Privacy Framework (DPF) on 10 July 2023. While EBM currently relies on SCCs as its primary transfer mechanism, the DPF demonstrates that the US government has taken concrete steps to enhance oversight and redress mechanisms for EU data subjects, including:
- Proportionality and necessity requirements for signals intelligence under Executive Order 14086.
- The Data Protection Review Court (DPRC), a new independent redress body allowing EU data subjects to complain about US signals intelligence activities.
- Oversight by the Privacy and Civil Liberties Oversight Board (PCLOB).
These reforms are directly relevant to any TIA assessment of the US legal framework, as they represent significant improvements to the protection of transferred data.
4. Safeguards Implemented by EBM
EBM has implemented the following technical, organizational, and contractual measures to ensure an equivalent level of protection for personal data transferred from the EEA, UK, or Switzerland, consistent with the requirements of the SCCs and EDPB guidance.
4.1 Technical Measures
| Measure | Description |
|---|---|
| Encryption in Transit | All data transmitted between the customer and the Ontario platform is protected using HTTPS and SFTP with TLS encryption. VPN connections are used for administrative access. |
| Encryption at Rest | Customer data stored in Azure Data Lake Storage and MS SQL databases is encrypted at rest using Azure-managed encryption keys. |
| Access Controls | Role-based access control (RBAC) is enforced via Microsoft Entra ID. Access to production systems is restricted to authorized personnel based on the principle of least privilege. |
| Logical Network Isolation | EBM uses Azure's Virtual Private Cloud (VPC) environment to isolate production infrastructure, with ingress permitted only via secure HTTPS, SFTP, and VPN endpoints. |
| Intrusion Detection | Intrusion detection systems and Azure Monitor are used to identify and alert on potential security incidents. Azure Defender provides cloud security monitoring. |
| Vulnerability Management | Regular vulnerability scans and periodic penetration testing are conducted over the production environment. |
| Logging and Monitoring | System activity logs are maintained via Azure Monitor Log Analytics workspaces. Access to log sinks is restricted. |
| Backup and Recovery | Backup infrastructure is maintained in Azure US East Region. Data backups are retained for up to 12 months following contract termination, in a secure, isolated environment. |
4.2 Organizational Measures
- Dedicated security leadership: EBM maintains a CISO and a DPO responsible for the overall direction of information security and data protection compliance.
- Information security program: EBM maintains a formal information security program aligned with SOC 2 Trust Services Criteria (Security) and ISO 27001:2022 certification.
- Employee training: All personnel with access to personal data are subject to security awareness training and are bound by confidentiality obligations.
- Background screening: Personnel are subject to pre-employment screening as part of the hiring process.
- Incident response: EBM maintains a formal incident response program with defined procedures for identifying, containing, and notifying affected customers of personal data breaches within 72 hours (or as soon as reasonably practicable).
- Vendor management: All third-party sub-processors and vendors (including Azure, AWS, Zendesk, and others) are subject to formal vendor risk assessment and contractual data protection requirements.
- Risk assessment: Annual and event-driven risk assessments are conducted to identify and address evolving threats to the confidentiality, integrity, and availability of personal data.
4.3 Contractual Measures
- EU Standard Contractual Clauses (Module Two: Controller-to-Processor) are incorporated into EBM ‘s Data Processing Agreement (DPA), which forms an annex to the Master Subscription and Services Agreement (MSSA).
- UK International Data Transfer Addendum (ICO IDTA, Version B1.0, effective 21 March 2022) is incorporated into the DPA for transfers of UK personal data.
- The DPA expressly obligates EBM to: (a) process personal data only on documented customer instructions; (b) implement and maintain appropriate technical and organizational measures (TOMs); (c) assist customers with data subject rights requests, DPIAs, and regulatory compliance; (d) notify customers of personal data breaches; (e) notify customers of government access requests to the extent legally permissible; and (f) resist unjustified government requests and seek judicial review or protective orders where possible.
- Sub-processor agreements impose equivalent data protection obligations on all sub-processors.
- EBM ‘s DPA expressly provides that if a government, law enforcement, or other authority demands access to personal data, EBM will (to the extent legally permitted) promptly notify the customer, cooperate with the customer’s efforts to intervene or object, and will not provide data unless legally compelled. If compelled, only the minimum necessary data will be disclosed, and the customer will be notified after the fact if prior notice is prohibited.
5. Risk Assessment and Conclusion
5.1 Assessment of Risk
Based on the analysis above, EBM concludes that the risk of US government access to personal data transferred by EEA or UK data exporters is low, for the following reasons:
- EBM has never received a national security request, FISA order, NSL, or any other government request for access to customer personal data as of the date of this assessment.
- The nature of EBM ‘s services (financial analytics SaaS for business customers) and the types of personal data processed (commercial financial and employee data) do not bring it within the typical profile of targets for US national security surveillance.
- US surveillance authorities (FISA § 702, NSLs) are targeted instruments that require specific predication; they do not authorize bulk collection of commercial business data.
- The EU-US Data Privacy Framework and Executive Order 14086 have introduced enhanced proportionality, necessity, and redress requirements governing US intelligence activities that are relevant to improving protection for transferred data.
- Robust technical safeguards (encryption at rest and in transit, RBAC, network isolation, intrusion detection) significantly reduce the risk of unauthorized access.
- Contractual safeguards, including the SCCs and the DPA’s government-access resistance clause, ensure that EBM is obligated to notify customers and challenge unjustified government requests.
6. Government Access Request Transparency
| National Security Letters (NSLs) received | 0 (to the extent disclosure is legally permissible) |
| FISA § 702 orders received | 0 (to the extent disclosure is legally permissible) |
| Other government access requests received | 0 (to the extent disclosure is legally permissible) |
| Data disclosed to any government authority | None |
| Period covered by this statement | From the inception of EBM through the date of this assessment (February 2026) |
EBM commits to updating this transparency statement on at least an annual basis and upon any material change in the above information, to the extent permitted by law.
7. Review and Updates
EBM will review and update this TIA:
- At least annually, or more frequently if required by changes in law, regulatory guidance, or EBM ‘s processing activities.
- Upon any new government access request being received.
- Upon any significant change to EBM’s sub-processor arrangements or technical infrastructure.
- Upon any material CJEU or UK court ruling affecting the validity of SCCs or other transfer mechanisms.
The current version of this TIA will always be made available on EBM ‘s website. Customers who require notification of material updates should contact EBM ‘s Data Protection Officer.
8. Contact Information
For questions about this Transfer Impact Assessment or EBM’s data protection practices, please contact us at CISO@xerxes.global.
9. Disclaimer
This Transfer Impact Assessment is published by EBM Software, LLC for information purposes only. It does not constitute legal advice. Customers should seek independent legal advice regarding their obligations under applicable data protection law and the adequacy of safeguards for their specific transfer circumstances.
Nothing in this document shall be construed as a representation that all regulatory requirements applicable to any specific customer or data transfer are satisfied. Customers remain solely responsible for their own compliance with the GDPR, UK GDPR, and any other applicable data protection laws.

