Audit-ready, by default. Not by sprint.
Cryptographically signed export packs for notified bodies and member-state authorities. Generated in seconds, scoped by access token, expired on a schedule you set.
- Cryptographic signatures
- SOC 2 + ISO 27001 attested
- EU residency (Frankfurt + Amsterdam)
A read-only surface, built for regulators.
Not a screen-share. Not a zipped folder of PDFs. A scoped, signed, time-bounded environment your auditor opens, reads, and verifies — without ever touching your console.
- Signed by
- console.dppautomate.eu · key 8F4B…E217
- Access expires
- in 47 days · 12 May 2027 23:59 UTC
- Recipient
- auditor@tuvsud.com
- Battery declaration · PDFPDF2.4 MB
- Substance composition · JSONJSON184 KB
- Chain of custody · XBRLXBRL612 KB
- Signature chain · JSONJSON14 KB
Four properties an auditor can verify themselves.
Signed by default.
Every export is cryptographically signed with a key the authority can verify against our public chain. Tamper-evident from generation to retrieval.
Scoped access.
Auditors receive only the SKUs, regulations and data fields they are approved to inspect. Nothing more leaks across the boundary.
Time-bounded.
Access links auto-expire on a date you set — typically 14 to 90 days. After that, the URL returns a signed, public revocation receipt.
One-click revocation.
Pull access for any auditor instantly. No recomputation of the pack, no second signature ceremony, no support ticket required.
Three steps from request to verification.
- 01Step
Generate.
Select the SKUs and the regulation scope. The pack is built, signed and indexed in under thirty seconds.
- 02Step
Share.
Send a single time-bounded link to the auditor or notified body. No accounts, no per-user provisioning.
- 03Step
Authority verifies.
A read-only portal serves PDF, JSON and XBRL exports — every artifact signed, every signature independently verifiable.
Three formats. One signature ceremony.
Print-ready compliance dossier with a verifiable signature page. The format most notified bodies still file by hand.
Notified-body friendlyStructured, schema-versioned export for downstream pipelines. Programmatic verification, no PDF parsing required.
ProgrammaticRegulator-grade taxonomy used by member-state authorities for cross-border reporting. Same source data, no second extraction.
Regulator standardBuilt for the room you walk into with a regulator.
SOC 2
Type II attestation, refreshed annually. Report available under NDA.
ISO 27001
Certified information security management. Statement of Applicability on request.
EU residency
Primary in Frankfurt, replica in Amsterdam. No transit outside the EU for customer data.
Cryptographic signatures
Every export and every passport revision is signed. Public chain for independent verification.
mTLS + OAuth 2
Auditor-side authentication uses mutual TLS or OAuth 2 with short-lived tokens. No shared passwords.
Customer-managed keys
Enterprise tier: bring your own KMS. We never see the unwrapped key material.
Trigger audit rooms from the systems you already run.
Spin up a signed, scoped, time-bounded audit pack from a workflow tool, a CI job or a procurement ticket. The pack is built and the recipient notified before the request returns.
curl -X POST https://api.dppautomate.eu/v1/audit-packs \
-H "Authorization: Bearer $DPP_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"sku_filter": ["VOLTA-9821-*"],
"regulation": "EU 2023/1542",
"formats": ["pdf", "json", "xbrl"],
"expires_at": "2027-03-01T00:00:00Z",
"recipient_email": "auditor@tuvsud.com"
}'The questions
compliance leads actually ask.
Six recurring questions from notified bodies, member-state authorities and the procurement teams that have to brief them. If yours is not here, the contact form goes to a person.
Book a compliance briefing →How do regulators verify the cryptographic signature?+
Each pack ships with a detached signature and a public key fingerprint. The auditor (or their tooling) fetches the corresponding public key from our published chain at trust.dppautomate.eu, recomputes the digest and checks it against the signature. The verification is offline-capable — no call back to our infrastructure is required.
Can I revoke an auditor’s access mid-engagement?+
Yes, instantly. Revocation is a single API call (or one click in the console). The pack itself is not recomputed and the signature stays valid — what changes is that the access endpoint returns a signed revocation receipt the moment the auditor tries to load it. The receipt itself is auditable.
Which notified bodies have you worked with?+
We have delivered audit packs into engagements with TÜV SÜD, TÜV Rheinland, DEKRA and Bureau Veritas, primarily for battery and electronics scopes. The specific reference list is available under NDA — most of these engagements predate the customer being publicly named.
How long are audit-room exports stored?+
Default retention is the longer of: ninety days past the expiration date you set, or the statutory retention period of the regulation in scope. For ESPR Battery this is currently ten years from the end of the calendar year of placing on the market. Customer-defined retention overrides are available on the Enterprise tier.
Do you support on-prem audit room (air-gapped)?+
Yes, for Enterprise customers in scopes where the regulator or the customer’s ISMS requires air-gapped delivery. We ship a hardened, single-node appliance that produces the same signed packs against the same public key chain. Comes with a written verification procedure the regulator can follow.
What happens to expired packs — are the cryptographic proofs retained?+
Yes. Expiration revokes access to the underlying data, but the signature, the public key, the digest and the revocation receipt are retained for the full statutory period. A regulator can verify a year later that a specific pack existed, was signed by a specific key, and was revoked at a specific moment — without needing to load the pack itself.