Business guide

This guide covers running PRYVC as a business user in the portal. For code-level integration (SDK, API, webhooks), see the developer docs.

1. Create your account

Once you are in, add a passkey under Team → Passkeys: from then on that device signs in to the portal with Face ID, Touch ID, or Windows Hello in one step — a passkey is possession plus biometric, so it stands in for both your password and the emailed security code. Your password and code keep working, so a lost passkey never locks you out.

Sign in at portal.pryvc.com with Google, Microsoft, or a work email and password. Your business starts in the free sandbox — integrate and test everything before paying.

2. Verify your domain

Shares and consent certificates are pinned to domains you prove you own. Under Settings → Domains, add your domain and create the DNS TXT record we show you. The Share button and consent widget only work on verified domains — that’s what makes a PRYVC consent artifact trustworthy.

Open Integration AI in the portal, paste the URL of the page with your form, and choose Share button. The assistant finds your form, maps its fields, and generates the exact script tag to paste before </body>. Your customers now fill the form in one click, and every fill arrives with a fingerprinted consent receipt.

What you get with each share:

Verified data — fields come from the customer’s encrypted profile, not their memory.
Always current — when a customer updates a field, every active in-scope share is refreshed and you’re notified (see Webhooks & events in the portal).
A receipt — date, purpose, fields, expiry, and fingerprint, visible under Shares.
Scan to share, for free — on a laptop, the consent screen offers a QR code; the customer approves on their phone and your form fills on the laptop. Same one-scan feel as paying by phone, no wallet, no charge, no extra code on your side. It is on for every Share button; add data-handoff="off" to the embed to turn it off.

If you buy, sell, or work leads in any category where consent may be questioned later — insurance, mortgage, solar, legal, home services, education — the Enterprise plan adds the accountless consent widget: your visitors don’t need a PRYVC account. On submit, PRYVC certifies exactly what they agreed to:

the disclosure text exactly as displayed,
every entity named as receiving the data,
purpose, page URL, timestamp, and evidence,
a tamper-evident fingerprint and a public verification URL anyone can check.

Use Integration AI → Certified consent widget to generate the embed. Certificates appear under Consent certs in the portal, searchable by subject email; your compliance team can pull full records via the certificate API (see developer docs).

5. Respecting revocations

When a customer revokes a share, you receive a formal cease notice and a webhook. You have 10 business days to comply; the deadline is tracked on both sides. Honoring revocations quickly is not just a legal obligation — it’s visible to the customer and builds the trust that makes them share with you again.

6. Proving it later

The moment that matters is months after the fact, when a buyer, carrier, or regulator asks you to substantiate a consent. Three things are available then, in increasing order of independence:

The public verification page. Every certificate has one. Hand over the link and the other party checks it themselves — no account, no API key, no call to you.

The certificate record. GET /v1/certs/{certId} with your API key returns the full record including the subject, for your own files or a CRM.

A portable evidence pack. GET /v1/certs/{certId}/evidence-pack exports a self-contained file that verifies offline, using an open-source verifier written from the published specification rather than from our code. It keeps working if PRYVC is unavailable — or gone.

That last one is the point of the whole design. Evidence that depends on its vendor still being around, and still agreeing with you, is a weak position in a dispute. A pack someone can check on their own machine, against a specification we don’t control, is not.

Details in the developer docs and the specification.

7. What you hold, and what you never will

This is where PRYVC differs most sharply from the tools you have used before, so it is worth being blunt about it.

Certified consent gives you a certificate on every submission where the visitor ticks your consent box. They need no PRYVC account and need never have heard of us. We seal the exact words shown, every named recipient, the purpose, the moment — and you get a page anyone can verify without involving you or us.

The Share button gives you more, when a consumer chooses it. Fresher data that stays current, a duration you did not have to administer, and a receipt the consumer holds too. But only when they opt in.

We never tick a consent box on anyone’s behalf — the button skips every checkbox when it fills a form — so approving a share and agreeing to your terms are two separate acts. That means four outcomes:

