about

It's pronounced PRY-V-C — as in "privacy."

Because that's the whole point.

why we built this

Handing over your contact details is the most common transaction on the internet — and the only one with no receipt. You type your email into a form, and from that moment you have no record of who has it, no say in what they do with it, and no practical way to take it back. Businesses aren't better off: they sit on decaying spreadsheets of typo'd, stale, legally ambiguous data that nobody remembers consenting to.

Sign-in solved this years ago — OAuth turned "give every site a password" into "grant scoped, revocable access." Your contact details never got the same upgrade. PRYVC is that upgrade: OAuth for contact details. Every share is scoped to exact fields, tied to a stated purpose, time-limited, cryptographically fingerprinted, and revocable with real consequences — a formal cease notice, a tracked 10-business-day deadline, and a documented paper trail if it's ignored.

We built it because consent should be an artifact, not a vibe — something both sides can point to, verify, and rely on. The longer version — the two evidence models, what consolidation did to the category, and the things we refuse to do — is on why we built this.

And because an artifact you can only verify by trusting us isn't much of an artifact, the mechanics are an open standard: PRYVC is the reference implementation of the Share Protocol (SP/1) — published canonicalization rules, fingerprints, hash-chained audit format, and test vectors that let anyone check our evidence independently.

who it's for

for people

Anyone tired of wondering where their details ended up

One free, encrypted profile. Share in one click, see every share on one screen, and revoke with legal teeth. Your fields are encrypted with a key unique to you, and no PRYVC screen or export shows them to our staff — selling your data isn't in our product or our business model. You are not the product here; your consent is, and it stays yours.

PRYVC for you →

for businesses

Teams who'd rather earn data than scrape it

The Share button turns forms into one-click conversions with verified, always-current data. Certified consent turns any lead flow you might have to defend later — insurance, mortgage, solar, legal, home services, education — into tamper-evident certificates that capture the disclosure and your policies exactly as they read at opt-in. Fixed pricing, never metered.

PRYVC for business →

everyone gets receipts

Consent a business can actually rely on

That is the whole point of the business side. When a company integrates the Share button or certified consent widget, it becomes a party to the transaction: it declares which entities receive the data, states a purpose, and sets a duration. The consumer sees exactly that and approves it. What comes out is a certificate the business is meant to lean on — the disclosure captured verbatim, the recipients bound into a SHA-256 fingerprint, the whole thing hash-chained, externally anchored, and verifiable at a public URL by a carrier or a regulator without asking us for permission.

Both sides keep a copy. That symmetry is the product: the business gets evidence it can produce under audit, and the person gets the same record, which is the part the industry has never offered.

Two mechanisms, deliberately different. It matters which one produced a given record.

business-driven

The Share button

The business declares in advance who receives the data, why, and for how long. The person sees exactly that and approves it. Intent is captured on both sides, and both walk away with the same receipt. This is evidence built to be relied on.

consumer-driven

The browser extension

A PRYVC member fills a form on a site that has no integration with us and no idea we exist. Nobody declared a purpose because nobody was asked to. The receipt is the member's own record of what they disclosed — not consent handed to that site. A company that wants consent it can rely on should integrate; it takes one script tag.

It is also why the extension never ticks a consent checkbox — it fills name, email, phone and address, and deliberately skips every checkbox, radio and password field. The consenting act stays the consumer's, so nothing we do could ever be characterised as manufacturing consent on someone's behalf.