SECJUR Digital Compliance Office

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 secjur GmbH · www.secjur.com

Report an error on this page Is this your product? →

Link to this page

SECJUR Digital Compliance Office: AI-assisted analysis on whats-best.ai SECJUR Digital Compliance Office: 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.

SECJUR Digital Compliance Office at a glance

Vendor
secjur GmbH
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
In the EU; pages mention Germany source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates SECJUR Digital Compliance Office 2.5/5, the mean of 6 judges. SECJUR's Digital Compliance Office combines compliance software with expert consulting, and the bench scored it strongest on framework coverage and integrations and automation, both sitting at 7 with no spread: fourteen frameworks from DSGVO and the Swiss nDSG to the EU AI Act run on one shared data basis with controls cross-mapped, and over sixty named connectors, a documented REST API and an MCP server feed registers from the existing IT estate. how scores are made
As of
Vendor pages captured 24 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

SECJUR Digital Compliance Office alternatives, European ones first →

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

The panel's verdict

SECJUR's Digital Compliance Office combines compliance software with expert consulting, and the bench scored it strongest on framework coverage and integrations and automation, both sitting at 7 with no spread: fourteen frameworks from DSGVO and the Swiss nDSG to the EU AI Act run on one shared data basis with controls cross-mapped, and over sixty named connectors, a documented REST API and an MCP server feed registers from the existing IT estate. Privacy management and audit readiness cluster at 6–7, with versioned, linked documentation, document packages and a live Trust Center. Rights and incidents holds at 4 — no public information on a 72-hour notification clock, verified request intake, or deletion periods tied to the record. Pricing transparency runs 0–2: Festpreis and planbare Paketpreise are described but never numbered, and pricing runs through 'Angebot anfordern'. Judges split on sovereignty: marketing claims 'Hosted in Germany' with development, hosting and support fully in Germany, while the vendor's own privacy policy discloses a Webflow website host in San Francisco and no legal page confirms where platform customer data is stored.

Report an error

Speaks for it

  • Framework coverage sits at 7 with no spread, fourteen frameworks from DSGVO and the Swiss nDSG to the EU AI Act cross-mapped on one shared data basis
  • Integrations and automation also sits at 7, with over sixty named connectors, a documented REST API and an MCP server exposing platform data to AI tools
  • Documentation is held centrally, linked and versioned, and the Compliance Hub builds document packages behind a live public Trust Center
  • Experts review AVV contracts and privacy incidents, with unlimited consulting at a fixed price

Report an error

Held against it

  • Pricing transparency scores run 0–2 — planbare Paketpreise and Unlimitierte Beratung zum Festpreis are described, but the captured pages state no prices for any edition, module or company size and pricing runs through 'Angebot anfordern'
  • Rights and incidents holds at 4, and we found no public information on a 72-hour notification clock, identity verification at intake, or deletion periods tied to the record
  • The captured pages give different figures for where data sits — 'Hosted in Germany' in marketing versus a privacy policy naming Webflow, Inc. in San Francisco for the vendor's website — and no legal page confirms where platform customer data is stored
  • We found no public information on a platform data processing agreement, a platform subprocessor list, or single sign-on with SCIM provisioning and webhooks
  • The captured pages give different figures for the cost advantage — 50 %, up to 55 % and up to 67 % günstiger — without reconciling them

Report an error

Best for

  • You need one record serving several regimes — DSGVO, Swiss nDSG, NIS2, TISAX — with controls mapped across frameworks rather than maintained per regime
  • You want an expert-managed setup where a dedicated expert builds and operates the system on a fixed-price package while your team supplies information and approvals
  • You want registers fed from your existing IT estate through over sixty integrations and a REST API instead of re-typing
  • You must send authorities or customers assembled document packages and a live Trust Center without reformatting

Report an error

Avoid if

  • You need to budget from public pages — the captured pages state no prices for any edition, module or company size and every configuration runs through 'Angebot anfordern'
  • Your obligations turn on a 72-hour breach clock, verified request intake or tracked deletion periods, for which we found no public information
  • Your procurement requires legal-page confirmation of data residency — the Germany claim appears in marketing copy while the privacy policy names a San Francisco host for the vendor's website

Report an error

The scores

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

Records & DPIA depth

Show 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.

Report an error

The External DPO

The Digital Compliance Office modules give me processing activities with TOMs and DSFA connected, vendor management with AVV contract review, and a record of processing built from templates with automation — the core build I need per client. The pages never show legal bases modelled into the record, DPIA need derived from it, or templates reusable across companies, and nothing speaks to multi-client operation for an external data protection officer, so I stop just above a solid modular offering. 2 8 8

