Preference pages

Preference pages are hosted pages where people ask your business to stop contacting them, to stop selling or sharing their information, or to unsubscribe from email. You link them from your footer and your emails. PRYVC delivers each request to you and keeps a record that it did.

They are included with every paid plan. You do not have to use them.

The three pages

Page	Address	What the person asks
Do not contact	preferences.pryvc.com/s/your-site/dnc	Stop contacting me by the channels I choose: text messages, phone calls, email (marketing and general messages), and postal mail.
Do not sell or share	preferences.pryvc.com/s/your-site/optout	Do not sell or share my personal information.
Unsubscribe	preferences.pryvc.com/s/your-site/unsub	Stop sending email to this address.

Each page shows your name, your logo and color, the verified domain it belongs to, and your own wording. Under your wording there is always a notice from PRYVC that says what the request covers, how long you have to act, and what PRYVC does. That notice cannot be edited or removed.

What PRYVC does, and what you do

• PRYVC delivers and records. The moment someone submits a page, PRYVC sends the request to you and records that it was received and delivered. Both events appear in the public ledger.
• You act. Removing the person from your lists, your dialer, your CRM and anyone you share data with is your responsibility. When you have done it, mark the request done.
• The person gets a receipt. It shows what they asked, when it was delivered to you, the date you must act by, and whether you have confirmed. It says “delivered” until you mark the request done, and “overdue” if the date passes first.

A request is never refused for lack of verification: anyone may ask a business to stop. So a request is not proof of who made it, and PRYVC marks every delivery verified: false.

These pages are not legal advice. Have your counsel review your wording, and decide what the law requires of you, before you go live.

PRYVC does not keep the person’s details

What a person types — email, phone, address, name — is encrypted, delivered to you, and then deleted. It is usually held for seconds, and at most until the next daily backup email.

What PRYVC keeps is the record: a reference, the kind of request, the channels, the page version the person saw, the dates, the delivery attempts, whether you marked it done, and a keyed hash of the email address and phone number. PRYVC holds the key, so the hash can be matched against an address or number you supply — it does not display the original.

Two consequences:

• The copy we deliver is your copy. PRYVC cannot re-send a request after delivery. Store what you receive.
• The queue lists references, not people. Match a reference to the person in your own webhook data or backup email.

Set it up

1. Open Preferences in the business portal.
2. Choose one of your verified domains, an address for your pages, and the name to show.
3. For each page, edit the heading and wording, Save draft, and Preview.
4. Publish each page you want. Publishing freezes that wording as a version.
5. Set a webhook URL and press Send a test. If you set none, requests arrive in an encrypted daily backup email instead.
6. Press Go live, then copy each page’s link into your footer and your email templates.

Only an owner can change the pages, the branding or the webhook. Anyone on your team can work the queue.

Versions: showing what a person saw

A published version never changes. When you edit a page or your branding and publish again, that is a new version, and visitors see it from then on. Every request records the version the person was shown, so for any request you can open What they saw and see the page exactly as it was, together with its hash.

Delivery

Webhook. Each request is posted to your URL, signed with your signing secret (shown once when you set the URL). A delivery that fails is retried four more times over the following hours. If it still fails, the request moves to the backup email and your owners are told the endpoint is failing. The developer reference is at developers.pryvc.com/preference-requests.

Encrypted backup email. Once a day, requests that could not be delivered by webhook are sent to your owners as an AES-256 encrypted zip. The password is never emailed: get it in the portal under Preferences → Backups. Sending the backup counts as delivery.

Either way, the deadline does not move.

The queue and the deadline

Every request has an act-by date, 10 business days after it was received. The same clock applies to all three pages; it is the shortest of the periods that apply to these kinds of request, so a page never promises more time than the strictest rule allows.

• Your owners are emailed when a request is within two business days of its date, and once more when it is overdue.
• Mark done records that you acted, and the person’s receipt then says so. The first confirmation stands; it cannot be changed afterwards.
• Record opens a printable record of the request: what was asked, what the person was shown, the delivery attempts, the hashes and the ledger link.
• If a request’s email matches a consent certificate you hold, the queue and the delivery flag it. PRYVC does not revoke the certificate: that decision is yours.

Limits

• Pages are served at preferences.pryvc.com, not on your own domain.
• Requests are not identity-verified.
• The Global Privacy Control browser signal is not handled here. The Site Watch consent gate treats it as a decline for trackers on your site.
• PRYVC does not push requests into your dialer, CRM or email platform. Use the webhook or the API.