Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.clickterm.com/llms.txt

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

​
General

ClickTerm is a clickwrap agreement management platform. It helps you present legal documents (Terms of Service, Privacy Policies, etc.) to your users, record their consent, and generate tamper-proof Certificates of Acceptance.
ClickTerm offers a free tier to get started, with usage-based pricing beyond that. Visit clickterm.com/pricing for current pricing details.
No. You can create an account and start using ClickTerm immediately on the free tier without a credit card.
ClickTerm provides SDKs for Web (JavaScript) and Android (Java/Kotlin). The REST API can be used from any backend language.

​
Templates & versions

Major versions (1.0, 2.0, 3.0) require all users to re-accept. Use them when terms change meaningfully. Minor versions (1.1, 1.2) are for small fixes like typos — users who accepted the latest major version are not prompted again. See Version types.
No. Published versions are immutable to preserve the integrity of consent records. To make changes, create and publish a new version.
Disabled templates are excluded from API responses. End users will not see the clickwrap dialog for disabled templates. Existing events and certificates are preserved.
Yes. When publishing, set the Effective at date and time to a future moment. The version will become active automatically when that time arrives. Until then, the previous version remains in effect.

​
Integration & SDK

The App ID is public and used in the client SDK. The App Key is secret and used only for server-side API calls. Never expose the App Key in frontend code. See Authentication.
Only calls to POST /clickwrap/verify count toward billing. Showing clickwraps to users (ClicktermDialog.show()) is free.
The SDK automatically checks if the user accepted the latest major version. If they have, no dialog is shown and the promise resolves immediately.
No. End users are identified by the endUserId you provide — this is your own internal identifier.
Dialog mode shows a full-screen modal overlay where the user accepts or declines. Inline mode (SDK v2.2.0+) embeds a checkbox directly in your page — you control when to submit via finalize(). Use dialog for standalone consent screens and inline for forms, registrations, or checkouts. See Displaying an inline clickwrap.
Yes. Each inline clickwrap needs its own container element with a unique id. Use ClicktermDom.finalizeAll() to submit them all at once. See Multiple inline clickwraps.
Yes. Both modes use the same ClicktermClient.initialize() call and the same templates. You can use dialog mode on some pages and inline mode on others.
ClickTerm is designed to support GDPR compliance by providing clear consent mechanisms, immutable audit trails, and downloadable certificates. See GDPR best practices. Consult your legal team for jurisdiction-specific requirements.
Yes, clickwrap agreements are widely recognized as legally enforceable when properly implemented. See Legal enforceability for details.
A digitally signed PDF that proves a specific user accepted a specific version of your agreement at a specific time. It includes the user ID, timestamp, IP address, device information, and the exact text of the agreement.