Enterprise Data Processing Addendum (DPA)
Binding Article 28 GDPR, UK International Data Transfer Addendum (IDTA), EU 2021/914 SCCs, and technical security annexes for publishing organisations.
Executive Summary & Procurement Readiness: This Enterprise Data Processing Addendum ("DPA") forms an integral, legally binding schedule to the Master SaaS & Author Studio Terms of Service or negotiated Master Subscription Agreement between British Noble ("Processor") and the subscribing publishing organisation ("Controller"). Engineered for frictionless legal and procurement sign-off by UK, European, North American, and MENA publishing groups, university presses, scholarly societies, and literary estates, this DPA satisfies Article 28 of the UK and EU GDPR, CCPA/CPRA Service Provider mandates, the revised Swiss FADP, and UAE Federal Decree-Law No. 45 of 2021 (PDPL).
Key contractual safeguards include: processing strictly on documented Controller instructions; zero secondary commercial use or AI foundation-model training; incident notification within ≤ 24 hours of confirming any Personal Data Breach; thirty (30) calendar days' prior written notice of Sub-Processor changes with objection rights; pre-incorporated EU 2021/914 Standard Contractual Clauses and the UK ICO International Data Transfer Addendum (IDTA); certified post-termination KMS cryptographic erasure; and Annex II Technical and Organisational Measures enforcing TLS 1.3, AES-256-GCM encryption, and per-tenant AWS KMS Hardware Security Module isolation. To accelerate institutional onboarding, enterprise legal counsel and Data Protection Officers may request a pre-executed, countersigned PDF copy together with our current Transfer Impact Assessment pack directly from Privacy@BritishNoble.com.
1. Incorporation, Scope & Statutory Definitions
This Data Processing Addendum applies automatically whenever and to the extent that British Noble processes Personal Data on behalf of Controller in the course of providing British Noble AI cloud workspaces, migration services, or technical support under the Agreement. In the event of any conflict between this DPA and the Master Terms of Service regarding the protection of Personal Data, the provisions of this DPA (and, where applicable, the Standard Contractual Clauses or UK IDTA) shall prevail.
"Applicable Data Protection Law" means all privacy and data-protection legislation applicable to the processing of Controller Personal Data under the Agreement, including: (a) the UK GDPR and UK Data Protection Act 2018; (b) Regulation (EU) 2016/679 (EU GDPR) and national implementing laws; (c) the Swiss Federal Act on Data Protection (FADP); (d) the California Consumer Privacy Act as amended by the CPRA (Cal. Civ. Code Sec. 1798.100 et seq.) and analogous US state privacy statutes; and (e) UAE Federal Decree-Law No. 45 of 2021 (PDPL) together with DIFC Data Protection Law No. 5 of 2020 where applicable. Terms such as "Controller", "Processor", "Data Subject", "Personal Data", "Processing", and "Personal Data Breach" carry the meanings defined in Applicable Data Protection Law.
2. Processing Strictly on Documented Controller Instructions
Pursuant to Article 28(3)(a) of the GDPR, British Noble shall process Controller Personal Data solely on documented instructions from Controller, which comprise the Agreement, this DPA, Controller's workspace configuration (including regional KMS residency selection, ONIX channel dispatch rules, and royalty payout approvals), and written support tickets initiated by authorised Controller administrators, unless processing is required by applicable statutory law to which British Noble is subject (in which case British Noble shall inform Controller of that legal requirement prior to processing, unless prohibited by law on important grounds of public interest).
British Noble shall immediately inform Controller if, in its reasonable opinion, an instruction issued by Controller infringes Applicable Data Protection Law. For purposes of the CCPA/CPRA, British Noble certifies under penalty of contract breach that it acts strictly as a "Service Provider" and shall not: (i) sell or share Controller Personal Data; (ii) retain, use, or disclose Controller Personal Data for any commercial purpose outside the direct business relationship with Controller, including training machine-learning models; or (iii) combine Controller Personal Data with personal information received from other sources except as expressly permitted by statute to maintain workspace security.
3. Workforce Screening, Confidentiality & Zero Standing Access
British Noble ensures that every employee, solutions architect, site reliability engineer, and authorised contractor permitted to support production infrastructure: (a) has passed pre-engagement identity and background verification to the fullest extent permitted by local labour law; (b) has executed a binding written confidentiality and intellectual-property protection undertaking surviving termination of employment; and (c) completes mandatory annual training covering GDPR compliance, publishing manuscript embargo protocols, and phishing defence.
Production engineering operates under a strict Zero Standing Privileges (ZSP) model. British Noble personnel have zero routine standing access to cleartext manuscripts, contributor tax forms, or payee bank accounts; diagnostic access to a tenant workspace occurs solely when explicitly enabled by a Controller administrator via a time-boxed support token or under peer-approved emergency P1 incident change control logged immutably to the tenant audit trail.
4. Binding Technical & Organisational Measures (Article 32)
Taking into account the state of cryptographic practice, implementation costs, and the high commercial and reputational sensitivity of unpublished literary works and contributor tax identifiers, British Noble implements and maintains throughout the Subscription Term all Technical and Organisational Measures ("TOMs") specified in Annex II of this DPA and in our Information Security & Cryptography Policy.
British Noble may upgrade cryptographic algorithms, hardware security modules, and defensive controls over time to address emerging threats, provided that no modification shall ever degrade or materially reduce the overall security posture, regional residency pinning, or tenant isolation commitments contracted during an active Subscription Term.
5. Sub-Processor Authorisation, 30-Day Notice & Flow-Down Liability
Controller grants British Noble general written authorisation pursuant to Article 28(2) of the GDPR to engage the vetted infrastructure Sub-Processors itemised in Annex III solely to deliver the contracted Platform services. Prior to permitting any Sub-Processor to process Controller Personal Data, British Noble conducts a formal security and privacy due-diligence audit and executes a written contract imposing data-protection and security obligations no less protective than those set forth in this DPA.
British Noble shall provide Controller's designated security and DPO contacts with at least thirty (30) calendar days' prior written notice before adding or replacing any Sub-Processor. Controller may object in writing on reasonable, documented data-protection grounds within fifteen (15) calendar days of receiving such notice by emailing Privacy@BritishNoble.com. Upon receipt of a timely objection, British Noble shall work in good faith to provide a configuration workaround that avoids the new Sub-Processor; if no commercially reasonable alternative can be provided before planned deployment, Controller may terminate solely the affected Platform capability without penalty and receive a pro-rata refund of prepaid unearned fees for that capability. British Noble remains fully liable to Controller for the performance of each Sub-Processor's data-protection obligations.
6. Data Subject Requests & Regulatory Impact Assessments
The Platform equips Controller administrators with native self-serve capabilities to search, export, rectify, anonymise, or purge contributor records, manuscript submissions, and portal accounts directly inside the workspace. Should a Data Subject submit a request to exercise GDPR Chapter III, CCPA, or UAE PDPL rights directly to British Noble regarding records controlled by Controller, British Noble shall notify Controller within two (2) business days and shall not respond substantively to the Data Subject without Controller's prior authorisation unless legally compelled.
Where Controller cannot fulfil a verified Data Subject Request using native workspace controls alone, British Noble shall provide prompt engineering assistance at no additional charge for standard requests. Furthermore, pursuant to Articles 35 and 36 of the GDPR and Article 21 of the UAE PDPL, British Noble provides architecture documentation, encryption topology maps, and DPO cooperation required for Controller's Data Protection Impact Assessments (DPIAs) and supervisory authority consultations.
7. Personal Data Breach Notification Within <= 24 Hours
Recognising that Controllers face strict 72-hour statutory reporting deadlines to supervisory authorities under Article 33 of the GDPR, British Noble commits to a substantially faster contractual SLA: British Noble shall notify Controller without undue delay and in all events within twenty-four (≤ 24) hours after confirming any Personal Data Breach affecting Controller Personal Data or Customer Content.
Initial and rolling incident notifications transmitted to Controller's designated security and DPO contacts shall detail, to the extent known: (a) the nature and timeline of the Personal Data Breach; (b) the categories and approximate volume of Data Subjects and Personal Data records affected; (c) the contact details of British Noble's CISO and DPO leading the response; (d) the likely operational consequences; and (e) the containment, forensic preservation, and cryptographic remediation measures executed and proposed. Notification of an incident shall not be construed as an admission of legal fault or liability. British Noble shall not issue any press release or public regulatory filing naming Controller without Controller's prior written consent, unless strictly required by statutory mandate.
8. Independent Attestations & Controller Audit Procedures
Upon written request (up to once annually, or immediately following any confirmed Personal Data Breach), British Noble shall make available to Controller under confidentiality protection its current Enterprise Security Assurance Pack, comprising ISO/IEC 27001:2022 and SOC 2 Type II control mapping reports, annual CREST third-party penetration test executive summaries confirming remediation of findings, and Cloud Security Alliance CAIQ v4 responses.
Where Applicable Data Protection Law or a competent supervisory authority requires verification beyond independent third-party attestations, Controller (or an independent, accredited third-party auditor bound by written confidentiality and not a competitor of British Noble) may conduct a scoped remote or on-site compliance audit upon thirty (30) calendar days' prior written notice during normal business hours (notice waived in the event of a confirmed Personal Data Breach or regulator-mandated inspection). Audits shall be conducted in a manner preserving the cryptographic confidentiality and availability of other publishing tenants.
9. International Transfer Mechanisms: EU SCCs & UK ICO IDTA
Controller Personal Data resides primarily within the sovereign cloud vault selected by Controller (UK eu-west-2, EU eu-central-1, US us-east-1, or UAE me-central-1). To the extent any instruction by Controller involves a restricted cross-border transfer of Personal Data subject to EEA, UK, Swiss, or UAE transfer rules to a jurisdiction lacking an adequacy decision, the parties hereby incorporate and execute by reference:
- EEA Transfers (EU SCCs): The Standard Contractual Clauses annexed to European Commission Implementing Decision (EU) 2021/914 of 4 June 2021, selecting Module Two (Controller to Processor) where Controller is a Data Controller and Module Three (Processor to Processor) where Controller acts as a Processor for an upstream imprint owner. Under Clause 7, the optional docking clause applies; under Clause 9(a), Option 2 (General Written Authorisation, 30 days) applies; under Clause 11, the optional redress clause is omitted; under Clause 17, Option 1 applies governed by the laws of Ireland; and under Clause 18(b), disputes shall be resolved before the courts of Ireland, with Annexes I, II, and III populated by Clauses 11 and 12 below.
- United Kingdom Transfers (UK IDTA): The International Data Transfer Addendum to the EU Commission Standard Contractual Clauses (Version B1.0) issued by the UK Information Commissioner under Section 119A of the Data Protection Act 2018, with Tables 1 to 3 populated by Clauses 11 and 12 below and Table 4 allowing either party to end the Addendum as permitted under Section 19 where statutory replacements are issued.
- Switzerland & UAE Transfers: For Swiss FADP transfers, references to the GDPR include the revised Swiss FADP and the Swiss FDPIC serves as competent authority; for UAE PDPL and DIFC transfers, equivalent standard data-protection clauses and sovereign encryption safeguards apply in full.
10. Post-Termination Data Return & Certified Cryptographic Destruction
Pursuant to Article 28(3)(g) of the GDPR, during the sixty (60) calendar day Retrieval Window following expiration or termination of the Agreement (or immediately upon Controller's earlier written request), Controller may export all Personal Data, contributor records, ONIX archives, production files, and royalty ledgers in structured, non-proprietary XML, CSV, JSON, and PDF formats at zero exit charge.
Within thirty (30) calendar days following the close of the Retrieval Window, British Noble shall irreversibly purge all Controller Personal Data from active databases and object storage and execute cryptographic destruction ("crypto-shredding" in alignment with NIST SP 800-88 Rev. 1 media sanitisation guidelines) of Controller's dedicated tenant AWS KMS Customer Master Key, rendering all residual encrypted blocks across immutable backup snapshots permanently undecipherable until automatic snapshot lifecycle expiry, except solely to the extent statutory law requires retention of isolated invoicing records. Upon request, British Noble's DPO and CISO issue a signed Certificate of Data & Key Destruction.
11. Annex I to the DPA & SCCs: Particulars of Processing
The statutory particulars required under Article 28(3) GDPR, Annex I of EU Decision 2021/914, and Table 1/3 of the UK IDTA are established as follows:
| Annex I Element | Binding Contractual Specification |
|---|---|
| Data Exporter (Controller) | The subscribing publishing organisation identified on the Order Form, acting as Controller (or upstream Processor for affiliated imprints) |
| Data Importer (Processor) | British Noble (operating British Noble AI cloud infrastructure), DPO contact: Privacy@BritishNoble.com |
| Categories of Data Subjects | Controller's internal publishing staff; contracted authors, co-authors, volume editors, peer reviewers, translators, illustrators, audiobook narrators, and literary agents; submission applicants |
| Categories of Personal Data | Professional names, email addresses, SSO identifiers, contributor biographies, ORCID/ISNI codes, contract split metadata, payee remittance details, and encrypted W-9 / W-8BEN tax forms |
| Special Categories / Sensitive Data | None required or intentionally collected; platform security applies uniformly across all workspace data |
| Frequency, Nature & Duration | Continuous automated cloud hosting, KMS encryption, ONIX compilation, and royalty calculation throughout the Subscription Term plus the 60-day Retrieval Window |
| Competent Supervisory Authority | UK ICO (for UK GDPR), Data Protection Commission of Ireland or Exporter's EU lead authority (for EU GDPR), Swiss FDPIC, or UAE Data Office |
12. Annex II (Technical Measures) & Annex III (Authorised Sub-Processors)
Annex II Summary of Technical & Organisational Measures: (1) Pseudonymisation & Encryption: Mandatory TLS 1.3 across all external and service-mesh edges; AES-256-GCM encryption at rest backed by FIPS 140-3 Level 3 AWS KMS Hardware Security Modules with unique per-tenant envelope keys and 365-day automated rotation; (2) Access & Confidentiality: SAML 2.0 / OIDC SSO, SCIM 2.0 lifecycle revocation, WebAuthn/TOTP MFA, imprint and Title-ID RBAC, and PostgreSQL Row-Level Security enforcing tenant boundaries; (3) Availability & Resilience: Multi-AZ synchronous database replication delivering a 15-minute RPO and 2-hour RTO alongside immutable WORM daily backups; (4) Regular Testing: Annual CREST-accredited penetration testing, continuous CI/CD SAST/DAST scanning, and immutable SIEM-exportable audit logging; (5) AI Isolation: Strict technical and contractual zero-training isolation on all tenant data.
Annex III Schedule of Authorised Infrastructure Sub-Processors:
| Sub-Processor | Operational Function | Pinned Processing Regions | Safeguard & Assurance |
|---|---|---|---|
| Amazon Web Services (AWS) | Sovereign compute, RDS multi-AZ databases, S3 storage & KMS HSM vaults | UK (eu-west-2), EU (eu-central-1), US (us-east-1), UAE (me-central-1) per tenant selection | ISO 27001, SOC 2 Type II, C5, EU SCCs & UK IDTA |
| Stripe Connect (Optional Module) | Multi-currency author & literary-agency royalty payout rails (active only if enabled by Controller) | Regional clearing aligned to Controller treasury entity | PCI-DSS Level 1, SOC 2 Type II, Regulated EMI, SCCs/IDTA |
| Wise Business Platform (Optional Module) | Batch international FX royalty wire file clearing (active only if enabled by Controller) | UK, EEA & US regulated clearing hubs | FCA / NBB Authorised Institution, ISO 27001, SCCs/IDTA |
| Customer-Configured SAML IdP | Federated identity verification (Okta, Microsoft Entra ID, or Google Workspace selected by Controller) | Governed directly by Controller's enterprise IdP tenant | Direct Controller agreement & SAML 2.0 X.509 signing |
Multi-Jurisdiction Governance
Aligned with UK GDPR, Data Protection Act 2018, EU SCCs, CCPA/CPRA, UAE Federal Decree-Law No. 45 of 2021 (PDPL), ISO/IEC 27001:2022, and SOC 2 Type II.
Zero Manuscript Training
Customer manuscripts, proof files, ONIX records, and royalty ledgers are isolated per tenant and never used to train foundation or shared models.
Data Protection & Procurement Desk
Enterprise procurement teams may request countersigned schedules, DPA exhibits, and audit certificates directly.
Privacy@BritishNoble.com →