Report an error

The In-House Counsel

The register of processing activities, TOMs, DPIAs and data subject requests are named modules, processing activities are described as carrying TOMs and DPIAs, vendor management covers processors with AVV contract review, and everything sits on a shared data model with templates and automation for the register. We found no public information on legal bases linked per activity, DPIA need derived from the record, or an Article 30 output formatted for a supervisory authority, so I hold it just below a fully connected model. 8 2 8

Report an error

The Drafted Generalist

The Digital Compliance Office lists a records-of-processing module with TOMs and privacy impact assessments attached, plus vendor management and contract management with AVV review, all described as sitting on one shared data state. That guided structure and the three-hours-instead-of-fifty claim for the register are exactly the relief I need; the captured pages do not show DPIA need being derived from the record, reusable templates across companies, or an Article 30 register formatted for a supervisory authority. 8 1 2 8

Report an error

The Lead Auditor

The platform lists the records of processing, DPIAs, TOMs and vendor management as named modules, with processing activities carrying their TOMs and DPIAs in one place and all modules working from a shared data basis, plus contract management with DPA review. The captured pages describe the linking as intelligent and versioned but show no legal bases modelled on the record, no DPIA need derived from the register, and no Art. 30 register output ready for a supervisory authority — so this sits above a modular product without reaching a fully connected system of record. 2 8 8 1

Report an error

The IT Integrator

The data protection module carries processing records with TOMs and DPIAs, vendor and contract management with AVV review, and data subject requests, all on one shared data basis that reuses what you record across frameworks — a connected model rather than a document pile. The pages do not show DPIA need being derived from the record or an authority-ready Article 30 export, so it lands below the top band. 2 8 8 1

Report an error

The Skeptic

The platform page lists a Verarbeitungsverzeichnis with TOMs and DSFA, plus vendor management and contract management including AVV review, all on a shared data basis — a real DSMS module set, and the GDPR page shows VVT templates with automation. But the deeper connections — legal bases tied to processing activities, DPIA need derived from the record, an Art. 30 register ready for a supervisory authority — we found no public information on, and the AVV review is a human expert reading your contracts rather than something the software models. 2 8 8

Report an error

Data subject rights & incidents

Show 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.

Report an error

The External DPO

Requests are handled 'fristgerecht' and incidents are captured, assessed and reported, with privacy incidents reviewed by experts — workflows rather than bare logs. I found no public information on the 72-hour clock, identity verification on intake, or deletion periods tied to the record with execution tracked, so I cannot place this higher. 2 8

Report an error

The In-House Counsel

Requests are worked 'fristgerecht' in a dedicated module, incidents are captured, assessed and reported with expert review of each privacy incident, and recurring deadlines plus automated email notifications exist. We found no public information on a 72-hour Article 33 clock, request intake with identity verification, or deletion periods recorded per processing activity — the clocks I defend on are not in evidence. 2 8 2

Report an error

The Drafted Generalist

Data subject requests get their own module promising deadline-compliant handling, and privacy incidents can be entered, assessed and reported with experts reviewing each case. That is a genuine register and a workflow start, but the captured pages do not document the 72-hour notification clock, an intake form with identity verification, or deletion periods tied to the processing record. 8 1 2

Report an error

The Lead Auditor

Data subject requests are described as handled within the deadline, and incidents can be recorded, assessed and reported, with experts reviewing each privacy incident. We found no public information on a 72-hour breach clock, deletion periods per processing activity, an intake portal with identity verification, or deadline escalation. 2 8

Report an error

The IT Integrator

Data subject requests are worked deadline-compliantly in their own module and incidents are captured, evaluated and reported, with experts reviewing privacy incidents — real workflows, not a logbook. We found no public information on a 72-hour breach clock, identity verification at intake, or deletion rules tied to processing records, so I stop it just above the register level. 2 8 1

Report an error

The Skeptic

Request handling 'fristgerecht' and incident capture with 'erfassen, bewerten, melden' give the operational half a shape, and the GDPR page shows privacy incidents entered and then reviewed by experts. We found no public information on the 72-hour notification clock, deadline reminders or escalation, identity verification at intake, or any deletion concept with tracked execution. 2 8

Report an error

Privacy regime coverage

Show 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.

Report an error

The External DPO

