This page is the official privacy policy URL for the Responder Pager mobile applications
(package / bundle ID com.responderpager.app on Android, com.responderpager.mobile on iOS) published on Google Play and the Apple App Store.
It describes how the apps interact with the Responder Pager service operated for your organization
(for example at https://app.responderpager.com). Have legal counsel review if your jurisdiction
requires a customized policy.
Summary. The apps are used by authorized responders to receive incident alerts, view incident
information, and submit response status. Sign-in uses your phone number and SMS verification codes. Push
notifications use Google Firebase Cloud Messaging on Android (and Apple Push Notification service on iOS).
Location is used only when you explicitly choose to share GPS coordinates for an incident location update—not
for continuous background tracking.
Who this applies to
This policy applies to individuals who use the Responder Pager mobile app on behalf of a participating agency
(fire, EMS, law enforcement, or other organization) that has been provisioned on the Responder Pager platform.
Your agency’s own policies may also apply.
Information we collect through the app
Account and profile data. Information associated with your responder account, such as name,
phone number, role, agency assignment, and similar fields your administrators maintain in Responder Pager.
Authentication data. When you sign in, the service sends a one-time verification code via SMS
to your phone number. The app exchanges that code with the Responder Pager API to establish a session. We log
authentication events as needed for security and troubleshooting.
Push notification identifiers. The app registers with
Firebase Cloud Messaging (FCM) on Android and with Apple Push Notification service
(APNs) on iOS. A device token is stored server-side so dispatch and system messages can reach your
device until you sign out, your administrator removes access, or the token is rotated or invalidated.
Incident and operational data. Actions you take in the app (for example marking
responding / not responding, viewing incidents you are allowed to see, and optional features such as radio log
access when enabled for your account) are sent to the Responder Pager API and stored as part of your agency’s
operational records.
Location (when you opt in per use). If you use a feature that updates an incident’s map
location from your device, the app requests foreground / when-in-use location access and
sends coordinates you confirm to the Responder Pager API. The app does not continuously track your location in
the background for advertising or analytics.
Device and app diagnostics. Standard technical metadata (such as app version, OS version, and
error reports you or your device submit) may be processed to keep the service reliable and secure.
How we use information
To authenticate you and maintain secure sessions.
To deliver time-sensitive incident and system notifications.
To display incidents, messages, and agency configuration your role is permitted to access.
To record response and operational activity for dispatch and agency reporting.
To protect the service against abuse, fraud, and security incidents.
Legal bases (where applicable)
Depending on region, processing may be based on contract (providing the service to your organization),
legitimate interests (security and reliability), or consent where required (for example for certain notifications
or location prompts shown by your device).
Sharing and subprocessors
Communications providers. SMS one-time codes and related messaging may be delivered through
providers such as Twilio (or comparable carriers integrated with your deployment), acting on
instructions from the Responder Pager service.
Google / Firebase. On Android, push delivery uses infrastructure operated by Google as part of
Firebase Cloud Messaging. Google’s terms and privacy notices for Firebase and Google Play Services also apply to
those components.
Apple. On iOS, push notifications are delivered through Apple’s Push Notification service.
No sale of personal information. We do not sell your personal information.
Agency access. Administrators and authorized dispatch users for your organization can access
operational data consistent with their roles and your agency’s use of Responder Pager.
Retention
Incident and response records are retained according to your agency’s operational and records policies and
the configuration of your Responder Pager deployment.
Security and authentication logs are retained for a period appropriate to detect abuse and meet legal
obligations.
Push tokens are removed or invalidated when you sign out, lose access, or replace your device registration.
Security
Data is transmitted between the app and the service using TLS (HTTPS). You should keep your device OS updated
and use a lock screen to protect access to the app.
Your choices and rights
You may sign out of the app at any time.
You can adjust notification permissions in your device settings; turning off notifications may mean you miss
incident pages.
For access, correction, export, or deletion requests, contact your agency administrator first.
They control accounts and many categories of operational data.
For additional privacy questions at the service level, use the contact path described on
Mobile support.
Children
Responder Pager is intended for professional public-safety and related agency use. It is not directed at children
under 13 (or the minimum age required in your region), and we do not knowingly collect personal information from
children for marketing purposes.
International transfers
Your data is processed in connection with the region where your organization’s Responder Pager service is hosted
and where subprocessors (such as Google, Apple, or SMS providers) operate. Additional safeguards may apply under
your contract with the service operator.
Changes to this policy
We may update this page to reflect product, legal, or regulatory changes. The “Last updated” date below will change
when we do. Material changes may also be communicated through your agency or in-app notices where appropriate.
Contact
Primary support for day-to-day account and paging issues is through your department or county
administrator. For product or privacy questions at the platform level, see
Mobile support.
Canonical URL: https://app.responderpager.com/mobile-privacy.html
Last updated: May 15, 2026