Skip to main content
Audact
See the offer

Detection alone is not evidence.

Partner orchestration · Planned

An orchestration layer over best-of-breed detection partners, bound to the Audact evidence chain. One audit trail. One escalation path.

  • Banking, insurance and telecom
  • Evidence binding hosted in Frankfurt

The threat

Three things that make a detection score insufficient on its own.

  • Voice-clone fraud is rising

    Synthetic-voice executive fraud and helpdesk impersonation are a growing operational-risk concern across European financial institutions.

  • Provenance manifests are removable

    C2PA manifests can be stripped on transcoding. A watermark-only defence fails the moment a clip is re-encoded by a phone network or a social platform.

  • A score is not a record

    A pass or fail that cannot be put in front of a supervisor is a liability, not a defence. What survives the meeting is the record, not the number.

The approach

We do not retrain biometric models. We bind the signals.

The plan is orchestration: take the vendor signals that already exist, bind them to the interaction they belong to, and hash them into your tenant's evidence root so the outcome is an auditable record rather than a number in a log.

  • Synthetic-voice detection

    Partner discussions · not contracted

    Best-of-breed classifiers for cloned and generated speech.

  • C2PA provenance

    Partner discussions · not contracted

    Cryptographic provenance manifests attached to generated audio.

  • Speaker biometrics

    Partner discussions · not contracted

    Speaker verification, where the deployment and the legal basis allow it.

  • Voice watermarking

    Partner discussions · not contracted

    An embedded synthesis-marker signal in the generated audio.

Nothing here is contracted, and we name a partner when there is a contract rather than a logo — the block is planned. Audact's own part is the orchestration layer and the metadata binding: each partner signal hash-chained into your tenant's evidence root.

Deployment profiles

Three profiles, each scoped to a regulatory posture.

  • Banking

    Planned

    Adjacent to strong customer authentication, with DORA-aligned operational resilience. Volume-based, with an enterprise SLA.

  • Insurance

    Planned

    Vishing defence on the claims line, with record-keeping that fits the IDD obligations. Volume-based, with an enterprise SLA.

  • Telecom

    Planned

    Carrier-grade integration, with joint detection of caller-line spoofing and voice cloning. Enterprise licence.

There is no separate price for this; it is not on sale. Talk to us.

Adjacent

The same buyers, the same committee.

Voice authentication shares its procurement route, its risk committee and its evidence requirements with transactional fraud-prevention tooling. That is why it sits next to the evidence chain rather than in a separate product.

  • Transaction fraud.
  • Identity verification.
  • Risk scoring.

Next step

Partnership enquiries.

Deployments are scoped per organisation. Banking, insurance and telecom buyers receive a tailored integration plan after an initial scoping call.

  • Evidence binding hosted in Frankfurt; a backup region in Ireland is being set up.
  • Vendor-neutral: bring your existing detection contract, planned.
  • Quarterly board-ready voice-risk report, planned.

Related

  • Proof

    What a receipt records, and what a third party can recompute.

  • Article 50

    Marking of synthetic audio, with the article numbers.