MenuClose

Data Processing Addendum

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.

This addendum is part of the Terms of Service between [owner to fill: company legal name] ("IncidentSuite", "we") and the agency that uses IncidentSuite (the "Customer"). For protected health information (PHI), the Business Associate Agreement the parties sign controls over this addendum.

1. Roles

We process personal data on the Customer's behalf and under its documented instructions: the Terms, this addendum, and how the Customer sets up and uses IncidentSuite. The Customer is responsible for the lawfulness of the data it puts in and of its instructions.

2. The processing

  • Subject and duration: providing IncidentSuite for the subscription, and the return and deletion after it ends.
  • Nature and purpose: hosting, storing, sending, processing, backing up and supporting the Service.
  • Kinds of personal data: users' names and contact details; calls and dispatch information; unit locations from a vehicle modem, tracker or station listener the Customer connects; incident reports; patient care reports (PHI); personnel records, including Social Security numbers, certifications, training and hours; controlled-substance records; messages; uploaded files; and logs.
  • People the data is about: the Customer's members and users; patients and members of the public involved in calls; and anyone else whose data the Customer puts in.

3. What we do

We (a) process personal data only on the Customer's documented instructions, unless the law requires otherwise, in which case we tell the Customer unless the law forbids it; (b) bind everyone who processes it to confidentiality; (c) keep the security measures in section 6; (d) use providers only as section 4 says; (e) help the Customer, as the processing allows, answer requests from the people the data is about and meet its security and breach-notice duties; (f) return or delete the data as section 7 says; and (g) give the Customer the information it reasonably needs to show compliance, as section 8 says.

4. Providers

The Customer authorizes us to use the providers below, as they stand today. Each works under its own written terms with us, except the public OpenStreetMap Overpass service, which has none; [lawyer: whether each provider's terms protect the data as this addendum requires]. We remain responsible for them. We give [owner to fill: number of days] days' notice, by email to the Customer's admins and on this page, before adding or replacing a provider that receives Customer Data, and the Customer may object on data-protection grounds.

ProviderWhat forWhat it receives
Google Cloud: Firestore, Cloud Run and functions, Cloud SQL, Cloud Storage, Identity Platform, KMS, Secret Manager, Logging, Pub/Sub, SchedulerHosting, databases, files, sign-inAll Customer Data and account data
Google: Firebase HostingServing the website's pagesRequests for the website's public pages; no Customer Data
Google: Firebase Cloud MessagingAlerts to phonesToday: a call's type, address and units, and up to 200 characters of an agency message
Google Maps Platform (Maps JavaScript, Geocoding, Directions, Routes, Navigation SDK)Maps, address lookup, routes, turn-by-turn navigationMap areas and coordinates; from the phone app, call addresses, and the destination and the member's location when navigation starts
Google Play services: Android's address lookup and the Wear OS data linkFinding a call's address on the phone; the watchThe call's address as typed; a call's type, address and units for a paired watch
Google Workspace (Gmail)The mailbox for emailed dispatch, when email intake is turned onRaw dispatch email; nothing today, as email intake is not running
Cloudflare, Inc.Domain names for incidentsuite.comNo Customer Data
OpenStreetMap Overpass (a public server in Germany)Street names near a location, in the phone appThe member's position and the coordinates around a call, rounded to about 11 meters, at most every 30 seconds
Twilio Inc.: SendGridThe emails IncidentSuite sendsNames, email addresses, the agency and report numbers; never call or chart details
Stripe, Inc.BillingThe agency's name, the billing admin's email address and an agency identifier; card details go to Stripe directly, never to us

Sent on the Customer's own instruction (the Customer's recipients or vendors, not our providers): NERIS, which receives approved incident reports, including the narrative and casualty details, when an admin sends each one; the Customer's billing company, which receives the full patient care report when the Customer sets it up; the Customer's own email service, if it picks one; and Active911, the Customer's paging service, read with its own login.

5. Where the data is

Customer Data is stored in Google Cloud in the United States. Service logs are kept by Google Cloud Logging, whose storage has no fixed region today, and the phone app's street-name lookups go to the OpenStreetMap Overpass service in Germany. If a transfer outside the United States needs a legal mechanism, the parties will put one in place.

6. Security measures

Our measures include: encryption in transit; field-by-field encryption of Social Security numbers and stored integration secrets, with a key for each agency; each agency's records kept apart in the database itself (row-level security) and by the rules on every read and write of the live data; role-based access; an append-only, signed audit log; a record of who opened each patient chart; two-step sign-in for every web sign-in; and rate limits on public forms and incoming feeds. Measures can change, but we will not reduce the overall protection during the subscription.

7. Return and deletion

While the subscription lasts, the Customer's admins can export all of its records at any time: every table, every patient care report, every file and every document, in one download (Settings, Export). When it ends, [owner to fill: how long and in what form the Customer can get its data back]; then we delete the Customer's personal data, except where the law or an active legal hold requires us to keep it. Database backups expire after 14 days. [owner to fill: deleted files' earlier versions are kept until a lifecycle rule is set]. PHI is returned or destroyed under the Business Associate Agreement.

8. Information and audits

On reasonable request, no more than once a year or after a security incident that affects the Customer, we give the Customer the information it reasonably needs to show compliance, such as our current security documentation, under confidentiality. An on-site audit, if any, is at the Customer's cost and scheduled to keep disruption low.

9. Security incidents

We tell the Customer of a security incident that affects its personal data without undue delay, and no later than [owner to fill: number of days] days after we find it, with what we know and what we are doing. Breaches of PHI are reported under the Business Associate Agreement.

10. Order of precedence

If documents conflict: the Business Associate Agreement (for PHI), then this addendum, then the Terms of Service.