Quickstart
Verified domain to filled form in five minutes. Start here.
PRYVC developer documentation
One script tag replaces your form friction with consented, always-current data.
What you integrate, and what you don’t
Section titled “What you integrate, and what you don’t”These docs cover the surfaces you build against: the Share button, certified consent, the API, and webhooks. Together they produce evidence you hold and can rely on — the consumer approved a named set of fields, for the purpose you declared, for a stated duration, and both sides keep a matching receipt.
PRYVC also ships a consumer browser extension that fills forms on sites with no integration at all. You do not integrate with it and you will not receive its data. Worth knowing it exists for one reason: if a visitor autofills your form with it, the record they keep is their evidence of what they disclosed — not consent you can rely on. It also never ticks a consent checkbox, so whatever consent you capture is still captured by you, your way. If you want consent you can produce under audit, that comes from integrating the Share button or certified consent.
If you received a “disclosure notice” from us
Section titled “If you received a “disclosure notice” from us”A consumer filled one of your forms using the PRYVC extension and chose, by pressing a button, to send you their record of it. We do not contact businesses on our own, we do not sell lists, and there is no automated outreach — a person decided to tell you, once.
That notice is their evidence of what they disclosed, not consent you can rely on: you declared no purpose and no recipients because you aren’t integrated. Your own consent capture is unaffected. The notice page carries a permanent one-click opt-out that needs no account.
Once you verify your domain, you stop receiving these entirely — integrated businesses are excluded before anything is sent, because you already have your own receipts.
If you’d like consent you can rely on, that’s what these docs cover.
SDK reference
Every attribute, method, and event of pryvc.js. Read it.
MCP server
Connect an AI agent over the Model Context Protocol — six tools, scoped to your token. Read it.
What you hold
Which artifact each integration produces, and why there is no event for a consumer who declines. Read it.
Webhooks
Signed deliveries with verification samples in four languages. Verify signatures.
Certified consent
Accountless consent certificates and the verification API (Enterprise). API reference.