Neutral by designOptional IP loggingVersion hashing
SECURITY
Calm security. Clear boundaries.
Receipt is built to be a focused utility: it records document access, review activity, and acknowledgement — then produces a file-ready record. No analysis. No inference. No magical claims.
Receipt is not an e-signature tool. It does not verify identity by default, and it does not assess understanding, consent, or intent.
Security posture
Receipt is designed around a simple idea: do less, but do it cleanly — and make the output useful.
Minimise data
Record only what’s needed to evidence access and acknowledgement.
Stay neutral
No “read and understood”, no “consented”, no guesswork.
Make it exportable
A consistent record your team can store with the matter.
If you need identity verification, signing, or advanced compliance workflows, Receipt should sit alongside those tools — not pretend to replace them.
Minimal claims
Receipt records observable events. It doesn’t assert understanding, intent, or consent — because those aren’t observable.
Optional IP logging
Where enabled, Receipt can store IP and user-agent data for access events. Leave it off when it’s not appropriate for your context.
Document integrity
Document hashing helps you evidence what was actually sent and reviewed — useful when versions change.
What Receipt records
Receipt is built around a small set of facts. Typical fields include:
Fields
• delivered_at / first_opened_at
• max_scroll_percent
• time_on_page_seconds
• acknowledgement + submitted_at
• (optional) ip + user_agent
• document hash / version
You control what you store and how long you keep it — align this with your internal policies and your Privacy notice.
What Receipt doesn’t do
No e-signatures
Receipt doesn’t replace signing workflows or identity verification tools.
No identity verification by default
It records access behaviour, not who someone “really is”.
No ‘understanding’ claims
Receipt never asserts comprehension, intent, consent, or agreement.
No analysis
No AI interpretation. No sentiment. No conclusions.
Data handling & retention
What you store (and for how long) should match your internal policies. Our Privacy page covers personal data and retention at a high level.