# United States, Federal (US-FED)

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

Source: https://esigncomply.com/docs/jurisdictions/us-fed

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 | `US-FED` |
| Version | 2026-11-21 |
| Effective | 2026-11-21 |
| Review state | research draft |
| Status | active |
| Prompt block | `us.core` |
| API | `GET /v1/jurisdictions/US-FED` |

The Federal pack carries ESIGN, the common core of the Uniform Electronic Transactions Act, the federal online-assent case law and the federal evidence rules. It is the baseline for every U.S. record: a state pack holds only differences from US-FED, and a state without a pack uses US-FED alone. Scope "All" means every record under the US-FED pack, "Consumer" means US-FED sessions whose signer class is consumer, and "Signature" means nda, contract, and other signature profiles.

## Coverage

Covered: esign statute, online assent, auto renewal, consumer consent, retention, copies, attribution, evidence, evidence wording, electronic agents, exclusions.

Not covered: fda part 11, irs esignature, remote online notarization, hipaa authorizations, notarization, state specific rules without a pack.

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).

### US-01 Explicit intent action and exact notice text {#us-01}

A record cannot be sealed without an explicit intent action by the signer (checkbox plus button, button with matching notice, typed name, drawn signature, or passkey) and the exact notice text shown.

- Enforcement: Block
- Triggers: `base`
- Scope: All
- Topics: esign statute
- Implemented in: Steps S9, S10

**Esign Comply records or checks**

- **Block.** Esign Comply does not seal a record without an explicit intent action by the signer (checkbox plus button, button with matching notice, typed name, drawn signature, or passkey) and the exact notice text shown.

