MaximusDev

Compliance tier

Every AI call, signed.

When your app touches real customer data, you can prove exactly what happened. Every prompt, every model response, every fingerprint — cryptographically receipt-stamped, in real time, by TraceSeal. No one else in this category can show you the maths.

Upgrade to Compliance — £39/mo See pricing detail

A real receipt

What you get back, every call.

The TraceSeal receipt. One per AI call your app makes. Stored forever. Verifiable by anyone with the public key. Shown here is a real receipt from yesterday afternoon, with the customer-identifying fields redacted.

receipt-9a3f2d7c.json1{
2  "version": "traceseal/v1",
3  "id": "rcpt_9a3f2d7c8e4b1f6a",
4  "app": "customer-feedback.maximusdev.app",
5  "issued_at": "2026-05-06T14:22:08.412Z",
6  "call": {
7    "provider": "anthropic",
8    "model": "claude-sonnet-4-5",
9    "input_tokens": 412,
10    "output_tokens": 189
11  },
12  "prompt_hash": "sha256:f7c2…b4e1",
13  "response_hash": "sha256:1a08…c93d",
14  "customer_subject": "sub_redacted_e8a2",
15  "signature": "ed25519:9a3f…7b21",
16  "verifier": "verify.traceseal.io/9a3f2d7c"
17}

What's signedThe hashes of the prompt and response — not the content itself, so customer data stays private. The signature is enough to prove "this exact pair existed at this exact moment".

What it provesThat on 6th May at 14:22, your app called claude-sonnet-4-5 for one specific (anonymised) customer. Nothing more, nothing less.

Who can checkAnyone, with the public verifier link. Your customer. A regulator. The auditor your buyer's IT team sends.

How it works.

01 — Build

Build like normal.

Describe your app, watch it build, ship it. No extra config. Compliance is a billing toggle, not a code change.

02 — Receipt

Each call gets stamped.

Every time your live app calls the AI, MaximusDev signs a receipt and tucks it into the TraceSeal ledger. Adds about 4ms.

03 — Show

Hand over the link.

When someone asks what your app did with their data, send them verify.traceseal.io/…. They can check it without logging in.

What this means for you, in plain English.

Written for founders, not lawyers

You can answer the awkward email.

"Where did my data go?" gets a real answer with a verifiable link, not a vague paragraph from your privacy policy.

Your buyer's procurement team relaxes.

"How do you handle AI usage logs?" is the question that kills deals. Now you have a one-line answer with a demo URL.

You can switch models without losing history.

The receipts are model-agnostic. If you move from Claude to GPT to local Llama next month, the audit trail stays continuous.

You get a monthly summary you can forward.

First Monday of every month, a one-page PDF lands in your inbox: total calls, models used, anomalies. Forward it to your DPO and move on.

You're not locked in.

The receipts are an open format. If you leave MaximusDev, you can take them with you and keep verifying.

It costs less than the meeting it prevents.

£39 a month. The procurement call where this comes up is usually a £100k deal.

Article 50 · EU AI Act

If you sell to the EU, this is the column you'll be ticking.

From August 2026, providers of certain AI-touching apps must keep records sufficient to demonstrate compliance with Article 50 disclosure rules. TraceSeal receipts cover the technical evidence side. The +£20/mo EU AI Act add-on packages it as a quarterly report.

Read the legal version →

Quarterly report includes

Article 50(1) disclosure log per app
Risk classification per deployment
Model provenance ledger
Incident register (if any)
Sign-off page for your DPO

Compliance starts at £39 a month.

Cancellable any month. EU AI Act add-on is +£20. Both billed in £.

See pricing Talk to us

MaximusDev

Compliance tier

Every AI call, signed.

When your app touches real customer data, you can prove exactly what happened. Cryptographically.

Upgrade — £39/mo →

A real receipt.

One per AI call. Stored. Verifiable.

"id": "rcpt_9a3f…6a",
"app": "feedback.app",
"model": "claude-sonnet-4-5",
"prompt_hash": "sha256:f7c2…",
"signature": "ed25519:9a3f…"

How it works.

01 — BUILD

Build like normal.

Compliance is a billing toggle.

02 — RECEIPT

Each call gets stamped.

Adds about 4ms.

03 — SHOW

Hand over the link.

Anyone can verify it.

What it means.

You can answer "where did my data go?" with a real link. Your buyer's procurement team relaxes. You're not locked in.

Upgrade to Compliance