Privacy, security & trust
Who can see what, and how that is enforced.
- Role-based access and permissions, set per agency and per feature
- Verification of responder background and qualifications before participation
- Multi-factor authentication for privileged consoles
- Timestamped audit logging of access and actions on sensitive records
- Controlled incident sharing — what is published is chosen, not default
- Medical and restricted information held behind additional access rules
- Encryption and data-protection safeguards in the deployed system
- Per-agency configuration, with safeguards and oversight for that agency
- Incident and access controls with reviewable records
Access is decided by role, permission and jurisdiction rather than by whoever is holding a phone. Every account's capabilities come from its verified role and its agency's configuration.
The safeguards listed are the ones in use in this deployment, and a capability that depends on an agency's own configuration is described as such. Security, audit and compliance questions are answered directly by the people who run it.
- Incident records — the report, the notes, the media and the stages they belong to, with the times they happened.
- Resource records — what equipment is where, its access detail, and its inspection and expiry dates.
- The emergency information a person enters on their own profile, and only that.
- Messages, notifications, and the audit records that show who accessed what.
- Access follows role, verification and qualification — a resident, a community responder and a dispatcher do not see the same screen.
- Medical detail, mental-health crises and restricted law-enforcement incidents are held to authorized personnel.
- A responder alert carries what the responder needs in order to act, and nothing beyond it.
- A shared link or public page carries only what was deliberately published or shared, and never the caller's identity.
- Authenticated access, record rules and HTTPS help protect information; they are not a claim of end-to-end or application-level field encryption.
- Sign-in is authenticated, and privileged screens — dispatch, administration, the database console — need their own separately issued credentials, held as hashes.
- Open privileged sessions are re-validated periodically rather than trusted indefinitely.
- Access rules are applied per record and per role, and administrative actions are written to an audit trail kept separately from the incident record.
- Two-factor sign-in on the privileged surfaces, and a third factor for the decisions that matter — a device check answered on a second screen before a dispatch, admin or database session is trusted.
- Lockdown triggers: a lost device, a suspected compromise or an administrator's decision ends open privileged sessions on the spot rather than waiting for them to expire.
- Open privileges run on a window rather than last forever, and an expired console has to answer for itself again before it is used.
- Healthcare deployments require their own risk assessment, operating procedures and any necessary agreements; these app features are not a HIPAA certification.
- What emergency information to keep on file, and what is shared when it is needed.
- Which alert locations to subscribe to — a home, a school, a workplace, a parent's address — and when to remove them.
- When a location is shared: a report you are making, resources near you, or while actually responding to a call.
- Deleting an account from inside the application, with the published privacy policy and privacy-rights pages stating what applies.
- Turning the second factor on, and choosing which device answers the check.
- Being told when a resource you hold is pulled onto a call, and withdrawing that at any time.
These are the application's intended safeguards, not a security certification. Access controls, privileged-console checks and privacy procedures must be reviewed for each deployment. The privacy policy and user agreement are available without signing in. Questions about a specific agency deployment, data-retention obligation or records request are answered directly — the contact address on this page reaches the people who build and run it.
- Community responders are never notified for law-enforcement, mental-health or hazmat calls; push alerts go out only for public-safety events needing immediate action, with limited information and location so live collaboration can occur
- Tamper-evident system tagging and complete timestamped audit logs of who did what and when
- Two-factor and three-factor sign-in depending on access requirements, agency rules and what is being accessed
- Layered encryption for data in storage, in transit and in use, with keys that rotate on a short cycle
- Certification and permission checks: people apply and submit proof of certification, and stay inside their field of training unless they submit new advanced certification
- A master kill switch that freezes the system into lockdown mode if a data leak is suspected, until the breach is fixed
The detail behind it
5 sectionsOpen any one to read it.Access is decided by role, verification, qualification and jurisdiction rather than by whoever is holding a phone, and it is applied per record rather than per screen.
- Role-based access and permissions, set per agency and per feature
- Verification of responder background and qualifications before participation
- Medical and restricted information held behind additional access rules
- Controlled incident sharing — what is published is chosen, not default
- Per-account audit records of who accessed what and when
Everything here describes the platform as built, subject to the configuration decisions of the community or agency using it.
Free for the people who need it, anywhere it runs.
It is not tied to one town or one county: a department, agency or community anywhere in the country or the world can run it. Residents are never charged. Departments pay for the parts they use, and donations let us put more resources into a community that could not otherwise afford them.
- · Defibrillators, naloxone and bleeding-control kits
- · Guides, voice instructions and training material
- · Mapping the equipment a community already has
Questions, corrections, or a resource we have missed — reach the team directly.