◆ Agreement records
Record the agreement version you both hold.
A loan between friends, a sublet, a co-founder split: it is in writing, nobody witnessed it, and nothing was filed anywhere. Both parties record the same file and each keeps a copy and a receipt. It distinguishes versions — it does not sign, witness, check anyone’s identity, or make anything binding.
The record is a Base transaction neither party can alter, and we cannot alter it either. Each of you keeps your own copy of the file and your own receipt — that is what makes it hold when you disagree.
What happens if we shut down →◦ Use cases
Built for agreement records workflows.
Agreement version
Keep the signed or acknowledged file with its receipt and separate identity and signature records.
Amendment checkpoint
Record selected amendment digests while retaining the communications that explain each change.
Supporting record set
Package messages, payment records, retained files, and receipts for context-specific review.
▸ FAQ
Common questions, answered plainly.
Does this make the agreement binding?
No. Whether an agreement binds anyone is a property of the agreement and the parties. Nothing here signs, witnesses, checks identity, or makes anything enforceable.
How do two people do this?
Both parties record the same file, and each keeps their own copy and their own receipt. Later, whichever copy is produced either reproduces the recorded fingerprint or it does not.
Is this an e-signature?
No, and if that is what you need, an e-signature product is the right tool. We do not sign, do not check identity, and do not witness.
Do I need an account?
Not to check a file or use the one-file guest offer when it is available. The verify page is public — no sign-in, nothing to install — and the public notarize page can send one browser-computed digest to checkout without an account. An account opens the signed-in console once you have verified your email address.