> ## 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.

# FAQs

> Frequently asked questions about ClickTerm.

## General

<AccordionGroup>
  <Accordion title="What is ClickTerm?">
    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.
  </Accordion>

  <Accordion title="How much does ClickTerm cost?">
    ClickTerm offers a free tier to get started, with usage-based pricing beyond that. Visit [clickterm.com/pricing](https://clickterm.com/pricing) for current pricing details.
  </Accordion>

  <Accordion title="Do I need a credit card to sign up?">
    No. You can create an account and start using ClickTerm immediately on the free tier without a credit card.
  </Accordion>

  <Accordion title="What platforms does ClickTerm support?">
    ClickTerm provides SDKs for **Web** (JavaScript) and **Android** (Java/Kotlin). The REST API can be used from any backend language.
  </Accordion>
</AccordionGroup>

## Templates & versions

<AccordionGroup>
  <Accordion title="What is the difference between major and minor 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](/product/templates/version-types).
  </Accordion>

  <Accordion title="Can I edit a published version?">
    No. Published versions are immutable to preserve the integrity of consent records. To make changes, create and publish a new version.
  </Accordion>

  <Accordion title="What happens if I disable a template?">
    Disabled templates are excluded from API responses. End users will not see the clickwrap dialog for disabled templates. Existing events and certificates are preserved.
  </Accordion>

  <Accordion title="Can I schedule a version to go live in the future?">
    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.
  </Accordion>
</AccordionGroup>

## Integration & SDK

<AccordionGroup>
  <Accordion title="What is the difference between App ID and App Key?">
    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](/api-reference/authentication).
  </Accordion>

  <Accordion title="What gets billed?">
    Only calls to `POST /clickwrap/verify` count toward billing. Showing clickwraps to users (`ClicktermDialog.show()`) is free.
  </Accordion>

  <Accordion title="What if the user has already accepted?">
    The SDK automatically checks if the user accepted the latest major version. If they have, no dialog is shown and the promise resolves immediately.
  </Accordion>

  <Accordion title="Do end users need a ClickTerm account?">
    No. End users are identified by the `endUserId` you provide — this is your own internal identifier.
  </Accordion>

  <Accordion title="What is the difference between dialog and inline mode?">
    **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](/dev/guides/displaying-inline-clickwrap).
  </Accordion>

  <Accordion title="Can I use multiple inline clickwraps on one page?">
    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](/dev/guides/displaying-inline-clickwrap#multiple-inline-clickwraps).
  </Accordion>

  <Accordion title="Can I mix dialog and inline mode in the same application?">
    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.
  </Accordion>
</AccordionGroup>

## Compliance & legal

<AccordionGroup>
  <Accordion title="Is ClickTerm GDPR compliant?">
    ClickTerm is designed to support GDPR compliance by providing clear consent mechanisms, immutable audit trails, and downloadable certificates. See [GDPR best practices](/product/compliance/gdpr-best-practices). Consult your legal team for jurisdiction-specific requirements.
  </Accordion>

  <Accordion title="Are clickwrap agreements legally binding?">
    Yes, clickwrap agreements are widely recognized as legally enforceable when properly implemented. See [Legal enforceability](/product/compliance/legal-enforceability) for details.
  </Accordion>

  <Accordion title="What is a Certificate of Acceptance?">
    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.
  </Accordion>
</AccordionGroup>