Electronic signature, eIDAS simple level
Signatures that hold up when someone asks for proof.
Send a PDF, place the fields, and let each signer sign from their own link. Every step is journalled, the file is sealed once with its evidence page bound in, and then it is deleted - because we are not a document vault.
What ends up in the record
- Who signed, from which address and which browser
- That they agreed to sign electronically, and when
- Which document exactly, by SHA-256 before and after
- That nothing moved since: PKCS#7 seal and RFC 3161 timestamp
- All of it inside the PDF, on a page bound in and sealed with it
Prepare
Upload the PDF, drop the signature, initials, date and text fields where they belong, and name the people who have to sign. Sequentially or all at once.
Sign
Each signer gets a personal link and, in a separate message, a short access code. They draw or type their signature. No account, no software, no reader plugin.
Keep the proof, not the file
The sealed PDF is downloaded by everybody who needs it, and then it goes: you choose between one and thirty days. The fingerprints and the record stay.
We do not keep your documents
Most services sell you storage. This one sells you proof. The sender picks how long the file lives in the system - up to thirty days after the request closes - and after that the binary is deleted, whether or not everybody remembered to download it. Every download is recorded, and anybody still missing their copy is reminded seven, three and one day before.
What survives is the evidence record: the SHA-256 of the sealed document, every consent, every address, every timestamp. That is what proves a signature. The file is not.