EU COMPLIANCE PLATFORM · REGULATION (EU) 2022/2554 · GDPR ART. 30api.compliance-audit.eu
PUBLIC / COMPLIANCE-AS-A-SERVICE

Sovereign Compliance. Zero-PII at Rest. Cryptographic Proof.

The architecture-not-policy compliance engine for GDPR, the EU AI Act, and DORA. Verify your audit trails, automate DSARs, and stream enterprise telemetry — without ever storing raw personal data.

JurisdictionEU · Frankfurt (europe-west1)
Engine statusOPERATIONAL
LedgerFirestore · append-only
PII field classes
5+
SSN · email · phone · card · key
Badge integrity
HMAC-SHA256
Signed per assessment
Retention rules
6 tiers
730d – 3650d statutory
Data residency
EU only
No replication outside Europe

Take a look — run the engine

Live calls against the production engine. Nothing is persisted.

LIVE
Request payloadapplication/json
Redacted responseAwaiting run
Run the check to see the redacted payload.
Rate-limited · 20 req/min · nothing stored

Service surface

Every capability below is live on the production engine.

CapabilityStatus
PII redaction
Operational
GDPR erasure
Operational
Compliance assessment
Operational
Signed trust badge
Operational
Audit report
API access
Pricing

One capability matrix. No sales call required.

Every gate is enforced in the API itself — the same matrix below is what the engine checks. No hidden tiers, no unlisted features, no surprises.

Feature / Capability
Free
€0
Indie hackers & evaluators
Pro
€79/mo
Early-stage B2B SaaS
Growth
€299/mo
Scaling B2B startups
Enterprise
€1,499+/mo
Regulated enterprises
Core PII sanitization & assessmentRate-limitedIncludedIncludedIncluded
Audit log retention window30 days1 year1 year7 years
Autonomous DSAR portal & mailbox token—
RoPA, consent cascades & trust badges—
AI model registry (EU AI Act)——
GitHub vendor risk discovery——
Incident ledgers & PDF export packages——
Real-time SIEM webhooks (HMAC-signed)———
Dedicated EU routing & erasure certificates———

Enforced server-side via feature flags on every tenant-scoped route — a blocked call returns 403 feature_not_in_tier, not a sales pitch.

No hidden extras

The questions enterprise software hopes you won't ask.

What happens if we hit our rate limits?

We throttle gracefully — you get a clear 429 with a retry window. We never surprise you with runaway overage bills or hold your data hostage.

Are there hidden setup fees for Pro or Growth?

Zero. Everything is self-serve. You only talk to us if you need custom enterprise routing or a dedicated SLA contract.

Where is my data processed?

100% in Frankfurt (europe-west1), with zero replication outside Europe. Raw PII is inspected ephemerally in-memory and never touches a disk.

Architecture, not policy

We can't leak what we never store.

Evaluated in memory only

Payloads are inspected during the request and discarded. Nothing is written to a database, a file, or a log — ever.

What we keep

Timestamps, payload sizes, pass/fail verdicts, call counts. Metadata — never content.

Near-zero processor footprint

Processing is transient and in-memory only — no personal data exists at rest on our side, so there is nothing to subpoena, breach, or govern.

Verifiable, not promised

Every assessment produces an HMAC-signed badge. Cryptographic proof beats a PDF policy.

Secrets doctrine

Your credentials get the same treatment as your audit trail.

Custom SMTP relays, webhook signing secrets, any integration credential — held to the identical sovereign, encrypted-at-rest, zero-echo standard as the compliance data itself.

Encrypted before it lands

Credentials are AES-256-GCM envelope-encrypted in the application layer — the regional database stores ciphertext only. The key-encryption key lives in Secret Manager; the runtime service account is read-only.

Write-only by design

Stored secrets are never returned by any API response and never rendered in any UI — there is no "show password" path to exploit. Rotation is a re-write, not a read.

Sovereign + provable

Configs live inside your tenant's regional Firestore partition — and every change is hash-chained into the same tamper-evident audit vault that proves your compliance history.

Open source · CI bridge

Gate every pull request — your code never leaves GitHub.

A zero-dependency, open-source GitHub Action that scans a deployed preview URL against the sovereign engine. Composite, auditable end-to-end, and free to fork.

Zero code exfiltration

The action audits a deployed preview or staging URL — source code never leaves your CI runner. Only abstract findings cross the wire.

Transparent & auditable

One zero-dependency Node 20 script using built-in fetch. No vendored packages, no compiled dist bundle — every line reviewable.

Inform aggressively, block conservatively

Builds fail strictly on unequivocal WCAG 2.2 Level A defects. Warnings and manual-review items land as a Markdown PR comment — never a surprise red build.

Three steps to a gated pull request

  1. 1
    Mint a scoped key

    Portal → API Keys → assess + read permissions. A demo-tier key works for evaluation.

  2. 2
    Add two repo secrets

    COMPLIANCE_API_KEY and COMPLIANCE_TENANT_ID under repository Settings → Secrets.

  3. 3
    Drop in the action

    Point target-url at your preview deployment. Advisories comment on the PR; Level A defects block the merge.

workflow · .github/workflows/compliance.yml
- uses: Terrygilligan/compliance-audit-verify-action@v1
  with:
    api-key: ${{ secrets.COMPLIANCE_API_KEY }}
    tenant-id: ${{ secrets.COMPLIANCE_TENANT_ID }}
    target-url: 'https://your-preview-deploy.example.com'
    fail-on: 'level-a'
Self-serve access · demo tierPOST /v1/demo/keys

Issue a demo API key

A cmp_demo_* key with read and assess permissions, valid 30 days. Run real assessments, open your dashboard, embed a signed badge.