Build clickwrap agreements into your product with templates, multi-language modals, version control, and tamper-proof Certificates of Acceptance for every user.
Four steps take a clickwrap agreement from your first template to court-ready evidence.
Author your legal document and drop in placeholders for the data you collect. Preview resolves the whole document with each signer's real details.
By accessing this website, you, Full Name (Job Title at Company Name), accept and agree to be bound by the terms and provisions of this agreement, effective Date.
Permission is granted to temporarily download one copy of the materials on the Company's website for personal, non-commercial transitory viewing only.
Service notices and the Certificate of Acceptance will be delivered to Email Address.
Agreed and accepted by Full Name, Job Title, on Date.
This is the dialog your users see, with placeholders resolved to real values. Check the box and choose.
Who accepted, what they accepted, when, and how, captured for every event. A record opens into a full, tamper-evident document once its signature is cryptographically verified.
Every verified acceptance produces a signed, immutable Certificate of Acceptance. Proof of who agreed, to what, and when.
© 2026 ClickTerm. This document is cryptographically sealed and legally protected. It may not be altered, reproduced, or distributed without prior written consent.
1 of 2
© 2026 ClickTerm. This document is cryptographically sealed and legally protected. It may not be altered, reproduced, or distributed without prior written consent.
2 of 2
ClickTerm covers the full clickwrap lifecycle: localization, placeholders, version control, team roles, and a tamper-evident audit log.
Inject user-specific data like name, email, company, VAT, and 5 custom fields into every agreement at runtime. Each value appears in the modal, the certificate, and the API response.
Serve clickwrap modals in 7 languages: English, German, French, Spanish, Chinese, Hindi, and Russian. Maintain separate localized content versions for each template.
Track every end user across all your apps. View their acceptance history, event statuses, placeholder values, and consent timeline in one place.
Schedule when an agreement becomes active and set a deadline for acceptance. Ideal for rolling out updated terms on a specific date or enforcing time-bound consent.
Invite team members and assign roles (Owner, Admin, or Member) with granular permissions for template management, publishing, billing, and user administration. All roles are included in every ClickTerm plan at no extra cost.
A tamper-evident chronological record of every action in your organization: events, template changes, user management, and integration updates.
ClickTerm uses PAdES digital signatures and HMAC-SHA256 verification to make every clickwrap acceptance legally defensible. Every record is cryptographically signed, stored immutably, and audit-ready for regulators.
Certificates of Acceptance are signed with PAdES (PDF Advanced Electronic Signatures), the EU standard recognized under eIDAS for advanced electronic signatures.
Every event is protected by HMAC-SHA256 signatures and SHA-256 content hashing. Verification confirms the event was not tampered with between the user's action and your backend.
Full audit trail with timestamped records, IP addresses, device metadata, and exact agreement text. Ready for GDPR data subject requests, CCPA, and regulatory audits. Have specific compliance questions? Reach out to our team.
Add ClickTerm to your web or mobile app in under an hour with a lightweight SDK and REST API. The acceptance flow opens inside your product, similar to reCAPTCHA, so users can accept terms without leaving your UI.
Create an integration in the ClickTerm dashboard and copy your App ID and Key.
Write your agreement in the editor, add placeholders, and publish the live version.
Include the SDK and call ClicktermDialog.show() in your frontend.
Send the signature to your backend, call the Verify API, and get a Certificate of Acceptance.
// Include the SDK script from CDN // cdn.clickterm.com/sdk/clickterm-widget-2.0.0.min.js const { ClicktermClient, ClicktermDialog } = window.Clickterm; // Initialize with your App ID ClicktermClient.initialize("YOUR_CLICKTERM_APP_ID"); // Show the clickwrap modal const result = await ClicktermDialog.show({ endUserId: "user-123", clickwrapTemplateId: "tmpl-456", language: "en", templatePlaceholders: { fullName: "Alice Example", email: "alice@example.com", company: "Acme Corp", }, }); console.log("Accepted:", result.signature); // Send result.signature to your backend for verification
// build.gradle — add the dependency // implementation 'com.clickterm:android-sdk:2.0.0' // 1. Initialize the SDK ClicktermClient.initialize("YOUR_CLICKTERM_APP_ID"); // 2. Show the clickwrap modal ClickwrapTemplate contentRequestBody = new ClickwrapTemplate( "YOUR_CLICKTERM_TEMPLATE_ID", endUserID, new HashMap<>(), "en" ); ClicktermDialog.show(this, contentRequestBody, null, new ClicktermDialog.OnAgreementResultListener() { @Override public void onSuccess(String clicktermSignature) { Log.i("Clickterm", clicktermSignature); // Send signature to your backend for verification } @Override public void onError(String message) { Log.e("Clickterm", message); } } );
// npm install @clickterm/react-native-sdk // Expo: add the plugin, then `npx expo prebuild` import * as Clickterm from '@clickterm/react-native-sdk'; // Initialize once, early in your app await Clickterm.initialize("YOUR_CLICKTERM_APP_ID"); // Show the clickwrap dialog const signature = await Clickterm.show({ clickwrapTemplateId: "tmpl-456", endUserId: "user-123", language: "en", templatePlaceholders: { fullName: "Alice Example", email: "alice@example.com", }, }); if (signature) { // Send signature to your backend for verification await sendToBackend(signature); }
# Verify a clickwrap signature curl -XPOST \ -H 'X-APP-ID: {YOUR_APP_ID}' \ -H 'X-APP-KEY: {YOUR_APP_KEY}' \ -H "Content-type: application/json" \ -d '{ "clicktermSignature": "{SIGNATURE}" }' \ 'https://api.clickterm.com/public-client/v1/clickwrap/verify' # Response { "clickwrapEventStatus": "ACCEPTED", "clickwrapEventId": "123e4567-e89b-12d3-a456-426614174000", "clickwrapTemplateId": "987e6543-e21b-45d3-b321-426614174999", "endUserId": "423e4567-e89b-12d3-a456-426614174000", "actionAt": "2025-08-20T14:30:00Z" } # Download Certificate of Acceptance curl -XGET \ -H 'X-APP-ID: {YOUR_APP_ID}' \ -H 'X-APP-KEY: {YOUR_APP_KEY}' \ 'https://api.clickterm.com/public-client/v1/clickwrap-events/{eventId}/certificate'
Here's what's shipping next, and what's further out on the roadmap.
Present multiple agreements in a single modal, each with its own checkbox. Users accept or decline each document individually in one step.
In developmentSend clickwrap agreements directly to end users by email. Recipients click a link to view and accept. No SDK integration required.
In developmentA single public page listing all your organization's published documents. One URL for your entire legal library: terms, policies, NDAs, always current.
In developmentGo beyond clickwrap with full electronic signature support. Collect legally binding signatures on contracts, proposals, and agreements.
PlannedA unified workspace to manage all document types (clickwrap, e-signature, and uploaded contracts) from creation through renewal.
PlannedUpload previously signed PDF documents and manage them alongside your digital agreements. Track, store, and reference legacy contracts in one place.
PlannedWe ship what you ask for. Share your idea and help shape the next release.
Request a featureWhat clickwrap software is, when it holds up in court, and how ClickTerm fits into your stack.
Yes. Clickwrap agreements, also called clickthrough agreements, are widely recognized as enforceable contracts in the US, EU, and many other jurisdictions. Courts consistently uphold clickwrap consent when the user is presented with the terms, required to take an affirmative action (such as clicking "Accept"), and the acceptance is properly recorded. ClickTerm captures all of this (the exact text, the user's action, timestamp, IP, and device) in a PAdES-signed Certificate of Acceptance.
ClickTerm records explicit, timestamped consent for each end user along with the exact version of the agreement they accepted. Every event includes full metadata: IP, timestamp, device, and a content hash, providing the audit trail required to demonstrate valid consent under the GDPR. The Certificate of Acceptance also serves as a standalone compliance record for data subject access requests.
A Certificate of Acceptance (CoA) is a digitally signed PDF generated after each accepted clickwrap event. It contains the event ID, user details, timestamp, IP address, agreement version, and a SHA-256 hash of the content. The PDF is signed using PAdES (PDF Advanced Electronic Signatures), an EU standard under eIDAS, ensuring tamper-proof integrity.
You can validate the signature using either Adobe Acrobat Reader or the DSS Demonstration WebApp.
In Adobe Acrobat Reader:
In the DSS Demonstration WebApp:
Minimal changes. Include the ClickTerm SDK script, initialize it with your App ID, and call ClicktermDialog.show() wherever you need consent. The modal runs in an isolated Shadow DOM, so it won't conflict with your styles or scripts. A backend call to the Verify API confirms the result. Most teams integrate in under an hour.
Published versions are immutable. When you update your agreement, you publish a new version. Existing acceptance records remain tied to the original version the user saw. You can then prompt returning users to accept the latest version, creating a new event with a new certificate. You get a complete version-by-version consent timeline for every end user.
Yes. Every organization starts with 500 free verified events per month. No credit card required. Beyond the free tier, pay-as-you-go pricing starts at €0.05 per event and decreases with volume. All features are available from day one, including PAdES certificates, multi-language support, and the full API.
ClickTerm