Plain answers about your data.

01Who we are

ResponderOS is a product of 911 Command LLC (referred to as "we," "us," or "ResponderOS" in this policy), a Virginia limited liability company established in 2024. The app is designed for front‑line public safety personnel — fire, EMS, and law enforcement — to document and manage shift‑level operational work.

Contact for any privacy question: privacy@responderos.app.

02What we collect

ResponderOS is built to do its job with as little data as possible. Here's everything we collect, why, and how it's classified for Apple's App Privacy disclosures:

What we explicitly do not collect

• Background location — location is used only in the foreground, for map features, and stops when you leave the incident or close the app
• Contacts, or camera/photo access beyond what you explicitly initiate (scanning a tag, attaching a photo to a record) — captured content goes only into that record
• Advertising identifiers (IDFA), tracking cookies, or cross‑app identifiers
• Your personal health, financial, or government ID information — patient care records your organization documents are covered in Sections 2 and 5
• Anything from other apps on your device

03How we use it

We use the data above only for the following purposes:

• To operate the service. Authenticating you, storing and syncing the records you create, delivering notifications you opted into.
• To improve the app. We may review aggregate, de‑identified patterns of how the app is used — for example, which screens are slow, which workflows have unusually high abandonment — to fix bugs and prioritize improvements. We do not read, analyze, or process the content you create (counseling logs, station notes, evaluations, etc.) for this purpose or any other.
• To generate summaries you request (optional AI features). If your organization enables it, certain features — such as trauma-session narrative summaries — send the relevant session data (vitals, interventions, timestamps; not patient names or addresses) to Anthropic's Claude API to generate a draft summary, server‑side, only when you request one. The output is a documentation starting point, not clinical advice. This data is never used to train AI models, and the feature is off unless your organization's administrator turns it on.
• To communicate with you. Sign‑in confirmations, password resets, security notices, and (only if you opt in) product updates.
• To comply with the law. If we receive a valid legal request, we will comply with it. We'll notify your organization administrator unless legally prohibited.

04What we don't do

This section exists because it's the part most worth being clear about.

• We do not sell, rent, or monetize personal data. Not to advertisers, not to data brokers, not to anyone.
• We do not run advertising in the app. No banner ads, no native ads, no sponsored content.
• We do not track you across other apps or websites. ResponderOS does not use Apple's App Tracking Transparency framework because we do not track.
• We do not read or analyze the personnel content you create. Your counseling logs, evaluations, station notes, and other records are stored encrypted and accessed only by you and authorized members of your organization. We do not use them to train models, improve features, or any other purpose.
• We do not share your data with anyone outside of the operational processors listed in Section 5.

05Sharing & processors

To operate the app, we rely on a small number of trusted infrastructure providers. They process data only on our instructions and only to provide the specific service named.

Google Firebase (Google LLC)

ResponderOS's backend runs on Google Firebase, which provides three services to us:

• Firebase Authentication — handles sign‑in. Receives your email and a hashed version of your password.
• Cloud Firestore — stores the records you create. Encrypted at rest in Google's US‑based data centers.
• Firebase Cloud Messaging — delivers push notifications. Receives your device push token and the contents of notifications we send.

Google's processing of this data is governed by the Firebase Data Processing and Security Terms. We do not use Firebase Analytics or Crashlytics. We use Firebase Performance Monitoring for aggregate, de‑identified app performance metrics (screen load and network timing) — it does not receive the content of your records.

Apple Inc. & Expo

Apple delivers push notifications to your device through the Apple Push Notification service (APNS), routed via Expo's push service (Expo, Inc.), which receives your device push token and notification contents in transit. Apple may also collect anonymous diagnostic information through iOS itself, governed by Apple's own privacy policy. Neither receives the stored content of your records.

LiveKit (voice)

Push‑to‑talk voice on incident channels is carried in real time by LiveKit's infrastructure. Audio is transmitted live to your channel and is not recorded or retained by us.

Anthropic (optional AI summaries)

If your organization enables AI summary features, the session data described in Section 3 is processed by Anthropic's Claude API to generate the requested summary. Anthropic processes it as a service provider and, under our API usage, does not use it to train models.

