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
- GDPR-aligned · encrypted
- EU residency (Frankfurt + Amsterdam)
A read-only surface, built for regulators.
Not a screen-share. Not a zipped folder of PDFs. A scoped, signed export pack your auditor opens, reads, and verifies - without ever touching your console. A dedicated audit room is on our roadmap.
- 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 · JSON-LDJSON184 KB
- Chain of custody · CSVXBRL612 KB
- Signature chain · JSON-LDJSON14 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-LD and CSV exports - every artifact signed, every signature independently verifiable.
Multiple 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.
ProgrammaticTabular export for spreadsheets and downstream tools. Same source data, no second extraction.
Spreadsheet-readyBuilt for the room you walk into with a regulator.
Encryption in transit
TLS on every public endpoint. Encryption applied end to end between our services.
Encryption at rest
AES-256 across databases, storage, and backups, with documented key rotation.
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.
GDPR-aligned
Article 28 DPA, EU Standard Contractual Clauses, and 30-day deletion windows. DPA available on request.
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.
Will my notified body accept these export packs?+
Export packs are read-only, cryptographically signed, and shipped in formats notified bodies and member-state authorities work with (PDF, JSON-LD, CSV). The recipient verifies the signature independently. We are happy to walk your notified body through the format during onboarding.
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 or air-gapped delivery?+
On-prem and air-gapped delivery are on our roadmap for Enterprise scopes where the regulator or the customer ISMS requires it. Today the platform is fully managed in the EU regions above, and export packs can be downloaded and stored on your own systems.
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.