bearomarkDocument signing

Sign documents. Yours stay yours.

Sealed in bearo, sent as a link. Recipients sign in the browser — nothing to install.

Check a signed document Got an envelope file? Sign it here

consulting-agreement.md

Sealed by Mara Winter <mara@winterstudio.example> — email verified 2026-09-02.

Consulting Agreement

Between Bearocratic OÜ and the Client, for advisory work.

1. Scope — the work described in Appendix A.

2. Term — twelve weeks from countersignature.

Sign with passkey

consulting-agreement.md (text/markdown)

sha256:18f4…ac06 — frozen · Fingerprint 13AA-8B58-B444

Document intact — bytes match the frozen hash.

Mara Winter (bearo) — valid key fdf7 2a08 8f18 f739 · email verified 2026-09-02 timestamp token attached
Carol Guest (guest) — valid key 94be caad 7094 9893 signed with a passkey — no bearo

VALID and COMPLETE

§ 01

Got an envelope?

Someone wants your signature. Here is the whole thing:

Open the signing link — or drop a received .envelope file into the signing page. You see exactly what you're signing before you touch anything.
Type your name and confirm with Touch ID, Face ID, or a security key.
From a link, the signed envelope goes back to the sender by itself. From a file, it downloads for you to send back. Keep a copy — it's your proof, forever.

Why this is safe

Read and signed in your browserReading, signing, checking — all in your browser. A signing link carries the envelope encrypted; the relay never holds the key. Anyone with the link can open it — treat the link like the document.
The file is the documentAn exported .envelope carries the document readable. Send it only over a channel you trust.
What you signed cannot changeChange a word, a signer, an addressee — the check fails. For everyone, forever.
Anyone can check it, any timeThe proof lives in the file, not in a company database. Checking is free, always.

§ 02

Know who signed

Seals can carry a verified email. A signing link is checked before the envelope opens; a file invitation carries a fingerprint to compare by eye.

the invitation — pasted into any email or chat

I've sent you a sealed document to sign: consulting-agreement.md.

Open this link: https://bearomark.io/s#6XcEsgQh…

You can read it and sign in your browser with Touch ID, Face ID, or a security key. Free, no account, nothing to install. When you sign, the envelope returns to me automatically.

Envelope fingerprint: 13AA-8B58-B444

The signing page shows the same fingerprint — if they differ, don't sign, and tell me.

§ 03

Want to send documents for signing?

Sealing happens in bearo, the encrypted notes app: write a note or pick a PDF, seal it, create a signing link — or export the envelope file and send it yourself. Free beta; signing and checking stay free for everyone you send to. The whole sending flow →

bearo — consulting-agreement.md

# Consulting Agreement

Between Bearocratic OÜ and the Client, for envelope-grade advisory work.

1. Scope — the work described in Appendix A.

2. Term — twelve weeks from countersignature.

3. Fees — as agreed, invoiced monthly.

Press your mark

Signing consulting-agreement.md freezes its exact bytes into the envelope — a changed comma is a new envelope.

Sign asMara Winter Passphrase••••••••••••

CancelSign

consulting-agreement.md

Mara Winter2026-09-02T10:00:12Z

Fingerprint 13AA-8B58-B444

VALID — sealed and timestamped

Create signing linkExport

§ 04

For the technical

The claims above, in mechanism form — check the math yourself.

One portable fileAn envelope is JSON: the document bytes, a SHA-256 hash frozen at sealing, and a chain of signatures each covering everything before it — edit any link and every later one breaks.
Real keys, stated plainlySenders sign with a per-vault ed25519 key; guests with a WebAuthn passkey (ES256) challenged by the envelope's exact state. Every public key travels in the file.
Independent timestampsRFC 3161 tokens from a public timestamp authority prove each signature existed by that moment. The request carries a hash, never the document.
Verified email, mechanicallyAn Ed25519 signature by the pinned attestor over email, sealing key, and time — minted only after a request signed by that key and a code answered from that inbox.
The fingerprint is the sealFirst twelve hex characters of the seal payload hash — the same bytes every signature covers. Nothing the signatures protect can change without changing it.
PDF envelopesThe same envelope carries application/pdf bytes; the signing page renders the exact frozen bytes in the browser's own viewer — what renders is what gets signed.
Verifiable without usThe format is documented and openssl-checkable; the CLI ships the reference verifier. If bearomark.io disappeared tomorrow, every envelope would still verify.
Encrypted deliveryA signing link holds a fresh 256-bit key in its fragment. The sender's app encrypts the envelope under a key derived from it before upload; the signed copy returns under a separate derived key. The relay stores ciphertext, hashed access tokens, sizes and lifecycle state — no plaintext, no keys.
Verify these pagesEvery release publishes the SHA-256 of each file these pages are made of; a scheduled witness compares the live site against it and alerts on drift. Check us yourself: the security page.