OpenPolicy Plus

import config from "#/lib/openpolicy";
import { createClient } from "@openpolicy/plus";

const client = createClient(config);

// Record consent when a user accepts your policies
await client.consent({
  user: { id: user.id, email: user.email, plan: user.plan },
});

// Check if policies changed since the user last consented
const changes = await client.changes(user.id);
if (changes.length > 0) {
  // Prompt the user to review and re-accept
}

// Check the current user's jurisdiction
const jurisdiction = await client.jurisdiction(user.id);
if (jurisdiction === "gdpr") {
  // Show cookie banner
}

Consent tracking

Know exactly who has accepted what, and when.

Every policy acceptance is timestamped and tied to a specific document version. Filter by policy, jurisdiction, or cohort — and export a full audit trail whenever compliance or legal asks for it.

• Per-user acceptance history across all policy types
• Version-aware: know if a user is on v3 or still on v1
• Jurisdiction-level compliance rates at a glance
• Export to CSV for legal and audit workflows

Compliance overview — last 30 days

Privacy Policy v3.2

Grace period ends in 4 days

Update management

Roll out policy changes without the scramble.

When your legal team updates your privacy policy, OpenPolicy+ creates a new version, surfaces a re-consent prompt to affected users, and tracks rollout progress in real time — so you're never left guessing who still needs to sign.

• Automatic versioning on every policy change
• Targeted re-consent: only prompt users who need to re-accept
• Live rollout progress by segment and jurisdiction
• Configurable grace periods before enforcement

PR bot

Catch compliance drift before it merges.

The OpenPolicy+ GitHub bot reviews pull requests that touch your policy config. It summarises what changed in plain English, flags jurisdiction gaps, and posts a diff of the generated document — keeping your legal team in the loop without pulling them into every code review.

• Automatic PR comments on policy config changes
• Plain-English summary of what changed legally
• Rendered document diff so reviewers see the real impact
• Optional approval gate before merging policy changes

import { defineConfig } from "@openpolicy/sdk";
import { dataCollected, thirdParties } from "@openpolicy/sdk";

export default defineConfig({
  company: {
    name: "OpenPolicy",
  },
  effectiveDate: "2026-01-01",
  jurisdictions: ["eu", "us"],
  dataCollected,
  thirdParties,
});

Built for developers

Policies that live in your repo, not a dashboard.

Define everything in TypeScript — fully typed, diff-friendly, and reviewable in your normal code review flow. OpenPolicy+ takes care of the legal rendering, consent tracking, and compliance reporting so your team stays in their IDE, not a legal portal.

• Fully typed config — autocomplete for jurisdictions, data types, and third parties
• Vite plugin — generates documents as part of your existing build pipeline
• Typed client — consume your policy metadata from any TypeScript app
• Open source core — the OpenPolicy framework is open-source and GPL3 licensed