Privacy Policy

Effective date: August 21, 2026

HIPAA readiness: EMS Narrative Builder includes technical safeguards intended to support HIPAA-regulated workflows, but the application does not self-certify HIPAA compliance. Compliance depends on the final deployment, applicable Business Associate Agreements, agency policies, security risk analysis, workforce practices, and proper use.

Information processed

The application may process EMS call information, demographics other than patient name, medical history, allergies, medications, assessment findings, vital signs, treatments, transport information, narratives, uploaded clinical documents, ECG attachments, and account information. EMS Narrative Builder does not collect a patient name in its current patient workflow.

Minimum necessary PHI

Users should enter only information necessary for the EMS documentation and clinical workflow. Patient names are intentionally excluded from the application workflow as a data-minimization control.

Local and cloud storage

Call information may be stored locally in the browser. Protected cloud features use authenticated per-user storage paths and block cloud synchronization when unauthenticated Storage access is not verified as denied. Cloud PHI use also requires a local agency/privacy/BAA authorization acknowledgment.

Automated document processing

Document extraction may use automated or AI-assisted processing. The application blocks that pathway until the deployment records an explicit acknowledgment that PHI processing has been approved, including applicable vendor and BAA requirements. Automated output must be reviewed before it is added to a call.

Diagnostics

Technical diagnostics are designed to minimize PHI and redact common patient-identifying context fields. Users should not place patient identifiers in bug reports or diagnostic descriptions.

Third-party services

The deployment may use Firebase/Google Cloud services and other configured processing providers. Organizations are responsible for determining whether required agreements and configurations are in place before regulated information is processed.

Security and responsibility

No electronic system can guarantee absolute security. Users and organizations remain responsible for account security, device security, access management, retention policies, breach procedures, and compliance with applicable laws and agency policies.

Contact

Support and privacy questions may be submitted through the in-app support/bug reporting features. A branded support address may be published as support@emsnarrativebuilder.com.