Proof a document was opened and reviewed, without over‑claiming what it meant.
Receipt gives you a clean, timestamped record of delivery, access, review activity and acknowledgement — designed to drop straight into the file.
Receipt is not an e‑signature tool. It doesn’t give legal advice or assess understanding — it simply records what happened.
Receipt Record
example
Document
Client Care Letter - Residential Conveyancing
Version hash: 9f2c…a81d
Recipient
Alex Smith
alex@client.com
Acknowledged
Yes
12 Feb 2026, 09:22
First opened
09:17
Scroll depth
100%
Time on page
4m 32s
Receipt records observable events (delivery, access, review activity, acknowledgement).
FOR TEAMS
Built for the moments where “we sent it” isn’t enough.
When things matter, you need a neutral record — not opinions or guesswork. Receipt captures the facts: delivery, access, review activity, and acknowledgement.
Neutral by design
Records what happened, when it happened, and who did it. No sentiment, no assumptions, no overreach.
Frictionless for recipients
One link. Open the document. Review it. Acknowledge it. No accounts, portals, or unnecessary friction.
Clean output for the file
A clean record your team can export and keep alongside the matter — consistent, readable, and audit‑friendly.
HOW IT WORKS
Three steps. No drama.
Receipt stays in its lane: it logs observable activity and acknowledgement, then produces a tidy record.
1) Share
Upload a PDF and send a single link. You stay in control the whole time.
2) Review
Receipt records access and on‑page review activity — time spent and scroll depth — while the PDF is viewed.
3) Acknowledge
The recipient confirms they’ve reviewed the document. Receipt timestamps it and attaches it to the record.
What gets recorded (and what doesn’t)
Receipt records timestamps, activity, and acknowledgement — nothing more.
Fields
• delivered_at / first_opened_at
• max_scroll_percent
• time_on_page_seconds
• acknowledgement + submitted_at
• (optional) ip + user_agent
• document hash / version
SECURITY
Designed for professional use.
Receipt is intentionally narrow — a focused utility with clear boundaries and clean records.
Minimal claims
No “signature”. No “consent”. No “understanding”. Just a neutral record you can keep with the matter.
Optional IP logging
If enabled, Receipt can store IP and user agent data for access events. Leave it off when it’s not appropriate.
Document integrity
Versioning via document hash helps you evidence what was actually sent and reviewed.
FAQ
Common questions
Is this an e-signature product?
No. Receipt records access, review activity and acknowledgement. It doesn’t provide e‑signatures or verify identity by default.
Does Receipt prove understanding?
No — and it doesn’t try to. Receipt records observable behaviour (open, scroll, time) plus a direct acknowledgement.
Do recipients need an account?
No. Recipients open a link, view the PDF, and (optionally) acknowledge, without requiring sign up.
Can we brand it?
Yes! Everything from your dashboard to the emails you send can be branded with your logo, text and colours.
Ready to generate a record in seconds?
Upload a PDF, send the link, and keep a clean record with the matter file.