GDPR plus the Swiss nDSG is named in the privacy module with a Bern entity behind it, and the machinery is real: one data basis with controls mapped across frameworks and the EU AI Act added as a maintained module in 2025. No UK GDPR or per-country variants beyond Switzerland appear, and a documented update cadence when a regime changes is reduced to a platform-updates page and past launch history. 2 5 1 5

Report an error

The In-House Counsel

GDPR and the revised Swiss nDSG sit in one privacy module, EU AI Act content launched in 2025 and NIS2 in 2023, platform updates are published, and controls are mapped across all frameworks on one shared data model — regime coverage as maintained content rather than a static checklist. We found no public information on ePrivacy/TTDSG, BDSG or UK GDPR variants, which keeps it short of the top level. 5 1 2 5

Report an error

The Drafted Generalist

GDPR and the Swiss nDSG are handled in one data protection module, the EU AI Act got its own management module in 2025, and controls are mapped across every framework on a shared data basis. One record serving several laws is precisely what I want so updates land once; we found no public information on BDSG-specific content, ePrivacy/TTDSG or per-country variants. 5 1 2 5

Report an error

The Lead Auditor

Fourteen frameworks from DSGVO and the Swiss nDSG to the EU AI Act, DORA and the whistleblowing law run on one platform with controls cross-mapped between them, so one record serving several regimes is evidenced rather than each regime standing alone. Newer duties (EU AI Act, ISO 9001) were added as maintained content in 2025 and a Bern office serves the revised nDSG market. We found no public information on BDSG-specific content, TTDSG/ePrivacy coverage, or a documented update cadence when a law changes. 5 2 1 5

Report an error

The IT Integrator

GDPR and the revised Swiss nDSG run in one data protection module, the EU AI Act arrived in 2025 as maintained content with an AI register, and controls map across frameworks on a single data basis — multi-regime coverage without fresh islands. We found no public information on BDSG-specific or TTDSG/ePrivacy content, and the update cadence appears only as a platform-updates resource, which caps it below the living-regime level. 2 5 1 5 3

Report an error

The Skeptic

DSGVO and the Swiss nDSG sit together in one privacy module 'an einem Ort', German specialities like Hinweisgeberschutzgesetz, NISG and Geldwäschegesetz are listed, controls are cross-mapped across frameworks on one shared data basis, and the EU AI Act arrived as maintained content in 2025. We found no public information on ePrivacy/TTDSG or UK GDPR, and beyond a 'Plattform-Updates' label the pages show no documented update cadence when a regime changes. 2 1 5 5

Report an error

Audit readiness & evidence

Show 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.

Report an error

The External DPO

Documentation is 'verknüpft und versioniert', evidence sits centrally retrievable 'wenn Behörden oder Kunden fragen', and the Compliance Hub builds document packages plus a live Trust Center — client-ready output I can send on without reformatting. Read-only auditor access and reproducing a record as it stood on a given date are not shown, which keeps it below the top band. 1 2 8

Report an error

The In-House Counsel

Documentation is stored centrally, linked and versioned, evidence is attached per control and retrievable for auditors, authorities and customers, and the compliance hub generates document packages plus a live trust center, with internal audit and management review run on the platform. We found no public information on a revision-safe change history, read-only auditor access, or reproducing any record as it stood on a given date — for a defensible file I would want those warranted. 1 2 4 8

Report an error

The Drafted Generalist

Documentation is described as central, linked and versioned, evidence is retrievable when authorities or customers ask, the Compliance Hub builds document packages behind a live Trust Center, and a dashboard shows progress per framework. Read-only auditor access and reproducing any record as it stood on a past date are not documented on the captured pages, so this is strong but not a standing audit-ready state. 1 2 4 8

Report an error

The Lead Auditor

Documentation is held centrally, linked and versioned, all measures are described as provable for audits, authorities and customers, and the Compliance Hub produces document packages alongside a live public Trust Center, with a dashboard showing progress per framework and experts handling internal audit and management review. We found no public information on revision-safe change history, read-only auditor access, or reproducing any record as it stood on a given date — the ask I put to every system first. 8 1 2 4

Report an error

The IT Integrator

Documentation is versioned and linked, every measure is documented as evidence for audits, authorities and customers, and the Compliance Hub assembles document packages with a live Trust Center, backed by a claimed 100% ISO 27001 audit success rate for customers. We found no public information on read-only auditor access or on reproducing any record as it stood on a given date, so the proof packs are strong but the standing-state test is not documented. 2 1 8 4

Report an error

The Skeptic

