Security and data handling

1.1 The audio is processed into text, and we do not store your recording on our servers. There is no recording history to browse.

1.2 Until the report is ready, a copy stays on your device, so a dropped signal or a closed tab does not lose your narration.

1.3 Audio that a software partner sends through our API is kept in a private store for 30 days, unless the partner chooses less, and then deleted.

1.4 Processing runs on a small number of service providers acting on our behalf, most of them US-based. We do not publish the list, but we share it in writing with any department that needs it for a data agreement.

1.5 Where we have a department's local street and place names, they are used during processing so local spellings come back right.

2.1 The transcript is processed into structured NERIS fields, the draft report you review, and stored with the report for your department.

2.2 We may use your reports to improve FireMic. Anonymous trial recordings are never used as training data.

3.1 Reports, including the transcript of what you said. The transcript is the evidence for what is in the report, so it is kept with the report.

3.2 Roster: names and roles of members, plus a PIN for officers and admins stored only as a one-way hash. We cannot read a PIN back, and a copy of the database on its own does not yield them.

3.3 Attachments, the photos you add to a report, in a private storage bucket with no public read access. Uploads go straight from your browser through a one-time signed link our server issues, and downloads use signed links. The key shipped to browsers cannot list or read the bucket.

3.4 Anonymous trial drafts, in a separate table with their own lifetime (section 5).

4.1 The database denies direct access by default. Nothing is readable straight from the browser; every read goes through our API.

4.2 The API works out your department from your session on our server. It never takes a department id from the request.

4.3 Everyone on your department's roster in FireMic can read its reports.

4.4 Membership is checked against the database on every request, so removing someone takes effect on their next action, not when their sign-in happens to expire.

4.5 Officer and admin sessions expire after 12 hours. A firefighter's lasts 30 days, so nobody is signing in at 3 a.m. on their own phone.

4.6 On a shared station tablet, sessions are per tab and are not shared between the people using the device.

4.7 Our own engineers can reach the database to run and support FireMic, as with any hosted service.

5.1 A trial draft is stored in a different table from any department's records. It is not in any department's dashboard, export, review queue or statistics.

5.2 Trial drafts you don't file are deleted after 30 days unless you sign in and claim them. A job runs daily and deletes them, and every read already ignores an expired draft. A trial report you file to NERIS's test system is kept, with its narration, until deleted; ask us and we delete our copy, and NERIS keeps its own.

5.3 A trial report cannot be filed to a real department's NERIS record. Filing one sends it to NERIS's test system under FireMic's own test department. Our server picks that destination, and nothing your browser sends can name another.

5.4 Anonymous trial recordings are never used as training data.

5.5 Your browser's anonymous id groups your drafts but does not unlock them. Reading a draft back also needs a secret key that our server issues, stores only as a hash, and keeps in a cookie your browser's scripts cannot read.

6.1 Anonymous trial drafts are deleted automatically after 30 days, as section 5 describes.

6.2 Attachments can be deleted from a report.

6.3 There is no delete button for a filed report in the product today. Ask us and we will delete a department's data from our database.

6.4 A report already filed to NERIS is NERIS's record, not ours. We cannot delete a federal filing on request; corrections go through NERIS.

7.1 Error reporting is off unless a reporting key is configured. When it is on, request bodies and cookies are stripped before an event leaves our systems, a list of sensitive fields (transcripts, report contents, NERIS data, audio and email addresses) is removed at one place, and your email is removed from the identity.

7.2 Usage analytics in the app is off unless a key is configured. When it is on, it does not capture what you type, and a filter drops any property whose name looks like a name, email, address, transcript, narrative, phone number, street, patient, city, ZIP, date of birth or Social Security number, along with any text long enough to be a narrative.

7.3 This marketing site has no server side and no database, and it sends nothing unless an analytics key is configured for it. When one is, the search boxes of the free tools (the NERIS incident type list and the NERIS ID lookup) send the words searched and how many results came back; nothing else typed on the site is sent.

8.1 The "NERIS V1 Data Exchange Compatible" badge means FireMic meets the technical requirements for connecting to the NERIS V1 API. It is not a certification or an endorsement beyond that.

8.2 FireMic does not hold SOC 2, ISO 27001 or an equivalent certification, and has not had a third-party penetration test.

8.3 We do not claim HIPAA compliance. Incident narratives can include patient information. If your department needs a HIPAA business associate agreement, or has questions about patient information, ask us and we will answer in writing.

8.4 The controls on this page are engineering controls, not an audit. Ask us to demonstrate any of them.

9.1 Report security problems through the email, phone or text links on this page. We will fix what you report and, if you want it, credit you for finding it.