VoiceLock EARLY ACCESS Reserve a pilot
EU AI Act Article 50 · enforceable 2 Aug 2026

Prove your AI voice agents said what the law requires.

Your voice platform plays the disclosure. It doesn't hand you evidence you can defend. VoiceLock produces independent, cross-platform proof that every call disclosed — in the format a regulator or a court actually asks for.

No product yet — we're building for the first ten teams. Pilots are free.

Illustrative record — example data.

The gap

Your platform's logs say a lot.
They don't say "disclosed, and here's proof."

Platforms record the call for their own analytics. When a regulator or a plaintiff asks you to prove the disclosure fired — on the day, in the right language, on every platform you run — that proof is buried in audio, in a format nobody's own logs were built to produce.

PLATFORM LOGwhat you have
# call transcript · Retell status: completed duration: 84s sentiment: neutral recording: audio.wav (5.1MB) disclosure: — not a field — # and nothing at all for # the calls you ran on Vapi

Useful for QA. In a dispute where the platform is also a defendant, its own logs are the weakest evidence you can hold.

VOICELOCK RECORDwhat you can defend
# disclosure_record · any platform disclosure: made @ 0.9s rule: EU AI Act Art. 50(1) language: matched (EN) spoken: "…an AI assistant…" verified: independent ASR anchored: RFC 3161 timestamp export: regulator CSV / PDF

One record format across every platform you use, verified by a party that isn't the platform — producible in hours, not a two-year discovery fight.

How it works

Point it at the calls you already make.

VoiceLock sits beside your voice platforms, not in the call path. Nothing to break, nothing to re-architect.

STEP 01

Connect

Link Retell, Vapi, Bland or Twilio with a webhook. Calls flow in as they happen — no change to how your agents run.

STEP 02

Verify

An independent check confirms the required disclosure actually appeared in the opening seconds, in the caller's language, mapped to the rule for that call's jurisdiction.

STEP 03

Prove

Every call becomes a timestamped, integrity-checked record. When the request lands, export a regulator-ready file across all your platforms in one click.

Who it's for

Teams who carry the liability, not just the calls.

Under Article 50 and the TCPA, responsibility sits with the deployer — the company running the agent — no matter whose platform placed the call.

Voice-AI agencies

You run campaigns for clients across more than one platform, and you're on the hook for their exposure. One evidence layer covering every client, every platform.

UK & EU deployers

If your agent speaks to an EU resident, Article 50 can put you in scope as the deployer — and disclosure-at-first-interaction becomes something you prove, not just a script setting.

Regulated & outbound teams

Healthcare, insurance, financial services, collections and high-volume BDR — where an unproven disclosure is a per-call penalty waiting on a docket.

EU AI Act — Article 50 transparency duty · enforceable 02 Aug 2026 US TCPA — AI voice classed as "artificial voice" (FCC, 2024) UK GDPR / PECR — automated calling & consent US state all-party consent — CA · FL · IL
Reserve a pilot

We're building for the first ten teams.

Pilots are free while we build. Tell us what you run and where your callers are, and we'll bring you in early — and shape it around how you actually work.

No spam, no sales sequence. One email when there's something real to show you.