Documentation is 'verknüpft und versioniert', evidence sits centrally retrievable when authorities or customers ask, and the module list carries audit questionnaires, supplier audits and document packages through a public Trust Center. Read-only auditor access, management reports at a click, and any record reproducible as it stood on a given date we found no public information on — and the claimed 100 % ISO 27001 audit success rate is a figure the captured pages do not substantiate. 1 8 2 4

Report an error

Integrations & automation

Show 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.

Report an error

The External DPO

A documented REST API, 60-plus named connectors spanning HR and payroll, identity, cloud and ERP, Jira, file-based register import for assets, risks and suppliers, recurring deadline tasks, an AI assistant where the customer grants approvals, and even an MCP server into Claude — this is the automation depth that saves me hours per mandate. I found no public information on webhooks, single sign-on with SCIM provisioning, or delegation and escalation rules. 2 9 2 1

Report an error

The In-House Counsel

A documented REST API, over sixty integrations across HR & Payroll, identity management, ERP and ticketing (JIRA among them), file import for assets, risks and suppliers, automated control checks and an AI assistant with an MCP server — the platform feeds from the real IT estate instead of re-typing. We found no public information on single sign-on with SCIM provisioning or webhooks. 2 9 2

Report an error

The Drafted Generalist

Over sixty named connectors across HR, identity, cloud and ticketing (AWS, Azure, BambooHR, JIRA), a documented REST API, file import for assets, risks and vendors, automated control checks and an AI assistant. That is the feeding-from-the-real-estate setup I need so nothing gets re-typed; single sign-on provisioning and webhooks are not documented on the captured pages. 2 9 2 3

Report an error

The Lead Auditor

A documented REST API and an MCP server exposing platform data into AI tools, plus a named connector catalogue of 60+ integrations across HR & Payroll, Identity Management, cloud, ERP and DevOps categories, with recurring deadlines, automated control checks under continuous monitoring, and an AI assistant for compliance questions. We found no public information on single sign-on with SCIM provisioning, webhooks, or escalation paths in workflow automation. 2 9 2

Report an error

The IT Integrator

This is my kind of page: 60+ integrations with Jira, Azure, AWS and HR sources named, an Identity Management category, a REST API to embed DCO data in your own systems, an MCP server exposing that data to AI tools, and automated control checks under continuous monitoring. The register import for assets, risks and suppliers is still done by file, and we found no public information on webhooks, single sign-on with SCIM provisioning or two-way sync, so the evidence does not reach the infrastructure level. 2 9 2 3

Report an error

The Skeptic

A documented REST API, 60+ API integrations with named connectors across HR, cloud, identity and ticketing (Jira, BambooHR, AWS, Azure), file-based register import, automated control checks under Continuous Monitoring and deadline reminders put this well past the basics. We found no public information on webhooks, SSO with SCIM provisioning or two-way sync; the AI features are named — KI-Assistent, MCP-Server, AI Firewall — but the pages show little substance behind the AI Firewall beyond the label. 2 9 2 3

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The External DPO

The contracting entity is secjur GmbH in Hamburg, and 'Hosted in Germany' with development, hosting and support fully in Germany is claimed prominently; the privacy policy, however, discloses that the vendor's website runs on Webflow, Inc. in San Francisco, and no legal page states where platform customer data is stored. I found no published data processing agreement or platform subprocessor list, and for a platform holding my clients' entire processing map that gap decides the level. 6 1 7 8

Report an error

The In-House Counsel

A German GmbH registered in Hamburg with a Swiss subsidiary, development, hosting and support stated as entirely in Germany, and a privacy policy addressing Article 44 third-country safeguards with German subprocessors named for recruiting and invoicing. The captured pages give different figures for where data sits — marketing states 'Hosted in Germany' while the privacy policy discloses a US-hosted website and US web analytics — and we found no public information on a data processing agreement for the platform, a platform subprocessor list, or the data centres used. 6 7 1

Report an error

The Drafted Generalist

A Hamburg GmbH with hosting, development and support stated as fully in Germany, ISO 27001 certification and a trust centre — the right words for where my compliance record would live. But we found no public information on a published data processing agreement or a platform subprocessor list, and the vendor's own privacy policy has their website running on Webflow in San Francisco. 4 6 7 1 2

Report an error

The Lead Auditor

The contracting entity is the secjur GmbH of Hamburg with a German register entry and VAT ID, and Germany is stated as the default for development, hosting and support — though that statement appears in marketing copy while the privacy policy itself names a San Francisco host for the vendor's website and no legal page confirms where platform customer data is stored. The privacy policy publishes subprocessors, including German processors Personio and sevDesk and Google LLC (USA) for web analytics, and names safeguards for third-country transfers. We found no public information on a data processing agreement for the platform, named data centres, or an on-premises option. 6 1 7 3

