UK Data Protection Addendum
Breachday LLC · breachday.io
Version 1.0 · Effective Date: October 16, 2026
Version 1.0 (effective October 16, 2026) is superseded byVersion 1.1, effective October 16, 2026.
Key terms
This UK DPA replaces the standard Breachday DPA for any Customer that accepts the Breachday UK Customer Supplement or signs this document. It governs Breachday's Processing of Customer Personal Data that is subject to UK GDPR.
| Item | Details |
|---|---|
| Provider | Breachday LLC, a Colorado limited liability company · 24411 E Mexico Ave, Aurora CO 80018, United States · compliance@breachday.io |
| Customer | As named in the Order Form or the execution block |
| Agreement | Breachday Terms of Service (breachday.io/terms) as supplemented by the Breachday UK Customer Supplement, and any Order Form |
| Version | UK Version 1.0 · Effective October 16, 2026 |
| Subprocessor List | breachday.io/subprocessors · 30 days' advance notice of new Subprocessors |
| Security Incident notice | compliance@breachday.io · within 48 hours after Breachday becomes aware of a Security Incident |
| Governing law | The law governing the Agreement, except Schedule 3 (UK transfer terms), which is governed by the laws of England and Wales |
Adapted from Bonterms DPA Version 1.0 (CC BY 4.0). Bonterms does not provide legal advice.
1. Definitions
1.1 "Agreement" means the Breachday Terms of Service as supplemented by the Breachday UK Customer Supplement, and any applicable Order Form, MSP Agreement or other written agreement governing the Service.
1.2 "UK GDPR" has the meaning in section 3(10) of the Data Protection Act 2018, as amended. "UK Data Protection Law" means the UK GDPR, the Data Protection Act 2018 and other UK law applicable to the Processing of Customer Personal Data under the Agreement, each as amended or replaced.
1.3 "Controller", "Processor", "Data Subject", "Personal Data" and "Processing" have the meanings in UK Data Protection Law.
1.4 "Customer Data" has the meaning in the Agreement and includes data, content and materials submitted to or generated within the Service by Customer or its users. "Customer Personal Data" means Personal Data contained in Customer Data that Breachday Processes on behalf of Customer under this UK DPA.
1.5 "Customer Instructions" means the documented instructions in the Agreement, this UK DPA, Customer's authorized use and configuration of the Service, and other reasonable written instructions consistent with the Agreement. They include Processing reasonably necessary to provide, host, secure, support, administer and maintain the Service; generate reports and exports; maintain backups; prevent fraud and abuse; enforce usage limits and MSP licensing; and comply with legal obligations.
1.6 "Restricted Transfer" means a transfer of Customer Personal Data outside the United Kingdom that is restricted under Chapter V of the UK GDPR.
1.7 "Security Incident" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data Processed by Breachday. Unsuccessful attempts that do not result in unauthorized access to Customer Personal Data, such as failed logins, scans or blocked attacks, are not Security Incidents.
1.8 "Service" means the Breachday tabletop exercise platform at app.breachday.io and associated features, APIs, exports and System Templates.
1.9 "Subprocessor" means a third party engaged by Breachday to Process Customer Personal Data on Breachday's behalf in connection with the Service. "Subprocessor List" means the current list at breachday.io/subprocessors.
1.10 "Client" means a third-party organization on whose behalf Customer is authorized to use the Service under an MSP Agreement. "MSP Agreement" means a separate written agreement permitting Customer to use the Service for Clients.
1.11 "DPA Effective Date" means the date Customer accepts the Agreement or signs this UK DPA, whichever is first.
1.12 Other capitalized terms, such as Order Form, Organization, Exercise Participant, Subscription, Confidential Information and Sensitive Personal Data, have the meanings in the Terms of Service.
2. Roles, scope and duration
2.1 Roles. (a) Where Customer uses the Service for its own organization, Customer is Controller and Breachday is Processor. (b) Where Customer uses the Service for a Client under an MSP Agreement, the Client is Controller, Customer is a Processor acting for the Client, and Breachday is Customer's Subprocessor. Customer confirms it has the Client's authorization to engage Breachday and the Subprocessors, and is responsible for passing Client instructions to Breachday, handling Client requests, and notifying the Client of Security Incidents reported by Breachday. (c) This UK DPA does not govern Personal Data that Breachday Processes as an independent Controller for its own account administration, billing, security logging, fraud prevention, legal compliance or corporate operations, as described in the Privacy Policy and the UK Customer Supplement.
2.2 Scope. This UK DPA applies to Breachday's Processing of Customer Personal Data on behalf of Customer to the extent UK Data Protection Law applies.
2.3 Duration. This UK DPA begins on the DPA Effective Date and continues until Breachday has ceased Processing Customer Personal Data on Customer's behalf, subject to Section 7 and lawful retention.
2.4 Order of precedence. If there is a conflict: (1) Schedule 3 (UK transfer terms) prevails; then (2) this UK DPA for Processing of Customer Personal Data; then (3) an executed Order Form or MSP Agreement for matters it expressly addresses; then (4) the UK Customer Supplement and the Terms of Service.
3. Processing of Customer Personal Data
3.1 Customer Instructions. Breachday will Process Customer Personal Data only on Customer's documented instructions, including those in Section 1.5, unless UK law requires otherwise. If UK law requires other Processing, Breachday will tell Customer before the Processing unless the law prohibits it. Breachday will promptly tell Customer if it considers that an instruction infringes UK Data Protection Law.
3.2 Details of Processing. The subject matter, nature, purpose and duration of Processing, the types of Customer Personal Data and the categories of Data Subjects are in Schedule 1.
3.3 Confidentiality. Breachday will limit access to Customer Personal Data to personnel and authorized Subprocessors that need it to perform the Agreement. Everyone authorized to Process Customer Personal Data is bound by confidentiality obligations. Breachday will protect Customer Personal Data as Confidential Information under the Agreement.
3.4 AI processing and no model training. Breachday will not use Customer Data to train or fine-tune Breachday or third-party AI models. When Customer's users use the AI Scenario Builder, prompt and response content is transmitted through OpenRouter for inference. Breachday configures routing to require Zero Data Retention (ZDR) eligible provider endpoints and to deny provider data collection where supported. Under OpenRouter's ZDR controls, eligible inference providers do not persist prompt or response content after processing. ZDR does not prevent transient Processing and does not prevent OpenRouter from retaining non-content request metadata under its own policies. Customer must not intentionally include Sensitive Personal Data or real credentials in AI prompts unless Breachday has expressly approved that Processing in writing.
3.5 Compliance with law. Each party will comply with UK Data Protection Law as it applies to that party's own Processing. Customer is responsible for having a lawful basis for the Processing it instructs, and for giving Data Subjects, including Exercise Participants, the transparency information UK Data Protection Law requires.
4. Subprocessors
4.1 Authorization. Customer generally authorizes Breachday to engage the Subprocessors on the Subprocessor List for the services described there. Where Customer acts for a Client, Customer gives this authorization on the Client's behalf. The current Subprocessors are:
| Subprocessor | Legal entity | Processing | Location | UK transfer terms |
|---|---|---|---|---|
| Supabase | Supabase Pte. Ltd. | Database, authentication, realtime features, object storage | United States project region as configured; contracting entity in Singapore, with supporting and operational processing as described in Supabase's terms | Supabase DPA: EU Standard Contractual Clauses with the UK Addendum |
| Vercel | Vercel Inc. | Application hosting and serverless compute | Primary U.S. deployment; distributed network and edge infrastructure may vary | Vercel DPA, applicable to the Pro plan: EU Standard Contractual Clauses with the UK Addendum |
| Cloudflare | Cloudflare, Inc. | Encrypted disaster-recovery backup storage (R2) | United States storage configuration; distributed network infrastructure | Cloudflare Customer DPA: UK Addendum where contractual transfer safeguards apply |
| Stripe | Stripe, LLC | Payment processing and subscription management | United States and other locations under Stripe's global infrastructure | Stripe DPA and Data Transfers Addendum, including the UK Addendum where required under those terms |
| Resend | Plus Five Five, Inc. (Resend) | Transactional email delivery | United States storage and sending configuration; supporting infrastructure may vary | Resend DPA: EU Standard Contractual Clauses with the UK Addendum |
| OpenRouter | OpenRouter, Inc. | AI model routing (AI Scenario Builder) | Varies by ZDR-eligible inference endpoint unless region-restricted | OpenRouter DPA, Section 13.3: UK Addendum |
4.2 Flow-down. Breachday will enter into a written contract with each Subprocessor that imposes the same data protection obligations as this UK DPA, as UK GDPR Article 28(4) requires, and remains responsible to Customer for each Subprocessor's performance.
4.3 Notice of new Subprocessors. Breachday will update the Subprocessor List and give at least 30 days' advance notice before a new Subprocessor begins Processing Customer Personal Data, ordinarily by in-Service notice or email. If an emergency replacement or new provider is reasonably necessary to maintain security, legal compliance or Service continuity and 30 days' notice is not practicable, Breachday will give notice as soon as reasonably practicable.
4.4 Objection. Customer may reasonably object to a new Subprocessor on documented data-protection grounds within 30 days after notice. The parties will work in good faith to resolve the objection. If they cannot, Customer may terminate the affected Service as its sole remedy for the objection and receive a pro-rata refund of prepaid, unused fees for that Service.
5. Security and Security Incidents
5.1 Security measures. Breachday will maintain technical and organizational measures designed to protect Customer Personal Data appropriately to the risk, as UK GDPR Article 32 requires. Schedule 2 describes the current measures. Breachday may update implementations over time but will not materially reduce the overall security of the Service during an active Subscription.
5.2 Security Incident notice. Breachday will use reasonable efforts to detect, investigate, contain and mitigate Security Incidents. Breachday will notify Customer without undue delay, and no later than 48 hours, after becoming aware of a Security Incident affecting Customer Personal Data. The notice will include, to the extent then known: the nature of the incident, the categories and approximate numbers of Data Subjects and records affected, likely consequences, measures taken or proposed, and a contact for follow-up. Breachday may provide this information in phases as the investigation develops. A notice is not an admission of fault or liability.
5.3 Regulatory notifications. Customer, as Controller, is responsible for any notice to the Information Commissioner, to Data Subjects, to Clients or to others that UK Data Protection Law requires of it. Breachday will give reasonable assistance under Section 6.
5.4 Customer responsibilities. Customer is responsible for evaluating whether the Service meets its legal and security requirements; configuring roles and access appropriately; enabling available security features suited to its risk; protecting room codes and credentials; and avoiding submission of prohibited Sensitive Personal Data.
6. Data Subject requests and assistance
6.1 Requests received by Breachday. If a Data Subject contacts Breachday about Customer Personal Data, Breachday will, where legally permitted, direct the request to Customer or notify Customer. Breachday will not respond on Customer's behalf except as required by law.
6.2 Assisting with Data Subject rights. On Customer's request, Breachday will give reasonable assistance, through appropriate technical and organizational measures and taking into account the nature of the Processing, to help Customer respond to requests to exercise Data Subject rights under UK Data Protection Law.
6.3 Assisting with Customer's other obligations. Taking into account the nature of the Processing and the information available to Breachday, Breachday will give reasonable assistance with Customer's obligations under UK GDPR Articles 32 to 36: security, notification of Security Incidents, data protection impact assessments, and prior consultation with the Information Commissioner. Breachday may charge reasonable costs for unusually burdensome assistance that UK Data Protection Law does not require it to provide free.
6.4 Cooperation with the regulator. Breachday will cooperate with the Information Commissioner on request, as UK GDPR Article 31 requires.
7. Return and deletion of data
7.1 During the Subscription. Customer may access, export and delete Customer Data through available Service features. Supported export formats may include PDF, DOCX and JSON.
7.2 At the end of the services. When the Services end, Customer may choose by written notice either the return (export) or the deletion of Customer Personal Data. Unless an Order Form, MSP Agreement or Enterprise agreement says otherwise, expiry of a paid Subscription starts a six-month read-only retention period during which Customer Data remains available for export. Breachday sends deletion reminders at 30 and 5 days before scheduled deletion. At the end of that period, or earlier if Customer asks for deletion, Breachday deletes Customer Personal Data from active systems unless Customer renews.
7.3 Backups and legal retention. Customer Personal Data deleted from active systems may remain in encrypted disaster-recovery backups for up to 7 days and is then deleted through rolling expiry. Backups are used only for disaster recovery. If a backup is restored, Breachday re-applies recorded deletion requests. Breachday may keep limited Customer Personal Data where UK law requires it, only for that purpose and subject to continuing confidentiality and security obligations.
7.4 Confirmation. On reasonable written request after deletion is complete, Breachday will confirm deletion in writing, subject to backup expiry and lawful retention.
7.5 Ephemeral sessions. Eligible Organizations may enable an ephemeral-session feature that deletes specified Exercise Session data after a configured period, with a default of 48 hours where the feature is enabled. Breachday may keep limited security, billing and operational logs separately from ephemeral-session content, as the Privacy Policy describes.
8. Audits and information
8.1 Records and information. Breachday will keep the records of Processing that UK Data Protection Law requires of processors and will make available the information necessary to demonstrate compliance with this UK DPA on written request, subject to confidentiality and security restrictions.
8.2 Independent reports. Breachday may first answer reasonable audit inquiries with current security documentation, summaries of completed third-party assessments or independent reports, under confidentiality. Breachday has not completed a SOC 2 examination as of the effective date of this UK DPA and does not represent that it holds a SOC 2 report.
8.3 Customer audits. Customer may audit Breachday's compliance with this UK DPA, at its own expense, within a reasonable scope. Unless the Information Commissioner or a Security Incident reasonably requires otherwise, an audit must: (i) occur no more than once per calendar year; (ii) be carried out by Customer or an independent auditor bound by confidentiality; (iii) take place at a mutually agreed time in business hours on reasonable notice; (iv) avoid unreasonable disruption to Breachday or the Service; (v) not access another customer's data, credentials, source code, vulnerability details, or information that would compromise security; and (vi) treat findings as Confidential Information. Breachday may charge reasonable costs for unusually burdensome audit support that UK Data Protection Law does not require it to provide free.
9. International transfers
9.1 Hosting location. The Service is hosted in the United States. Customer acknowledges that Customer Personal Data will be transferred from the United Kingdom to Breachday and its Subprocessors in the United States, and that some Subprocessors operate distributed or global infrastructure as described on the Subprocessor List. Breachday does not represent that all transient Processing occurs only in the United States.
9.2 Transfer terms. The parties agree that Schedule 3 applies to every Restricted Transfer under this UK DPA. Schedule 3 takes effect on the DPA Effective Date.
9.3 Onward transfers. Breachday will transfer Customer Personal Data onward only to Subprocessors engaged under Section 4, and only with the safeguards that UK Data Protection Law requires for the onward transfer.
9.4 Information for transfer assessments. Customer, as exporter, is responsible for its own assessment of the transfer. Breachday will give information reasonably needed for that assessment, including Schedule 2, the Subprocessor List and the information in Section 4.
9.5 Replacing the transfer terms. If another transfer mechanism recognized under UK Data Protection Law becomes available for these transfers, the parties may agree in writing to rely on it in place of Schedule 3.
10. Liability and general terms
10.1 Liability. Claims under this UK DPA are subject to the liability terms of the Agreement, except that nothing in the Agreement limits or excludes (a) Breachday's liability to Data Subjects under Schedule 3, or (b) any liability that cannot be limited or excluded by law.
10.2 Amendments. The parties may amend this UK DPA by written agreement, including to reflect changes in UK Data Protection Law. Breachday may update the Subprocessor List under Section 4, update Schedule 2 implementations under Section 5.1, and make non-material administrative updates on reasonable notice.
10.3 Severability and entire agreement. If a provision is unenforceable, it will be modified to the minimum extent needed to make it enforceable, and the rest remains in effect. This UK DPA, with the Agreement and Schedule 3, is the parties' entire agreement on Breachday's Processing of Customer Personal Data.
10.4 Third parties. This UK DPA creates no rights for third parties, except the Data Subject rights in Schedule 3 and any rights that UK Data Protection Law expressly gives Data Subjects.
10.5 Governing law. This UK DPA is governed by the law that governs the Agreement, except that Schedule 3 is governed by the laws of England and Wales, and disputes under Schedule 3 are subject to the courts of England and Wales, as the UK Addendum requires.
10.6 Contact. Privacy, security and data-protection inquiries: compliance@breachday.io.
Schedule 1: Details of Processing
| Item | Details |
|---|---|
| Subject matter | Operation of the Breachday tabletop exercise platform, including authentication, exercise facilitation, report generation, file storage, support, security and platform administration |
| Nature of Processing | Collection, storage, organization, retrieval, access, use, transmission, transient AI inference, export generation, backup and deletion as necessary to provide and secure the Service |
| Purposes | Provide and operate the Service; authenticate users; deliver exercises and reports; provide support; secure the platform; maintain backups; manage authorized MSP access; enforce plan and licensing limits; comply with legal obligations |
| Frequency | Continuous, for the duration of the Subscription |
| Duration and retention | The active Subscription plus the read-only retention period in Section 7, unless deleted earlier, with up to 7 further days in encrypted disaster-recovery backups and any legally required limited retention |
| Data Subjects | Account holders and organization users; Exercise Participants; MSP users; Client personnel; vendor or business contacts entered by Customer; other individuals whose Personal Data Customer lawfully includes in Customer Data |
| Account Personal Data | Name, business email, authentication identifiers and hashed credentials, verification status, organization membership and role, 2FA data if enabled, profile image URL if provided, and MSP relationships where applicable |
| Participant Personal Data | Display name, role-seat selection, session responses, votes, confidence ratings, hotwash feedback, participant session identifiers, timestamps, and limited technical request data such as IP address where captured in security or server logs |
| Customer-entered Personal Data | Business contact information and other Personal Data Customer chooses to include in vendor records, scenarios, playbooks, support tickets, lessons learned or related content. Customer should minimize and anonymize Personal Data where feasible |
| Special category or sensitive data | Breachday does not require and is not intended to Process special category data, PHI, live payment card data, real credentials or other Sensitive Personal Data. Customer must not intentionally submit such data unless Breachday has expressly approved it in writing and the required agreements are in place |
| Transient AI Processing | AI Scenario Builder prompts and outputs are transiently Processed through OpenRouter and ZDR-eligible inference endpoints. Prompt and response content is not intended to be persistently stored by eligible inference providers after processing; non-content request metadata may be retained by OpenRouter |
| Payment data | Payment card numbers and CVV data are processed by Stripe and are not stored by Breachday. Breachday may store Stripe identifiers, subscription status and related billing metadata |
Schedule 2: Technical and Organizational Measures
Breachday maintains a security program appropriate to the size and nature of the Service. Implementations may evolve, but Breachday will not materially reduce the overall security of the Service during an active Subscription. Current measures include:
Access controls
- Role-based access controls for Organization users and privileged Breachday personnel
- Two-factor authentication support for authenticated users and required confirmation controls for high-impact operations
- Restricted privileged access based on operational need
- Controlled MSP access to authorized Client Organizations
- Participant access limited to designated Exercise Sessions through room access controls
Encryption and credential protection
- TLS 1.2 or later for application data in transit where supported
- Encryption at rest provided by Breachday infrastructure providers for database and object storage
- Cryptographic protection for room passwords and authentication secrets appropriate to their function
- Encrypted disaster-recovery backup storage
Tenant and application security
- Organization-scoped authorization and tenant isolation enforced in application data-access paths
- Separate privileged administrative functions and security logging
- Content Security Policy and other security-related HTTP headers appropriate to the application
- Rate limiting and abuse controls on public or sensitive endpoints
- Webhook authenticity validation where supported by the integration
- Automated static, dynamic, dependency or equivalent application-security testing integrated into the software-development lifecycle, with findings handled according to risk
Logging, monitoring and incident response
- Security-relevant privileged administrative actions recorded in restricted audit logs
- Server and security logging used for detection, diagnostics, abuse prevention and incident response
- Documented processes for investigating and responding to suspected Security Incidents
- Customer Security Incident notification as described in Section 5.2
Data lifecycle and resilience
- Automated post-expiration deletion processes for Customer Data
- Optional ephemeral-session deletion for eligible plans
- Deletion of unverified signup accounts after the configured lifecycle
- Rolling retention for server and security logs and disaster-recovery backups
- Daily or otherwise regularly scheduled backup processes appropriate to the Service, with encrypted off-site disaster-recovery copies retained up to 7 days
- Re-application of recorded deletion requests after a backup restore
Organizational measures
- Confidentiality obligations for personnel with access to Customer Personal Data
- Access review and least-privilege practices appropriate to Breachday's workforce and systems
- Subprocessor privacy and security obligations
- Security vulnerability reporting through compliance@breachday.io
- Reasonable security documentation and audit assistance under Section 8
Schedule 3: UK Transfer Terms
Part 1: Incorporation. This Schedule applies to each Restricted Transfer from Customer (the exporter) to Breachday (the importer). The parties enter into the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) as amended by the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, Version B1.0, issued by the Information Commissioner under section 119A of the Data Protection Act 2018 and in force from 21 March 2022 (the "UK Addendum"). Module Two (controller to processor) applies, and Module Three (processor to processor) applies where Customer acts for a Client. Those documents are incorporated by reference and completed by the tables below. The UK International Data Transfer Agreement is not used.
Table 1: Parties
| Item | Exporter | Importer |
|---|---|---|
| Start date | DPA Effective Date | DPA Effective Date |
| Name | Customer, as named in the Order Form or execution block | Breachday LLC |
| Address | As stated in the Order Form or execution block | 24411 E Mexico Ave, Aurora CO 80018, United States |
| Contact | As stated in the Order Form or execution block | compliance@breachday.io |
| Role | Controller (or Processor, where acting for a Client) | Processor (or Subprocessor, where Customer acts for a Client) |
| Signature | By accepting or signing this UK DPA | By accepting or signing this UK DPA |
Table 2: Selected SCCs, Modules and Selected Clauses
| Item | Selection |
|---|---|
| Modules | Module Two; Module Three where Customer acts for a Client |
| Clause 7 (docking clause) | Not included |
| Clause 9(a) (subprocessors) | Option 2, general written authorization, with 30 days' notice as set out in Section 4 |
| Clause 11(a) (optional independent dispute resolution) | Not included |
| Clauses 17 and 18 | Replaced by the UK Addendum: the laws and courts of England and Wales |
Table 3: Appendix Information
| Item | Where completed |
|---|---|
| Annex 1A: List of parties | Table 1 above |
| Annex 1B: Description of transfer | Schedule 1 |
| Annex II: Technical and organizational measures | Schedule 2 |
| Annex III: List of Subprocessors | Section 4.1 and the Subprocessor List |
Table 4: Ending the UK Addendum when the Approved Addendum changes. Neither Party.
Part 2: Mandatory Clauses. The Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the Information Commissioner and laid before Parliament under section 119A of the Data Protection Act 2018 on 2 February 2022, as revised under Section 18 of those Mandatory Clauses, apply to this Schedule and are incorporated by reference.
Part 3: Conflicts. If this Schedule conflicts with another part of this UK DPA, this Schedule prevails, as Section 2.4 states.
Execution
By signing below, or by accepting the Breachday UK Customer Supplement or an Order Form that refers to this UK DPA, Customer and Breachday agree to be bound by this UK Data Protection Addendum (UK Version 1.0), including Schedule 3, as of the DPA Effective Date.
| BREACHDAY LLC (Provider) | CUSTOMER |
|---|---|
| Signature: | Signature: |
| Name: | Name: |
| Title: | Title: |
| Date: | Company: |
| Registered address: | |
| Date: |