Payments (Stripe, Apple, Google, RevenueCat)

Individual subscriptions purchased on iOS/Android are processed by Apple or Google through in‑app purchase, with entitlements managed by RevenueCat; web and organizational purchases are processed by Stripe. We never see or store full payment card details — payment processors handle those directly.

Mapbox (maps)

Map tiles and geocoding for incident maps are served by Mapbox, which receives the map coordinates your device requests in order to render the map.

Your organization (if applicable)

If you use ResponderOS through an organizational license — for example, your fire department or EMS agency — the data you create within the app is accessible to authorized administrators within that organization, under the access controls they configure. This includes your live position on an incident map while you are on an active incident, which is visible to other authorized members of your organization and is removed when you leave the incident or close the app. Your organization is the data controller for personnel and patient care records; ResponderOS is a data processor acting on the organization's behalf. Organizations handling Protected Health Information are responsible for their own HIPAA and state-law compliance, including executing any required Business Associate or Data Processing Agreement with us.

06Data retention

We retain data only as long as it serves the purposes described in this policy:

• Account data. Retained for as long as your account is active. If you delete your account, we delete the associated authentication record within 30 days.
• Personnel records you create. Retained according to your organization's retention policy. If you use ResponderOS individually (without an organization), records you create are retained until you delete them or delete your account.
• Backups. Encrypted backups may retain data for up to 90 days after deletion before being permanently overwritten, as part of normal disaster recovery.
• Legal holds. Where required by law, we may retain specific records longer. If this happens to your data, we'll notify you unless prohibited.

07Your rights

Regardless of where you live, you can do the following at any time:

• Access — request a copy of the data we have about you.
• Correct — fix anything inaccurate.
• Delete — request deletion of your account and associated data.
• Export — receive your data in a portable format (JSON or CSV).
• Withdraw consent — for any optional processing you previously opted into (e.g., product update emails).
• Object — to any processing you believe is unnecessary or excessive.

To exercise any of these, email privacy@responderos.app. We'll respond within 30 days. We do not charge for these requests.

Residents of California, Virginia, Colorado, Connecticut, and Utah

You have additional rights under your state's privacy laws (CCPA/CPRA, VCDPA, CPA, CTDPA, UCPA), including the right to opt out of the "sale" or "sharing" of personal information. ResponderOS does not sell or share personal information as those terms are defined under any of these laws. You can still exercise any of the rights listed above by contacting us.

08Security

We take security seriously because the records you put into ResponderOS are operationally sensitive. Our practices include:

• Encryption in transit using TLS 1.2 or higher for all network communication.
• Encryption at rest for all stored data, using Google Firebase's default AES‑256 encryption.
• Role‑based access controls at the organization level — your administrators decide who can see what.
• Org access is admin‑controlled — anyone can create an individual account, but joining an organization (and seeing any of its data) requires an invitation or admin‑approved join request from that organization.
• Audit logging of administrative actions within your organization.
• No password storage on our end. Firebase Authentication hashes passwords; we never see or store them in plain text.

No system is ever fully secure. If you become aware of a vulnerability, please report it to security@responderos.app. If a breach affects you, we'll notify you within 72 hours of becoming aware of it, as required by applicable law.

09Children's privacy

ResponderOS is a professional tool for adult public safety personnel. It is not directed to children under 13, and we do not knowingly collect personal information from anyone under 13 years of age. If we learn that we have collected information from a child under 13, we will delete it promptly. If you believe a child has provided us with personal information, contact us at privacy@responderos.app.

10Where data is stored

ResponderOS data is stored in the United States, in Google Firebase data centers. If you access the app from outside the U.S., your data will be transferred to and processed in the U.S. By using ResponderOS, you consent to this transfer. We do not currently support data residency in other jurisdictions; if your organization requires it, contact us to discuss options.

11Changes to this policy

If we make material changes to this policy, we'll notify you by email and/or by an in‑app notice before the changes take effect. The effective date at the top of this page reflects when the current version was published. Continued use of ResponderOS after a change indicates acceptance of the updated policy.

12Contact

Questions, requests, complaints — bring them all here. We respond to every privacy email, usually within a few business days.