Verdocs Accept records every time someone accepts your terms of service, privacy policy, or license: the exact version they saw, who they were, when, and what was on their screen. Each acceptance comes with a signed certificate.
From $250 for 10,000 acceptances. See pricing →
A web component with a React wrapper. It takes your brand's colors and logo, and your CSS can override any of the theme variables.
Nearly every product asks people to accept its terms at signup or checkout. Very few keep a real record of it. When an acceptance is questioned later, in a billing dispute, a regulator's inquiry, or a motion to compel arbitration, someone has to rebuild it from server logs and old code. Which version of the terms was live that day? What did the screen say? Did the person check the box, or was it checked for them?
Verdocs Accept answers those questions with a record made at the moment of acceptance, not reconstructed after the fact.
Admins write each agreement in the Verdocs web app and publish it as a numbered version. A published version is locked: its text never changes, and we record a SHA-256 hash of it, who published it, and when.
When you publish, you choose whether the change requires re-acceptance. A typo fix leaves everyone current. A material change sends everyone back through acceptance the next time they arrive.
Drop the Verdocs Accept component into your app, send people to a hosted page, or keep your own UI and record the outcome from your server. People who are already current see nothing at all.
Every acceptance and every decline becomes a permanent record. For any one of them, download a signed certificate, a replay of what was on screen, and an evidence package anyone can verify.
A typo fix leaves everyone current. A material change sends everyone back through acceptance the next time they arrive.
A web component with a React wrapper that sits inside your signup form, checkout, or settings page.
Send people to a page in your brand, and they return to your app when they're done.
Show the terms in your own UI and record each outcome through our API. You can attach your own screenshot or HTML to the record.
A modal dialog, an inline checkbox under a form, scroll-to-the-end (the accept button unlocks only after the text has been read to its end), and several agreements at once, each with its own checkbox.
Every checkbox names its agreement and links to the full text, and the accept button says what clicking it means. These defaults follow the patterns courts have upheld. If a customization weakens them, such as a terms link that doesn't look like a link, notice text too small or faint to read, or a button that doesn't say "agree" or "accept", the component warns your developers in the browser console.
The component and the hosted page take your brand's colors and logo, and your CSS can override any of the theme variables. Certificates carry your logo too.
Draft freely, then publish. Before you do, compare the draft word by word with the current version. Published versions are locked and hashed, and an agreement with a published version is never deleted.
Ask whether a person is current on one or more agreements, and get back the versions they still need to accept. Starting a session answers the same question, so people who are current never see a prompt.
You identify each person with your own user ID, not a browser cookie, and attach metadata such as an email address, a session ID, or attribution data. It's stored with the acceptance and printed on its certificate.
Every acceptance and decline sends a webhook to your server, and the component tells your page with DOM events, so your app can unlock the next step the moment someone accepts.
Verdocs already records exactly which disclosure each signer accepted. Verdocs Accept brings that same standard to your terms.
Records never change once they're written, and declines are recorded too.
"I have read and agree to the Terms of Service"
Button: "Agree and continue"
Every acceptance and every decline becomes a permanent record.
Each organization's records form a hash chain. Change, remove, or insert a record after the fact, and the chain no longer checks out. You don't have to take our word for it: the evidence package includes what's needed to verify a record yourself.
Change, remove, or insert a record after the fact, and the chain no longer checks out.
A PDF with the agreement versions and their hashes, the person, the time, the IP address and browser, and how the terms were shown, signed the same way we sign envelope certificates.
The screen the person saw, rendered as an image.
One ZIP with the certificate, each agreement version as a PDF, the replay, the raw record, and what's needed to verify it.
If the person is already current, the session says so and there's nothing to show. A full quickstart, the API reference, and webhook details are in the developer docs.
Read the docs// Your server
const session = await createClickwrapSession(endpoint, {
user_id: 'user-123',
agreements: ['terms-of-service', 'privacy-policy'],
metadata: {email: 'jane@example.com'},
});// Your app
<VerdocsClickwrap token={session.token} onAccepted={unlockCheckout} />The Agreements page in the Verdocs web app shows how many people are current on each agreement. Look up anyone by your user ID or by email to see every acceptance and decline, and download the certificate, replay, or evidence package in one click.
Look up anyone by your user ID or by email to see every acceptance and decline.
Built for insurance, accounting, legal, financial services, HR, and real estate platforms, where "they agreed to it" has to hold up:
policyholder portal terms and consent to electronic delivery.
account terms, privacy notices, and e-sign consent at onboarding.
client portal terms and engagement terms.
handbook and policy acknowledgments, re-collected when the policy changes.
platform terms for agents, buyers, and renters.
Prepaid packs from $250 for 10,000 acceptances, and your first 1,000 production acceptances are free. No onboarding, platform, or per-seat fees.
It's how your app collects acceptance of your terms with a checkbox, and how Verdocs keeps proof of each one: the version, the person, the time, what they saw, and a signed certificate.
Only when you say so. Each time you publish a version, you choose whether it requires re-acceptance.
No. Use the component, send people to the hosted page, or keep your own UI and record each outcome from your server.
Yes. Every acceptance and every decline is recorded, with its own certificate.
Verdocs Accept gives you a complete record and defaults that follow the patterns courts have upheld. Whether your terms are enforceable depends on the terms themselves and where you operate, so ask your counsel.
Verdocs turns on Verdocs Accept for your organization. Book a demo and we'll set it up.