EU-Sovereign Voice-Agent Infrastructure
Their compliance is a promise.
Ours is a signature.
Recitna runs AI phone agents whose compliance you do not have to take on faith. Every call issues a signed credential stating where each layer processed the call, which sub-processors touched it, and what was retained. You verify it yourself, against our published key, in about a minute.
Live Croatian production pilot · real call proof belowreal call 2026-07-20 · verifies against the published key
The Proof
A real production call. Every layer in the EU. Don't believe us: check.
On 20 July 2026 a caller spoke Croatian to a deployed Recitna agent over live media and booked a real appointment. Speech recognition and the language model ran inside hardware-attested trusted execution environments in the EU. The voice was synthesized by our own trained model on our own EU worker. No external speech or language provider outside an attested EU TEE touched call content. The call issued the credential below.
curl -O https://recitna.com/auditor-pack/credential_zero_us_subprocessors.json
curl -O https://recitna.com/verify_recitna.py
pip install cryptography
python verify_recitna.py credential_zero_us_subprocessors.json
VALID: signature verifies against the published key (recitna-key-1)
residency: {"llm": "attested-tee-eu", "media": "eu-livekit", "storage": "eu",
"stt": "attested-tee-eu", "tts": "eu-self-hosted"}
sub-processors (2):
- edgeless-privatemode role=llm region=eu posture=attested-tee
- livekit role=media region=eu posture=scc
non-EU sub-processors: NONE
The verifier is ~100 lines you can read. It fetches our published key registry (a public repository on a separate host, independent of this page), resolves the credential's key id, and checks the Ed25519 signature over the canonical credential bytes. Change any byte of the credential and it fails. The in-browser check runs the same cryptography via WebCrypto, entirely on your machine; this page has no backend and never sees what you verify. The signing key never leaves our deployment secret store.
Per-Layer Honesty
The credential states what is proven, and names what is not.
Most vendors hand you a DPA and an "EU region" checkbox. We enumerate every hop with its true posture. Where a layer is attested, the credential binds the call to a debug-off TEE measurement. Where a vendor is a US company operating in an EU region under Standard Contractual Clauses, the credential says exactly that instead of hiding it. Auditors trust documents that show their own limits.
| Layer | Posture on the proven call | Detail |
|---|---|---|
| Speech-to-text | attested TEE, EU | Whisper inside an AMD SEV-SNP confidential-computing environment (Germany). Fail-closed: if attestation does not verify, audio never leaves. |
| Language model | attested TEE, EU | Open-weights model in the same attested environment. The credential records the TEE measurement, debug-off, and the manifest digest. |
| Text-to-speech | self-hosted, EU | Our own trained voice model, synthesized on our EU worker. No external TTS provider sees call content. |
| Media transport | EU region, US vendor, SCC | EU-region media plane operated by a US company under SCC. Named plainly as a sub-processor; swappable to EU-owned infrastructure as a hardening step. |
| Storage | EU-resident | 90-day purge and GDPR right-to-erasure, built in and tested (erasure reaches every phone-number format variant). |
Attestation scope, stated honestly: the credential proves our attested open-source proxy recorded this TEE measurement with debug disabled. It is not an independent re-verification of the hardware report; that is the self-hosted roadmap step. The caller also hears an audible "you are speaking with an AI" disclosure at call start (EU AI Act, Article 50).
The Engagement
The Sovereign Voice Pilot
This is not self-serve SaaS, by design. It is a white-glove, fixed-scope engagement: you bring one call flow that matters (reception, booking, intake, triage), we deliver it running on sovereign infrastructure, on a real number, with the auditor pack your DPO can independently verify. You walk out of the pilot with a working agent and a compliance file, not a vendor promise.
Included
- One call flow, one language, scoped together in a working session. Croatian is proven end to end today; other EU languages are scoped honestly in the pilot.
- Sovereign deployment: attested TEE speech recognition and language model, EU media, EU storage, AI-Act disclosure spoken on every call.
- Per-call signed credentials plus the rendered compliance report: the pack you hand to your DPO, auditor, or procurement.
- Deterministic action rails for the moves that must never go wrong (bookings fire only on confirmed offered slots; danger cues force-escalate to a human).
- Runs in parallel with whatever answers your phones today. Nothing is ripped out.
Not included, on purpose
- A dashboard-first SaaS. The pilot is operated for you; the product hardens around paying use, not ahead of it.
- On-premise deployment in your data center. That exists as an enterprise engagement on your GPUs, scoped after a pilot, priced separately.
- Every language and every integration on day one. One flow, done properly, verified. Then we extend.
Run the verification above first. If the artifact means something to your DPO, we should talk. If not, no call needed.
The guarantee is cryptographic
If any credential we issue for your calls fails to verify against our published key, the pilot is free. And you can leave at any time and take your data with you under right-to-erasure. You are not trusting our word at any point in this engagement; that is the entire idea.
Who This Is For
Built for the buyer whose project is stuck.
Your DPIA blocked the voice-AI vendor
Legal flagged US sub-processors in the audio path and the project stalled. A per-call credential with attested EU processing is the unblock document.
You sell into regulated buyers
Healthcare, insurance, finance, legal, public sector. Your customers ask where the audio goes. "Verify it yourself" beats "trust our DPA" in every procurement review.
AI Act obligations landed on your desk
Article 50 disclosure is spoken on every call, in the caller's language, by default. GDPR Art. 28 and 32 posture is enumerated per call, not asserted annually.
You need proof, not positioning
Anyone can put "EU" on a landing page. One vendor hands you a cryptographic receipt per call and shows you the tamper test failing, live, in your own browser. That is the difference this page exists to demonstrate.