The visitor	You hold
Shares and ticks your box	Both: a fingerprinted share and a verifiable certificate
Shares, leaves your box unticked	The share only — fingerprinted, in the tamper-evident chain
Ignores the button, ticks your box	The certificate only
Ignores the button, leaves your box unticked	Nothing

Make your consent checkbox required and the last row cannot happen. Every submission then produces at least a certificate, and the ones where somebody chose to share produce both. That is the configuration we recommend.

One distinction worth knowing, because it decides what you rely on in a dispute: a certificate is publicly verifiable — anyone with the link can check it, and an evidence pack verifies offline. A share is auditable but not publicly verifiable: it is fingerprinted and written into the tamper-evident chain, whose head is checkpointed to a separately operated ledger every fifteen minutes, but there is no public page a carrier can open. The Share button is the better source of data; certified consent is the better source of proof.

We do not tell you who declined

If someone opens the consent screen and closes it, nothing reaches us and nothing reaches you. There is no “declined” event, no report of who considered sharing and thought better of it, and no hidden identifier tracking the attempt. Our script makes no network request at all until a person acts — not on page load, not on render.

Vendors in this space usually sell the opposite, and it is worth understanding why we will not.

A record that someone declined is a record about a person whose only interaction was refusal. Collecting it would contradict the thing we ask you to tell your customers. And a script that had to phone home to notice a decline would make us a tracker on your site, embedded by you, watching your visitors. We would rather not be able to.

Why unilateral evidence is the weaker kind

The instinct is that proof you can generate yourself is stronger, because it does not depend on anyone else. In a dispute it is the reverse.

A row in your CRM saying consent = true, next to a page that has since changed, is what everyone already has. It is exactly what gets challenged, and it does not survive contact with a serious auditor.

A certificate holds up because a real person acted, the exact words they saw are fingerprinted, and a carrier or regulator can verify it without asking you and without asking us. That strength comes entirely from the consumer having driven it. Making the artifact easier to produce on demand would make it worth less, not more — which is the whole reason this product is shaped the way it is.

Event forms: QR capture at tradeshows

Collecting leads at a booth is exactly the moment TCPA exposure is created — you collect a name and number, then call and text for weeks. Event forms give you a hosted, consent-grade capture form with a printable QR, so every booth signup arrives with provable express written consent attached.

How it works

Under Events in the portal, create the event (name, venue, dates).
Add a capture form: pick a template — lead capture, permission to contact, list signup, giveaway entry, or quote request — name the parties who will do the contacting, and choose the channels (calls, texts, email). PRYVC generates the consent language; you don’t write or edit disclosures. See the template gallery for a mockup of each.
Download the QR code or the print-ready booth sign, set the form live, and put it on your table. Visitors scan with their own phone — their device, their session — and submit in seconds. No PRYVC account needed.
Each submission lands in your systems in real time via a signed webhook, or — if you don’t run one — in a daily encrypted backup email. The zip password is only retrievable in the portal, never sent by mail.

What PRYVC keeps (almost nothing)

Submissions are encrypted the moment they arrive and destroyed as soon as you have your copy — webhook delivery or backup email, whichever happens. What remains is the evidence: the exact consent text shown (hashed and versioned), a fingerprint of the submitted data, the timestamp, and a public ledger anchor. The registrants grid in the portal shows that metadata — it is deliberately not a CRM. Match rows to your delivered copy by the record hash.

Editing rules

Event details (name, venue, dates) stay editable until a form under the event goes live or the first submission arrives — after that they lock, because they are part of what consumers consented under and the dates drive automatic form expiry. Forms can be paused any time; live forms close automatically when the event’s end date passes. Events with recorded submissions cannot be deleted — the consent trail is permanent even though the personal data is long gone.

Plans

Plan	Price	Includes
Sandbox	Free	Full integration testing with fake data
Business	$299/yr	Share button, REST API, webhooks, unlimited shares
Enterprise	$1,999/yr fixed	Everything in Business + accountless certified consent, certificate API, Integration AI. Never metered — no per-lead fees.

Upgrade any time under Billing in the portal, or try everything first on the live demo.