Consent management
Proof that is still proof in five years
The point of a consent record is the day somebody disputes it. What was signed is kept exactly as it was signed, with a hash that shows it has not been altered since, and every event against it is logged with a time and an IP address.
Consent events
General photoshoot consent · Amara Okonkwo
Scroll sideways for the times and addresses
| Event | Who | When | From |
|---|---|---|---|
| Request sent | Administrator | 1 Aug 2026, 09:14 | 203.0.113.24 |
| Form opened | Amara Okonkwo | 3 Aug 2026, 18:02 | 198.51.100.7 |
| Signed | Amara Okonkwo | 3 Aug 2026, 18:04 | 198.51.100.7 |
| PDF downloaded | Administrator | 4 Aug 2026, 10:31 | 203.0.113.24 |
- Snapshot hash
- 6015b9e332435fdead66676e97ba3b114a3033f50dc5c0853cc5a27072d56e7e
Taken over the signed document at the moment it was signed. Any later change to the stored copy produces a different hash, and the mismatch is the proof.
Illustrative example
What is kept
Not a summary of the form. The document, as rendered to the person at the moment they put their name to it.
01
A snapshot of what was signed
The wording, the ticked usages, the completed fields and the signature, stored as one document. Editing the template afterwards does not touch it.
02
A hash key over that snapshot
A checksum taken at the moment of signing. Any change to the stored copy, however small, produces a different hash and shows up as a mismatch.
03
Every event against it
Sent, opened, signed, downloaded, revoked, superseded. Each with who did it, when, and the IP address it came from.
04
A PDF you can hand over
Download a signed consent as a PDF, for a legal team, an auditor or the person who signed it. It is the snapshot, not a regenerated approximation of it.
Admin reporting
Who downloaded what, and what they said it was for
The consent trail and the download trail are the same question asked from two ends. Administrators get both: the events on a consent, and the record of every file that left the platform, with the purpose stated at the time.
- Download usage across the library, by person and by file
- Share history, so a link sent outside the organisation is accounted for
- Consent events with IP addresses, for the ones that end up disputed
- Read from the platform rather than assembled from four exports
More in consent
Creating forms
Create custom consent forms. Save multiple templates, define scope, add custom options and pre-fill selected fields.
Read more
Sending forms
Email finalised consent forms to one or multiple recipients. They get a link and a QR code, and can sign from their phone.
Read more
People directory
Everyone who appears in your library, with faces found in your photographs added to them automatically.
Read more
Consent records
Always know exactly what someone agreed to. And prevent mistakes, with consent checked at the moment somebody tries to download a file.
Read more
Next step
We’d love to explain more…
Still got questions? Curious to see LightRocket in action? Want to know more about pricing?
We’re always happy to show off our system and, yes, we’ll even help out with discounts and pricing.