Skip to content
ZipDPDP
DOCUMENTATION

Start with the business flow. Then connect the software.

The first setup is an organization, a project, its systems and purposes, and a reviewed notice. Technical integrations follow the same purpose and evidence model.

CAPABILITIES

From policy to daily work

01

Set up your workspace

Verify your account, create an organization and project, then use the checklist to inventory data and assign owners.

Explore
02

Publish the widget

Verify your domain, publish a notice and widget version, and use the generated site key for that domain.

03

Use the consent API

A backend can ask for a purpose-specific decision using a scoped credential. Deny when a decision is unavailable.

04

Handle webhooks

Verify each signature, deduplicate event IDs, process asynchronously and reconcile the outcome.

05

Map rights requests

Offer a public request route, verify identity, assign an owner and keep response evidence.

06

Review limits

Customer-specific notices, legal decisions, connected-system deletion and pilot fit require human review.

Public API reference and copyable integration examples are being prepared for release. Trial access currently requires the production registration gate to be enabled.

START WITH A CLEARER PLAN

Make the next privacy task visible.

Bring your team, systems and evidence into one working view.

Start a trial