for business · sandbox is free
PRYVC fixes both: a Share button that fills your forms in one click with verified, always-current details — and a certified-consent widget that turns every submission into tamper-evident proof your compliance team can take to an audit.
two products, one embed
Share button · $299/yr
Enterprise · $1,999/yr fixed
Need more? · custom
Everything in Enterprise, plus custom integration work, migration from an existing consent vendor, a named contact with response commitments, security review support, and contract terms your counsel drafts rather than accepts. Priced per engagement.
new · event forms
Booth leads are where TCPA exposure is born: you collect a name and a number, then call and text for weeks. Badge scanners hand you data with zero consent evidence. Event forms hand you both.
Once you have your copy, PRYVC purges the personal data and keeps only hashes and consent metadata. We hold your leads for minutes, not months.
integrate in minutes
Paste your page URL into the portal's Integration AI: it finds your form, maps every field, and hands you paste-ready code for either product.
audit-grade
Hash-chained audit log, canonical fingerprints, and disclosure text captured exactly as displayed — built on the open, independently verifiable Share Protocol, with chain heads anchored to a separately operated, published ledger and a public ledger anyone can inspect. When a carrier or regulator asks, you answer in seconds.
respectful by default
Scoped fields, visible purposes, and honored revocations turn data collection from a liability into a relationship your customers opt into.
integrate + test free in sandbox · pay when you go live
dig deeper
guide
Business guide →
Account to first share in five steps — no engineer needed.
compliance
Certified consent, explained →
What a certificate proves, who can verify it, and why named recipients matter.
see it
A real, live certificate →
The public verification page your carriers and auditors would see.
build
Developer docs →
SDK, API reference, webhooks & signing, sandbox guide.
try
Live demo & button styles →
Working forms issuing real certificates against a demo tenant.
standard
The Share Protocol (SP/1) →
The open standard your evidence is written in. Published spec, public conformance suite, independent verifier.
the compliance layer, live
The PRYVC public ledger →
Our entire audit chain, browsable by anyone, verifiable in your own browser — sequence, action, and hashes only, never personal data. Chain heads are anchored every 15 minutes to Engrave and published, so anyone who records a checkpoint can later prove whether the history behind it changed. Engrave is operated by an affiliated company.
verify.pryvc.com/ledger
no lock-in, by construction
The usual question in a compliance review is what happens to your records if the vendor raises prices, gets acquired, or disappears. With most consent vendors the honest answer is that the evidence goes with them — the format is proprietary and validating a certificate means asking the vendor to vouch for itself.
PRYVC's evidence is written in Share Protocol (SP/1), an open specification under CC BY 4.0 with a public conformance suite and an independent, zero-dependency verifier written from the spec text rather than from our code. Anyone — your compliance team, your carrier, opposing counsel — can recompute our fingerprints and audit chain without our cooperation, our servers, or our permission. Export an evidence pack and it verifies offline, years later, whatever has happened to us.
The standard is open
Anyone may implement SP/1. We assert no patent claims over independent implementations.
We're the reference
PRYVC wrote SP/1 and remains its first and most complete implementation — the only full hub in production.
The network is ours
The spec travels. The consumer network, extension, policy monitoring, and revocation machinery are what you're buying.
what's coming
People are already handing errands to AI assistants, and filling in a quote form is exactly the kind of errand they hand over. The lead is real and the person genuinely wants the quote — but the evidence underneath it quietly stops working.
Consent tooling built on session replay and behavioral signals assumes a human at a browser: mouse movement, keystroke timing, time-on-page. An agent produces none of that. Its session either looks like a bot and gets scored as fraud, or it looks clean and proves nothing. Either way the artifact you are paying for stops answering the question a carrier will ask, and you cannot tell the difference from the outside.
A person still ticks the box
Our agent surface offers no way to grant consent — there is no such tool, by design. An agent can read, update and revoke; agreeing needs a human at a consent screen.
Evidence a machine can check
A fingerprint over canonical facts is verifiable by software against a published spec. A screen recording is something only a human can watch and only a vendor can vouch for.
Already built, not planned
An MCP server is live today with realm-scoped tokens, and the tooling is documented so an agent can find it without asking us.
We are not claiming to know when this becomes the majority of your traffic. We are saying the evidence you collect today should still mean something when it does — and that a record built to be recomputed survives the shift, while a record built to be watched does not.
Questions, volume, or a compliance review? Talk to us · Support