Report an error

The IT Integrator

A German GmbH in Hamburg holds the record, with hosting, development and support claimed entirely in Germany and ISO 27001 certification claimed — the compliance data would sit under German law. The captured pages qualify that: the Germany hosting statement is marketing copy, the vendor's own website runs on Webflow in San Francisco, and we found no public information on a customer data processing agreement, a platform subprocessor list or named data centres. 6 1 4 3 7

Report an error

The Skeptic

The contracting entity is secjur GmbH in Hamburg with a German register number and VAT ID, 'Hosted in Germany' is claimed with development, hosting and support fully in Germany, and the investors shown are European. But the Germany-exclusivity appears only in marketing copy, the privacy policy states the vendor's own website runs with Webflow, Inc. in San Francisco and names Google LLC (USA) as an analytics processor, and we found no public information on a data processing agreement, a platform subprocessor list, or where customer platform data is actually stored. 6 1 7 3

Report an error

Pricing transparency

Show 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.

Report an error

The External DPO

The captured pages state the model — 'Planbare Paketpreise', 'Unlimitierte Beratung zum Festpreis', positioned against hourly consulting — but no figure appears anywhere and the path is 'Angebot anfordern'. Every configuration is a sales conversation, so I cannot price a client from public pages. 4 2 1 8

Report an error

The In-House Counsel

The model is public — Festpreis, 'Planbare Paketpreise', 'Unlimitierte Beratung zum Festpreis', '50% günstiger als klassische Beratung' — but no figure, edition boundary or per-entity price is published, and everything runs through 'Angebot anfordern'. A buyer cannot compute any part of the invoice from public pages, and consulting is bundled with the software rather than separated. 2 3 4

Report an error

The Drafted Generalist

The captured pages describe the pricing model — fixed price, plannable package prices, unlimited expert consulting — but show no figures, and pricing ends in 'Angebot anfordern'. I know the shape of the invoice, not its amount, so budgeting for my eighty-person firm starts with a sales call. 2 1 4 8

Report an error

The Lead Auditor

Only the pricing model is public: a fixed price, "planbare Paketpreise", unlimited consulting at a fixed price, and the claim of being 50 percent cheaper than classic consulting. The captured pages state no prices for any edition, module or company size, and pricing runs through "Angebot anfordern" — a buyer cannot compute an invoice from the public pages alone. 4 3 2 1

Report an error

The IT Integrator

No price figure is public: "Planbare Paketpreise" sits behind "Angebot anfordern", and the fixed-price model with unlimited consulting at a fixed price is described but never numbered — even the 50- and 250-employee comparison segments carry no amounts. A buyer cannot compute any invoice from these pages; every configuration is a sales conversation. 4 2 1 8

Report an error

The Skeptic

The pages promise 'Planbare Paketpreise' and 'Unlimitierte Beratung zum Festpreis' yet show no figure a buyer could compute with — the route to an invoice is 'Angebot anfordern', and consulting is bundled into the package rather than priced separately. The captured pages also give different figures for the cost advantage (50 %, up to 55 %, and up to 67 % günstiger) without reconciling them. 4 2 1 8 3

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 unverified
Why unverified?

The exclusivity claim appears only in homepage marketing copy; the privacy policy itself states the vendor's website is hosted by Webflow, Inc. in San Francisco, USA, and no legal page confirms where platform 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 determined — uncited Report an error

Questions about SECJUR Digital Compliance Office

Is SECJUR Digital Compliance Office European?

Yes. whats-best.ai classifies SECJUR Digital Compliance Office as EU-Made. Its vendor, secjur GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does SECJUR Digital Compliance Office store data?

SECJUR Digital Compliance Office stores customer data in the EU, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 2 Nov 2026.

Does SECJUR Digital Compliance Office have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to SECJUR Digital Compliance Office?

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: SECJUR Digital Compliance Office 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 (9)

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

  1. 1 Vendor homepage www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  2. 2 Platform page www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  3. 3 ISMS product page www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  4. 4 ISO 27001 product page www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  5. 5 About page www.secjur.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 24 Aug 2026 Details →
  6. 6 Imprint www.secjur.com Checked 16 Nov 2026 Details →
  7. 7 Privacy policy www.secjur.com Checked 16 Nov 2026 Details →
  8. 8 Privacy regime coverage — found from sitemap www.secjur.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  9. 9 Integrations & automation — found from sitemap www.secjur.com Checked 16 Nov 2026 Details →