Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.clearpolicy.app/llms.txt

Use this file to discover all available pages before exploring further.

An attestation is the record created when a recipient confirms they have read and agreed to a document. ClearPolicy manages the full workflow: sending a request by email, guiding the recipient through a simple completion page, and storing a tamper-evident record of the response. No accounts, apps, or downloads are required for recipients.

​
Attestation types

ClearPolicy supports two types of attestation, which you set at the document level and can override per request:
The recipient reads the document and clicks a button to confirm they have read and understood it. This is the simplest form of attestation — one click, no typing required. Use acknowledgments for policies and notices where a confirmed read is sufficient.

​
How requests are sent

When you send an attestation request, ClearPolicy:
  1. Creates a request record linked to the specific document revision and the recipient’s contact.
  2. Generates a unique, personal token for that recipient.
  3. Sends an email to the recipient containing a link that includes their token.
Each link is specific to one person and one request — it cannot be used by anyone else.

​
The recipient experience

The recipient clicks the link in their email and lands on a public page that shows the document content. The page requires no login. From there, depending on the attestation type:
  • For an acknowledgment, they click to confirm they have read the document.
  • For a signature, they type their name into a field and submit.
Once submitted, the page confirms their completion and offers a downloadable receipt. If the sender included a recipient message, it appears as a highlighted note on the attestation page and in the email, giving the recipient additional context about why they received the request. If the request has an expiration deadline, the attestation page displays a warning banner with the deadline so the recipient knows when they need to complete it. The expiration date also appears in the request details on the page.
Recipients access their attestation page through a personal link only. If they lose the email, you can send them a reminder from within ClearPolicy.

​
What gets recorded

When a recipient completes a request, ClearPolicy creates an attestation record that captures:
  • Timestamp — the exact date and time of completion.
  • IP address — the network address of the device used.
  • User agent — the browser and operating system information.
  • Signature name — for signature-type attestations, the name the recipient typed.
  • Document hash — a cryptographic fingerprint of the document content at the time of signing, used to verify the document has not been altered.
These details form an auditable record that can be downloaded as a receipt.

​
Request lifecycle

An attestation request moves through the following statuses:
The email has been delivered to the recipient. They have not yet opened the attestation link.
The recipient has opened their personal link and viewed the document.
The recipient has completed the request. A permanent attestation record has been created.
The request was canceled before the recipient completed it. A request can be canceled manually by your team, or automatically by ClearPolicy when a newer revision supersedes the one the request was sent for.
The request passed its expiration date without being completed. Expired requests can no longer be completed by the recipient. You can configure requests to expire automatically in your organization settings.

​
Superseded requests

When you publish a new revision of a document and send fresh requests, ClearPolicy automatically cancels any pending requests that were tied to an older revision of the same document for the same contact. This keeps your request list clean and ensures recipients only receive the latest version. For example, if you sent a request for version 1 of a policy and then published version 2 and sent new requests, any still-pending version 1 requests are automatically canceled. The activity log for each canceled request shows “Superseded by a newer revision” so you can see exactly why it was closed.
Only pending requests are affected. Requests that have already been completed, expired, or manually canceled are not changed.

​
Sending reminders

If a request is still pending, you can send the recipient a reminder email. The reminder delivers the same personal link to their inbox so they can complete the request without searching for the original email. You can also set up automatic reminders to follow up with recipients on a schedule.
Use reminders to follow up with people who have viewed but not yet completed a request — this is often the most effective nudge to drive completions.

​
Downloadable receipts

Once a request is completed, a PDF receipt is available for download. The receipt includes the document content, the attestation details (timestamp, IP address, type), and the signature name if applicable. You can use receipts for your own records or to provide evidence of completion to auditors or stakeholders.
Last modified on April 17, 2026