Privacy Policy
Version 0.2 (draft), November 21, 2026
Draft for the owner's legal review. Not in effect: a lawyer reviews it and the slots marked "owner to fill" are filled before it takes effect.
IncidentSuite is software for fire, EMS and rescue departments ("agencies"). It is made by [owner to fill: company legal name], [owner to fill: mailing address] ("IncidentSuite", "we"). This policy covers the website at incidentsuite.com, the web app at app.incidentsuite.com, the IncidentSuite phone app, and the department websites agencies publish with IncidentSuite.
1. Whose data this is
- Your agency's records belong to your agency. When an agency uses IncidentSuite, it decides what goes in, who can see it, and how long it is kept. We handle those records only to run the service for that agency, as its service provider.
- Patient information. IncidentSuite is not yet offered for real patient information. Agencies use it with made-up data until our business associate agreement is available, from [owner to fill: the date the BAA is available].
- If you are a patient, a resident or a member of an agency, the agency's own privacy notice also applies to you. Ask the agency first about records it holds about you.
2. What we collect
Your account
- Your name and email address.
- Your password, held by Google's sign-in service and never readable by us, and your two-step sign-in (an authenticator app).
- The agencies you belong to, and your role in each.
- Your devices: name, model, app version, when added and when last seen.
- When you signed in. Sign-in attempts, including failed ones, are logged.
- The settings you choose.
- Your profile, if you fill it in: phone number, position and department. Only you and your agency's admins see your phone number. IncidentSuite staff can look it up for support, and each look is recorded in your agency's change log.
What your agency puts in IncidentSuite
Depending on the modules it uses:
- personnel and HR records (Social Security numbers are encrypted with a key for each agency);
- certifications, training, schedules and hours;
- equipment, inspections, permits and pre-plans;
- calls from the agency's dispatch system and unit status, and unit locations from a vehicle modem, tracker or station listener the agency connects;
- incident reports and patient care reports;
- safety and exposure records;
- messages between members;
- files attached to any of these.
From your agency's dispatch system: each call as the dispatch system sends it. The raw message is kept for the number of days your agency sets (1 to 365, normally 30), and the call itself as part of the agency's records.
Location and the phone app
- The phone app uses your device's location to show you on the map and to give directions to a call.
- To show directions and street names, the app sends Google the call's location and address, and your location. The phone's address lookup (Google Play services) receives the call's address. Starting turn-by-turn navigation gives Google's Navigation SDK the destination and your location, under Google's terms.
- The app looks up nearby street names on the public OpenStreetMap Overpass service, run in Germany, sending your position and the coordinates around the call, rounded to about 11 meters, at most every 30 seconds. We are replacing it.
- If you pair a watch, the call's type, address and units go to it through Google Play services.
- A new call reaches your phone through Google's Firebase Cloud Messaging. Today an alert carries the call's type, address and units, and a message alert carries up to 200 characters of the message.
- The camera is used only to scan a QR code. Pictures are not kept or sent.
On a department website
What a resident types into a form an agency publishes (for example a burn permit or a records request): name, contact details, address and the request. It goes to that agency.
On our website and the web app
We use no analytics, no advertising and no tracking cookies. The web app's cookies only keep you signed in, remember which agency you are working in, and sign you out after 30 minutes without use. Our hosting logs requests (the network address, the time and what was asked for) to run and protect the service.
3. How we use it
Only to run the service for your agency; to secure it, including sign-in checks, the audit log and stopping abuse; to support you when you or your agency ask; to bill your agency; and to meet legal duties. We never sell data, never use it for advertising, and never use patient information for anything but providing the service to your agency.
4. Who receives data
- Your agency's members and admins see what their roles allow.
- Places your agency chooses to send records: NERIS (the national fire incident reporting system), when an admin sends an approved report; the agency's billing company, when the agency connects one; the agency's own email service, if it sets one; and Active911, the agency's paging service, with its own login.
- Our service providers. Each one, with what it receives, is listed in the Data Processing Addendum: Google (Cloud, Firebase Cloud Messaging, Maps, Play services, and Workspace when email intake is turned on), Cloudflare (our domain names only), the OpenStreetMap Overpass service, Twilio SendGrid (our emails, which never carry call or patient details) and Stripe (billing; card details go to Stripe directly and never reach us).
- The law: we disclose data when the law requires it, and we tell the agency first unless the law forbids it.
5. Where it is kept
Your agency's records and your account are kept in Google Cloud data centers in the United States (us-central1 and Google's US multi-region). Our service logs are kept by Google Cloud Logging, whose storage has no fixed region today. Location lookups sent to the OpenStreetMap Overpass service go to Germany.
6. How long
- Your agency's records: for as long as your agency uses IncidentSuite, until it deletes them or its agreement ends. Its admins can export all of its records at any time (Settings, Export). When the agreement ends, [owner to fill: how the agency's records are returned and deleted, and when].
- Raw dispatch messages: your agency's setting, 1 to 365 days.
- Database backups: 14 days. Deleted files: [owner to fill: deleted files' earlier versions are kept until a lifecycle rule is set].
- Service logs: 400 days. They carry ids, never record content.
7. Security
- Every account signs in to the web with a password and two-step sign-in. Web sign-ins end after 30 minutes without activity.
- Each agency's data is walled off, in the database and in every rule that reads it.
- Each time someone opens a patient chart, it is recorded in an audit log.
- Data is encrypted in transit and at rest. Social Security numbers are also encrypted with a key for each agency.
- IncidentSuite staff access to an agency shows in that agency's change log.
More on the Security page.
8. Your choices
- Your profile and settings: change them in the app or the web app.
- Deleting your account: in the web app, under Account, Sign-in and security, Delete account. It deletes your account and sign-in, your profile, settings and devices, your membership in every agency, your drafts, and your account's own record with its email history. It does not delete what you added to an agency's records, such as reports you submitted, charts you signed and entries in the audit log, nor an agency's note of when you left (with your email address) or your personnel record there: those are the agency's records, so ask the agency about them.
- Records an agency holds about you, as a patient, a resident or a member: ask that agency. We help it answer.
- Your rights under a state privacy law: [lawyer: which state privacy laws apply to IncidentSuite as a service provider to public agencies, and what to say]. Contact us at the address below.
9. Children
IncidentSuite accounts are for adults working with an agency. Records an agency keeps may concern patients of any age; they are handled as above, for the agency.
10. Changes
We post a new version here with a new version number and date. We tell agency admins by email before a change that affects what we collect or who receives it.
11. Contact
Privacy: privacy@incidentsuite.com. Security problems: hello@incidentsuite.com. Post: [owner to fill: mailing address].