Wired Relations
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Wired Relations ApS · www.wiredrelations.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.
Wired Relations at a glance
- Vendor
- Wired Relations ApS
- Headquarters
- Incorporated in Denmark source, captured 2 Nov 2026
- Data hosting
- In the EU source, captured 16 Sep 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Wired Relations 3/5, the mean of 6 judges. Wired Relations (product name Cerivo) is strongest on audit readiness, 7 with no spread: evidence stored against the controls being tested, the Statement of Applicability and record of processing generated on demand. how scores are made
- As of
- Vendor pages captured 16 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Wired Relations (product name Cerivo) is strongest on audit readiness, 7 with no spread: evidence stored against the controls being tested, the Statement of Applicability and record of processing generated on demand. Privacy management follows at 6-7: connected processing-activity records, an Article 28 processor register, guided Article 35 DPIA workflows. Rights and incidents is weakest at a flat 4 — rights requests are workflows with the one-month deadline tracked, but incident handling is shown as root-cause and corrective-action logging. Framework coverage splits 4 to 6 — the pages map security standards (ISO 27001/2, NIS2, CIS 18, ISAE 3402) alongside GDPR with no public information on UK GDPR, BDSG, Swiss nDSG or AI Act content, and judges divide over how much the cross-framework control reuse offsets that. Sovereignty runs 6-7, lower scores weighing differing captured statements on sub processor location and the privacy policy allowing transfers outside the EU/EEA in some cases, against a Danish chain and Frankfurt and Paris hosting. Pricing remains "Talk to us" for the paid editions; free account and free trial are public.
Speaks for it
- Evidence stored in the platform linked to the controls being tested, with auditors able to see what is in place and what is missing
- A connected privacy core — processing activities with legal bases, data categories and systems, an Article 28 processor register with tracked review cycles, and Article 35 DPIA workflows with a complete audit trail
- Rights requests run as workflows with assigned ownership, the one-month deadline tracked and outcomes documented per request
- Single sign-on with user provisioning, Azure Active Directory user synchronisation (37 users synchronised), Slack notifications, a public API and automatically recurring tasks with owners and due dates
- Danish group entities at one Copenhagen address, hosting on AWS and MongoDB Atlas stated as exclusively within the EU/EEA in data centres in Frankfurt (Germany) and Paris (France), a published sub processor list reviewed yearly and a data processing agreement offered
Held against it
- Incident handling is shown as root-cause and corrective-action logging, with no public information on a 72-hour breach clock, authority notification output or deletion periods recorded per processing activity
- No public information on national privacy law variants such as BDSG, the Swiss nDSG or UK GDPR, or on AI Act or ePrivacy duties as maintained content
- No public information on technical and organisational measures assigned directly to processing activities, on DPIA need derived from the record, or on multi-client use for external data protection officers
- The captured pages give different statements on sub processor location — one restricted to the EU/EEA, another allowing countries with an adequate level of protection — and the privacy policy states data may in some cases be transferred outside the EU/EEA under stated safeguards
- No public information on revision-safe change history across records or on reproducing any record as it stood on a given date
Best for
- You need GDPR accountability in one connected system — record of processing, Article 28 processor register, Article 35 DPIAs and Article 30 reporting generated from the same data
- You are preparing an ISO 27001 or NIS2 audit and want evidence stored against controls, with one-click Statement of Applicability generation and Excel export
- Your compliance calendar depends on recurring work — tasks that recur automatically with owners and due dates, and vendor questionnaires sent pre-filled and returned into the system
- You want a Nordic vendor — Danish group entities at one Copenhagen address, hosting in Frankfurt and Paris, and a yearly ISAE 3000-II assurance report
Avoid if
- You need end-to-end breach operations — the incident handling shown is root-cause and corrective-action logging, and we found no public information on a 72-hour clock or supervisory-authority notification output
- You must maintain several national privacy regimes — the frameworks published alongside GDPR are ISO 27001/2, NIS2, CIS 18 and ISAE 3402, and we found no public information on UK GDPR, BDSG or AI Act content
- You run a multi-client consultancy — the published base structure includes 1 company, and we found no public information on reusable templates across client companies
- You require a provably EU-only chain end to end — the privacy policy states data may in some cases be transferred outside the EU/EEA under Data Privacy Framework or standard contractual clause safeguards
The scores
| Criterion | Panel median |
|---|---|
| Records & DPIA depth | 3.5 of 5 |
| Data subject rights & incidents | 2 of 5 |
| Privacy regime coverage | 2.5 of 5 |
| Audit readiness & evidence | 3.5 of 5 |
| Integrations & automation | 3 of 5 |
| European sovereignty | 3.5 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
Processing activities are mapped with legal bases, data categories and systems in one place, a processor register tracks DPAs and review cycles under Article 28, DPIA workflows under Article 35 keep a complete audit trail, and risks connect to processing activities, systems and vendors — the connected model I bill hours against. The pages do not show TOMs assigned directly to processing activities, DPIA need derived from the record, or reusable templates across client companies, which is what a thirty-mandate practice lives on. The RoPA and other reports auto-generate, so the Article 30 output is client-ready. 3 3 1 3
The In-House Counsel
The record of processing activities maps activities to legal bases, data categories and systems and is auto-generated for the supervisory authority, processors and their data processing agreements sit in a vendor register, and DPIAs run as a guided Article 35 workflow with a full audit trail. What holds it below the top bands: I found no public information on DPIA need being derived from the record, on reusable templates across companies for external data protection officers, or on technical and organisational measures assigned per processing activity — the controls I can see live in the ISO module, tied to frameworks and risks. 3 3 3 1
The Drafted Generalist
The privacy product pages show a real records core: processing activities mapped with legal bases, data categories and systems, a processor register per Article 28 with data processing agreements and review cycles tracked, and an Article 35 DPIA workflow that captures decisions with an audit trail — and the Article 30 register is auto-generated. I stop short of the top because we found no public information on technical and organisational measures being assigned to individual processing activities, on DPIA need being derived from the record, or on multi-client use for an external data protection officer. 3 3 3 1
The Lead Auditor
The record of processing activities is documented with activities, legal bases, data categories and systems mapped in one place, processors and their data processing agreements tracked under Article 28, and impact assessments run per Article 35 with decisions captured and a maintained audit trail. Risks and mitigating controls connect to processing activities, systems and vendors, which reads as a connected data model rather than parallel folders. We found no public information on assessments being triggered from the record itself, on reusable templates across companies, or on multi-client use by external data protection officers, so it stops short of the system-of-record level. 3 3 3 2 1
The IT Integrator
The record of processing activities maps activities, legal bases, data categories and systems, processors and their data processing agreements are tracked under Article 28, DPIAs run as a guided Article 35 workflow with an audit trail, and risks are connected to specific activities, systems and vendors — a connected model rather than parallel registers — with the Article 30 register auto-generated as a report. I found no public information on DPIA need being derived from the record, on TOMs assigned directly to processing activities, or on multi-client capability for external data protection officers. 3 3 3 1
The Skeptic
This is a real record system, not a template pack: processing activities carry legal bases, data categories and systems, an Article 28 register tracks processor agreements and review cycles, Article 35 DPIA workflows capture decisions with an audit trail, risks link to activities, systems and vendors, and the Article 30 register is generated from the data. I found no public information on technical and organisational measures being modelled and assigned to processing activities, or on DPIA need being derived from the record, which is what the highest level requires. 1 3 3 3
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
Rights requests run as workflows with ownership, the one-month deadline tracked and outcomes documented for access, erasure and portability — genuinely operational, not a log. Incidents are logged with root causes and corrective actions linked to controls and risks, but I found no public information on a 72-hour breach clock, authority notification output, deletion periods recorded per processing activity, or evidence that deletions were executed. 3 3 5 4
The In-House Counsel
Rights requests carry ownership, a tracked one-month deadline and documented outcomes — that is the clock I need — but the incident module is an ISMS-style log of root causes and corrective actions linked to controls and risks. I found no public information on a breach register with the 72-hour clock, a workflow producing the Article 33 notification, or deletion periods recorded per processing activity, so I cannot treat the incident side as defensible yet. 3 3 5
The Drafted Generalist
Rights handling looks genuinely operational: Chapter III requests get an owner, the one-month deadline is tracked, and outcomes are documented, with notifications when tasks are due. The incident side is described as logging root causes and corrective actions linked to controls and risks rather than a 72-hour breach workflow, and we found no public information on deletion periods recorded per processing activity or an intake portal with identity verification. 3 3 5 1
The Lead Auditor
Rights requests under GDPR Chapter III are handled as workflows with ownership assigned, the one-month response deadline tracked and outcomes documented, and incidents are logged with root causes and corrective actions linked to controls and risks. We found no public information on a 72-hour notification clock, on severity assessment producing the authority notification, or on deletion periods tied to processing activities with execution tracked, so the operational half is only partly evidenced. 3 3 5 1
The IT Integrator
Rights requests run as genuine workflows — ownership assigned, the one-month deadline tracked, outcomes documented per request — and incidents are logged with root causes and corrective actions tied to controls and risks. I found no public information on a 72-hour breach clock, authority notification outputs, an intake portal with identity verification, or deletion rules tied to the record of processing, so this reads as solid tracking rather than end-to-end operations. 3 5 3
The Skeptic
Rights requests are concrete — ownership assigned, the one-month deadline tracked, outcomes documented for access, erasure and portability — but the incident side is generic root-cause and corrective-action logging tied to controls and risks, not a 72-hour breach workflow. I found no public information on a request intake portal with identity verification, deletion periods per processing activity, or notifications produced for the supervisory authority. 3 3 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
GDPR is a full module, and one control links to ISO 27001, NIS2, CIS 18, ISAE 3402 and custom frameworks with a single update reflecting everywhere it applies — one record serving several regimes. I found no public information on national privacy law variants such as BDSG, the Swiss nDSG or UK GDPR, on AI Act or ePrivacy duties, or on a published update cadence when a regime changes. 5 2 1 3
The In-House Counsel
GDPR is operationalised deeply — Articles 30, 35, 28 and Chapter III all appear — and one control maps across ISO 27001/2, NIS2, CIS 18, ISAE 3402 and custom frameworks with a single update. Those are management-system frameworks rather than privacy regimes: I found no public information on BDSG, Swiss nDSG, UK GDPR, TTDSG/ePrivacy or AI Act content, nor a published update cadence when the law moves; the in-house Nordic lawyers are an advisory service, which suggests maintained content but does not prove it inside the product. 5 2 3 1
The Drafted Generalist
GDPR is built in as a full module, and the security pages show one control linked across ISO 27001/2, NIS2, CIS 18 and ISAE 3402 with a change reflected everywhere it applies — genuinely one record, several regimes. Those additions are information-security regimes, though, and we found no public information on Swiss nDSG, UK GDPR, BDSG or AI Act duties as maintained content or on a published update cadence when a law moves. 5 1 2
The Lead Auditor
GDPR is operationalised as a module with registers and privacy documentation, and one control can be linked across GDPR, ISO 27001/2, NIS2, CIS 18 and ISAE 3402 with a single update reflecting everywhere it applies, with data reused across frameworks. We found no public information on national privacy law variants such as BDSG, nDSG or UK GDPR, on ePrivacy or AI Act content, or on a published update cadence when a regime changes. 5 2 1 3 8
The IT Integrator
GDPR is implemented as a full module — processing activities, DPIAs, data subject requests, vendor register — and the cross-framework design is real: one control links to multiple frameworks with updates reflected everywhere, and data is reused across frameworks. The regimes named alongside GDPR are security and GRC standards (ISO 27001/2, NIS2, CIS 18, ISAE 3402); I found no public information on additional privacy regimes such as national data protection laws, UK GDPR or AI Act duties as maintained content. 5 3 1
The Skeptic
GDPR is the one privacy regime operationalised with registers and workflows, and the cross-framework story is genuine for security regimes — one control links across ISO 27001/2, NIS2, CIS 18, ISAE 3402 and custom sets, with data reused across GDPR, ISMS and ISO. I found no public information on national privacy law variants such as BDSG, the Swiss nDSG or UK GDPR, or on ePrivacy or AI Act duties as maintained content. 1 3 5
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
Evidence is stored against the controls being tested with auditors able to see what is in place and what is missing, the Statement of Applicability and RoPA generate at a click for management or external auditors, policies are versioned with adoption tracked, historical questionnaires are saved for comparison, and read-only access exists. I found no public information on a revision-safe change history across all records or on reproducing a record as it stood on a given date. 5 5 1 4 3 8
The In-House Counsel
Evidence is stored linked to the controls being tested, auditors can see what is in place and what is missing, the statement of applicability is generated in one click with an Excel export, and management reporting combines control status, risk exposure, open tasks and policy adoption, with read-only access available for reporting purposes. I found no public information on a revision-safe change history across records or on reproducing any record as it stood on a given date, which is what I would want in a contested inspection. 5 5 1 3 4 8
The Drafted Generalist
Evidence is stored in the platform linked to the controls being tested and auditors can see what is in place; the Statement of Applicability and the records-of-processing report generate in a click and export to Excel, with management reporting that combines control status, risk exposure, open tasks and policy adoption. Policy versioning and saved historical questionnaires give history, but we found no public information on reproducing any record exactly as it stood on a given date. 5 5 1 4
The Lead Auditor
Evidence is stored in the platform linked to the controls being tested and visible to auditors, the Statement of Applicability and the record of processing are generated at a click with implementation status, and management reporting combines control status, risk exposure, open tasks and policy adoption; policies are versioned with acknowledgement tracking and the assessment workflow keeps a complete audit trail. We found no public information on a revision-safe change history across all records or on reproducing any record as it stood on a given date — the standing state I want to see before an audit, not assembled in the week before it. 5 5 4 1 3 3
The IT Integrator
Evidence is stored in the platform linked to the controls being tested where auditors can see what is in place and what is missing, the Statement of Applicability generates on demand at any given time, reports are produced for management or external auditors, and policies are versioned with adoption tracking. DPIAs claim a complete audit trail and a customer ties their ISO 27001 certification to documenting controls in the system; I found no public information on revision-safe history for every record or formal read-only auditor accounts. 5 5 4 1 3
The Skeptic
Auditor-facing proof goes beyond a PDF export: evidence is stored in the platform linked to the controls being tested, the SoA and RoPA generate at a click for management or external auditors, DPIAs carry a complete audit trail, historical vendor questionnaires are kept for comparison, and read-only access exists for reporting purposes. I found no public information on a revision-safe change history for every record or on reproducing any record as it stood on a given date. 1 4 8 3 5 5
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
Single sign-on with user provisioning, a public API, pre-built integrations, Azure Active Directory user synchronisation and Slack notifications are documented, and tasks recur automatically with owners, due dates and notifications when audits fall due. The API's coverage of core objects is not detailed, and I found no public information on webhooks, SCIM provisioning, workflow escalation or AI assistance. 3 3 5 8 2 4
The In-House Counsel
A public API, pre-built integrations, SSO with user provisioning, Azure Active Directory user synchronisation and Slack notifications are all evidenced, and recurring tasks with owners, due dates and notifications automate the review cycles. I found no public information on documented REST coverage of the core objects, webhooks, SCIM or AI assistance, and the API price is stated to depend on actual usage, so its scope is not fully visible to a buyer. 3 3 3 5 8
The Drafted Generalist
Single sign-on with user provisioning, a public API, pre-built integrations, Azure Active Directory user synchronisation and Slack notifications are all named, and the automation story is real for recurring work: tasks recur automatically with owners, vendor audits run on a recurring schedule, and audit questionnaires go out pre-filled and return themselves. We found no public information on webhooks, on the API's documentation depth, or on AI assistance with human review. 3 3 5 8
The Lead Auditor
Single sign-on with user provisioning, a public API and named connectors including Azure Active Directory user synchronisation and Slack notifications are documented, alongside recurring tasks with owners and due dates, automated vendor questionnaire round-trips and vendor lists uploaded to start audit workflows. We found no public information on webhooks, on SCIM-based provisioning specifically, or on a documented REST surface for the core objects. 3 3 4 8 1
The IT Integrator
This is what I look for: live Azure Active Directory user synchronisation (37 users synchronised), SSO with user provisioning, a public API whose price depends on actual usage, Slack notifications, tasks that recur automatically with owners and due dates, and audit questionnaires that vendors answer and return into the system without re-typing. It stops short of behaving like infrastructure: I found no public information on webhooks, a ticketing or HR connector, or documented REST coverage of the core objects, and the vendor onboarding shown is a list upload rather than a connector. 3 3 3 8 5 2
The Skeptic
Single sign-on with user provisioning, a public API, Azure Active Directory user synchronisation, Slack notifications, vendor-list upload and automatically recurring tasks with owners and due dates are all named on the captured pages. I found no public information on webhooks, SCIM by name, ticketing or HR connectors, or documented REST coverage of the core objects — and the API is priced by actual usage with no public rate, which leaves its breadth an open question. 2 3 8 3 5
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
A Danish group — every entity registered at Nannasgade 28, Copenhagen — with customer data hosted exclusively in the EU in named centres in Frankfurt and Paris, a published subprocessor list with yearly reviews, a data processing agreement offered, and yearly ISAE 3000-II audits: the compliance record lives where I want it. The captured pages give different statements on subprocessor location, one restricting them to the EU/EEA and another allowing countries with an adequate level of protection, and the privacy policy acknowledges some transfers outside the EU/EEA under the Data Privacy Framework and standard contractual clauses. I found no public information on an on-premises or sovereign-cloud option. 5 6 6 6
The In-House Counsel
The contracting chain is Danish — Wired Relations ApS as a group company of Cerivo ApS in Copenhagen — hosting sits in named EU data centres in Frankfurt and Paris on AWS and MongoDB Atlas, a data processing agreement is offered, and a complete sub processor list is published with yearly risk reviews. It stays short of the top band because the privacy policy states that data may in some cases be transferred outside the EU/EEA under the Data Privacy Framework or standard contractual clauses, and the captured pages give different formulations of the sub processor policy, one limited to inside the EU/EEA and one allowing countries with an adequate level of protection; I also found no public information on an on-premises or sovereign-cloud option. 5 6 6 6
The Drafted Generalist
The company is Danish within an all-Danish group, customer data runs on AWS and MongoDB Atlas in named centres in Frankfurt and Paris, sub-processors are reviewed yearly from a published list, and a data processing agreement is offered. The captured pages give different positions on third-country transfers — the security pages say sub-processors sit inside the EU/EEA while the privacy policy reserves transfers outside it under Data Privacy Framework and standard contractual clause safeguards — so I cannot call the chain fully EU-clean end to end. 5 6 6
The Lead Auditor
All contracting entities sit in Copenhagen under a Danish group, hosting is stated as exclusively EU/EEA in named data centres in Frankfurt and Paris, a complete sub processor list is published with yearly risk reviews, a data processing agreement is offered, and technical and organisational measures plus an annual ISAE 3000 report are published. The captured pages give different pictures on third-country transfers — the security page states sub processors are inside the EU/EEA only, while the privacy policy says data may in some cases be transferred outside the EU/EEA with safeguards — and we found no public information on an on-premises or sovereign-cloud option, so I stop short of a fully clean chain. 5 6 6 6
The IT Integrator
The chain is European on the pages captured: a Danish group of entities at one Copenhagen address, hosting on AWS and MongoDB Atlas in data centres named as Frankfurt and Paris exclusively within the EU/EEA, a data processing agreement offered, and a complete sub-processor list published with yearly reviews. The captured pages give different figures on third-country transfers — sub processors restricted to the EU/EEA on the security page, while the privacy policy states data may in some cases be transferred outside it under Data Privacy Framework or standard-clause safeguards — and I found no public information on an on-premises or sovereign-cloud option. 5 6 6 6
The Skeptic
The chain is Danish — Wired Relations ApS sits in the Cerivo ApS group — data lives in named EU data centres in Frankfurt and Paris on AWS and MongoDB Atlas, a data processing agreement is offered, subprocessors are risk-assessed yearly, and a complete list is claimed. The captured pages give different statements on subprocessor location: the security page says inside the EU/EEA only, while the privacy policy allows processors in adequacy countries and transfers outside the EU/EEA in some cases under the Data Privacy Framework or standard contractual clauses; I found no public information on an on-premises or sovereign-cloud option. 5 6 6 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
No monetary figure appears anywhere: Pro and Enterprise both say "Talk to us", and module pricing is described only qualitatively — depending on number of assessments, actual API usage, or setup — though a free account and a free trial are public. Edition inclusions and boundaries such as policy audiences of up to 200 users are listed, but for a ten-client consultancy the invoice is a sales conversation, which is this market's norm. 2 1
The In-House Counsel
The only public price points are the free account and free trial; both the Pro and Enterprise editions read "Talk to us", and the pricing notes say the API price depends on actual usage, some setup depends on configuration, and assessments are priced by their number — so the real invoice for any paying configuration is a sales conversation. A policy audience limit of 200 users is the only quantified boundary published on the pricing page. 2 1
The Drafted Generalist
A free account and free trying are public, and a few boundaries are stated — one company in the base structure, policy tracking for audiences of up to 200 users — but both the Pro and Enterprise plans say "Talk to us", and add-ons are priced by actual API usage, number of assessments or setup. For an 80-person firm like mine the real invoice stays a sales conversation, which is normal for this market but leaves me budgeting blind. 2 1
The Lead Auditor
A free account and free trial are public and the Pro and Enterprise editions list their inclusions, but both carry "Talk to us" rather than a price, and module pricing is described only by its drivers: "Price depends on number of assessments", "Price depends on actual API usage", "Price depends on setup". A buyer cannot compute a real invoice from the public pages alone, which is common in this market and recorded here as a description rather than a verdict. 2 1
The IT Integrator
The pricing page names the editions (Pro, Enterprise) with their inclusions, a free account is offered publicly, and add-ons declare their pricing basis — actual API usage, number of assessments, setup — which shows how an invoice is shaped. Every paid figure is 'Talk to us', so a buyer cannot compute the real invoice from public pages alone. 2 1
The Skeptic
Both named editions say 'Talk to us', the add-ons are priced by opaque factors — the API by actual usage, assessments by count, one integration by setup — and limits such as one company or policy audiences up to 200 users appear with no figures, so beyond a free account and a free trial nothing is computable. The in-house Nordic lawyers' advisory is advertised on the pricing page itself, bundled with the software and unpriced separately. 1 2 2
European sovereignty — proven facts
2 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 DK
unverified
Why unverified?Wired Relations ApS is listed as a group company under Cerivo ApS (also Denmark); only a business registration number is given, with no commercial register named. |
2/2 pts | 6 Report an error |
|---|---|---|---|
| Hosting location | EU only | 4/4 pts | 5 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 determined | — | uncited Report an error |
Questions about Wired Relations
Is Wired Relations European?
Yes. whats-best.ai classifies Wired Relations as EU-Made. Its vendor, Wired Relations ApS, is incorporated in Denmark, per the vendor’s page captured 2 Nov 2026.
Where does Wired Relations store data?
Wired Relations stores customer data in the EU, per the vendor’s page captured 16 Sep 2026.
Does Wired Relations have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Wired Relations?
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: Wired Relations alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. Wired Relations ApS is listed as a group company under Cerivo ApS (also Denmark); only a business registration number is given, with no commercial register named.
- 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.
- 55 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 22 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 support 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.wiredrelations.com Checked 16 Nov 2026 Details →
- 2 Vendor pricing page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
- 3 Privacy/GDPR product page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
- 4 ISMS product page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
- 5 Security/trust page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
- 6 Privacy policy wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 26 Oct 2026 Details →
- 7 Privacy regime coverage — found from sitemap www.wiredrelations.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 8 Audit readiness & evidence — found from sitemap www.wiredrelations.com Checked 16 Nov 2026 Details →