This policy covers the IncidentSuite app, IncidentSuite accounts, and the account and agency pages on incidentsuite.com. It says what is collected and stored, who can see it, where it goes, how long it is kept, and how to delete it.
Some of it needs a newer app than version 0.5, the version available now. Version 0.5 keeps incident reports on the device and sends them only through your phone's own mail app; it does not save reports, drafts or settings to your IncidentSuite account and does not sign in with a sign-in code. Where a part of this policy needs the newer app, it says with an updated app.
Location
The app uses your location on the device to show your position on the call map and the route to the call. Your location is not sent to IncidentSuite. Map and route requests go to Google Maps, under Google's privacy policy.
To show the nearest intersection, while a map is open the app sends your approximate location (rounded to about 10 meters), at most once every 30 seconds, to a public server of the OpenStreetMap Overpass API, a third-party service. Nothing else is sent with it: no account, name or other identity. The street address shown for your location comes from your phone's own address lookup, on the device.
Camera
The camera is used only to scan a QR code: the one Active911 shows to link the app to your agency's feed, and, with an updated app, a sign-in code made on another device or on the website. Images are not stored or sent anywhere.
Active911
The app reads your agency's Active911 feed with an Active911 device code or token. Calls, member names and responses come from Active911 and are shown on the device. When you press a status button, that response is sent to Active911. How IncidentSuite stores Active911 codes is described under Active911 logins and codes below.
Your IncidentSuite account
An IncidentSuite account is optional. If you create one, we store your email address, your name, your password (held by Firebase Authentication, a Google service, never by IncidentSuite in readable form), the agencies you belong to and your role in each, and your personal defaults (your device on the Active911 feed and the name on your reports). When you sign up we also ask for your first and last name, your mobile phone number, your position (for example Firefighter or Captain), the department you serve with and its state and county; you can change them on your account page. Your name and position are shown to the members of each agency you belong to. Your mobile phone number is shown to the admins of the agencies you belong to, so they can reach you, and to IncidentSuite staff when they help you or your agency (each time they look, it is recorded); other members never see it, it is copied to an agency only while you are its member, and we do not use it for marketing or send you text messages. Your department, state and county are kept on your profile, which only you can read. Each agency membership also records when you joined, whether an admin has suspended you, and when you last signed in, copied from Firebase Authentication every few minutes. To tell you when your password or your account's email address changes, we keep when your password last changed and your email address as Firebase Authentication reports them, and email you (at the old and the new address, for an address change) when either changes.
Members of an agency can see each other's name, email address, role, whether they are suspended, when they last signed in, their personal defaults, and the status of their Active911 login (its type, at most the last 4 characters of a device code, and when it was set, never the login itself).
With an updated app, settings you choose in the app, such as alert filters, alert tones, how long calls stay active and the app's layout, are saved to your account so they follow you to your other devices. Only you can read them. Some settings stay only on the device: background alerts, alert sound on or off, which Active911 device is you on that phone, and demo mode.
An invitation to join an agency stores the invited email address, the role offered and the email address of the admin who sent it. The invited person can see these and the agency's name, and the agency's admins can see the invitation, until it is accepted, declined or revoked. The invitation is emailed to the invited address, with replies going to the admin who sent it.
Your devices
With an updated app, each phone, tablet or computer that signs in to your account in the app is listed under your account with the name you give it, its platform and model, the app version, when it was added and how (with your password or with a sign-in code), and when it was last seen. Up to 20 devices. You can rename or remove a device on your account page; a removed device is signed out at once, even if it is lost, and so is every other sign-in of yours (you sign in again). Signing in on the website does not add a device.
The admins of each agency you belong to see the same list of your devices (never an Active911 code), and can remove a device from your account, which signs it out and ends your other sign-ins too.
A sign-in code lets a new device sign in to your account without your password. Your account page makes them now; signing in with one needs an updated app. A code is 8 characters, works once, for 5 minutes, and is stored only in a one-way scrambled (hashed) form. A used code is deleted; an unused one is deleted automatically after it expires, usually within a day. To slow down guessing, the server counts sign-in code tries from each network address for 10 minutes, keyed by a hash of the address rather than the address itself; these counts are deleted automatically the same way.
Active911 logins and codes
You can save an Active911 login for each agency you belong to, and a separate Active911 code for each of your devices, because a device code works on one device at a time. The login or code itself can be read only by you: by your signed-in devices, and by you on the website. Once saved, the website never shows it again.
An agency admin can set, replace or remove your Active911 login and codes, but can never read them. You and your agency's admins see the name given to each code, its type, at most the last 4 characters of a device code, and which of your devices uses it.
When you leave an agency or are removed from it, your Active911 login and codes for that agency are deleted.
Agency devices
An agency can register devices it owns, such as truck tablets. An agency device signs in as itself, not as a person. Its record holds the name and kind the admin gave it, an apparatus, the member it is assigned to (if any), the Active911 code given to it, when and by which admin it was set up, an identifier for the app install on it, its platform, model and app version, and when it was last seen. The agency's admins see the record, and so does the member it is assigned to. The device can read its agency's settings, its own record and the Active911 code given to it, and nothing about members or reports. An agency's Active911 codes for its devices can be read only by the device a code is given to: admins set them but cannot read them back. Setting up an agency device needs an updated app.
Incident reports
With the app available now (version 0.5), incident reports are written and kept on the device, and sent only when you email them through your phone's own mail app. IncidentSuite does not receive them.
With an updated app, a report you write is saved to your agency in IncidentSuite's Google Cloud (Firebase) database as a draft while you work on it, so you can continue on another of your devices. Only you can read your drafts.
When you submit a report, the app uploads it as a PDF, and IncidentSuite emails the report addresses your agency's admins have set to say it came in. The email comes from noreply@incidentsuite.com through Twilio SendGrid, and replies go to you. It gives the incident number, the agency, and your name and email address, and it can give the date the report was received; it links to IncidentSuite, where an admin signs in to read the report. The report and its PDF are not in the email. Until the earlier IncidentSuite app is retired, a report sent from that app goes through the earlier service: its email attaches the PDF, also gives the call type, address, time received and disposition, and comes through Google Workspace. If your agency uses a report template with required answers and one is missing, the report comes back to you as a draft instead.
A report contains what you and the app put in it: the incident number, call type and category, address, city, cross street and the call's map coordinates, dispatch notes, units, times, the personnel on the call and their responses, actions taken, disposition, your narrative, your name as author, which of your devices saved it, and the answers to your agency's report template, such as the fields NERIS asks for. Reports can include patient care details, for example in the narrative, the dispatch notes or names. IncidentSuite stores only the fields a report already has.
IncidentSuite does not have a HIPAA business associate agreement covering this service. If your agency must keep patient information under such an agreement, do not put patient details in IncidentSuite reports.
A submitted report and its PDF can be read by you and by your agency's admins, and the email goes to the addresses your agency set. A submitted report is your agency's record: nobody can change or delete it in IncidentSuite, including you and your agency's admins. A correction is a new report that names the one it corrects.
The first time you sign in with an updated app, reports already on the phone are copied to the agency once: ones you had already emailed from your mail app as submitted, the rest as drafts. Copied reports are kept as the agency's records and are not emailed by IncidentSuite; a copied draft is emailed only once you finish and submit it.
Agency administration
An agency's admins can see its members and their devices as described above, change roles, suspend and restore members, remove members, remove a member's device, set a member's Active911 login and codes without reading them, and ask IncidentSuite to send a member a password reset email. Firebase Authentication sends that email to the member's own address.
IncidentSuite keeps a change log for each agency, which its admins can read: who made each change (their account and email address), when, and what changed from what to what. It covers members, roles and suspensions, invitations, Active911 logins and codes and which device uses which (by name and kind only, never a login or a code), devices, agency settings and report templates. Nobody can edit or delete it, and its entries are kept when a person leaves or deletes their account.
When someone leaves an agency or is removed from it, the agency keeps a note of when, with their email address and whether they were suspended at the time, so an old invitation cannot bring them back. Its admins can see the notes of people who left while suspended, and can let such a person be invited again.
Billing
An agency's subscription is handled by Stripe. When an admin starts a subscription, IncidentSuite sends Stripe the agency's name, that admin's email address and an agency identifier. Card and payment details are entered on Stripe's own pages and never reach IncidentSuite. IncidentSuite keeps the subscription's status, plan, price, number of seats, trial and renewal dates, and Stripe's identifiers for the customer and subscription. Invoices and payment methods stay with Stripe, under Stripe's privacy policy.
Invitations and report emails come from noreply@incidentsuite.com through Twilio SendGrid. IncidentSuite keeps a record of each one it sends: the recipients, subject, message text, which report or invitation it was for, and whether it was delivered. Account emails, such as email address verification and password reset, are sent by Firebase Authentication.
Where it is stored
IncidentSuite's database, report files and server functions run in Google Cloud (Firebase) data centers in the United States. Account sign-in is handled by Firebase Authentication. The service providers that receive data, each as described above, are Google (Firebase, Google Cloud, Google Maps, and Google Workspace for the earlier app's email), Twilio SendGrid, Stripe, the OpenStreetMap Overpass API and Active911.
Advertising and analytics
The app and the website have no advertising and no analytics. We do not sell your data.
Deleting your data
On your account page you can remove your Active911 login and codes, remove your devices, leave an agency, and delete your account.
Leaving an agency, or being removed from it, deletes your membership there, your Active911 login and codes for it, its copy of your device list, and your report drafts there.
Deleting your account deletes your account, your membership in every agency, your Active911 logins and codes, your report drafts, your devices, your app settings, invitations sent to you and invitations you sent. It does not delete:
- reports you submitted, which are your agencies' records and keep your name as author;
- the agencies' change logs, which can name you, and their notes of when you left;
- the records of emails IncidentSuite sent, such as report emails that give your name and email address;
- what Stripe holds, if you started an agency's subscription.
Changes to this policy
When this policy changes, the new version is posted on this page with a new effective date.
Contact
Questions about this policy: privacy@incidentsuite.com.