Wired Relations

EU-Made Report an error

Panel 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

Wired Relations: AI-assisted analysis on whats-best.ai Wired Relations: AI-assisted analysis on whats-best.ai (dark)

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

Wired Relations alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Lead Auditor

Weighted verdict

Audits management systems for a living and has seen every folder of screenshots. Optimizes for revision-safe history, evidence packs on demand, and a defensible answer to "show me the state on date X". Rejects systems where the audit trail is assembled the week before the audit.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Lead Auditor

Panel median The Lead Auditor This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Lead Auditor
Records & DPIA depth 3.5 of 5 3.5 of 5
Data subject rights & incidents 2 of 5 2 of 5
Privacy regime coverage 2.5 of 5 2 of 5
Audit readiness & evidence 3.5 of 5 3.5 of 5
Integrations & automation 3 of 5 3 of 5
European sovereignty 3.5 of 5 3.5 of 5

Records & DPIA depth

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.

Report an error

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

Report an error

Data subject rights & incidents

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.

Report an error

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

Report an error

Privacy regime coverage

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.

Report an error

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

Report an error

Audit readiness & evidence

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.

Report an error

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

Report an error

Integrations & automation

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.

Report an error

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

Report an error

European sovereignty

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.

Report an error

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

Report an error

Pricing transparency not rated — the vendor publishes no price

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.

Report an error

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

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

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

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.

Sources (8)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.wiredrelations.com Checked 16 Nov 2026 Details →
  2. 2 Vendor pricing page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
  3. 3 Privacy/GDPR product page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
  4. 4 ISMS product page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
  5. 5 Security/trust page wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 16 Sep 2026 Details →
  6. 6 Privacy policy wiredrelations.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 26 Oct 2026 Details →
  7. 7 Privacy regime coverage — found from sitemap www.wiredrelations.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  8. 8 Audit readiness & evidence — found from sitemap www.wiredrelations.com Checked 16 Nov 2026 Details →