Switzerland (CH)
Rules, fixed strings, exclusions, retention floors and fact keys of the CH pack, version 2026-11-21 (research draft).
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
- CH
- Version
- 2026-11-21
- Effective
- 2026-11-21
- Review state
- research draft
- Status
- active
- Prompt block
- ch.core
- API
- GET /v1/jurisdictions/CH
Applies to flows subject to Swiss law: a Swiss form screen, with permitted electronic written-form equivalents routed to Swiss QES plus Swiss qualified timestamp verification. Where electronic replacement of handwriting is permitted, use a ZertES-qualified electronic signature combined with a ZertES-qualified timestamp, subject to contrary statutory or contractual provisions. EU qualification does not establish Swiss qualification, and public deeds and other special forms need separate treatment.
Coverage
Covered
- swiss form screen
- swiss qes and qualified timestamp routing
- signature classification
- privacy notice
- minimal sdk capture
- processor agreement
- retention and erasure
- international transfers
Not covered
- qualified signatures
- notarization
- national special forms beyond the screen
- sector rules
- eu pre contract information and correction
- eu payment disclosures and button
- eu durable confirmation
- eu online withdrawal function
- eu language and intelligible terms
- eu evidence timestamp seal and validation rules
- eu trust service and nis2 classification
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 and Guidance and adoption.
Explicit act on a frozen document version
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack. The spec gives no Swiss-specific wording or source for this row; the EU text and sources are reused.
- 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 eIDAS Art. 3(9) to (12), 25; French Civil Code Art. 1367
Signature level classification
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack: EU qualification does not establish Swiss qualification; where electronic replacement of handwriting is permitted, use a ZertES-qualified electronic signature combined with a ZertES-qualified timestamp, subject to contrary statutory or contractual provisions (section 9.1). The spec gives no Swiss-specific wording for the classification; the EU text is reused and its article references are to eIDAS.
- 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.
Jurisdiction, signer and document category screen
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack as the Swiss form screen: public deeds and other special forms need separate treatment (section 9.1).
- 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 Swiss Code of Obligations Arts. 11, 14 and 216
EU minimal capture by default
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack. The spec gives no Swiss-specific wording or source for this row; the EU text and sources are reused.
- 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; ePrivacy Directive Art. 5(3)
Privacy information and distinct consent request
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack. The spec gives no Swiss-specific wording or source for this row; the EU text and sources are reused.
- 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
Data processing agreement before live keys
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack. The spec gives no Swiss-specific wording or source for this row; the EU text and sources are reused.
- 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
Retention, erasure and restriction
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack. The spec gives no Swiss-specific wording or source for this row; the EU text and sources are reused.
- 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; EDPB final blockchain guidelines
Hosting, access paths and transfers
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.
- Triggers
- base
- Scope
- All. Applied under the CH pack. The spec gives no Swiss-specific wording or source for this row; the EU text and sources are reused.
- 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; DPF decision; SCC decision
Swiss written form and Swiss QES routing
Block Swiss written-form documents in the generic flow. Verify Swiss QES plus Swiss qualified timestamp where an electronic equivalent is permitted, subject to contrary law or contract.
- Triggers
- base
- Scope
- All. Applied under the CH pack: the Swiss part of the row. EU qualification does not establish Swiss qualification (section 9.1). The UK part is in the UK pack.
- Implemented in
- SS-6
Esign Comply records or checks
- Block
Esign Comply blocks Swiss written-form documents in the generic flow and verifies Swiss QES plus Swiss qualified timestamp where an electronic equivalent is permitted, subject to contrary law or contract.
Recommendations
- Recommendation
Route Swiss statutory written-form documents outside the generic flow. Verify Swiss qualification and any applicable timestamp.
Legal sources Swiss CO Art. 14(2bis); Swiss Federal Office of Communications
Fixed strings
Wording served in required_strings[] when its rule fires. Render verbatim strings exactly; fill every element of an element list.
signer information · prompt block ch.core
{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
Exclusions
A blocked category returns 422 document_type_excluded at session creation. A warning category proceeds and the warning is recorded.
| Category | Treatment | Rule | Legal sources |
|---|---|---|---|
| Switzerland: any contract with a statutory written-form requirementCH/statutory-written-form | blockedBlocked from generic flow | EU-20 | |
| Documents requiring notarization or a public deed, including real-estate transfersCH/public-deed | blocked | EU-08 | Swiss Code of Obligations Art. 216; Swiss Code of Obligations Arts. 11, 14 and 216 |
Sources watched
Initial version.