Legal sources: [Electronic signature requires "intent to sign": 15 U.S.C. § 7006(5)](https://www.law.cornell.edu/uscode/text/15/7006); UETA § 2(8)

### US-02 Record bound to document version hash {#us-02}

Every record is bound to the SHA-256 hash of each exact document version. The verification endpoint recomputes and confirms the match.

- Enforcement: Block
- Triggers: `base`
- Scope: All
- Topics: esign statute, evidence
- Implemented in: DV-2, SDK-3, E1

**Esign Comply records or checks**

- **Block.** Esign Comply checks that the record is bound to the SHA-256 hash of each exact document version. The verification endpoint recomputes and confirms the match. (checks: CR-08)

Legal sources: ["Attached to or logically associated with" the record: 15 U.S.C. § 7006(5)](https://www.law.cornell.edu/uscode/text/15/7006); [New York regulation: linked "during transmission and storage": NY ITS ESRA regulation](https://its.ny.gov/electronic-signatures-and-records-act-esra-regulation)

### US-03 Immutable, retrievable document versions {#us-03}

Document versions are immutable, individually identified, and retrievable for the full retention period.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: esign statute, retention
- Implemented in: Section 13.3, RT-1

**Esign Comply records or checks**

- **Service.** Esign Comply keeps document versions immutable, individually identified, and retrievable for the full retention period.

Legal sources: [Accurate reflection of the information: 15 U.S.C. § 7001(d)(1)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-04 Agreement to transact electronically {#us-04}

The ceremony records the signer's agreement to transact electronically for the transaction, and the interface offers a way to decline. For acceptances the agreement is recorded from context; for signature profiles the notice text must state that the signer agrees to sign electronically.

- Enforcement: Warn; Recommendation
- Triggers: `base`
- Scope: All
- Topics: esign statute
- Implemented in: Prompt rules, CR-12

**Esign Comply records or checks**

- **Warn.** Esign Comply checks that the ceremony records the signer's agreement to transact electronically for the transaction. For acceptances the agreement is recorded from context; for signature profiles the notice text must state that the signer agrees to sign electronically. (checks: CR-12)

**Recommendations**

- **Recommendation.** State in the notice that the signer agrees to sign or transact electronically, and give the signer a way to decline.

Legal sources: UETA § 5(b) and (c); [ESIGN, 15 U.S.C. § 7001(b)(2)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-05 Review step before the final act {#us-05}

Signature profiles and purchases include a review step before the final act, and the record shows it was presented.

- Enforcement: Warn; Recommendation
- Triggers: `base`
- Scope: Signature, purchase contexts
- Topics: esign statute, payment
- Implemented in: Step S6, CR-13

**Esign Comply records or checks**

- **Warn.** Esign Comply checks that signature profiles and purchases include a review step before the final act, and that the record shows it was presented. (checks: CR-13)

**Recommendations**

- **Recommendation.** Show a review step before the final act in signature and purchase flows, so the signer can catch and correct errors.

Legal sources: UETA § 10(2): an individual may avoid an erroneous record if the automated system gave no opportunity to prevent or correct the error

### US-06 Electronic agents and human-only profiles {#us-06}

When an automation or AI agent performs the act, the record carries `actor_type: electronic_agent`, the principal, and the authorization reference. Human-only profiles reject non-trusted events.

- Enforcement: Block for human profiles
- Triggers: `base`
- Scope: All
- Topics: esign statute, electronic agents
- Implemented in: SDK-6, section 13.8

**Esign Comply records or checks**

- **Block.** Block for human profiles: human-only profiles reject non-trusted events. When an automation or AI agent performs the act, the record carries `actor_type: electronic_agent`, the principal, and the authorization reference.

Legal sources: [15 U.S.C. § 7001(h)](https://www.law.cornell.edu/uscode/text/15/7001); UETA § 14

### US-07 Technology-neutral signature methods {#us-07}

The product accepts any signature method and never describes one method as legally required. Documentation states that the method affects evidentiary strength, not validity.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: esign statute
- Implemented in: Section 8.4

**Esign Comply records or checks**

- **Service.** Esign Comply accepts any signature method and never describes one method as legally required. Its documentation states that the method affects evidentiary strength, not validity.

Legal sources: [Technology neutrality: 15 U.S.C. § 7002](https://www.law.cornell.edu/uscode/text/15/7002); [Technology neutrality: 15 U.S.C. § 7004](https://www.law.cornell.edu/uscode/text/15/7004)

### US-08 Affirmative act of assent {#us-08}

Assent must be an affirmative act. Pre-checked boxes, assent by continued browsing, and assent inferred from page load are rejected.

- Enforcement: Block
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: SDK-5, SDK-6, CR-01

**Esign Comply records or checks**

- **Block.** Esign Comply checks that assent is an affirmative act. It rejects pre-checked boxes, assent by continued browsing, and assent inferred from page load. (checks: CR-01)

Legal sources: [Nguyen v. Barnes & Noble](https://openjurist.org/763/f3d/1171/nguyen-v-barnes-noble-inc); [Specht v. Netscape](https://law.justia.com/cases/federal/appellate-courts/F3/306/17/642323/); [Kauders v. Uber](https://law.justia.com/cases/massachusetts/supreme-court/volumes/486/486mass557.html)

### US-09 Notice names action and agreement; label matches {#us-09}

The notice names the specific action and the specific agreement, and the action control's label matches the notice. Example: notice "By clicking 'Agree and continue', you agree to the Terms of Service"; button "Agree and continue". Vague wording such as "by clicking below" is flagged.

- Enforcement: Block when notice or label is missing; Warn on mismatch heuristics
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: CR-02, CR-03

**Esign Comply records or checks**

- **Block.** Block when notice or label is missing: Esign Comply checks that the notice is present and names the specific action and the specific agreement, and that the action control has a label. (checks: CR-02)
- **Warn.** Warn on mismatch heuristics: Esign Comply checks that the action control's label matches the notice. Vague wording such as "by clicking below" is flagged. (checks: CR-03)

Legal sources: [Berman v. Freedom Financial (9th Cir. 2022): a click manifests assent only if the user is explicitly advised it will](https://openjurist.org/30/f4th/849/daniel-berman-v-freedom-financial-network-llc); [Chabolla v. ClassPass: button text that did not match the notice](https://cdn.ca9.uscourts.gov/datastore/opinions/2025/02/27/23-15999.pdf); [Godun v. JustAnswer (9th Cir. 2025): button text alone cannot replace an explicit advisal](https://law.justia.com/cases/federal/appellate-courts/ca9/24-2095/24-2095-2025-04-15.html); [9th Cir. No. 25-7161 (Nov. 2026) (unpublished memorandum)](https://cdn.ca9.uscourts.gov/datastore/memoranda/2026/11/05/25-7161.pdf)

### US-10 Notice placement in the same viewport {#us-10}

The notice sits above or directly beside the action control, in the same viewport, visible without scrolling at the moment of assent. The SDK records bounding boxes and viewport size.

- Enforcement: Block if not in viewport; Warn on placement below the control
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: CR-04

**Esign Comply records or checks**

- **Block.** Block if not in viewport: Esign Comply checks that the notice and the action control are in the same viewport, with the notice visible without scrolling at the moment of assent. The SDK records bounding boxes and viewport size. (checks: CR-04)
- **Warn.** Warn on placement below the control: Esign Comply checks that the notice sits above or directly beside the action control. (checks: CR-04)

Legal sources: [Specht v. Netscape (submerged screen)](https://law.justia.com/cases/federal/appellate-courts/F3/306/17/642323/); [Meyer v. Uber (2d Cir. 2017) (spatially and temporally coupled)](https://opencasebook.org/casebooks/19251-contracts-2026/resources/11.1.4-meyer-v-uber-technologies-inc/); [Chabolla v. ClassPass (outside the natural flow)](https://cdn.ca9.uscourts.gov/datastore/opinions/2025/02/27/23-15999.pdf); [Tejon v. Zeus Networks (11th Cir. 2026)](https://media.ca11.uscourts.gov/opinions/pub/files/202411114.pdf); [Cruz v. Tapestry (Cal. Ct. App. 2025) (small gray notice beneath a prominent button)](https://www.lcwlegal.com/news/enforcing-arbitration-agreements-court-declines-to-enforce-sign-in-wrap-arbitration-agreement-that-was-visually-overshadowed-by-other-elements-on-checkout-page)

### US-11 Terms links look like links {#us-11}

Links to terms look like links: a colour that contrasts with body text, not underline alone. The SDK records computed styles for link and body text.

- Enforcement: Warn
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: CR-05

**Esign Comply records or checks**

- **Warn.** Esign Comply measures whether links to terms look like links: a colour that contrasts with body text, not underline alone. The SDK records computed styles for link and body text. (checks: CR-05)

Legal sources: [Berman v. Freedom Financial (9th Cir. 2022)](https://openjurist.org/30/f4th/849/daniel-berman-v-freedom-financial-network-llc); [Cullinane v. Uber](https://www.faegredrinker.com/-/media/files/insights_db/publications/2018/08/cullinane-v-uber.pdf?la=en&hash=D30D0AFB9465944EF83BCE65BEEB36F44153BF77); [Meyer v. Uber (2d Cir. 2017)](https://opencasebook.org/casebooks/19251-contracts-2026/resources/11.1.4-meyer-v-uber-technologies-inc/)

### US-12 Legible notice text {#us-12}

Notice text is legible: font size at least that of surrounding body text and a contrast ratio of at least 4.5 to 1. The threshold is an engineering proxy, not a legal standard.

- Enforcement: Warn
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: CR-06

**Esign Comply records or checks**

- **Warn.** Esign Comply measures whether notice text is legible: font size at least that of surrounding body text and a contrast ratio of at least 4.5 to 1. The threshold is an engineering proxy, not a legal standard. (checks: CR-06)

Legal sources: [Berman v. Freedom Financial (9th Cir. 2022) (tiny gray font)](https://openjurist.org/30/f4th/849/daniel-berman-v-freedom-financial-network-llc); [Tejon v. Zeus Networks (11th Cir. 2026) (dim gray)](https://law.justia.com/cases/federal/appellate-courts/ca11/24-11114/24-11114-2026-05-01.html); [Chabolla v. ClassPass (light gray)](https://cdn.ca9.uscourts.gov/datastore/opinions/2025/02/27/23-15999.pdf)

### US-13 Visually distinct assent region {#us-13}

The SDK counts competing action controls in the viewport and flags an assent region that is not visually distinct.

- Enforcement: Warn
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: CR-07

**Esign Comply records or checks**

- **Warn.** The SDK counts competing action controls in the viewport, and Esign Comply flags an assent region that is not visually distinct. (checks: CR-07)

Legal sources: [Cullinane v. Uber: "If everything on the screen is written with conspicuous features, then nothing is conspicuous"](https://www.faegredrinker.com/-/media/files/insights_db/publications/2018/08/cullinane-v-uber.pdf?la=en&hash=D30D0AFB9465944EF83BCE65BEEB36F44153BF77); [Davitashvili v. Grubhub (2d Cir. 2025) (enforced; concurrence called the interface "likely the high-water mark")](https://clsbluesky.law.columbia.edu/2025/04/03/cleary-gottlieb-discusses-second-circuit-decision-on-consumer-arbitration-agreements/)

### US-14 Working terms link serving registered version {#us-14}

At ceremony time the terms link resolves and serves content whose hash equals the registered version.

- Enforcement: Block
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: SDK-4, CR-08

**Esign Comply records or checks**

- **Block.** Esign Comply checks at ceremony time that the terms link resolves and serves content whose hash equals the registered version. (checks: CR-08)

Legal sources: [9th Cir. No. 25-328 (Aug. 2025) (unpublished memorandum): an inoperable link meant no mutual assent](https://cdn.ca9.uscourts.gov/datastore/memoranda/2025/08/20/25-328.pdf)

### US-15 Capture of the rendered assent region {#us-15}

The assent region as rendered is captured (markup, computed styles, layout metrics) with device class, browser, viewport, orientation, and locale, then hashed and stored.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: online assent, evidence
- Implemented in: Step S7, SDK-5

**Esign Comply records or checks**

- **Service.** Esign Comply captures the assent region as rendered (markup, computed styles, layout metrics) with device class, browser, viewport, orientation, and locale, then hashes and stores it.

Legal sources: [The screen is judged from the user's perspective: Meyer v. Uber (2d Cir. 2017)](https://opencasebook.org/casebooks/19251-contracts-2026/resources/11.1.4-meyer-v-uber-technologies-inc/); [Dawson v. Target (N.D. Cal. No. 3:24-cv-08167): no basis to find the plaintiff was presented with the screens in the company's declaration](https://www.govinfo.gov/content/pkg/USCOURTS-cand-3_24-cv-08167/pdf/USCOURTS-cand-3_24-cv-08167-0.pdf)

### US-16 Checks run at the actual viewport {#us-16}

Checks US-10 to US-13 run at the viewport actually used. The conformance checker also replays test ceremonies at standard mobile and desktop sizes.

- Enforcement: Warn
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: Section 12.6

**Esign Comply records or checks**

- **Warn.** Esign Comply runs checks US-10 to US-13 at the viewport actually used. The conformance checker also replays test ceremonies at standard mobile and desktop sizes.

Legal sources: [Meyer v. Uber (2d Cir. 2017)](https://opencasebook.org/casebooks/19251-contracts-2026/resources/11.1.4-meyer-v-uber-technologies-inc/); [Keebaugh v. Warner Bros.](https://www.govinfo.gov/content/pkg/USCOURTS-ca9-22-55982/pdf/USCOURTS-ca9-22-55982-0.pdf)

### US-17 Transaction context and checkbox method {#us-17}

Sessions declare a transaction context: `account_signup`, `one_time_purchase`, `free_trial`, `auto_renewal`, `contract_signature`, `nda`, `policy_update`, `other`. Purchase, trial, and renewal contexts require the checkbox method. The checkbox requirement is an Esign Comply design policy, not a rule stated by any court (US-07).

- Enforcement: Block
- Triggers: `base`
- Scope: All
- Topics: online assent, payment, auto renewal
- Implemented in: SS-2, CR-09

**Esign Comply records or checks**

- **Block.** Esign Comply checks that the session declares a transaction context (`account_signup`, `one_time_purchase`, `free_trial`, `auto_renewal`, `contract_signature`, `nda`, `policy_update`, `other`) and that purchase, trial, and renewal contexts use the checkbox method. The checkbox requirement is an Esign Comply design policy, not a rule stated by any court (US-07). (checks: CR-09)

Legal sources: [Context matters and one-off or renewal transactions get stricter scrutiny: Sellers v. JustAnswer](https://case-law.vlex.com/vid/sellers-v-justanswer-llc-1081469097); [Chabolla v. ClassPass](https://cdn.ca9.uscourts.gov/datastore/opinions/2025/02/27/23-15999.pdf); [Cruz v. Tapestry, 113 Cal.App.5th 943 (2025) (court noted the merchant could have required a checkbox)](https://www.lcwlegal.com/news/enforcing-arbitration-agreements-court-declines-to-enforce-sign-in-wrap-arbitration-agreement-that-was-visually-overshadowed-by-other-elements-on-checkout-page); [Explicit-advisal sign-in wraps have also been enforced in purchase flows: N.D. Cal. No. 3:24-cv-03980](https://www.govinfo.gov/content/pkg/USCOURTS-cand-3_24-cv-03980/pdf/USCOURTS-cand-3_24-cv-03980-0.pdf)

### US-18 Material terms updates and outstanding signers {#us-18}

When a material new version is published, the API reports which signers are outstanding. The generated prompt recommends that the customer's tool build a blocking screen with an unchecked checkbox and a confirm button. Earlier acceptances stay on record.

- Enforcement: Service; Recommendation; Report
- Triggers: `base`
- Scope: All
- Topics: online assent
- Implemented in: DV-4, `GET /signers/{id}/status`

**Esign Comply records or checks**

- **Service.** When a material new version is published, the Esign Comply API reports which signers are outstanding. Earlier acceptances stay on record.

**Recommendations**

- **Recommendation.** Before a material terms update takes effect, notify users and present a blocking screen with an unchecked checkbox and a confirm button.

**What you can send us**

- **Report.** The customer may send its own evidence of the terms-update notice it gave users (`notice.sent`). Esign Comply seals it on receipt as customer-supplied material and does not verify it. (supplement types: `notice.sent`)

Legal sources: [Good v. Uber (Mass. 2024)](https://law.justia.com/cases/massachusetts/supreme-court/2024/sjc-13490-0.html)

### US-19 Viewing recorded as measured events {#us-19}

Viewing is recorded as measured events only: link opened, time visible, scroll depth. The product never reports that a signer "read" a document.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: online assent, evidence
- Implemented in: Step S6

**Esign Comply records or checks**

- **Service.** Esign Comply records viewing as measured events only: link opened, time visible, scroll depth. It never reports that a signer "read" a document.

Legal sources: [Notice and assent, not reading, are the test: Meyer v. Uber (2d Cir. 2017)](https://opencasebook.org/casebooks/19251-contracts-2026/resources/11.1.4-meyer-v-uber-technologies-inc/); [Actual viewing as evidence: Kauders v. Uber](https://law.justia.com/cases/massachusetts/supreme-court/volumes/486/486mass557.html)

### US-20 Automatic renewal consent and receipt {#us-20}

For `auto_renewal` contexts the ceremony requires express affirmative consent to the renewal terms, presented clearly and conspicuously in visual proximity to the consent control (Esign Comply policy: a separate unchecked control). The renewal terms include the five California disclosures (section 12.8). It stores the exact renewal text and delivers a retainable receipt (SR-7) that carries the customer's acknowledgment content. The seller remains responsible for that content, including the cancellation policy. As an Esign Comply default, not a statutory period, it keeps these records for at least three years or one year after termination, whichever is longer (RT-10); neither statute cited here sets a retention period. This is the Federal-pack default for every U.S. consumer; state packs add state-specific style tests, disclosures, reminders, and cancellation steps (CA-08 to CA-10, NY-03 to NY-07, MA-05 to MA-07, and the renewal rows of the other state packs).

- Enforcement: Block; Service; Obligation; Report
- Triggers: `base`
- Scope: Consumer
- Topics: auto renewal, cancellation, payment, retention
- Implemented in: CR-10, SR-7, RT-10

**Esign Comply records or checks**

- **Block.** For `auto_renewal` contexts, Esign Comply checks that the ceremony captured express affirmative consent to the renewal terms, presented clearly and conspicuously in visual proximity to the consent control (Esign Comply policy: a separate unchecked control), and that the renewal terms include the five California disclosures (section 12.8). (checks: CR-10; adds steps: `renewal_terms.presented`, `renewal_consent.captured`)
- **Service.** Esign Comply stores the exact renewal text and delivers a retainable receipt (SR-7) that carries the customer's acknowledgment content. As an Esign Comply default, not a statutory period, it keeps these records for at least three years or one year after termination, whichever is longer (RT-10).

**Your obligations**

- **Obligation.** Seller: clearly disclose material terms before taking billing information, get express informed consent before charging, and provide a simple way to stop recurring charges. (duty holder: Seller)

**What you can send us**

- **Report.** The customer may send its own evidence of a cancellation request it received (`cancellation.requested`). Esign Comply seals it on receipt as customer-supplied material and does not verify it. (supplement types: `cancellation.requested`)

Legal sources: [ROSCA requires express informed consent before charging: 15 U.S.C. § 8403](https://www.law.cornell.edu/uscode/text/15/8403); [Express affirmative consent and a retainable acknowledgment: Cal. Bus. & Prof. Code § 17602](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?sectionNum=17602&lawCode=BPC); [Required offer terms: Cal. Bus. & Prof. Code § 17601](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?sectionNum=17601&lawCode=BPC)

### US-21 Pre-consent disclosure of electronic-records rights {#us-21}

Before consent, the signer sees a clear and conspicuous statement of: any right to receive the record on paper; the right to withdraw consent and any conditions, consequences, or fees; whether consent covers this transaction only or categories of records; how to withdraw and how to update contact details; how to get a paper copy and any fee. The API rejects a consent event if the registered disclosure lacks any element.

- Enforcement: Block; Obligation
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent
- Implemented in: Step S3, disclosure template with required fields

**Esign Comply records or checks**

- **Block.** Esign Comply checks that the registered disclosure contains each element (any right to receive the record on paper; the right to withdraw consent and any conditions, consequences, or fees; whether consent covers this transaction only or categories of records; how to withdraw and how to update contact details; how to get a paper copy and any fee) and that it was presented before consent. The API rejects a consent event if the registered disclosure lacks any element. (checks: CR-16; adds steps: `disclosure.presented`)

**Your obligations**

- **Obligation.** Customer (record provider): give the consumer the required pre-consent disclosure. Esign Comply checks only that each element is present in the registered text. (duty holder: Customer (record provider))

Legal sources: [15 U.S.C. § 7001(c)(1)(A) and (B)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-22 Hardware and software requirements statement {#us-22}

The disclosure states the hardware and software needed to access and retain the records.

- Enforcement: Block; Obligation
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent
- Implemented in: Step S3

**Esign Comply records or checks**

- **Block.** Esign Comply checks that the registered disclosure states the hardware and software needed to access and retain the records. (checks: CR-16; adds steps: `disclosure.presented`)

**Your obligations**

- **Obligation.** Customer (record provider): state accurately the hardware and software the consumer needs to access and keep the records. (duty holder: Customer (record provider))

Legal sources: [15 U.S.C. § 7001(c)(1)(C)(i)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-23 Access demonstration for the delivery format {#us-23}

The consumer consents, or confirms consent, electronically in a way that reasonably demonstrates access to the format that will be used. Default mechanism: Esign Comply serves a sample in the delivery format containing a code; the signer enters the code.

- Enforcement: Block
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent
- Implemented in: Step S4

**Esign Comply records or checks**

- **Block.** Esign Comply checks that the consumer consented, or confirmed consent, electronically in a way that reasonably demonstrates access to the format that will be used. Default mechanism: Esign Comply serves a sample in the delivery format containing a code; the signer enters the code. (checks: CR-16; adds steps: `access.demonstrated`)

Legal sources: [15 U.S.C. § 7001(c)(1)(C)(ii)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-24 Affirmative electronic-records consent {#us-24}

Consent is an affirmative act on an unchecked control and is stored with the disclosure version.

- Enforcement: Block
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent
- Implemented in: Step S5

**Esign Comply records or checks**

- **Block.** Esign Comply checks that consent is an affirmative act on an unchecked control, and stores it with the disclosure version. (checks: CR-16; adds steps: `econsent.given`)

Legal sources: [15 U.S.C. § 7001(c)(1)(A)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-25 Withdrawal of electronic-records consent {#us-25}

Withdrawal: an API endpoint and a link in every receipt. Withdrawal is timestamped, sent to the customer by webhook, and prospective only; earlier records remain.

- Enforcement: Service; Obligation
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent, withdrawal
- Implemented in: `POST /signers/{id}/consents/withdraw`, `consent.withdrawn`

**Esign Comply records or checks**

- **Service.** Esign Comply provides withdrawal through an API endpoint and a link in every receipt. Withdrawal is timestamped, sent to the customer by webhook, and prospective only; earlier records remain.

**Your obligations**

- **Obligation.** Customer: after a consumer withdraws consent, stop relying on electronic delivery to satisfy a writing requirement for that consumer. (duty holder: Customer)

Legal sources: [15 U.S.C. § 7001(c)(1)(B)(iii), (c)(4)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-26 Material change to hardware or software requirements {#us-26}

When the customer marks a change to hardware or software requirements as material, affected consumers are flagged; electronic delivery sessions for them require the revised statement, a no-fee withdrawal option, and a new access demonstration.

- Enforcement: Block; Obligation; Report
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent
- Implemented in: Disclosure versioning, step S4

**Esign Comply records or checks**

- **Block.** When the customer marks a change to hardware or software requirements as material, Esign Comply flags affected consumers; electronic delivery sessions for them require the revised statement, a no-fee withdrawal option, and a new access demonstration. (adds steps: `disclosure.presented`, `access.demonstrated`)

**Your obligations**

- **Obligation.** Customer (record provider): before a material change in hardware or software requirements, give affected consumers the revised requirements and the right to withdraw without fees. (duty holder: Customer (record provider))

**What you can send us**

- **Report.** The customer may send its own evidence of the notice of revised requirements it gave affected consumers (`notice.sent`). Esign Comply seals it on receipt as customer-supplied material and does not verify it. (supplement types: `notice.sent`)

Legal sources: [15 U.S.C. § 7001(c)(1)(D)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-27 Paper-copy requests {#us-27}

Paper-copy requests made in the signer view are sealed as an annotation, and the configured fee disclosure is shown. A request the customer receives by its own channels, and the delivery of the paper copy, are reported as supplements (`paper_copy.delivered`). Fulfilment is the customer's responsibility.

- Enforcement: Service; Obligation; Report
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent, copies
- Implemented in: Annotation `paper_copy_requested`; supplement `paper_copy.delivered`

**Esign Comply records or checks**

- **Service.** Esign Comply seals paper-copy requests made in the signer view as an annotation (`paper_copy_requested`) and shows the configured fee disclosure.

**Your obligations**

- **Obligation.** Customer: provide a requested paper copy in the way the disclosure describes, charging no more than the disclosed fee. (duty holder: Customer)

**What you can send us**

- **Report.** A request the customer receives by its own channels, and the delivery of the paper copy, are reported as supplements (`paper_copy.delivered`). Esign Comply seals it on receipt as customer-supplied material and does not verify it. (supplement types: `paper_copy.delivered`)

Legal sources: [15 U.S.C. § 7001(c)(1)(B)(i) and (iv)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-28 Customer disclosures stored verbatim {#us-28}

Esign Comply stores customer disclosures verbatim and never alters, summarizes, or delays them.

- Enforcement: Service
- Triggers: `base`
- Scope: Consumer (section 9.2.3 prints no Scope column: these apply when a statute or regulation requires information to be given to a consumer in writing)
- Topics: consumer consent
- Implemented in: DV-1

**Esign Comply records or checks**

- **Service.** Esign Comply stores customer disclosures verbatim and never alters, summarizes, or delays them.

Legal sources: [15 U.S.C. § 7001(c)(2)(A)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-29 Downloadable, printable executed copies {#us-29}

Each signer can download the executed record and document with no technical measure that prevents saving or printing.

- Enforcement: Service; Recommendation
- Triggers: `base`
- Scope: All
- Topics: copies
- Implemented in: SR-1, SR-2, RT-9

**Esign Comply records or checks**

- **Service.** Esign Comply lets each signer download the executed record and document with no technical measure that prevents saving or printing.

**Recommendations**

- **Recommendation.** Do not deliver signed records in a way that blocks saving or printing, because such a record is not enforceable against the recipient.

Legal sources: UETA § 8(a) and (c): a record whose printing or storage is inhibited is not enforceable against the recipient; [15 U.S.C. § 7001(e)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-30 Accurate, reproducible record retention {#us-30}

Records are retained in a form that accurately reflects the information and can be reproduced, for the configured period. Early deletion is blocked except through the erasure workflow.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: retention
- Implemented in: Section 10.9

**Esign Comply records or checks**

- **Service.** Esign Comply retains records in a form that accurately reflects the information and can be reproduced, for the configured period. Early deletion is blocked except through the erasure workflow.

Legal sources: [15 U.S.C. § 7001(d)(1)](https://www.law.cornell.edu/uscode/text/15/7001); UETA § 12

### US-31 Continued access and export after cancellation {#us-31}

Records stay accessible to every party entitled to them, including the signer, for the retention period, and remain exportable for 12 months after the customer cancels (RT-3). After that, the customer's exported copy is the retained record unless a statutory floor or legal hold applies (RT-10). The statutory retention duty usually sits with the customer.

- Enforcement: Service; Obligation
- Triggers: `base`
- Scope: All
- Topics: retention, copies
- Implemented in: RT-3, RT-5, RT-9, RT-10

**Esign Comply records or checks**

- **Service.** Esign Comply keeps records accessible to every party entitled to them, including the signer, for the retention period, and exportable for 12 months after the customer cancels (RT-3). After that, the customer's exported copy is the retained record unless a statutory floor or legal hold applies (RT-10).

**Your obligations**

- **Obligation.** Customer: where another law requires keeping a record, keep an accurate, accessible copy for that period, including after exporting from Esign Comply. (duty holder: Customer)

Legal sources: [15 U.S.C. § 7001(d)(1)(B), (e)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-32 Append-only, hash-chained evidence {#us-32}

Evidence is append-only and hash-chained; any modification is detectable; roots are anchored outside the primary system. The technology is a product choice, not a statutory requirement.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: evidence
- Implemented in: Section 10.3

**Esign Comply records or checks**

- **Service.** Esign Comply keeps evidence append-only and hash-chained, so that any modification is detectable, and anchors roots outside the primary system. The technology is a product choice, not a statutory requirement.

Legal sources: [Accuracy: 15 U.S.C. § 7001(d)(1)(A)](https://www.law.cornell.edu/uscode/text/15/7001); New York: authenticity may be shown by circumstantial evidence without a mandatory signing-vendor affidavit; CPLR 4539(b)'s tamper-prevention foundation concerns image reproductions of hard-copy originals, not born-digital agreements. Esign Comply documents its protocols and their operation for the specific record as a product practice; [Knight v. New York & Presbyt. Hosp. (N.Y. 2024), reversing the 2023 decision](https://www.nycourts.gov/reporter/3dseries/2024/2024_05870.htm); [Sanchez v. NYC Med. Practice, P.C. (1st Dept. 2025)](https://www.nycourts.gov/reporter/3dseries/2025/2025_05206.htm); [Hash identity: FRE 902(14)](https://www.law.cornell.edu/rules/fre/rule_902)

### US-33 Server time and external timestamp {#us-33}

Every event carries Esign Comply server time; client-reported time is stored separately; an external timestamp token is attached.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: evidence
- Implemented in: EV-2, E4

**Esign Comply records or checks**

- **Service.** Esign Comply stamps every event with its server time, stores client-reported time separately, and attaches an external timestamp token.

Legal sources: [Made "at or near the time": FRE 803(6)](https://www.law.cornell.edu/rules/fre/rule_803)

### US-34 Attribution data on every record {#us-34}

Each record states how the signer was tied to the act: identifier, authentication or verification method, result, delivery channel and address, IP address, user agent, session.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: attribution, evidence
- Implemented in: Section 10.2

**Esign Comply records or checks**

- **Service.** Esign Comply states on each record how the signer was tied to the act: identifier, authentication or verification method, result, delivery channel and address, IP address, user agent, session.

Legal sources: Attribution "may be shown in any manner, including a showing of the efficacy of any security procedure": UETA § 9; [Espejo v. Southern California Permanente](https://law.justia.com/cases/california/court-of-appeal/2016/b262717.html); [Cal. Ct. App. A166785 (2024)](https://www4.courts.ca.gov/opinions/archive/A166785.PDF)

### US-35 Chain of custody for signature profiles {#us-35}

Signature profiles record the chain of custody: who initiated the session, how and to what address the document or code was delivered, when it was opened, how the signature was applied, and how the executed copy was returned.

- Enforcement: Service
- Triggers: `base`
- Scope: Signature
- Topics: attribution, evidence
- Implemented in: Steps S1 to S11

**Esign Comply records or checks**

- **Service.** For signature profiles, Esign Comply records the chain of custody: who initiated the session, how and to what address the document or code was delivered, when it was opened, how the signature was applied, and how the executed copy was returned.

Legal sources: [The facts found missing in Fabian, as quoted in Moncibaez](https://www.courtlistener.com/opinion/5304357/moncibaez-v-stericycle-inc-ca24/)

### US-36 Configurable assurance level {#us-36}

Assurance level is configurable and stated plainly on the record. Signature profiles default to L2.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: attribution
- Implemented in: Section 8.3

**Esign Comply records or checks**

- **Service.** Esign Comply makes the assurance level configurable and states it plainly on the record. Signature profiles default to L2.

Legal sources: UETA § 9; [Cal. Ct. App. A166785 (2024): evidence did not show only the employee could have signed](https://www4.courts.ca.gov/opinions/archive/A166785.PDF)

### US-37 One-click evidence package {#us-37}

One-click evidence package with record, document, hashes, chain proof, notice capture, attribution data, and a plain-language process description.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: evidence
- Implemented in: Section 10.6

**Esign Comply records or checks**

- **Service.** Esign Comply provides a one-click evidence package with record, document, hashes, chain proof, notice capture, attribution data, and a plain-language process description.

Legal sources: [FRE 901(b)(9)](https://www.law.cornell.edu/rules/fre/rule_901); [FRE 902(13), (14)](https://www.law.cornell.edu/rules/fre/rule_902)

### US-38 Custodian declaration under penalty of perjury {#us-38}

A named records custodian signs only an unsworn declaration under penalty of perjury in the applicable form in section 9.8.8. Describe the custodian's qualifications, how the original records were made at or near the time in the regular course and as a regular practice, why the process is accurate, the copy hash checks and the steps in the specific ceremony. Certify only Esign Comply's own records and observed facts, not customer assertions or signer identity. Explain the notice steps the litigant must handle. For California, note the printout presumption (Evid. Code § 1552) and retain the ceremony account. For New York, use only the CPLR 2106 affirmation for any applicable CPLR 4518 and CPLR 3122-a foundation. The protocol and specific account support authentication, but New York does not categorically require a vendor affidavit for born-digital agreements (Knight; Sanchez). Where the court requires a notarized affidavit, it is not offered in this version.

- Enforcement: Service; Obligation
- Triggers: `base`
- Scope: All
- Topics: evidence, evidence wording
- Implemented in: Section 10.8

**Esign Comply records or checks**

- **Service.** A named Esign Comply records custodian signs only an unsworn declaration under penalty of perjury in the applicable form in section 9.8.8. It describes the custodian's qualifications, how the original records were made at or near the time in the regular course and as a regular practice, why the process is accurate, the copy hash checks and the steps in the specific ceremony. It certifies only Esign Comply's own records and observed facts, not customer assertions or signer identity, and explains the notice steps the litigant must handle. A notarized affidavit is not offered in this version.

**Your obligations**

- **Obligation.** Litigant (customer as proponent): give the adverse party reasonable written notice before trial or hearing and make the record and declaration available for inspection. (duty holder: Litigant (customer as proponent))

Legal sources: [FRE 803(6)](https://www.law.cornell.edu/rules/fre/rule_803); [FRE 902(11), (13), (14)](https://www.law.cornell.edu/rules/fre/rule_902); [28 U.S.C. § 1746](https://www.govinfo.gov/content/pkg/USCODE-2024-title28/html/USCODE-2024-title28-partV-chap115-sec1746.htm); [United States v. Browne](https://www.courtlistener.com/opinion/4251248/united-states-v-tony-browne/); California authentication cases above; [California printout presumption: Evid. Code § 1552](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=EVID&sectionNum=1552); [New York: CPLR 2106](https://www.nysenate.gov/legislation/laws/CVP/2106); [New York: CPLR 4518](https://www.nysenate.gov/legislation/laws/CVP/4518); [New York: CPLR 3122-a](https://www.nysenate.gov/legislation/laws/CVP/3122-A); [Knight v. New York & Presbyt. Hosp. (N.Y. 2024)](https://www.nycourts.gov/reporter/3dseries/2024/2024_05870.htm); [Sanchez v. NYC Med. Practice, P.C. (1st Dept. 2025)](https://www.nycourts.gov/reporter/3dseries/2025/2025_05206.htm)

### US-39 Versioned public system description {#us-39}

A dated, versioned public system description for every release, so a declarant can describe the process in force on the date of any record.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: evidence
- Implemented in: Section 10.8

**Esign Comply records or checks**

- **Service.** Esign Comply publishes a dated, versioned public system description for every release, so a declarant can describe the process in force on the date of any record.

Legal sources: [FRE 901(b)(9)](https://www.law.cornell.edu/rules/fre/rule_901)

### US-40 Public verification of hash and ledger inclusion {#us-40}

Public verification of hash and ledger inclusion without trusting the customer.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: evidence
- Implemented in: Section 10.7

**Esign Comply records or checks**

- **Service.** Esign Comply offers public verification of hash and ledger inclusion without trusting the customer.

Legal sources: [FRE 902(14) committee note on hash identity](https://www.law.cornell.edu/rules/fre/rule_902)

### US-41 New York evidence package contents {#us-41}

For New York parties, the evidence package includes the signing protocol and tamper-prevention controls, both generally and as applied to the specific record, suitable for inclusion in a declaration, plus explicit intent evidence. This is a product practice for supporting authentication, not a categorical vendor-affidavit or CPLR 4539(b) requirement for born-digital agreements.

- Enforcement: Service
- Triggers: `base`
- Scope: All (NY)
- Topics: evidence
- Implemented in: `VERIFY.md`, system description

**Esign Comply records or checks**

- **Service.** For New York parties, Esign Comply includes in the evidence package the signing protocol and tamper-prevention controls, both generally and as applied to the specific record, suitable for inclusion in a declaration, plus explicit intent evidence. This is a product practice for supporting authentication, not a categorical vendor-affidavit or CPLR 4539(b) requirement for born-digital agreements.

Legal sources: [Knight, N.Y. 2024 (circumstantial proof sufficed on a venue motion)](https://www.nycourts.gov/reporter/3dseries/2024/2024_05870.htm); [Sanchez, 1st Dept. 2025 (signed agreement, certificate and audit log sufficed for the initial arbitration showing without a vendor affidavit)](https://www.nycourts.gov/reporter/3dseries/2025/2025_05206.htm)

### US-42 Optional signer age attestation {#us-42}

Optional signer age attestation. The evidence report states that the record does not establish capacity.

- Enforcement: Service; Recommendation
- Triggers: `base`
- Scope: All
- Topics: age
- Implemented in: Session `signer.age_attested`

**Esign Comply records or checks**

- **Service.** Esign Comply offers an optional signer age attestation (`signer.age_attested`). The evidence report states that the record does not establish capacity.

**Recommendations**

- **Recommendation.** Consider an age attestation step where minors may sign, since a minor may disaffirm a contract and the record does not establish capacity.

Legal sources: [Minors may disaffirm: Cal. Fam. Code § 6710](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=FAM&sectionNum=6710)

### US-43 No assertion of legal validity {#us-43}

The API never returns a field asserting legal validity. Evidence reports and certificates state what was recorded.

- Enforcement: Service
- Triggers: `base`
- Scope: All
- Topics: esign statute, evidence
- Implemented in: CERT-4

**Esign Comply records or checks**

- **Service.** The Esign Comply API never returns a field asserting legal validity. Evidence reports and certificates state what was recorded.

Legal sources: [ESIGN removes only the electronic-form objection: 15 U.S.C. § 7001(a)](https://www.law.cornell.edu/uscode/text/15/7001)

### US-44 New York: ESIGN and ESRA, not UETA {#us-44}

New York pack: for New York parties the rule set applies ESIGN and ESRA, not UETA-specific provisions (UETA § 5, § 10), and screens the ESRA § 307 exclusions (section 9.5). This rule is part of `US-FED` and fires for New York signers or New York governing law whether or not the `US-NY` pack (section 9.8.2) is enabled. This is an inference from the statute text, for counsel confirmation.

- Enforcement: Block for excluded types; Recommendation
- Triggers: `base`
- Scope: All (NY)
- Topics: esign statute, exclusions
- Implemented in: Section 9.5, SS-6

**Esign Comply records or checks**

- **Block.** Block for excluded types: for New York signers or New York governing law, Esign Comply screens the ESRA § 307 exclusions (section 9.5) and blocks the excluded document types.

**Recommendations**

- **Recommendation.** Confirm that New York transactions are assessed under ESIGN and ESRA rather than UETA-specific provisions.

Legal sources: [New York has not enacted UETA, so the 15 U.S.C. § 7002(a)(1) path is unavailable](https://www.law.cornell.edu/uscode/text/15/7002); [15 U.S.C. § 7001(a) applies to transactions in or affecting interstate commerce](https://www.law.cornell.edu/uscode/text/15/7001); [N.Y. State Tech. Law § 307](https://www.nysenate.gov/legislation/laws/STT/307)

## Fixed strings

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

### `econsent_heading`

us.consumer_econsent heading. Rule US-21, prompt block `us.consumer_econsent`, kind `verbatim`.

```text
Consent to receive records electronically
```

Legal sources: US-21, US-22, US-27; [15 U.S.C. § 7001(c)(1)(B)-(C)](https://www.law.cornell.edu/uscode/text/15/7001)

### `econsent_subheadings`

us.consumer_econsent heading: fixed sub-headings. Rule US-21, prompt block `us.consumer_econsent`, kind `elements`.

Elements:

- What you are agreeing to
- Whether this consent covers one transaction or all records
- Your right to receive paper copies
- How to request a paper copy after consenting, and any fee
- How to withdraw consent, and any conditions, consequences, or fees
- How to update your contact details
- What you need to access and keep the records

Legal sources: US-21, US-22, US-27; [15 U.S.C. § 7001(c)(1)(B)-(C)](https://www.law.cornell.edu/uscode/text/15/7001)

### `econsent_access_demonstration`

us.consumer_econsent access demonstration. Rule US-23, prompt block `us.consumer_econsent`, kind `verbatim`.

```text
To confirm you can open the records we will send, open this sample and enter the code shown inside it.
```

Legal sources: US-23

### `renewal_consent`

us.purchase renewal consent (unchecked; by Esign Comply policy separate from the terms checkbox). Rule US-20, prompt block `us.purchase`, kind `verbatim`.

```text
I agree that my subscription continues and renews automatically every {renewal term} at {price}{, which may change to {new price} on {date}} until I cancel. {Minimum purchase obligation, if any.} Cancellation policy: {cancellation policy}. I can cancel at {cancel path}.
```

Legal sources: US-20; [Offer terms: Cal. Bus. & Prof. Code § 17601](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?sectionNum=17601&lawCode=BPC)

### `typed_signature_notice`

signature.typed notice. Rule US-01, prompt block `signature.typed`, kind `verbatim`.

```text
By typing your name and clicking {button label}, you agree to sign this agreement electronically and to be bound by it.
```

Legal sources: US-01, US-04

## 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 |
|---|---|---|---|---|
| `US-FED/wills` | Wills, codicils, testamentary trusts | Blocked |  | [15 U.S.C. § 7003](https://www.law.cornell.edu/uscode/text/15/7003) |
| `US-FED/family-law` | Adoption, divorce, and other family-law documents | Blocked |  | [15 U.S.C. § 7003](https://www.law.cornell.edu/uscode/text/15/7003); [French Civil Code Art. 1175](https://www.legifrance.gouv.fr/codes/id/LEGISCTA000032006712/) |
| `US-FED/court-documents` | Court orders, notices, and official court documents | Blocked |  | [15 U.S.C. § 7003](https://www.law.cornell.edu/uscode/text/15/7003) |
| `US-FED/section-7003-notices` | Notices of utility cancellation; default, foreclosure, eviction for a primary residence; cancellation of health or life insurance; product recalls; hazardous-materials documents | Blocked |  | [15 U.S.C. § 7003](https://www.law.cornell.edu/uscode/text/15/7003) |
| `US-FED/ucc-records` | Records governed by the Uniform Commercial Code other than §§ 1-107 and 1-206 and Articles 2 and 2A | Blocked |  | [15 U.S.C. § 7003(a)(3)](https://www.law.cornell.edu/uscode/text/15/7003) |
| `US-FED/transferable-records` | Transferable records | Blocked (product scope: requires a single authoritative copy and a control system Esign Comply does not offer) |  | [ESIGN authorizes these under control rules: 15 U.S.C. § 7021](https://www.law.cornell.edu/uscode/text/15/7021) |
| `US-FED/notarization` | Documents requiring notarization or a public deed, including real-estate transfers | Blocked |  | [U.S.: product scope, not an ESIGN exclusion. Esign Comply does not perform, arrange or resell notarization in this version (N3); electronic and remote notarization is governed by state law (NASS)](https://www.nass.org/initiatives/remote-electronic-notarization); [ESIGN § 7001(g) permits a notary's electronic signature but does not supply one](https://www.law.cornell.edu/uscode/text/15/7001); [15 U.S.C. § 7003 does not exclude real-estate transfers](https://www.law.cornell.edu/uscode/text/15/7003); [Europe: German BGB § 311b](https://www.gesetze-im-internet.de/bgb/__311b.html); [Europe: Dutch Civil Code 3:89](https://wetten.overheid.nl/BWBR0005291/2025-07-01/); Europe: Swiss Code of Obligations Art. 216 |
| `US-FED/powers-of-attorney` | United States: powers of attorney and health-care directives | Blocked (state formality rules; product scope) |  | State law; [New York: N.Y. State Tech. Law § 307](https://www.nysenate.gov/legislation/laws/STT/307) |

## Retention floors

| Rule | What is kept | Floor | Legal sources |
|---|---|---|---|
| US-20 | Automatic-renewal consent records: the exact renewal text and the retainable receipt that carries the customer's acknowledgment content | At least three years or one year after termination, whichever is longer (RT-10). An Esign Comply default, not a statutory period. | Esign Comply default, not a statutory period; neither statute cited in US-20 sets a retention period (RT-10) |

## Evidence wording

Selected with `wording` when a certificate is requested. It changes the wording of the statement only, never the ceremony rules.

### Forum: Federal

- Rule: US-38
- Authentication: FRE 902(13) or (14): separately certify accurate system output or verified copy.
- Business records: FRE 803(6); for FRE 902(11), state knowledgeable source, keeping and regular practice.
- Declaration form: Sign and date the § 1746 unsworn declaration. For 902(11), state knowledgeable source, keeping and regular practice. For 902(13) or (14), separately certify accurate system output or verified copy. Check the separate rule if the certification is for foreign records or signed abroad.
- Timing wording: made at or near the time
- Notice reminder: Give reasonable written notice before trial or hearing and make record and certification available for inspection. No fixed interval.
- Notes: Analogue to FRE 902(13) and (14): Yes. What the statement must not claim there: System or copy authentication proves hearsay foundation, authorship, act time or truth. Limit in this version (Federal foreign elements): Verify the applicable criminal-penalty and notice rules before relying on a declaration involving foreign records or a foreign signing. Use testimony or another authorized procedure where the standard form is insufficient. Time evidence and ledger claims. RFC 3161 tokens. May say: A verified token supports existence of the matching datum by the authority's stated time, subject to validation and clock accuracy. Must not say: It proves exact creation or signing time, signer identity, truth or automatic admissibility. Hash matching. May say: The recomputed digest of identified bytes matches the identified sealed digest; matching source and export hashes support copy identity. Must not say: Matching hashes prove accuracy of the original, authorship or that no intermediate alteration occurred. Public ledger anchors. May say: The inclusion proof links the record commitment to an identified checkpoint; a verified public anchor corroborates existence of that checkpoint by the anchor time. Must not say: The product qualifies by default under Vermont, Arizona or Illinois blockchain statutes; anchoring proves underlying act time, attribution or truth. "Contemporaneous". May say: Product shorthand for the original record's timing; use the rule's words and distinguish server receipt, reported act time and certificate issuance. Must not say: The later certificate was itself made at the event, or "contemporaneous" is a statutory status.

Legal sources: [FRE 803(6)](https://www.law.cornell.edu/rules/fre/rule_803); [FRE 902](https://www.law.cornell.edu/rules/fre/rule_902); [28 U.S.C. § 1746](https://www.govinfo.gov/content/pkg/USCODE-2024-title28/html/USCODE-2024-title28-partV-chap115-sec1746.htm); [RFC 3161](https://www.rfc-editor.org/rfc/rfc3161.html); [FRE 902(14) and committee note](https://www.law.cornell.edu/rules/fre/rule_902); [12 V.S.A. § 1913](https://legislature.vermont.gov/statutes/section/12/081/01913); [A.R.S. § 44-7061](https://www.azleg.gov/ars/44/07061.htm); [205 ILCS 730/5 and /10](https://www.ilga.gov/Legislation/ILCS/Articles?ActID=4030&ChapterID=20&Print=True); [CPLR 4518](https://www.nysenate.gov/legislation/laws/CVP/4518); [G.L. c. 233 § 78](https://malegislature.gov/Laws/GeneralLaws/PartIII/TitleII/Chapter233/Section78)

## Sources watched

- [ESIGN: 15 U.S.C. § 7001](https://www.law.cornell.edu/uscode/text/15/7001)
- [ESIGN: 15 U.S.C. § 7002](https://www.law.cornell.edu/uscode/text/15/7002)
- [ESIGN: 15 U.S.C. § 7003](https://www.law.cornell.edu/uscode/text/15/7003)
- [ESIGN: 15 U.S.C. § 7004](https://www.law.cornell.edu/uscode/text/15/7004)
- [ESIGN: 15 U.S.C. § 7006](https://www.law.cornell.edu/uscode/text/15/7006)
- [ESIGN: 15 U.S.C. § 7021](https://www.law.cornell.edu/uscode/text/15/7021)
- [ROSCA: 15 U.S.C. § 8403](https://www.law.cornell.edu/uscode/text/15/8403)
- [Cal. Bus. & Prof. Code § 17601](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?sectionNum=17601&lawCode=BPC)
- [Cal. Bus. & Prof. Code § 17602](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?sectionNum=17602&lawCode=BPC)
- [Regulation Z: 12 CFR 1026.5](https://www.ecfr.gov/current/title-12/chapter-X/part-1026/subpart-A/section-1026.5)
- [Regulation E: 12 CFR 1005.4](https://www.ecfr.gov/current/title-12/chapter-X/part-1005/subpart-A/section-1005.4)
- [FRE 803](https://www.law.cornell.edu/rules/fre/rule_803)
- [FRE 901](https://www.law.cornell.edu/rules/fre/rule_901)
- [FRE 902](https://www.law.cornell.edu/rules/fre/rule_902)
- [28 U.S.C. § 1746](https://www.govinfo.gov/content/pkg/USCODE-2024-title28/html/USCODE-2024-title28-partV-chap115-sec1746.htm)

## Changelog

Initial version.
