Evidence Bundle
An evidence bundle is the complete record of a single user interaction with a Propper Click agreement. It's assembled automatically at the moment of interaction and sealed so it cannot be altered after the fact.
This is what you produce if you're ever asked to prove that a specific person agreed to a specific version of your agreement at a specific time.
Screenshot: annotated screenshot of an Evidence Bundle detail view, with callouts on user info, snapshot preview, version references, and the tamper-evident seal section
What's inside a bundle
Who interacted and when
Every bundle identifies the user and the context of their interaction:
| What's captured | Why it matters |
|---|---|
| User reference | The ID your application passed to Propper — links the acceptance to a person in your system |
| IP address | Network location at the time of interaction |
| Browser and device | Browser type, operating system, and version |
| Language | Which language the agreement was displayed in |
| Timestamp | Exact date and time of the interaction (UTC) |
Passing a user ID and email when you set up the SDK ensures every bundle is linked to a real person in your system. See SDK Initialization.
Exactly what the user saw
A snapshot of the agreement is captured at the moment the user interacts — not the current version, but the exact version they were shown. This includes the text, layout, and styling, so you can reproduce precisely what was presented.
Screenshot: side-by-side comparison of a live agreement and its stored snapshot, showing they are identical
Which version of your agreement
Each bundle records the content version and policy version of the agreement shown. When your terms change over time, this tells you exactly which version each user responded to — critical for demonstrating compliance when policies evolve.
See Version Management for how template versions work.
Proof it hasn't been tampered with
Every bundle is cryptographically sealed when it's created. This means you — and anyone you share it with — can verify that the record hasn't been altered since the moment it was generated. Propper checks this automatically; if a record appears in your dashboard, it's intact.
PDF certificate
A human-readable certificate is generated for every bundle. It summarises the key details of the acceptance in a format suitable for sharing with legal counsel, auditors, or regulators — no dashboard access required.
Screenshot: redacted example of a PDF Certificate showing agreement title, user info, timestamp, and the tamper-evident seal section
See Document Validity & Trust for guidance on presenting this certificate as official proof to federal agencies, courts, or regulators.
Consent category choices (Consent templates only)
For Consent Management templates, the bundle also records each category choice individually — for example, "Marketing: accepted, Analytics: declined." See Consent Tracking for details.
What's captured by template type
Different template types produce slightly different bundles. Use this to confirm what you'll have available for audits:
| What's captured | Static | Generated | Consent |
|---|---|---|---|
| User reference, IP, browser, timestamp | ✓ | ✓ | ✓ |
| Snapshot of the agreement as shown | ✓ | ✓ | ✓ |
| PDF certificate | ✓ | ✓ | ✓ |
| Tamper-evident seal | ✓ | ✓ | ✓ |
| Content version + policy version | ✓ | ✓ | ✓ |
| Personalised content and generated document | ✓ | ||
| Per-category consent choices | ✓ |
Downloading a bundle
You can download a PDF certificate or the complete bundle archive from the Evidence detail view in the dashboard.