Prynt Reveal — Sub-processors
Who receives visitor data when you use Prynt Reveal, what each one can see, and what is deliberately not on this list.
Draft of November 3, 2026
What counts as a sub-processor
A sub-processor is a third party that receives personal data of your website visitors on your behalf. The data sources Prynt downloads (network and company registries) receive nothing from us, so they are not sub-processors; they are listed separately below for transparency.
This list covers Prynt Reveal. The platform-wide list for Prynt's device-intelligence product is on the Trust page. Both are referenced by the Reveal DPA annex.
Current sub-processors
| Provider | Country | Purpose for Reveal | What it can see |
|---|---|---|---|
| PryntID (own infrastructure) — API, database and console on servers operated by PryntID | United States | Ingestion (/v1/reveal/collect), company resolution, console, storage | The whole Reveal data set: minimised IP + hash, session, company, first-party identities collected with consent |
| Cloudflare, Inc. | United States (global network) | DNS, CDN, TLS and DDoS protection for api.pryntid.com — the beacon passes through Cloudflare | Request metadata in transit, including the visitor's full IP address (Prynt reads it to resolve the company, then stores only the minimised form) |
| Stripe, Inc. | United States | Billing of Reveal plans and credit packs | Your billing data — 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 it; the console does not send Reveal data to the assistant |
Destinations you choose (not our sub-processors)
Slack, HubSpot, n8n, Zapier, generic webhooks and the recipients of email integrations are configured by you. You decide whether contact details are included (includeContact, off by default: people are masked) and you hold your own data-processing agreement with each of them.
Outbound payloads never carry an IP address, an IP hash, a fingerprint or a device id (visitorId).
People-identity providers: none
Prynt Reveal uses no third-party provider to identify people. The provider path exists in the code only as a disabled adapter, and an automated test checks that it never creates a person while it is switched off. If that ever changed, this list would be updated before, with 30 days' notice.
Data sources (no personal data transferred)
- iptoasn (IP-to-ASN tables)
- DB-IP Lite (CC BY 4.0)
- PeeringDB (network classification only)
- bgp.tools (ASN tags)
- MaxMind GeoLite2 (development only)
- Wikidata / Common Crawl (company facts)
These are downloaded datasets: lookups run on Prynt's own servers and nothing about your visitors is sent to them.
Exception to watch: reverse DNS lookups (disabled by default) and any one-off RDAP query send the queried IP to the DNS resolver or the regional internet registry. If either is enabled in production, it becomes a transfer and the resolver (for example Cloudflare 1.1.1.1) is added to this list first.
Changes and objections
We give 30 days' notice by email before adding or replacing a sub-processor. You may object; if we cannot address the objection, you may terminate Reveal without penalty.
Questions: [email protected].
This draft is informational; the executed DPA and annex govern.