00:00Trust

People decide. Audio stays home. Everything is logged.

Emergency calls are the worst moments of people's lives. Here is how Rescuora is designed to deserve a place on the call.

Trust model · summary
Decisions
Always people
Audio
Stays in your building
Suggestions
Logged with outcome
Certification
None claimed; audits planned

00:04Principles

Four rules the product cannot break

A person decides

Rescuora suggests. Call-takers ask, confirm and dispatch.

Original first

The caller's own words are always shown above any translation.

Never colour alone

Every alert carries a word and a shape.

No silent changes

Model updates are signed, logged and installed when you choose.

00:09Method

How a center adopts Rescuora safely

  1. Weeks 1–2

    Synthetic tests

    Models are checked against Simora test calls in your languages.

  2. Weeks 3–8

    Shadow mode

    Rescuora runs on live calls for supervisors only. Call-takers see nothing.

  3. Review

    Supervisor review

    Supervisors score captions, tags and suggestions against what happened.

  4. Decision

    Your go or no-go

    Your center decides whether call-takers see Rescuora, and for which features.

00:15Standards context

The rules your center works under, and what Rescuora does about them

FrameworkWhat it coversHow Rescuora supports itStatus
NENA i3 (NG911)Next-generation 911 call deliveryTakes audio through a media fork; designed to sit beside i3 systemsIn design
FBI CJIS Security PolicyCriminal-justice information in the USOn-prem storage, encryption, access logs, personnel controlsPlanned review
HIPAAHealth information in US EMSEncryption, access control, audit log; agreements with covered entitiesPlanned
GDPRPersonal data in the EUData stays with the center as controller; retention set by the centerPlanned
ISO/IEC 27001Information security managementRescuora's own security programPlanned audit
SOC 2 Type IISecurity controls of a service providerRescuora's own controlsPlanned audit

Rescuora is pre-launch and holds no certifications or audit reports. It does not certify centers, publish dispatch protocols or replace your compliance team. Audits marked planned have not started.

00:22Audit trail

Every suggestion, and what a person did with it

audit.log · excerpt
00:19.4  suggest   call=4127 compressions_start shown
00:21.0  asked     call=4127 by=ct-07
00:09.8  cad_draft call=4127 field=location
00:12.2  confirm   call=4127 field=location by=ct-07 edited=true

ExampleIllustrative log lines.

What the log answers
  • What did the call-taker see, and when?
  • Which suggestions were asked, skipped or reworded?
  • Which CAD fields were edited before confirmation?
  • Which model version was running?

00:30Security

Controls in the first release

ControlDesign
Data locationAudio, transcripts and logs on the appliance in your building
EncryptionAt rest with keys held by the center; TLS between all components
AccessSingle sign-on with roles for call-takers, supervisors and IT
Vendor accessNone by default; time-limited, approved and logged when needed
UpdatesSigned packages, shadow-tested, installed in your window
RetentionSet by the center; deletion logged

00:41Questions

Trust questions

A person on our product or engineering team answers every message.

Q01Who owns the call data?

Your center. Rescuora processes it on your hardware under your retention rules.

Q02Do you train on our calls?

Only if your center opts in, and only from reviewed corrections under your agreement. Raw audio is not sent to us.

Q03What happens if the appliance fails?

Calls continue as they do today. Rescuora sits beside the call path, never in it.

Dispatch

Bring your security team to the walkthrough

We will go through the appliance, the network design and the audit log with your IT and compliance leads.