# United Kingdom (UK)

> Rules, fixed strings, exclusions, retention floors and fact keys of the UK pack, version 2026-11-21 (research draft).

Source: https://esigncomply.com/docs/jurisdictions/uk

A pack records which rules Esign Comply applied. It is not a statement that a flow meets the law of this jurisdiction.

> **Research draft.** This pack has not yet been reviewed by counsel admitted in the jurisdiction. Until that review, U.S. state packs run in test mode only.

| | |
|---|---|
| Code | `UK` |
| Version | 2026-11-21 |
| Effective | 2026-11-21 |
| Review state | research draft |
| Status | active |
| Prompt block | `uk.core` |
| API | `GET /v1/jurisdictions/UK` |

Separate domestic pack for flows subject to UK law: UK eIDAS, national form rules and the applicable UK Consumer Contracts Regulations. UK eIDAS is a distinct domestic regime; it recognizes EU-qualified services, not the other way around automatically, and ECA s.7 makes a logically associated electronic signature and its certification admissible on authenticity or integrity questions. UK consumer regulations are applied independently, and the EU Art. 11a online withdrawal function is not imported.

## Coverage

Covered: uk eidas, signature classification, national form rules, uk consumer contracts regulations, pre contract savable terms and correction, payment disclosures and button, durable confirmation, intelligible terms, privacy notice, minimal sdk capture, evidence timestamps and seals, processor agreement, retention and erasure, international transfers.

Not covered: qualified signatures, notarization, national special forms beyond the screen, sector rules, eu online withdrawal function, eu trust service and nis2 classification, scottish and northern irish special forms.

A pack covers selected rules, not every law in that state or country. The record identifies what was applied. Your team is responsible for legal review and for building and sending post-signing notices.

## Rules

