Short answer: when a contract is signed in ReqMe, we record who signed, when, from where, what exactly they were shown when they agreed, and a fingerprint of the document at that moment. That record is the point — it is what lets a signature be evidenced later if anyone questions it.
What gets recorded #
For each signature, the record holds:
- The time of signing.
- The signatory’s name and email address.
- Whether that email address was verified by a one-time code sent at the moment of signing.
- The IP address and browser of the signing session.
- The exact text of the confirmation shown at signing, and which version of it — so it is possible to establish what the person actually agreed to, not merely that they clicked.
- A cryptographic fingerprint of the document as signed, which changes if a single character of the document changes.
This record appears on the last page of the signed contract PDF, which stays on the request for both you and your client to download.
Why the confirmation text is stored #
Most systems record that somebody signed. Fewer record what they were told they were agreeing to. Storing the confirmation wording and its version means a signature from a year ago can be read against the exact screen that produced it, rather than against whatever the wording says today.
What the document fingerprint does #
It is a check on the document, not on the person. If the signed file is later altered, the fingerprint no longer matches, and that mismatch is detectable. It does not prevent alteration — it makes alteration visible.
What kind of signature this is #
Under the EU eIDAS Regulation (No 910/2014), signatures collected in ReqMe are simple electronic signatures. That is a factual classification, not a limitation we apologise for — most business agreements are signed this way.
ReqMe provides tooling to support e-signature workflows; legal validity depends on applicable law and correct use. Whether a particular signature holds up in a particular dispute is a question for a lawyer who knows your situation, not something a platform can promise in advance.
What ReqMe can do is make the record as complete as possible, so that if the question ever arises, there is something substantial to answer it with.
Requiring a signature, or not #
Contracts are signed by both sides. Proposals are your choice: you can require a signature, or let a client accept with a click. A proposal that needs a signature behaves like a contract; one that does not is closer to an indicative quote.
Choose deliberately. Requiring a signature adds a step and produces a stronger record; not requiring one is faster and produces a lighter one.
How long the record is kept #
Signature records are kept as evidence of the signature. The retention periods that apply are set out in our Privacy Policy.
Frequently asked questions #
Does my client need a ReqMe account to sign? #
No. They sign from the link you send them.
Can I see who signed and when? #
Yes — it is on the final page of the signed contract, which both you and your client can download from the request.
What if the document is changed after signing? #
The fingerprint recorded at signing will not match the altered file, which is how the change becomes detectable.
Is a drawn signature stronger than a typed one? #
The drawing is not what carries the weight — the surrounding record is: the verified email, the timestamp, the session details and the confirmation text.
Is this legally binding? #
That depends on the agreement, the jurisdiction and the circumstances, and it is a question for your lawyer. ReqMe’s part is producing a complete and accurate record of what happened.
Need help? #
If this page did not answer your question, send it to us. Tell us what you were trying to do and what happened instead — that is usually enough for us to spot the problem straight away.
Prefer email? hi@reqme.co
