Skip to main content

Privacy Policy Consent

Capture versioned, auditable proof that each user acknowledged your Privacy Policy, and stay ahead of GDPR, CCPA, and other data protection requirements as your policy evolves.

Coming Soon

Screenshot: Privacy Policy acknowledgment prompt embedded below a sign-up form

Before You Begin​

  • Your Privacy Policy text is ready.
  • You understand which environments (Staging, Production) you'll deploy to.

Step 1: Create a Static Template​

  1. Go to Click → Templates → New Template.
  2. Set the type to Static.
  3. Name it clearly (e.g., Privacy Policy, Global).
  4. Click Save. The template starts in Draft status.

Step 2: Add Content and Configure Compliance Settings​

  1. In the Content tab, paste your Privacy Policy text.
  2. Set the Acknowledgment checkbox label (e.g., "I acknowledge that I have read and understood the Privacy Policy").
  3. Enable Require Checkbox.
  4. In Settings, confirm the default retention period — records are kept for 7 years (2,555 days) by default.
tip

Enable the option to display the acceptance date and time to the user at the moment of consent — a useful transparency signal for privacy-conscious users.

Step 3: Publish​

Click Publish to move the template out of Draft. A template must be Published before it can be deployed.

Step 4: Deploy​

  1. Go to Deployments → New Deployment.
  2. Select your published template, enter your domain and path (e.g., yourcompany.com / /signup).
  3. Set environment to Staging first, then Production.
  4. Click Activate.
note

Only one active deployment is allowed per domain/path — activating a new one automatically deactivates the existing deployment on that path.

Coming Soon

Screenshot: Deployment configuration screen with domain, path, and environment fields

Step 5: Install the SDK​

const sdk = ProperClick.init({
  apiKey: 'your-api-key',
  environment: 'production'
});

await sdk.renderByDomain('yourcompany.com', '/signup', {
  containerId: 'privacy-container',
  onAccept: (response) => console.log('Accepted:', response.receiptId)
});

Full SDK installation guide · Rendering modes

Handling Policy Updates​

When your Privacy Policy changes, do not edit the published content.

Coming Soon

The New Version workflow — where you create a versioned draft and enable Re-consent on Update to re-prompt users who accepted a prior version — is in development.

In the meantime, clone the template (⋯ → Clone), paste the updated policy in the new draft, publish it, and update your deployment to point to the new template.

Each acceptance record captures the exact version of the policy that was shown, so your audit trail remains accurate regardless of how the policy evolves.

Version Management →

Evidence & Compliance​

Every acceptance automatically creates an immutable Evidence Bundle capturing:

What's recordedWhy it matters
User identifier, IP address, browserConfirms who accepted
The exact policy version presentedConfirms which version they accepted
A tamper-evident record of the displayed contentProves exactly what was shown
Retention expiry dateAutomatic purge after the retention window (supports GDPR right to erasure)

Evidence records are write-once — they cannot be modified after creation.

Compliance details → · Data Retention →

note

Click provides the technical infrastructure for consent capture. The wording of your Privacy Policy and legal sufficiency of your flow should be reviewed by qualified legal counsel.

Next Steps​