Prynt Reveal — Data Processing Annex
This annex supplements the Data Processing Agreement for customers who use Prynt Reveal. It lists only what Reveal adds to or changes in the main DPA; everything else is inherited from it.
Draft of November 3, 2026
1. Roles and scope
You (the customer) are the data controller for the visitors of your websites. Prynt is the data processor. Reveal performs two operations, both only on your documented instructions — your console configuration: verified websites, consent mode, URL and country rules, integrations.
- Company-level identification. The organisation a visit comes from, derived from the visitor's network (IP address and public network registries). Never a name.
- First-party people. Only when a visitor identifies themself to you — a form, a login or a record you import from your CRM — and you record the basis on which they did (a consent reference), Prynt links that identity to their visits.
Prynt is not an independent controller of any visitor data. Prynt never identifies an anonymous visitor as a person, never buys identity data, never sells or shares visitor data and never combines the data of different customers to identify a person. There is no third-party people provider in the pipeline; that path is disabled in the code.
2. Nature and purpose of the processing
To identify, at company level, the organisation from whose network your website is visited; and, only when a visitor identifies themself to you with a recorded consent basis (consentRef), to link that first-party identity to their sessions. To score interest (pages, duration, recurrence) and deliver alerts to the destinations you configure.
3. Categories of data subjects and data
- Data subjects: visitors of your websites; your contacts who identify themselves through a form, a login or your CRM import.
- IP address: minimised (/24 for IPv4, /48 for IPv6) and hashed with a platform salt before storage. The full address is not stored in any Reveal table.
- Network context: ASN, network organisation, country, city, network type (business, ISP, hosting).
- Session: pages, durations, referrer, UTM parameters, a session id (
rvs_) and, when your site runs the Prynt agent, a device id (vst_). - Company: the organisation resolved for the session and the confidence of that match.
- First-party identity: e-mail (hashed; the clear value only because you collected it), name, the consent reference, and the evidence of how the identity was obtained.
- Newsletter signal: when your e-mail tool adds a token to links and the visitor has consented, only a hash of that token — it marks a known contact, it never identifies anyone.
No special categories of data are processed. You agree not to deploy Reveal on pages about health, children or other sensitive subjects without a prior review with us.
4. Consent and signals
The Reveal script stores nothing in the browser until you tell it consent was given (your banner, a detected consent manager, or your configuration). Global Privacy Control is honoured. Visitors in Europe default to consent-off. In explicit consent mode nothing is resolved without consent. No identity is ever accepted from a non-consented request, whatever the request contains.
You remain responsible for your banner and your privacy notice; model texts are at the end of this annex.
5. Duration and deletion
For the term of your subscription. Visit data is purged after your plan's history window (7, 30, 90 or 365 days); identities and evidence until you delete them or a data-subject request is processed; the credit ledger (which holds no visitor data) for accounting purposes. At the end of the service, everything is deleted within 30 days.
6. Sub-processors
The third parties below receive visitor data on your behalf for Reveal. The maintained list is at /legal/reveal-subprocessors. We give 30 days' notice by e-mail before adding one; you may object and terminate without penalty.
| Provider | Location | What for | What it can see |
|---|---|---|---|
| PryntID (own infrastructure) | United States | Ingestion, company resolution, console, storage | The Reveal data set: minimised + hashed IP, session, company, first-party identities you collected with consent |
| Cloudflare, Inc. | United States (global network) | DNS, CDN, TLS and DDoS protection for api.pryntid.com — the beacon passes through it | Request metadata in transit, including the visitor's full IP address |
| Stripe, Inc. | United States | Billing of Reveal plans and credit packs | Your billing contact and payment details — never visitor data |
| Twilio Inc. (SendGrid) | United States | Transactional email: daily Reveal recap, data-subject-request notices, quota alerts | Your team's addresses and the recap content (company names; people masked unless you enable includeContact) |
| DeepSeek | China | The console assistant | Only what a person types into the assistant — the console does not send Reveal data to it |
Destinations you choose (Slack, HubSpot, n8n, Zapier, your own webhooks, e-mail recipients) are your processors, not ours: you configure them, you decide whether a person's contact details leave the console (off by default; people are masked), and you hold your own agreement with each of them. Outbound payloads never carry an IP address, an IP hash, a fingerprint or a device id.
Data sources that receive nothing from us and are therefore not sub-processors: iptoasn, DB-IP Lite (CC BY 4.0), PeeringDB (network classification only), bgp.tools (ASN tags), Wikidata / Common Crawl (company facts). Reverse DNS lookups are disabled by default; if we ever enable them, the resolver becomes a sub-processor and is added to the list first.
7. Security measures specific to Reveal
- Every query is scoped to your account; our automated test suite calls every console and API route with another customer's identifiers and fails on any successful answer.
- Integration secrets are encrypted at rest; identifiers are hashed with a salt; every console action is written to the audit log; platform operators require multi-factor authentication.
- Deletion requests remove the person, their identifiers, evidence and session links, and leave a suppression so the person is not re-created.
8. Data-subject rights
Anyone can opt out of identification on every site that uses Reveal at /legal/reveal-opt-out (also in Spanish and Portuguese); identification of that address stops immediately, platform-wide, and the deletion is processed by an operator within 30 days. You can record and process access and deletion requests from the console; we assist you with requests and regulator enquiries, and we notify you of requests received through the public page that concern your data.
9. International transfers
Reveal runs on servers Prynt operates in the United States. For visitors in the EU/EEA and the UK, the Standard Contractual Clauses (module 2) and the UK Addendum incorporated in our DPA apply; a transfer impact assessment is available on request. Prynt operates from Ecuador and registers its international transfers with the SPDP where required.
The SPDP registration point is pending confirmation by our counsel.
10. CCPA / CPRA service-provider terms
Prynt does not sell or share personal information; does not retain, use or disclose it outside the direct business relationship with you or for any purpose other than providing Reveal; does not combine the personal information of different customers to identify a person (sessions, accounts and people are never joined across customers); and certifies that it understands these restrictions.
11. Your obligations
- Have a lawful basis and a notice for company-level identification, and obtain the consent your jurisdiction requires before signalling consent to the script.
- Do not use Reveal data for decisions covered by the FCRA, to re-identify anonymous visitors, for unsolicited e-mail in breach of CAN-SPAM or equivalent laws, or in sensitive sectors without a prior review.
- Honour opt-outs, and do not try to link device ids across sites of different controllers.
Review your use of Reveal and these texts with your own counsel.
12. Audit and liability
As in the main Data Processing Agreement.
Model texts for your site
Suggested wording — review it with your own counsel before publishing.
Cookie banner line
Under an analytics or functional category, never a strictly-necessary one:
We use Prynt Reveal to recognise the company you are visiting from (based on your network, never your name) and, only if you identify yourself to us, to link that to your visit. You can opt out at any time at pryntid.com/legal/reveal-opt-out.
Privacy-policy paragraph
Company-level visitor identification. We use Prynt Reveal (PryntID, United States) to understand which organisations visit our website. Prynt derives the organisation from the network your device connects from (IP address, which is minimised and hashed before storage) together with public network registries. It does not identify you as an individual and does not use data purchased from third parties. If you identify yourself to us — for example by submitting a form or logging in — we may link that first-party information to your visits so that our team can follow up, and we record the basis on which you shared it. Prynt processes this data on our behalf under a data processing agreement, does not sell it and does not share it with other Prynt customers. Legal basis: our legitimate interest in understanding business interest in our products (and your consent where our cookie banner asks for it). Retention: [plan window] for visit data; identities until you ask us to delete them. You can opt out of identification on every site that uses Prynt at pryntid.com/legal/reveal-opt-out, or ask us at [[email protected]].
Opt-out page text (if you host your own)
Opt out of visitor identification. Enter the email address you have used on our website. From that moment no site that uses Prynt Reveal will link that address to a visit again, and we will process the deletion of what we hold about it within 30 days. We never confirm whether an address was known to us. Company-level statistics (which organisations visit, without names) are not affected.
This draft is informational; the executed DPA and annex govern.