Each rule is split into parts, and each part has one class. Only record conditions (Block, Warn) can affect a session, and only after the profile has adopted them. See [Jurisdiction packs](https://esigncomply.com/docs/guides/jurisdictions.md) and [Guidance and adoption](https://esigncomply.com/docs/guides/guidance.md).

### EU-01 Explicit act on a frozen document version {#eu-01}

An explicit act labelled to show agreement or signing, targeting a frozen document version. No assent inferred from login, page view, or a pre-ticked control. Changing the document invalidates the session.

- Enforcement: Block; Recommendation
- Triggers: `base`
- Scope: All. Applied under the UK pack: UK eIDAS is a distinct domestic regime, and ECA s.7 makes a logically associated electronic signature and its certification admissible on authenticity or integrity questions (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused.
- Topics: online assent, esign statute
- Implemented in: S6, S9, DV-3

**Esign Comply records or checks**

- **Block.** Esign Comply checks on its own record that the assent control was unchecked or empty at load and was changed by a trusted user event (CR-01), and that the explicit act targets a frozen document version. No assent is inferred from login, page view, or a pre-ticked control; changing the document invalidates the session. (checks: CR-01)

**Recommendations**

- **Recommendation.** Use a clearly labelled assent or signing control tied to the exact version. Do not infer intent from login, viewing a page, or a pre-ticked control.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents); [ECA 2000 s.7](https://www.legislation.gov.uk/ukpga/2000/7/section/7)

### EU-02 Observed facts separated from asserted facts {#eu-02}

Observed facts are separated from customer-asserted facts in the record, the evidence report, and the export. Unsupported labels such as "identity verified" are refused when only the customer asserts them.

- Enforcement: Service
- Triggers: `base`
- Scope: All. Applied under the UK pack: UK eIDAS is a distinct domestic regime, and ECA s.7 makes a logically associated electronic signature and its certification admissible on authenticity or integrity questions (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused.
- Topics: evidence
- Implemented in: PP-1, section 13.8

**Esign Comply records or checks**

- **Service.** Esign Comply separates observed facts from customer-asserted facts in the record, the evidence report, and the export, and refuses unsupported labels such as "identity verified" when only the customer asserts them.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents); [ECA 2000 s.7](https://www.legislation.gov.uk/ukpga/2000/7/section/7); [Golden Ocean v Salgaocar](https://caselaw.nationalarchives.gov.uk/ewca/civ/2012/265)

### EU-03 Signature level classification {#eu-03}

signature_level is a service classification: simple for L1–L3 signing; not_applicable where signing intent is not evidenced. advanced requires recorded proof of all Article 26 requirements; qualified requires full signing-time validation under Section 9.3.1. No silent changes or fallback.

- Enforcement: Block
- Triggers: `base`
- Scope: All. Applied under the UK pack: UK eIDAS is a distinct domestic regime; it recognizes EU-qualified services, not the other way around automatically (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused and its article and section references are as printed in the EU row.
- Topics: signature level
- Implemented in: Section 9.3.1

**Esign Comply records or checks**

- **Block.** Esign Comply checks the signature_level on its own record: simple for L1–L3 signing; not_applicable where signing intent is not evidenced; advanced only with recorded proof of all Article 26 requirements; qualified only with full signing-time validation under Section 9.3.1. No silent changes or fallback.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents); [ICO guide to eIDAS](https://ico.org.uk/for-organisations/guide-to-eidas/what-is-the-eidas-regulation)

### EU-04 L3 credential authentication limits {#eu-04}

L3 authenticates a previously registered credential using a one-use challenge bound to a frozen pre-signature transaction payload. Reject known shared accounts and cross-document reuse; no administrator may act as the signer. Do not infer Article 26 compliance, legal identity or sole control.

- Enforcement: Block
- Triggers: `base`
- Scope: L3, AES. Applied under the UK pack: UK eIDAS is a distinct domestic regime (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused and its article reference is as printed in the EU row.
- Topics: signature level, evidence
- Implemented in: VF-4

**Esign Comply records or checks**

- **Block.** Esign Comply checks on its own record that L3 authenticates a previously registered credential using a one-use challenge bound to a frozen pre-signature transaction payload, and rejects known shared accounts, cross-document reuse and any administrator acting as the signer. The record does not infer Article 26 compliance, legal identity or sole control.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents)

### EU-05 Timestamp tokens and qualified timestamp label {#eu-05}

RFC 3161 tokens bind the record hash. Verify imprint, nonce, signature, chain and policy; keep server receipt, client-reported and token times separate. Require the specific service's historical qualification at token issuance and full component validation for a qualified label.

- Enforcement: Service
- Triggers: `base`
- Scope: All. Applied under the UK pack: UK eIDAS is a distinct domestic regime; it recognizes EU-qualified services, not the other way around automatically (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused.
- Topics: evidence
- Implemented in: E4

**Esign Comply records or checks**

- **Service.** Esign Comply binds the record hash with RFC 3161 tokens; verifies imprint, nonce, signature, chain and policy; keeps server receipt, client-reported and token times separate; and applies a qualified label only with the specific service's historical qualification at token issuance and full component validation.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents); [RFC 3161](https://www.rfc-editor.org/rfc/rfc3161.html)

### EU-06 Provider seal kept distinct from signer signature {#eu-06}

Esign Comply's seal on evidence is labelled as the provider's seal and is kept distinct from the signer's signature.

- Enforcement: Service
- Triggers: `base`
- Scope: All. Applied under the UK pack: UK eIDAS is a distinct domestic regime (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused.
- Topics: evidence
- Implemented in: Section 10.5

**Esign Comply records or checks**

- **Service.** Esign Comply labels its seal on evidence as the provider's seal and keeps it distinct from the signer's signature.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents)

### EU-07 Validation evidence preservation and renewal {#eu-07}

Preserve validation evidence and test offline; renew external proof before assurance degrades. Use Section 10.6's export profile without claiming qualified validation, preservation or archiving.

- Enforcement: Service
- Triggers: `base`
- Scope: All. Applied under the UK pack: UK eIDAS is a distinct domestic regime (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused.
- Topics: evidence, retention
- Implemented in: Section 10.6, RT-7

**Esign Comply records or checks**

- **Service.** Esign Comply preserves validation evidence and tests it offline, renews external proof before assurance degrades, and uses Section 10.6's export profile without claiming qualified validation, preservation or archiving.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents)

### EU-08 Jurisdiction, signer and document category screen {#eu-08}

Require customer-confirmed applicable jurisdictions, signer country, signer class and document category. Block unresolved or special-form cases pending manual clearance. A pass is not a legal determination; cryptography does not replace required witnessing or public form.

- Enforcement: Block; Recommendation
- Triggers: `base`
- Scope: All. Applied under the UK pack as the national form screen: in England and Wales individual deeds generally need physically present witnessing, attestation and delivery, and companies have separate execution routes; route Scottish and Northern Irish special-form cases separately (section 9.1).
- Topics: exclusions
- Implemented in: SS-6

**Esign Comply records or checks**

- **Block.** Esign Comply checks its own record for customer-confirmed applicable jurisdictions, signer country, signer class and document category (CR-18), and blocks unresolved or special-form cases pending manual clearance. A pass is not a legal determination; cryptography does not replace required witnessing or public form. (checks: CR-18)

**Recommendations**

- **Recommendation.** Confirm applicable jurisdictions, signer country and class, and document category. Seek local review for unresolved formalities; do not rely on the product check as legal clearance.

Legal sources: [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents); [Law of Property (Miscellaneous Provisions) Act s.1](https://www.legislation.gov.uk/ukpga/1989/34/section/1); [Companies Act s.44](https://www.legislation.gov.uk/ukpga/2006/46/section/44)

### EU-09 Pre-contract information, correction and savable terms {#eu-09}

The in-scope service provider discloses contracting steps, filing and access, offered languages and applicable codes; provides pre-order error correction and savable terms; and acknowledges orders electronically without undue delay. The trader presents written consumer terms in plain, intelligible language and should give consumers a real chance to read the exact pinned version before assent. Esign Comply checks only its own recorded facts and may store any customer-supplied acknowledgment evidence as asserted. Apply Arts. 10–11 exceptions only to the specified paragraphs, not Art. 10(3).

- Enforcement: Block; Obligation; Recommendation; Report
- Triggers: `base`
- Scope: All. Applied under the UK pack: apply UK consumer regulations independently (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused and its article references are to the EU instruments cited in the EU pack.
- Topics: online assent, copies, language
- Implemented in: Prompt rules, CR-13, CR-14

**Esign Comply records or checks**

- **Block.** Esign Comply checks only its own recorded facts: review is presented before the final act and covered EU users can actually identify and correct inputs before ordering (CR-13); covered EU flows offer the exact pinned terms in storable and reproducible form before assent, and a later receipt is not a substitute (CR-14). Section 9.4 states the live-mode effect as: block covered EU orders without correction, otherwise Warn (CR-13); block covered EU flows, otherwise Warn (CR-14). (checks: CR-13, CR-14; adds steps: `review.presented`)

**Your obligations**

- **Obligation.** In-scope service provider: disclose contracting steps, filing/access, offered languages and relevant codes/access; provide pre-order error correction and storable, reproducible terms; acknowledge orders electronically without undue delay. Trader: draft written consumer terms in plain, intelligible language. (duty holder: In-scope service provider; Trader)

**Recommendations**

- **Recommendation.** Offer the exact pinned terms and give consumers a real opportunity to read them before assent.

**What you can send us**

- **Report.** The customer may send its own evidence that an order was acknowledged (order.acknowledged). Esign Comply may store any customer-supplied acknowledgment evidence as asserted and does not verify it. (supplement types: `order.acknowledged`)

Legal sources: [Consumer Contracts Regulations](https://www.legislation.gov.uk/uksi/2013/3134)

### EU-10 Payment disclosures and order button {#eu-10}

For a covered order creating a payment obligation, including a later conditional obligation, the trader presents the Art. 6(1)(a), (e), (la), (o), (p) information clearly and prominently directly before the action and obtains explicit acknowledgment. If the final action uses a button or similar control, label it legibly only "Order with obligation to pay" or an unambiguous local equivalent. Esign Comply applies CR-11 only to facts in its own record and may retain customer-supplied disclosure evidence as asserted.

- Enforcement: Block where the payment duty applies, whatever the purpose value; Obligation; Report
- Triggers: `base`
- Scope: Applicable EU distance orders. Applied under the UK pack where the UK Consumer Contracts Regulations apply: apply UK consumer regulations independently (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused and its article references are to the EU instruments cited in the EU pack.
- Topics: payment, online assent
- Implemented in: CR-11

**Esign Comply records or checks**

- **Block.** Block where the payment duty applies, whatever the purpose value. Esign Comply applies CR-11 only to facts in its own record: for a covered payment obligation, including conditional payment, it tests the required disclosures directly before ordering and the sole approved, legible acknowledgment label. (checks: CR-11)

**Your obligations**

- **Obligation.** Trader: show required information clearly, prominently and directly before a covered paid order; obtain explicit acknowledgment, including for conditional payment. Label any final button only with easily legible statutory wording or an unambiguous equivalent. (duty holder: Trader)

**What you can send us**

- **Report.** The customer may send its own disclosure evidence (payment.disclosure_presented). Esign Comply may retain customer-supplied disclosure evidence as asserted and does not verify it. (supplement types: `payment.disclosure_presented`)

Legal sources: [Consumer Contracts Regulations](https://www.legislation.gov.uk/uksi/2013/3134)

### EU-11 Durable confirmation of the contract {#eu-11}

The trader provides personally addressed durable confirmation within a reasonable time and no later than goods delivery or before service begins, including the concluded contract, applicable Art. 6(1) information not already given durably, and applicable Art. 16(m) consent and acknowledgment. Esign Comply records its own sends and failures if it handles delivery; a trader's send is stored only if reported and is tagged asserted. Require a tested delivery route as a release criterion.

- Enforcement: Service; Obligation; Recommendation; Report
- Triggers: `base`
- Scope: Applicable distance contracts. Applied under the UK pack where the UK Consumer Contracts Regulations apply: apply UK consumer regulations independently (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused and its article references are to the EU instruments cited in the EU pack.
- Topics: copies
- Implemented in: SR-1, SR-2, SR-6

**Esign Comply records or checks**

- **Service.** Esign Comply records its own sends and failures if it handles delivery. A tested delivery route is a release criterion.

**Your obligations**

- **Obligation.** Trader: give durable contract confirmation including required information and applicable digital-content consent acknowledgment, within a reasonable time and no later than goods delivery or before service starts. (duty holder: Trader)

**Recommendations**

- **Recommendation.** Test the confirmation route before go-live. If sending yourself, keep the artifact, method, send time and failure details.

**What you can send us**

- **Report.** The trader may report its own send of the confirmation (copy.delivered, or order.acknowledged for a contract confirmation sent on a durable medium). A trader's send is stored only if reported and is tagged asserted; Esign Comply does not verify it. (supplement types: `copy.delivered`, `order.acknowledged`)

Legal sources: [Consumer Contracts Regulations](https://www.legislation.gov.uk/uksi/2013/3134)

### EU-13 Offered languages and intelligible terms {#eu-13}

The in-scope service provider discloses offered languages; the trader presents written consumer terms in plain, intelligible language. Recommend allowing the consumer to select an offered version. Esign Comply records language where observed and keeps any customer report separate; locale match is not a universal rule.

- Enforcement: Block if a mandatory language is unmet; Warn; Obligation; Recommendation; Report
- Triggers: `base`
- Scope: All. Applied under the UK pack: apply UK consumer regulations independently (section 9.1). The spec gives no UK-specific wording for this row; the EU text is reused and its article references are to the EU instruments cited in the EU pack.
- Topics: language
- Implemented in: CR-15

**Esign Comply records or checks**

- **Block.** Block if a mandatory language is unmet: Esign Comply checks the stored language on its own record against mandatory local requirements (CR-15). (checks: CR-15)
- **Warn.** Esign Comply records language where observed and checks the stored language against consumer choice and understanding, not locale alone (CR-15). Locale match is not a universal rule. (checks: CR-15)

**Your obligations**

- **Obligation.** In-scope service provider: disclose offered contracting languages. Trader: present written consumer terms in plain, intelligible language. (duty holder: In-scope service provider; Trader)

**Recommendations**

- **Recommendation.** Let consumers choose an offered version they understand. Do not treat locale match as a universal legal rule.

**What you can send us**

- **Report.** The customer may report the language in which it presented the offer (language.presented). Esign Comply keeps any customer report separate from the language it observed and does not verify it. (supplement types: `language.presented`)

Legal sources: [Consumer Contracts Regulations](https://www.legislation.gov.uk/uksi/2013/3134)

### EU-14 EU minimal capture by default {#eu-14}

Apply EU minimal capture by default. Document each purpose; keep drawn signatures, fingerprinting and optional terminal data off. Esign Comply keeps its optional measurements off unless cleared under PRV-4; customers operating their own terminal access obtain prior consent unless an applicable exemption covers the operation.

- Enforcement: Service; Obligation; Recommendation
- Triggers: `base`
- Scope: All. Applied under the UK pack. The spec gives no UK-specific wording or source for this row; the EU text and sources are reused.
- Topics: privacy capture, privacy
- Implemented in: PP-7, SDK-8, section 17.3

**Esign Comply records or checks**

- **Service.** Esign Comply applies EU minimal capture by default: drawn signatures, fingerprinting and optional terminal data stay off, and its optional measurements stay off unless cleared under PRV-4.

**Your obligations**

- **Obligation.** Customer operating terminal access: obtain prior consent to store or access terminal information unless the transmission or strictly necessary exemption applies. (duty holder: Customer operating terminal access)

**Recommendations**

- **Recommendation.** Document each capture purpose and leave optional terminal measurements and drawn-signature capture off by default.

Legal sources: [GDPR Arts. 5, 6, 25](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng); [ePrivacy Directive Art. 5(3)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02002L0058-20091219)

### EU-15 Privacy information and distinct consent request {#eu-15}

The controller gives the required privacy information and presents any written consent request distinctly from other matters. Recommend a layered notice and a separate label for any notice acknowledgment; if the customer reports display, Esign Comply records the report as asserted.

- Enforcement: Obligation; Recommendation; Report
- Triggers: `base`
- Scope: All. Applied under the UK pack. The spec gives no UK-specific wording or source for this row; the EU text and sources are reused.
- Topics: privacy
- Implemented in: Prompt rules

**Your obligations**

- **Obligation.** Controller: give required privacy information on purposes, recipients and applicable roles. If seeking consent in a written declaration covering other matters, present the request distinctly. (duty holder: Controller)

**Recommendations**

- **Recommendation.** Use a layered notice and label any notice acknowledgment separately from assent and consent.

**What you can send us**

- **Report.** The customer may report that its privacy notice was displayed (privacy_notice.presented). Esign Comply records the report as asserted and does not verify it. (supplement types: `privacy_notice.presented`)

Legal sources: [GDPR Arts. 7, 13–14](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng)

### EU-16 Data processing agreement before live keys {#eu-16}

Before issuing live keys, require an Art. 28 DPA with authorization and objection process for subprocessors, required flow-down terms, assistance, audit and controller choice of return or deletion.

- Enforcement: Block; Obligation
- Triggers: `base`
- Scope: All. Applied under the UK pack. The spec gives no UK-specific wording or source for this row; the EU text and sources are reused.
- Topics: privacy
- Implemented in: Section 11.5, section 17.3

**Esign Comply records or checks**

- **Block.** Before issuing live keys, Esign Comply requires on its own record an Art. 28 DPA with authorization and objection process for subprocessors, required flow-down terms, assistance, audit and controller choice of return or deletion.

**Your obligations**

- **Obligation.** Controller: engage processors with sufficient guarantees, set binding Article 28 terms and authorize subprocessors in writing as applicable. (duty holder: Controller)

Legal sources: [GDPR Arts. 28, 32–36](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng)

### EU-17 Retention, erasure and restriction {#eu-17}

The controller sets necessary retention, honors applicable erasure and restriction rights, and limits any hold to what is necessary. Esign Comply tests erasure on its own evidence and restored backups, limits public immutable data to non-identifying aggregates, and tags reports of customer erasure as asserted.

- Enforcement: Service; Obligation; Recommendation; Report
- Triggers: `base`
- Scope: All. Applied under the UK pack. The spec gives no UK-specific wording or source for this row; the EU text and sources are reused.
- Topics: retention, privacy
- Implemented in: Section 17.3

**Esign Comply records or checks**

- **Service.** Esign Comply tests erasure on its own evidence and restored backups, and limits public immutable data to non-identifying aggregates.

**Your obligations**

- **Obligation.** Controller: keep identifiable data no longer than necessary, erase when required, and apply restriction and exceptions only where their conditions are met. (duty holder: Controller)

**Recommendations**

- **Recommendation.** Set retention by data class, test erasure through restore paths, and document the necessity, scope and review date of legal holds.

**What you can send us**

- **Report.** The customer may report an erasure or restriction it completed in its own systems (erasure.completed). Esign Comply tags reports of customer erasure as asserted and does not verify them. (supplement types: `erasure.completed`)

Legal sources: [GDPR Arts. 5, 17–18, 25, 28](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng); [EDPB final blockchain guidelines](https://www.edpb.europa.eu/system/files/2026-07/edpb_guidelines_202502_blockchain_v2_en.pdf)

### EU-18 Hosting, access paths and transfers {#eu-18}

Esign Comply verifies its hosting and access paths for its own operations. The party making a covered transfer verifies the recipient and applicable adequacy coverage, or puts an applicable safeguard and assessment in place. Same-entity employee access alone is not a transfer; apply security controls. No unverified EU-only claims.

- Enforcement: Service; Obligation; Recommendation
- Triggers: `base`
- Scope: All. Applied under the UK pack. The spec gives no UK-specific wording or source for this row; the EU text and sources are reused.
- Topics: privacy
- Implemented in: Section 16, section 17.3

**Esign Comply records or checks**

- **Service.** Esign Comply verifies its hosting and access paths for its own operations. Same-entity employee access alone is not a transfer; security controls apply. Esign Comply makes no unverified EU-only claims.

**Your obligations**

- **Obligation.** Customer acting as exporter: use applicable Chapter V grounds for covered transfers, verify recipient and adequacy scope or applicable safeguards, and apply risk-appropriate security. (duty holder: Customer acting as exporter)

**Recommendations**

- **Recommendation.** Map hosting, access and recipients. Do not assume an EU region eliminates transfers or claim EU-only processing without verification.

Legal sources: [GDPR Arts. 32, 44–46](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng); [DPF decision](https://eur-lex.europa.eu/eli/dec_impl/2023/1795/oj/eng); [SCC decision](https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj/eng)

### EU-20 UK deeds routed outside the generic flow {#eu-20}

Block UK deeds in the generic flow and route according to execution jurisdiction and party type.

- Enforcement: Block; Recommendation
- Triggers: `base`
- Scope: All. Applied under the UK pack: the UK part of the row. The Swiss part is in the CH pack.
- Topics: exclusions
- Implemented in: SS-6

**Esign Comply records or checks**

- **Block.** Esign Comply blocks UK deeds in the generic flow and routes them according to execution jurisdiction and party type.

**Recommendations**

- **Recommendation.** Route UK deeds outside the generic flow. Verify the UK execution formalities for the jurisdiction and party.

Legal sources: [Law of Property (Miscellaneous Provisions) Act s.1](https://www.legislation.gov.uk/ukpga/1989/34/section/1); [Companies Act s.44](https://www.legislation.gov.uk/ukpga/2006/46/section/44)

## Fixed strings

Wording served in `required_strings[]` when its rule fires. Render verbatim strings exactly; fill every element of an element list.

### `signer_information`

signer information. Rule EU-15, prompt block `uk.core`, kind `verbatim`.

```text
{Company} uses Esign Comply to record this event on its behalf. See {Company}'s Privacy Notice for purposes and roles.
```

Legal sources: [GDPR Arts. 7, 13–14](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng)

### `review_or_correct`

pre-contract and confirmation. Rule EU-09, prompt block `uk.core`, kind `verbatim`.

```text
Review or correct your details
```

Legal sources: [Consumer Contracts Regulations](https://www.legislation.gov.uk/uksi/2013/3134)

### `download_or_print_terms`

pre-contract and confirmation. Rule EU-09, prompt block `uk.core`, kind `verbatim`.

```text
Download or print the exact terms
```

Legal sources: [Consumer Contracts Regulations](https://www.legislation.gov.uk/uksi/2013/3134)

## Exclusions

A blocked category returns `422 document_type_excluded` at session creation. A warning category proceeds and the warning is recorded.

| ID | Category | Treatment | Rule | Legal sources |
|---|---|---|---|---|
| `UK/ew-deeds` | England and Wales: deeds | Block the generic route; individual signatures generally require physically present witnessing, attestation and delivery. Companies may use alternative execution routes. | EU-20 | [Law Commission report](https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/912233/Electronic-Execution-Report.pdf); [Companies Act s.44](https://www.legislation.gov.uk/ukpga/2006/46/section/44) |

## Sources watched

- [UK eIDAS amendment](https://www.legislation.gov.uk/uksi/2019/89/contents)
- [ECA 2000 s.7](https://www.legislation.gov.uk/ukpga/2000/7/section/7)
- [Law of Property (Miscellaneous Provisions) Act s.1](https://www.legislation.gov.uk/ukpga/1989/34/section/1)
- [Companies Act s.44](https://www.legislation.gov.uk/ukpga/2006/46/section/44)
- [Consumer Contracts Regulations](https://www.legislation.gov.uk/uksi/2013/3134)
- [ICO guide to eIDAS](https://ico.org.uk/for-organisations/guide-to-eidas/what-is-the-eidas-regulation)

## Changelog

Initial version.
