Data Protection
SECJUR Digital Compliance Office
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 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? →
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, a compliance automation platform from secjur GmbH of Hamburg (Registergericht Hamburg, HRB 170383), is strongest on privacy regime coverage and integrations & automation: judges credit 10+ standards, cross-mapping, custom frameworks, a visible shipping cadence (NIS2 framework Q2 2023; EU AI Act and ISO 9001 launched 2025) and über 60 API-Anbindungen with JIRA named. It is weakest on pricing transparency (0-1: no prices anywhere, only 'bis zu 67% günstiger' against an unnamed baseline) and data subject rights & incidents (0-1: no data subject request intake, Art. 12/33 clocks, breach register or deletion workflow in evidence), with records & DPIA depth at 1-2, where 'Datenschutz' appears as a module name with no RoPA, DPIA, processor or TOM facts behind it — thin privacy evidence for a product filed under Data Protection. Sovereignty scores sit in one band: the GmbH and 'HOSTED IN GERMANY' banners hold, but no DPA, subprocessor list or named data centers appear, and the evidence lists ownership, data residency and subprocessors as unknown. No split between the judges was large enough to flag; persona-weighted totals span 2.2-3.3.
Speaks for it
- 10+ standards with cross-mapping and custom frameworks, and new law shipped on a visible cadence (NIS2 framework Q2 2023; EU AI Act and ISO 9001 in 2025)
- Über 60 API-Anbindungen with JIRA explicitly named (integrations & automation 4-6)
- Verifiable German entity — secjur GmbH, Registergericht Hamburg HRB 170383, VAT DE316838124 — behind 'HOSTED IN GERMANY' claims
- Vendor holds its own ISO 27001 certification and lists an internal data protection officer contact
- Optional certified compliance experts available alongside the self-service platform
Held against it
- No public price on any captured page — only relative claims like 'bis zu 67% günstiger' against an unnamed baseline
- No evidenced data subject rights or breach operations — no DSR intake, Art. 12/33 clocks, breach register or deletion workflow (data subject rights & incidents 0-1)
- 'Datenschutz' is a module name with no evidenced RoPA, DPIA, processor/DPA or TOM structure (records & DPIA depth 1-2)
- Audit evidence is outcome marketing — a claimed 100% success rate at customer ISO 27001 audits — with no revision-safe history, evidence packs or auditor roles (audit readiness & evidence 2-3)
- No published DPA, subprocessor list or named data centers in evidence, and the evidence lists ownership, data residency and subprocessors as unknown
Best for
- You are building an ISO 27001 ISMS first, with 20+ policy templates and a step-by-step navigator, and DSGVO rides along as one framework among 10+
- You want cross-mapped controls across a security-heavy catalogue (NIS2, DORA, TISAX, SOC 2) on one platform
- Your compliance work already lives in JIRA and you want tasks, notifications and priorities wired in through über 60 API-Anbindungen
- You are a German-market buyer who values a Hamburg-registered GmbH (HRB 170383) and 'HOSTED IN GERMANY' claims
Avoid if
- You need to run data subject requests and breach notifications inside the system — ask the vendor: the public pages we read do not show it
- You need a structured privacy register (RoPA/VVT, DPIA questionnaires, processor and TOM management) — ask the vendor: the public pages we read do not show it
- You must know the invoice before a sales call — ask the vendor: the public pages we read do not show it
- You require a published DPA, subprocessor list and named data centers before entrusting your compliance record
The scores
Records & DPIA depth
Show reasoningHide reasoning
How this is scored
The DSMS core: records of processing (RoPA/VVT), data protection impact assessments, processor/DPA management and TOMs — how deeply the legal artifacts are modeled and connected.
0 — Document templates in a folder tree; the "register" is a Word file with version numbers in the filename.
3 — A structured RoPA with basic fields and a DPIA questionnaire, but processors, TOMs and legal bases live outside the system.
5 — RoPA and DPIA as linked modules with templates; processor management and TOM assignment exist but are shallow, and group reuse is copy-paste.
8 — A connected data model — processing activities linked to systems, processors, TOMs and legal bases — with DPIA triggers derived from the record, reusable group templates, and outputs a supervisory authority accepts.
10 — Privacy records as a system of record: the RoPA drives DPIAs, processor management and TOM coverage from one data model, multi-client/mandate capability included, and the documentation is audit-ready without manual assembly.
The External DPO
The entire privacy record surface is the word 'Datenschutz' in a product list plus a DSGVO claim — not one fact about RoPA/VVT structure, DPIA questionnaires, processor/DPA management or TOM assignment. As a multi-mandate practice I cannot even tell whether thirty clients live in one account or thirty; nothing here resembles the connected data model the anchor at 8 demands. 1 5
The In-House Counsel
A 'Datenschutz' module exists in name and 'DSGVO' appears in the standards list, but the evidence evidences not one RoPA field, DPIA questionnaire, processor register or TOM library — what is documented is a policy generator with 20+ templates and a step-by-step assistant. Templates plus task lists are not a connected data model, and I will not move my VVT onto evidence this thin. 1 3 4 5
The Drafted Generalist
All the evidence confirms is a 'Datenschutz' module name and DSGVO listed as a supported standard — not one word about a RoPA, DPIA questionnaires, processor management or TOMs. I'd be building the register this product is supposedly for, and I can't tell from this evidence whether it's more than a template pack. 1 4 5
The Lead Auditor
The entire DSMS evidence is one word — 'Datenschutz' in the product list — with nothing behind it: no RoPA, no DPIA questionnaire, no processor, DPA or TOM model anywhere in the evidence. A module name is not a data model, and silence on the core register means I score by the low anchors. 1 5
The IT Integrator
The evidence names a 'Datenschutz' module and DSGVO among the regulations, but not one fact about a RoPA, DPIA, processors/DPAs or TOMs — the module is a label with nothing behind it in evidence. I can't credit a structured register, let alone a linked data model, so it barely clears document-template territory. 1 5
The Skeptic
The evidence offers a 'Datenschutz' module name and the slogan 'DSGVO STANDARDS' — and not a single RoPA field, DPIA questionnaire, processor/DPA entry, TOM or legal basis. For a product filed under Data Protection, every captured capability page is ISMS/ISO; the privacy register is a navigation label, so I can't credit even anchor-3 structure. 1 3 4 5
Data subject rights & incidents
Show reasoningHide reasoning
How this is scored
The operational half of the DSMS: data subject request handling with statutory clocks, breach register and authority notification, deletion concepts that actually delete.
0 — Requests arrive by email and live there; breaches are a phone call and a memo.
3 — A request log and a breach list exist, but deadlines are manual, intake is unstructured, and deletion rules are documentation rather than workflow.
5 — DSR workflows with the Art. 12 clock tracked, structured breach register with the 72-hour clock, deletion concepts assignable to records; automation is reminders.
8 — Intake channels for requests (portal/form), identity-check support, deadline automation with escalation, breach severity assessment and authority-report output, deletion rules tied to the RoPA with execution tracking.
10 — Rights and incidents as operations: end-to-end request handling an authority audit walks through, breach workflows that produce the Art. 33 notification, and deletion automation with evidence that the deletion happened.
The External DPO
Zero facts concern data subject requests, statutory clocks, breach registers, Art. 33 output or deletion — the only adjacent items are generic automated email notifications, task organization, and a whistleblower module, which is a different legal duty entirely. Missing evidence is information here: I have to assume my clients' DSRs and incidents would be handled outside this system. 1 2
The In-House Counsel
Complete silence on data subject requests, the Art. 12 clock, a breach register, the Art. 33 notification and deletion tracking — the module lists contain no rights or breach function at all. The nearest facts are automated email notifications and tasks organized by project, which is a to-do list, not a statutory clock that never slips. 1 2
The Drafted Generalist
The evidence is completely silent on data subject requests, statutory clocks, a breach register and deletion workflows — the whistleblower module is a different law entirely, and 'automated email notifications' is not rights handling. For a criterion about operational DSMS work, that silence scores at the bottom. 1 2
The Lead Auditor
Not a single fact mentions data subject requests, a breach register, authority notification or deletion concepts — not even a bad version of them — across the homepage, platform and product pages. Unevidenced is nonexistent under my rule, so this sits at the email-and-memo floor. 1 5
The IT Integrator
Complete silence: no DSR intake, no Art. 12 clock, no breach register, no deletion workflow appears anywhere, and the module list contains no rights or incident capability at all. By the anchors, total absence on the operational half of a DSMS is a 0. 1 5
The Skeptic
Complete silence on data subject requests, Art. 12/33 clocks, breach registers and deletion execution; the only adjacent facts are generic 'automated email notifications' and 'tasks organized by projects and priorities', which is reminder plumbing, not rights operations. Silence this total scores at the floor. 2
Privacy regime coverage
Show reasoningHide reasoning
How this is scored
Which privacy regimes the product actually operationalizes — GDPR, BDSG, Swiss nDSG, UK GDPR, ePrivacy, EU AI Act privacy duties — and whether one record maps across them or each regime is a fresh island.
0 — One regime, hard-coded; anything else is "on the roadmap".
3 — GDPR plus one national law as separate checklists; the same processing activity is documented once per regime.
5 — The major regimes for its market with partial cross-mapping; newer duties (AI Act, ePrivacy changes) present as content packs of varying depth.
8 — Broad current coverage with one-record-many-regimes mapping and visible maintenance as regimes evolve.
10 — Regime coverage as a living product: multiple privacy regimes on one data basis, per-country variants, and documented update cadence when the law moves.
The External DPO
DSGVO and an EU AI Act framework (launched 2025) are evidenced, and cross-mapping between frameworks is claimed — but the cross-mapping story is built around the ISO/NIS2 security stack, not privacy regimes. No BDSG, no Swiss nDSG despite a Bern subsidiary since 2023, no UK GDPR, so privacy coverage is essentially one regime plus an AI content pack. 1 4 5
The In-House Counsel
DSGVO and an EU AI Act framework with real launch dates (NIS2 in Q2 2023, AI Act in 2025) plus cross-mapping between frameworks show a maintained catalogue. But no BDSG, no Swiss nDSG despite a Bern office, no UK GDPR and no ePrivacy are evidenced — privacy coverage is one regime plus AI-Act duties delivered as a content pack. 1 4 5
The Drafted Generalist
Seven regulations including DSGVO and the EU AI Act, claimed cross-mapping between frameworks, and a visible habit of shipping new law as it arrives (NIS2 in Q2 2023, AI Act and ISO 9001 in 2025) — that's real maintenance, not roadmap talk. But no BDSG, no Swiss nDSG despite their own Bern subsidiary, no UK GDPR or ePrivacy, so the privacy-regime breadth thins out past GDPR. 1 4 5
The Lead Auditor
Breadth is real: DORA, NIS2, DSGVO, EU AI Act, HinSchG and more on one platform, cross-mapping between frameworks claimed, and a visible cadence (NIS2 framework Q2 2023, EU AI Act and ISO 9001 launched 2025). But the privacy lens is thin — no BDSG, nDSG, UK GDPR or ePrivacy in evidence, and the mapping claims are ISMS-control-centric, so privacy regimes read as one island plus content packs. 1 4 5
The IT Integrator
Cross-mapping between frameworks and custom frameworks are confirmed, with a visible maintenance cadence — NIS2 launched Q2 2023, EU AI Act and ISO 9001 in 2025. But on privacy regimes specifically only DSGVO appears; BDSG, nDSG, UK GDPR and ePrivacy are entirely absent from the evidence, so coverage is broad-adjacent but not anchor-8 broad. 1 4 5
The Skeptic
Credit where due: 10+ standards, claimed cross-mapping, an early NIS2 framework and a 2025 EU AI Act launch show breadth and visible maintenance. But through the privacy lens only DSGVO is evidenced — no BDSG, no Swiss nDSG despite a Bern subsidiary since 2023, no UK GDPR or ePrivacy — so one-record-many-privacy-regimes is a claim about controls, not a demonstrated privacy capability. 1 4 5
Audit readiness & evidence
Show reasoningHide reasoning
How this is scored
Whether the system produces defensible proof: revision-safe history, evidence collection, reports for auditors, authorities and management.
0 — Exports are screenshots; history is overwritten in place.
3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.
5 — Versioned records, standard report generators for the core registers, evidence attachments per activity; assembling a full audit file still takes days.
8 — Revision-safe change history, audit-scoped evidence packs on demand, management and authority reports current at a click, auditor access roles.
10 — Audit readiness as a standing state: continuous documentation status per regime and scope, exportable proof packs an auditor accepts as-is, and a defensible answer to "show me the state on date X".
The External DPO
The audit story is outcome marketing — '100% success rate at ISO 27001 audits' — with no evidence of revision-safe change history, evidence packs, report generators or auditor access roles. For a compliance automation platform whose homepage sells certifications, the absence of any documented audit-trail capability is itself the finding; I'd spend days assembling a supervisory-authority file. 1 4
The In-House Counsel
What the evidence offers is the vendor's own ISO 27001 certificate and a '100% success rate' at customer audits — a claim, not a mechanism. Revision-safe history, evidence packs, auditor access roles and any answer to 'show me the state on date X' are unevidenced, so the defensible trail would have to be assembled by hand. 3 4
The Drafted Generalist
The only audit evidence is a marketing claim of '100% success rate' at customer ISO audits plus the vendor's own certification — nothing about revision-safe change history, evidence packs, auditor reports or access roles. When the auditor asks 'show me the state on date X', I'd be assembling that file by hand. 3 4
The Lead Auditor
The pitch is audit outcomes — '100% Erfolgsrate bei ISO 27001 Audits unserer Kunden' and '70% schneller' — with a policy generator and 20+ templates that produce documents. But nothing evidences revision-safe history, versioned registers, evidence packs or auditor reports; that is an audit success rate asserted in marketing, not a system that can answer 'show me the state on date X'. 3 4
The IT Integrator
The only audit evidence is outcome marketing — '100% Erfolgsrate bei ISO 27001 Audits' — plus the vendor's own ISO 27001 certification; nothing on revision-safe history, evidence packs, auditor roles or report generators. Claims about passed audits aren't a mechanism for producing defensible proof, so this sits at the PDF-and-promises level. 2 4
Integrations & automation
Show reasoningHide reasoning
How this is scored
Whether the platform feeds from the real IT estate — directory import, ticketing, API — and automates the recurring privacy work instead of re-typing it.
0 — A closed island: manual entry in, PDF out, no API.
3 — CSV/Excel import and export; no live connections, no API worth the name.
5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing or SSO); automation is reminders and recurrence.
8 — Real connector set (ticketing, HR or asset sources), webhooks, SSO/SCIM, workflow automation with delegation and escalation, useful AI assistance with human review.
10 — The platform behaves like infrastructure: API parity for the data model, event streams, bidirectional sync with the estate, and automation that measurably removes the recurring toil (reviews, attestations, evidence pulls) rather than renaming it.
The External DPO
'Über 60 API-Anbindungen' with JIRA named is a genuinely broad connector claim, and automated notifications plus project/priority task organization show some workflow machinery — but no documented REST API for core objects, no directory import, no SSO/SCIM, no webhooks, and no delegation/escalation evidenced. The automation shown is reminders and to-do lists, which is anchor-5 territory nudged up only by the connector count. 1 2
The In-House Counsel
'Über 60 API-Anbindungen', a JIRA integration and automated email notifications is the anchor-5 shape: ticketing plus reminders. No directory import, SSO/SCIM, webhooks or delegation with escalation are evidenced, so recurring privacy work would be renamed rather than automated. 2
The Drafted Generalist
Over 60 API integrations with JIRA named, plus automated notifications and project/priority task organization, is a genuine connector story. But no directory import, no documented REST API, no SSO/SCIM or webhooks are evidenced, and the automation on show is reminders and task lists rather than removing re-typing. 2
The Lead Auditor
'Über 60 API-Anbindungen' and a named JIRA integration clear the CSV-only bar. The automation story, though, is automated email notifications and tasks sorted by project and priority — reminders with better posture — with no documented REST API, directory import, SSO/SCIM or webhooks in evidence. 2
The IT Integrator
'Über 60 API-Anbindungen' with JIRA explicitly named is the right instinct and the in-house AI team suggests real tooling, but no AD/Entra directory import, no documented REST API, no webhooks and no SSO/SCIM are evidenced anywhere. The automation actually shown is automated email notifications and task lists — a ticketing connector plus reminders, not estate sync. 2 5
The Skeptic
'Über 60 API-Anbindungen' plus a named JIRA connector is a real start, but the 60 is a headline with no list, and there's no documented REST API, directory import, SSO/SCIM or webhooks in evidence. The AI story is a team org chart ('Development, Artificial Intelligence, Product Owner'), not a shipped feature with human review. 2 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 — entity, hosting, subprocessors, DPA. A platform that maps your processing is itself your most concentrated processing.
0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your RoPA.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.
5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.
8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.
10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, on-premises or sovereign-cloud options, and the whole chain documented publicly.
The External DPO
The entity and hosting half is actually solid: secjur GmbH registered in Hamburg (HRB 170383), 'HOSTED IN GERMANY' claimed, and ownership is European VC (Visionaries Club, Berlin; Alea Capital, Portugal). But there is no published DPA, no subprocessor list, and no named data centers anywhere in the captured evidence — for the system that would hold the RoPA of thirty clients, an undocumented subprocessor chain is disqualifying of anything above mid-band. 3 4 6 5
The In-House Counsel
The imprint puts a German GmbH with Hamburg registry number and German VAT behind the product and 'HOSTED IN GERMANY' is bannered, but no DPA, no TOMs, no subprocessor list and no named data centers appear on any captured page, and ownership is VC-backed and unconfirmed. For the system that would concentrate my company's entire compliance record, the chain I most need to verify is exactly the one that is missing. 3 4 6 5
The Drafted Generalist
The bones are European: German GmbH with a Hamburg register entry, hosting claimed in Germany, European investors and even an internal DPO email. But no published DPA, no subprocessor list, no named data centers, and the evidence itself flags ownership and residency as unverified — for the system holding my RoPA, I can't confirm the chain is clean. 3 4 6 5
The Lead Auditor
The entity is verifiable — secjur GmbH, Registergericht Hamburg HRB 170383 — and 'HOSTED IN GERMANY' is the vendor's own banner, so this is not the non-EU-hosting floor. But for the platform holding your compliance record, the rest of the chain is a black hole: no DPA, no subprocessor list, no named data centers anywhere in the evidence, which caps it far below the published-chain anchors. 3 4 6
The IT Integrator
German GmbH (HRB 170383, Hamburg, DE VAT ID) with 'HOSTED IN GERMANY' and apparently European ownership (Visionaries Club, Alea) gets past anchor-3 territory. But there is no published DPA, no subprocessor list and no named data centers in evidence — for the system that would hold the RoPA, that's an undocumented chain and it caps well below rubric level 8. 3 4 6 5
The Skeptic
A German GmbH with a real Handelsregister entry and 'HOSTED IN GERMANY' claims put the entity and hosting on the right side. But no DPA, no TOMs and no subprocessor list anywhere in the captured pages — a compliance vendor whose own chain goes undocumented, which caps it below rubric level 5. 3 6
Pricing transparency
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 — An entry price exists, but module add-ons, entity counts or bundled consulting make the real total incomputable.
5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.
8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; 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 public price exists on any captured page — the only numbers in the pricing dimension are a €5.5m seed round and 'bis zu 67% günstiger'. For a consultancy pricing a ten-client rollout, every configuration starts with a sales conversation, which is exactly rubric level 0. 1 3
The In-House Counsel
Not one price on any captured page; the only signal is 'bis zu 67% günstiger' against an unnamed baseline, with six modules and optional expert support all behind a sales conversation. The real invoice is incomputable from public pages. 1 2 3
The Drafted Generalist
No public prices at all — the only numbers in the evidence are relative marketing claims like 'up to 67% cheaper' and '70% faster to ISO 27001', which compute nothing. Before I take this to my managing director, I'd have to book a sales call just to learn the invoice. 3 4
The Lead Auditor
The only numbers touching price are ratios — 'Bis zu 67% günstiger' and 'Bis zu 70% Aufwandsreduktion'. No edition prices, no billing period, no module or entity boundaries, so the invoice is a sales conversation: that is anchor zero exactly. 3 4
The IT Integrator
No prices at all: the only number anywhere near pricing is 'Bis zu 67% günstiger', a discount against an invoice I cannot compute from public pages. Per the anchors this describes the B2B norm rather than condemning it, but it's still a 0 — every configuration is a sales conversation. 3 5
European sovereignty — proven facts
1 of 4 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | EU only ⚠ unverified | 3/3 pts | 1 Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 24 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency. Hosting claim appears only in homepage marketing copy; the privacy policy excerpt covers the marketing website only and no DPA or terms excerpt states where the compliance platform's customer data is hosted.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- 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.
- 14 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
- 9 subprocessors 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
- 4 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
- 4 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
- 1 integrations 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
- 1 pricing 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.secjur.com Checked 5 Oct 2026 Details →
- 2 Platform page www.secjur.com Checked 5 Oct 2026 Details →
- 3 ISMS product page www.secjur.com Checked 5 Oct 2026 Details →
- 4 ISO 27001 product page www.secjur.com Checked 5 Oct 2026 Details →
- 5 About page www.secjur.com Checked 5 Oct 2026 +1 earlier capture: 24 Aug 2026 Details →
- 6 Imprint www.secjur.com Checked 5 Oct 2026 Details →
- 7 Privacy policy www.secjur.com Checked 5 Oct 2026 Details →
- 8 Privacy regime coverage — found from sitemap www.secjur.com Checked 5 Oct 2026 Details →
- 9 Integrations & automation — found from sitemap www.secjur.com Checked 5 Oct 2026 Details →