Data Processing Agreement
Last updated: October 31, 2026
This summary describes how Prynt processes personal data on your behalf. A signable DPA is available to any customer on request at [email protected].
Roles
You (the customer) are the data controller. Prynt is the data processor, processing device and network signals only to provide the identification and fraud-detection service you configure — never for our own purposes and never sold.
Scope of processing
- Categories of data: pseudonymous device signals, a derived visitor ID, IP address (minimized per your configuration), and any linkedId/tag you send.
- Purpose: visitor identification and bot/fraud risk scoring for your properties.
- Duration: identification data is kept for your plan's retention window (Free 30 days, Pro 90, Scale 365, Enterprise as agreed) and deleted automatically after it; everything is deleted on account closure or on request. See retention.
Security & sub-processors
Prynt encrypts secrets at rest, restricts access, and maintains an audit log. The current sub-processors are listed on our Trust page, and we update that list before adding a new one.
The intelligence network
What is shared between accounts: one-way, salted hashes of the visitor IDs, IP addresses and account IDs (linkedId) that an account reported as fraud or abuse — through the outcomes API or «Mark as fraud» in the console — and nothing else. An entity an account only put on its deny list, or only blocked with one of its rules, counts for less and enters the network only when several accounts agree. Raw values, email addresses and identities are never exchanged, and a hash cannot be turned back into the value.
What Prynt counts across accounts: whether the same device (a hash of its on-device fingerprint), the same IP address or a newly appearing network (ASN) shows up at several accounts within 24 hours, and which bot user-agent tokens appear across them. This runs on our servers. An account only ever receives a flag and a number of other accounts — never which accounts, and never anything about their visitors. Visitor IDs stay scoped to the account that issued them and are not linked across customers.
Every account contributes by default and can stop at any time in the console (Rules & Risk › Reputation network). From the next rebuild, every six hours, its labels and its traffic are left out of both the shared hashes and the counts. Checking the network keeps working either way.
How the network works · Data Processing Agreement
Your rights & assistance
Prynt honors GPC/Do-Not-Track, supports data export and right-to-erasure, and assists with data-subject requests and regulator inquiries under GDPR Art. 28 and LGPD.
This summary is informational; the executed DPA governs.