PrivacyPerfect
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Privacy Perfect B.V. · privacyperfect.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
PrivacyPerfect at a glance
- Vendor
- Privacy Perfect B.V.
- Headquarters
- Incorporated in the Netherlands source, captured 2 Nov 2026
- Data hosting
- In the EU source, captured 2 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 2 Nov 2026
- Panel verdict
- The AI panel rates PrivacyPerfect 3/5, the mean of 6 judges. PrivacyPerfect's strongest scoring is on connected privacy operations: rights and incident handling sits at 7, with breach reportability decided from the built-in processing inventories, reports configurable per supervisory authority, stored notification records and reasons not to notify, and data subject requests run as a managed workflow; privacy management runs 6-7, the lower score citing unproven registers for processors' data processing agreements and technical and organisational measures. how scores are made
- As of
- Vendor pages captured 1 Nov 2026 to 2 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
PrivacyPerfect's strongest scoring is on connected privacy operations: rights and incident handling sits at 7, with breach reportability decided from the built-in processing inventories, reports configurable per supervisory authority, stored notification records and reasons not to notify, and data subject requests run as a managed workflow; privacy management runs 6-7, the lower score citing unproven registers for processors' data processing agreements and technical and organisational measures. Scores drop for audit readiness and sovereignty at 4 and integrations at 3-4: the pages show repeatable reporting, but we found no public information on versioned records, evidence packs or auditor access, and while the vendor states it is fully EU-based and processes all client data in the Netherlands, we found no public information on a data processing agreement or subprocessor list. The spread worth naming is framework coverage at 6-7, where one rationale credits GDPR operationalised on EDPB guidance and another calls the 13+ jurisdictions claim a bare marketing figure. Pricing transparency runs 0-1: a free trial and a demo booking, and no public price on the captured pages.
Speaks for it
- A new transfer impact assessment auto-fills from the existing processing activity, and selecting a Standard Contractual Clause automatically flags the assessment need.
- Breach reportability is decided from the built-in processing inventories, with reports configurable per supervisory authority and notification records and reasons not to notify stored.
- Data subject requests run as a managed workflow with request-type validation, follow-up actions, reminders and one-click identification of data sources and recipients.
- Coverage spans four modules — Privacy Management, Information Security Management, Third Party Risk and AI Assessment Manager — with registrations claimed across 13+ major jurisdictions including Europe and Japan.
- The vendor states it is fully EU-based and processes all client data in the Netherlands, with ISO 27001 certification claimed and PrivacyAgent B.V. of Rotterdam named in the terms.
Held against it
- We found no public information on an API, single sign-on, or directory and ticketing connectors, leaving any feed from the real IT estate unproven.
- Audit readiness scores sit at 4, with no public information on revision-safe change history, on-demand evidence packs or auditor access, and the ISO 27001 statement carrying no certificate number.
- We found no public information on a data processing agreement, a subprocessor list or named data centres beyond the stated Netherlands processing.
- The 13+ jurisdictions claim names no national law with its own templates, and we found no public information on an update cadence for legal content when a regime changes.
- We found no public price for any edition or module, the only entry points being a free trial and a demo booking.
Best for
- You run GDPR day to day and want breach reportability and data subject requests decided from one connected inventory instead of re-typed records.
- You assess international transfers often and want the TIA to start from the existing processing record, with Standard Contractual Clause selection auto-flagging the assessment need.
- You want a single platform spanning Privacy Management, Information Security Management, Third Party Risk and the AI Assessment Manager on a GDPR-first basis.
Avoid if
- You need state-on-a-given-date audit evidence; audit readiness scores sit at 4 and we found no public information on change history, evidence packs or auditor access.
- Your privacy records must sync from an existing estate via API, single sign-on or directory and ticketing connectors; integrations and automation scores run 3-4 and we found no public information on any of these.
- You must see a published data processing agreement, subprocessor list or named data centres before lodging your compliance record in one cloud; sovereignty scores sit at 4.
- You need a public starting price to budget against; the captured pages show a free trial and a demo booking and we found no public price.
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 3.5 of 5 |
| Data subject rights & incidents | 3.5 of 5 |
| Privacy regime coverage | 3 of 5 |
| Audit readiness & evidence | 2 of 5 |
| Integrations & automation | 2 of 5 |
| European sovereignty | 2 of 5 |
Records & DPIA depth
Show reasoningHide reasoning
How this is scored
The DSMS core: records of processing activities (RoPA/VVT, Art. 30 DSGVO), data protection impact assessments (DSFA, Art. 35), processor and DPA management (AVV), and technical and organisational measures (TOMs) — how deeply the legal artefacts are modelled and connected.
0 — Not a privacy management tool; at most a set of document templates with no structured records.
3 — A structured record of processing activities with templates, and a DPIA questionnaire or checklist.
5 — Records of processing and DPIAs as modules with templates, processors and their DPAs recorded, and TOMs documented and assigned to processing activities.
8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA need derived from the record, reusable templates across companies, and outputs (Art. 30 register, DPIA report) ready for a supervisory authority.
10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client capability for external data protection officers, and the documentation is audit-ready without manual assembly.
The External DPO
This is the architecture I bill hours on: assessments pre-fill from the existing processing activity, the need for a transfer impact assessment is tracked per activity and auto-triggered when a standard contractual clause is selected, and breach analysis draws on the same built-in processing inventory. The half missing for a thirty-mandate practice: we found no public information on processors with their data processing agreements recorded, on technical and organisational measures assigned to processing activities, or on reusable templates across companies for multi-client use. 3 4 5 7 7
The In-House Counsel
Records sit at the centre: data mapping, quick-fill DPIAs, and per-processing tracking of which TIA, DPIA or LIA still needs doing, with a new transfer assessment auto-filled from the existing processing record. I stop short of the top band because processors with their data processing agreements, and technical and organisational measures assigned to processing activities, are not verifiable on the captured pages. 3 5 7
The Drafted Generalist
This is where I would actually get work done: a transfer impact assessment starts from an existing processing activity and fills itself in, selecting a standard contractual clause automatically flags whether an assessment is needed, and TIAs, DPIAs and LIAs sit in one place tracked per processing activity. The record system is fully customisable with quick-fill records, and both the breach logic and the request module read from the same processing records. I found no public information on how vendors' data processing agreements or technical and organisational measures are documented and attached to each activity. 3 5 7 7
The Lead Auditor
Privacy records, DPIAs, TIAs and LIAs are centralised and tied to processing activities — a TIA can be started from an existing processing activity with the information auto-filled, and the tool tracks which processing activity still needs an assessment. We found no public information on processor and DPA registers or on technical and organisational measures assigned to processing activities, so the connected data model is only half-proven. 1 3 7 7
The IT Integrator
The records are genuinely connected rather than re-typed: a transfer impact assessment starts on an existing processing activity with the relevant information automatically filled in, assessments (TIA, DPIA, LIA) sit centralised alongside the privacy records with tracking of which activity has been assessed, and the breach and data subject modules draw directly from the built-in processing inventories. I found no public information on processor DPA registers, technical and organisational measures assigned to activities, or reusable templates across companies, which keeps it short of a fully connected data model. 3 7 5 4
The Skeptic
Processing records, DPIAs, LIAs and transfer impact assessments are documented as centralised and tied to the specific processing activity — a new assessment auto-fills from the existing record and selecting Standard Contractual Clauses automatically flags the assessment need, which is a connected data model rather than a template pack. What keeps me short of the top of that scale: we found no public information on how processors' data processing agreements or technical and organisational measures are modelled and linked to processing activities, and no authority-ready DPIA report output is described. 3 7 7
Data subject rights & incidents
Show reasoningHide reasoning
How this is scored
The operational half of the DSMS: handling data subject requests within the Art. 12 deadline, a breach register with the 72-hour notification of Art. 33, and deletion concepts that are carried out.
0 — No handling of data subject requests or data breaches in the product.
3 — A log of data subject requests and a register of data breaches, with templates for the responses.
5 — Request workflows with the one-month Art. 12 deadline tracked and reminders, a breach register with the 72-hour clock and a risk assessment per breach, and deletion periods recorded per processing activity.
8 — An intake form or portal for requests with identity verification, deadline escalation, breach severity assessment producing the authority notification, and deletion rules tied to the RoPA with execution tracked.
10 — Rights and incidents as operations: end-to-end request handling an authority audit can walk through, breach workflows that produce the Art. 33 and Art. 34 notifications, and deletion automation with evidence that the deletion happened.
The External DPO
Requests run as workflow rather than a log — registration, request type validation, automatic identification of the involved records and recipients, collaboration with reminders and approval requests — and the breach side determines reportability to the supervisory authority and data subjects from the processing inventories, with reports configurable to each authority's format and stored notification records including the reasons not to notify. We found no public information on an intake portal with identity verification, the one-month deadline clock, or deletion execution evidence, which is what separates a good register from an audit-proof operation. 3 4 5
The In-House Counsel
The breach module draws on the built-in processing inventories to determine whether an incident must be reported to the supervisory authority and the data subjects, produces reports configurable to each authority's format, and stores the notification records together with the reasons not to notify — that is the Article 33/34 file I need. Requests run as managed workflows with reminders and one-click identification of data sources and recipients; we found no public information on a 72-hour clock, identity verification at intake, or deletion execution with evidence. 4 5
The Drafted Generalist
The request side is a guided workflow rather than a spreadsheet: registration, validating the request type, identifying the processing activities involved, follow-up actions, reminders, approval requests and one-click detection of data sources and recipients. The breach register covers reported and unreported incidents, weighs consequences using the existing processing inventories to decide whether the supervisory authority and data subjects must be told, and produces reports configurable to each authority's format. I found no public information on a tracked one-month deadline clock, identity verification at intake, or a 72-hour timer. 4 5
The Lead Auditor
The breach side is genuinely operational: a register of reported and unreported incidents, reportability decided from the existing processing inventories, per-authority configurable reports, and notification records plus reasons not to notify stored in the system. Requests run through registration, validation, record identification and follow-up with automated reminders and approval requests; we found no public information on an intake portal with identity verification or on deletion execution being tracked. 3 4 5
The IT Integrator
Requests run as a managed workflow — registration, request type validation, identification of the processing activities involved, follow-up actions, collaboration, automated notifications, reminders and approval requests — and the breach module determines reportability to the supervisory authority and data subjects from the existing inventories, with reports configurable to each authority's format and notification records plus reasons not to notify stored. I found no public information on an intake portal with identity verification, or on the one-month and 72-hour deadline clocks being tracked and escalated. 4 5
The Skeptic
Request handling is a documented workflow — registration, validation of the request type, follow-up actions, reminders, approvals, collaboration — with data sources and recipients identified at a click, and the breach register draws on the processing inventories to decide whether the supervisory authority and data subjects must be notified, storing the notification records and the reasons not to notify. We found no public information on a data-subject intake portal with identity verification, an explicit one-month or 72-hour deadline clock, or deletion execution being tracked; retention terms are configurable, but carrying them out is not described. 4 5
Privacy regime coverage
Show reasoningHide reasoning
How this is scored
Which privacy regimes the product operationalises — DSGVO/GDPR, BDSG, TTDSG/ePrivacy, Swiss nDSG, UK GDPR, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.
0 — No privacy regime built in; a generic task or document tool.
3 — GDPR implemented with its registers, templates and checklists.
5 — GDPR plus the national law of its market (BDSG, nDSG or UK GDPR) named and supported with their own templates or requirements.
8 — Several regimes on one record with requirements mapped across them, newer duties (AI Act, ePrivacy/TTDSG) covered as maintained content, and updates published when a regime changes.
10 — Regime coverage as a living product: many privacy regimes and per-country variants on one data basis, and a documented update cadence when the law moves.
The External DPO
Registrations across thirteen-plus jurisdictions including Europe and Japan, from GDPR to global regulations, a dedicated AI assessment manager module, and internal policies cross-referenced across frameworks instead of duplicated per certification — that cross-referencing is exactly the reuse I need across mandates. We found no public information on named national-law templates, on whether one record maps across regimes, or on a documented update cadence when the law moves. 1 3 6 7
The In-House Counsel
GDPR is operationalised on guidance from national supervisory authorities and the EDPB, breach reports adapt to each authority's format, registrations are supported across 13+ major jurisdictions, and a dedicated AI assessment module covers the newer AI duties, with policies cross-referenced across frameworks instead of duplicated. We found no public information on named national law variants or a published update cadence when a regime changes — my standing test for legal content nobody visibly maintains. 3 5 6 7
The Drafted Generalist
They advertise privacy registrations for 13+ major jurisdictions from GDPR to global regulations, let one internal policy be cross-referenced across multiple frameworks instead of duplicated, and sell an AI Assessment Manager alongside the privacy core. I found no public information on per-country template variants or a published update cadence when a regime changes. 3 6 7
The Lead Auditor
GDPR is the backbone, with claims of 13+ jurisdictions from GDPR to global regulations, breach reports configurable per supervisory authority, and a request module built on EDPB and national authority guidance. An AI Assessment Manager module puts newer duties inside the product; we found no public information on multiple regimes mapped onto one record or a published update cadence when a regime changes. 1 3 4 5
The IT Integrator
The pitch is one platform from GDPR to global regulations, with privacy registrations across thirteen-plus jurisdictions including Europe and Japan, a dedicated AI Assessment Manager module, and framework management that cross-references policies to ISO 27001 and ISAE 3042 to avoid duplicate documentation. I found no public information on which national laws are supported by name with their own templates, or on a documented update cadence when a regime changes. 3 1 6 7
The Skeptic
GDPR is clearly the home ground, an AI Assessment Manager module covers the newer AI duties, internal policies can be cross-referenced across multiple frameworks, and the vendor claims 13-plus major jurisdictions including Japan. That jurisdiction count is a bare marketing figure — no national law is named with its own templates, and we found no public information on an update cadence for legal content when a regime changes; the weekly newsletter is news, not product maintenance. 1 3 6 7
Audit readiness & evidence
Show reasoningHide reasoning
How this is scored
Whether the system produces defensible proof: change history, evidence collection, and reports for auditors, authorities and management.
0 — No reports, history or evidence; the product only stores the current state.
3 — PDF or Word reports of the registers, and documents attachable to records.
5 — Versioned records or a change history, report generators for the core registers (RoPA, DPIA, TOMs), and evidence attached per processing activity or measure.
8 — A revision-safe change history, audit evidence packs generated on demand, management and data protection officer reports at a click, and read-only auditor access.
10 — Audit readiness as a standing state: documentation status shown continuously per regime and scope, proof packs an auditor accepts as they are, and any record reproducible as it stood on a given date.
The External DPO
Repeatable reporting and breach reports configurable to each supervisory authority's format are client-ready output, transfer assessments are presented as an auditable, defensible basis, and notification records are stored with reasons not to notify. We found no public information on change history or revision safety, on audit evidence packs generated on demand, or on read-only auditor access — the trail an authority walks through, not just reads. 3 4 7
The In-House Counsel
I can point to repeatable reporting, automated review management, stored breach notification records with reasons not to notify, and transfer assessments built to give an auditable, defensible basis — useful, but reporting is not an audit trail. We found no public information on versioned records, a revision-safe change history, evidence packs or read-only auditor access, so I cannot call the documentation defensible on the system's own showing. 3 4 7
The Drafted Generalist
You get repeatable, fully configurable reporting, automated review management, transfer assessments the vendor describes as an auditable and defensible basis, and a place to store notification records and the reasons not to notify. I found no public information on version history, on-demand evidence packs, or read-only access for an auditor. 3 4 6 7
The Lead Auditor
Assessments are stated to produce an accurate, consistent, auditable and defensible decision basis, breach notification records are stored in-system, and reporting is repeatable — that is reports and per-case evidence, not standing audit readiness. We found no public information on revision-safe change history, evidence packs generated on demand, or auditor access, which is exactly the state-on-a-given-date question an authority asks. 3 4 7
The IT Integrator
There is real evidence work documented: repeatable reporting, breach reports fully configurable per supervisory authority format, stored records of notifications and of the reasons not to notify, transfer assessments built to give an accurate, auditable and defensible basis, and framework management keeping documentation up to date through review cycles. I found no public information on versioned records, a revision-safe change history, evidence packs generated on demand, or read-only auditor access. 3 4 7 6
The Skeptic
Reports exist — repeatable reporting, and breach reports configurable to each supervisory authority's format — and the transfer assessment methodology claims an auditable, defensible decision basis, but that is a claim about an output document, not about the system. We found no public information on change history or versioning, evidence attached to records, on-demand evidence packs, or auditor access, and the ISO 27001 sentence on the homepage carries no certificate number or registry reference either. 3 4 7
Integrations & automation
Show reasoningHide reasoning
How this is scored
Whether the platform feeds from the real IT estate — directory import, ticketing, SSO, API — and automates the recurring privacy work instead of re-typing it.
0 — No import, export or integration; data is typed in and printed out.
3 — CSV or Excel import and export, and reminders for recurring reviews.
5 — Single sign-on, a documented API or a few named connectors (directory, ticketing), and recurring tasks with reminders and assignment.
8 — A documented REST API for the core objects, a named connector set (directory, ticketing, HR or asset sources), webhooks, SSO with SCIM provisioning, workflow automation with delegation and escalation, and AI assistance with human review.
10 — The platform behaves like infrastructure: API coverage of the whole data model, events or webhooks for every object, two-way sync with the estate, and recurring work (reviews, attestations, evidence collection) automated and documented.
The External DPO
The internal automation genuinely saves hours: assessments pre-filled from the record, SCC selection automatically triggering the transfer impact assessment need, automated review management, and reminders with approval requests in request handling. But we found no public information on an API, single sign-on, connectors to directory, ticketing or HR sources, or import and export — for thirty mandates that is the difference between a system of record and thirty subscriptions to retype into. 3 5 7 7
The In-House Counsel
The recurring privacy work is automated — risk assessments, review management, notifications, reminders and quick-fill of records. But we found no public information on an API, single sign-on, directory or ticketing connectors, or import and export, so I cannot confirm the platform feeds from the real IT estate rather than re-typed data. 3 5 7
The Drafted Generalist
The recurring privacy work inside the tool is genuinely automated: assessments pre-filled from the processing record, contract-clause selection triggering assessment needs, automated review management, reminders and approval requests. I found no public information on an API, single sign-on, or connectors to directories, ticketing or HR sources, so nothing shows it feeds from the real IT estate instead of hand-typing. 3 5 7
The Lead Auditor
The recurring privacy work is automated and real: quick-filled records and DPIAs, automated risk identification, a TIA auto-triggered by selecting standard contractual clauses, automated review management, and one-click identification of data locations for requests. We found no public information on a documented API, single sign-on, or directory and ticketing connectors, so the pages show no feed from the real IT estate. 3 5 7 7
The IT Integrator
In-product automation is credible — quick-fill DPIAs and privacy records, transfer assessments auto-filled from the processing activity, selecting a Standard Contractual Clause automatically identifying the need for a TIA, and automated review management with reminders, notifications and approval requests. But the estate side is undocumented: I found no public information on an API, webhooks, single sign-on, SCIM provisioning, directory or ticketing connectors, or import and export, so I cannot confirm this platform would sync with the Entra ID, Jira and CMDB we already run rather than becoming another island. 3 5 7 7
The Skeptic
Inside the platform, automation is genuinely evidenced: quick-fill DPIAs, automatic risk identification, automated review management, reminders, approval requests, one-click data-location detection. Outside the platform we found no public information on an API, single sign-on, webhooks, directory or ticketing connectors, or spreadsheet import and export on the captured pages. 3 5 7
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the compliance record of the whole company actually lives and under whose law: contracting entity and parent company, hosting location, subprocessors (hosting, AI features, email, support tooling), DPA. A platform that maps your processing is itself your most concentrated processing. Independently sourced by the sovereignty pipeline; describe what is proven, and treat what is not stated as unknown rather than non-EU.
0 — Proven non-EU end to end: non-EU entity and non-EU hosting with no EU option, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist; hosting location and subprocessors are not stated, or EU hosting is offered only on request or on top tiers.
5 — EU hosting stated as the default, a data processing agreement and a subprocessor list published; a parent company or a subprocessor may sit outside the EU.
8 — EU entity, EU hosting in named data centres, a subprocessor list with no non-EU processor touching customer content, and the DPA and TOMs published.
10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, an on-premises or sovereign-cloud option, and the whole chain documented publicly.
The External DPO
The vendor states all client data is processed in the Netherlands, fully EU-based, and the terms of use name PrivacyAgent B.V. with a registered office in Rotterdam. We found no public information on a data processing agreement, a subprocessor list, or named data centres — and a platform that maps a client's most concentrated processing owes the buyer that chain publicly. 1 2 4
The In-House Counsel
The vendor states it is fully EU-based and processes all client data in the Netherlands, contracts run through PrivacyAgent B.V. of Rotterdam, and the company is ISO 27001 certified — entity and hosting are European on the vendor's own pages. We found no public information on the data processing agreement, the subprocessor list or named data centres, and that gap is exactly what I must close before lodging our compliance record in one cloud. 1 2 4
The Drafted Generalist
The vendor's own homepage states it is fully EU-based and processes all client data in the Netherlands, the terms of use name PrivacyAgent B.V. as the company behind PrivacyPerfect with a Rotterdam address, and ISO 27001 certification is claimed. I found no public information on a published subprocessor list, a data processing agreement, or the named data centres used. 1 2 4
The Lead Auditor
The contracting entity is a Dutch B.V. registered in Rotterdam, and the vendor states it is fully EU-based, processing all client data in the Netherlands, with ISO 27001 certification claimed. The data processing agreement, transfer impact assessment offering and subprocessor list are unknown on the captured pages, so the jurisdictional picture is proven at the ends and undocumented in the middle. 1 2 4
The IT Integrator
EU hosting is stated as the default — all client data processed in the Netherlands under GDPR — the terms name PrivacyAgent B.V. with registration number at a Rotterdam address as the contracting entity, and ISO 27001 certification is claimed. I found no public information on a published data processing agreement, a subprocessor list, or the law named in the governing law section, so the chain beyond EU hosting and the Dutch entity stays unproven rather than disproven. 1 2 4
The Skeptic
EU hosting is stated outright — all client data processed in the Netherlands — and the terms name a Dutch B.V. with a Rotterdam office and registration number as the contracting entity. But we found no public information on a data processing agreement, a subprocessor list, or the data centres used, and the terms put the entity behind the trade name as 'PrivacyAgent B.V.', so a buyer should confirm precisely whom they are contracting with. 1 2 6
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.
0 — No public prices at all; every configuration is a sales conversation.
3 — A public "from" price or one priced edition; the other editions, modules or entity counts are not public.
5 — Public prices per edition or tier with the billing period (monthly or annual) stated and the main inclusions listed.
8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated, software separated from consulting, and VAT treatment given; only genuine corporate-group contracts are custom.
10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a 10-client consultancy is a two-minute exercise.
The External DPO
The only public entry points are a free trial and a Book A Demo button; we found no public information on editions, module prices, billing periods or entity boundaries. Computing a per-client, per-year invoice from public pages alone is not possible — every configuration begins with a sales conversation. 4 5 6 7
The In-House Counsel
The captured pages publish a free trial and a demo booking and we found no public pricing of any kind — no editions, modules, user counts or billing terms. The invoice is only computable through a sales conversation, which is common in this market but leaves the buyer without even a starting figure. 1 6
The Drafted Generalist
The captured pages offer a free trial and a demo booking and nothing else about money; I found no public prices, editions or billing periods, so there is nothing to compute a real invoice from without a sales conversation. 4 6
The Lead Auditor
The only public commercial signals are a free trial and a bookable demo; no edition, module or entity pricing appears on the captured pages, so a buyer cannot begin to estimate the invoice from public material. 6 7
The IT Integrator
The captured pages offer a free trial and a demo booking and I found no public price on any of them — not for the Privacy Management, Information Security, Third Party Risk or AI Assessment Manager modules, nor editions, user or entity boundaries, billing periods or setup fees. Computing a real invoice from these pages alone is not possible; every configuration starts with a sales conversation. 6 4 5
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in NL
unverified
Why unverified?Only the main office location and a registration number are given; no commercial register (e.g. KvK) is named, but the country is explicit. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?Homepage marketing copy; no privacy policy, DPA or subprocessor list in the excerpts confirms where customer data is stored. |
4/4 pts | 1 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment |
Not needed, no transfer outside the EU/EEA
unverified
Why unverified?Inferred from a homepage marketing claim about processing, not from a compliance document addressing transfers or subprocessors; the vendor publishes no TIA of its own (S7 only describes a TIA feature sold to customers). |
1/1 pts | 1 Report an error |
Questions about PrivacyPerfect
Is PrivacyPerfect European?
Not determined: the vendor’s pages as captured do not say where PrivacyPerfect is based. Its vendor, Privacy Perfect B.V., is incorporated in the Netherlands, per the vendor’s page captured 2 Nov 2026.
Where does PrivacyPerfect store data?
PrivacyPerfect stores customer data in the EU, per the vendor’s page captured 2 Nov 2026.
Does PrivacyPerfect have a free plan?
Not stated on the vendor’s pages as of 2 Nov 2026.
What are the best alternatives to PrivacyPerfect?
As of 19 Nov 2026, the panel rates preeco | datenschutz (3.5/5), caralegal (3.5/5) and Dastra (3.5/5) highest among the other 46 Data Protection products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is preeco | datenschutz (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: PrivacyPerfect alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Transfer impact assessment. Inferred from a homepage marketing claim about processing, not from a compliance document addressing transfers or subprocessors; the vendor publishes no TIA of its own (S7 only describes a TIA feature sold to customers).
- Weak sourcing — Legal entity. Only the main office location and a registration number are given; no commercial register (e.g. KvK) is named, but the country is explicit.
- Weak sourcing — Hosting location. Homepage marketing copy; no privacy policy, DPA or subprocessor list in the excerpts confirms where customer data is stored.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page privacyperfect.com Checked 2 Nov 2026 Details →
- 2 Terms of service — found from the homepage privacyperfect.com Checked 2 Nov 2026 Details →
- 3 Records & DPIA depth — found from sitemap privacyperfect.com Checked 2 Nov 2026 Details →
- 4 Data subject rights & incidents — found from sitemap privacyperfect.com Checked 2 Nov 2026 Details →
- 5 Data subject rights & incidents — found from sitemap privacyperfect.com Checked 2 Nov 2026 Details →
- 6 Privacy regime coverage — found from sitemap privacyperfect.com Checked 2 Nov 2026 Details →
- 7 Transfer-impact assessment (TIA) — found from the homepage privacyperfect.com Checked 2 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →