Skip to content
Protocore Design Systemv1.6.9
Patterns / Legal

Legal document

A long-form policy: a sticky table-of-contents rail, numbered clauses, a definitions list, and a last-updated stamp.

LEGAL
Live · @protocore/pds
Legal

Terms of Service

Last updated

1. Acceptance of terms

By accessing the Protocore protocol, SDK, or console (the "Services"), you agree to be bound by these terms. If you are entering into this agreement on behalf of an organisation, you represent that you have authority to bind it.

2. The Services

Protocore provides settlement infrastructure that routes, nets, and finalizes value across connected rails. The Services are provided on a best-effort basis subject to the availability commitments in your order form.

3. Your data

You retain all rights to the transaction data you submit. We process it solely to operate the Services, maintain the sealed ledger, and meet our regulatory obligations. We never sell it.

4. Acceptable use

You may not use the Services to facilitate unlawful settlement, evade sanctions, or overwhelm shared infrastructure. We may suspend access where continued use presents a risk to the network.

5. Liability

To the maximum extent permitted by law, Protocore's aggregate liability is limited to the fees paid in the twelve months preceding the claim. Nothing here limits liability that cannot lawfully be limited.

Defined terms

Ledger
The append-only, cryptographically sealed record of every settled movement.
Rail
A connected settlement network — SEPA, card, wire, or an on-chain path.
Finality
The point at which a settled transfer is irrevocable on its rail.
Order form
The document setting out your plan, seats, and availability commitments.

When to use

Legal pages are read under duress — usually by someone looking for one clause. The template optimises for that: a sticky table-of-contents rail tracks the reader's place through a long document, clauses are numbered and headed so they're linkable and quotable, defined terms get a DefinitionList so meaning is unambiguous, and a last-updated stamp establishes which version you're bound to. Prose stays at a readable measure; nothing decorative competes with the words.

Use it for terms, privacy policies, DPAs, acceptable-use, and any long-form policy document.

Structure

01
Document header
An Eyebrow, a Display title, and a last-updated RelativeTime in its 'both' form so relative and absolute agree.
02
Sticky TOC rail
A vertical Steps list in a position:sticky aside, tracking the reader through the clauses on wide viewports.
03
Numbered clauses
Each clause is a Heading + Text section, numbered for linking, quoting, and cross-reference.
04
Defined terms
A DefinitionList pins the meaning of the load-bearing terms used throughout the document.

Key components

Open any component to read its full API and live examples.