synthmind

Every message, judged as things stood when it went out.

Answer the complaint with a message-by-message record. Each send is checked against your agreed policy at the instant it went out, with the supporting rows shown and every gap in the history named.

Discuss my deadline 4,000 € per audit · one history up to 100,000 input rows · one corrected re-run

Illustrative example · one campaign, three messages

Blocked at sendm-4472 · sent 2026-02-15 10:03 UTC

Rule 3, from your sentence: a message may be sent to a contact whose consent is confirmed and not revoked at the time of sending.

consent confirmed 2025-11-02 09:14 consents.csv line 118

revoked 2026-01-20 16:40 consents.csv line 2207

no re-confirmation before 2026-02-15 10:03 consents.csv read to its end, feed finished 2026-03-01

Certificate: the verdict follows from these rows and rule 3. Checked by a part of the system that did not compute it. Passed.

Mailable at send, barred todaym-4480 · sent 2026-02-20 08:30 UTC

revoked 2026-01-20 16:40, re-confirmed 2026-02-01 11:02 consents.csv lines 2207, 2391

suppressed since 2026-03-04 suppressions.csv line 77

Listed apart from the breaches, with both dates. A query against today's suppression list would have called this one a breach.

Not yetm-4490 · sent 2026-03-01 09:00 UTC

suppression feed ends 2026-02-28 suppressions.csv, last row

The verdict waits on the March suppression export. It is not guessed.

What you get back

Blocked at sendThe list Legal asked for. Each message with the rule and the rows it rests on.

Lawful then, barred nowListed apart, with the dates. These are the ones a query against today's list gets wrong.

Not yetWhat the history cannot say, and which feed closes it.

The rules we wrote, each beside the sentence of your policy it came from. You approve the reading before anything runs.
A certificate for every verdict, checked by a part of the system that did not compute it. A verdict that cannot be shown from the rows is refused and named, never printed.

How it runs

File in, listing out. We run it. A one-page intake tells us which column is which and which clock the timestamps use. You get the listing the same working day after we accept complete files and you approve our reading of the policy; files accepted before 12:00 CET count for that day. If a feed was wrong, you send a corrected one and we run it again.

What you give us

Contacts as pseudonymous ids. We never see names or addresses.
Consents and revocations, with their timestamps.
Suppressions, with the period each one is valid.
Messages, with the instant each one was sent.
Your policy, in three to six plain sentences.

Price

4,000 € per audit

One history of up to 100,000 input rows across all files. One re-run after a corrected feed. Invoiced before the run. If your files or your policy cannot support the audit, we say so before the invoice and nothing is owed.

Not included: legal advice, a dashboard, an integration with your email platform, or the software itself.

What the certificate establishes

That each verdict follows from the agreed rules and the supplied records. It does not establish that the records are complete, or that your policy meets the law. Those stay with you and your counsel, and the listing is built so they can check them: every verdict names its rows, and every gap says what is missing.

Start

Write to Harri Sarsa with the date on the letter. You get the intake page the same day.

hello@muoto.xyz