Effective date: October 14, 2026
This Privacy Policy describes how RescueMetrics BioPerformance, LLC ("RescueMetrics BioPerformance," "we," "us," or "our") collects, uses, stores, and shares information when you use our websites, Command Post / research platform, and Shift Pulse fire fighter mobile applications (together, the "Services"), including the Android and iOS apps published as Shift Pulse (package / bundle com.rescuemetrics.firefighter).
By using the Services, you agree to this Policy. If you do not agree, do not use the Services.
1. Who we are
Controller: RescueMetrics BioPerformance, LLC
Contact: mike@rescuemetricsbio.com
Website: rescuemetricsbio.com
2. Scope
This Policy covers:
- Web apps at platform.rescuemetricsbio.com and related branded hosts
- Native Shift Pulse apps for iOS and Android (published as Shift Pulse; package / bundle
com.rescuemetrics.firefighter) - Related enrollment, wearable connection, and operational dashboards we operate for fire / EMS and research agencies
Agency customers may have their own policies for how they enroll members and use organizational dashboards. This Policy explains what RescueMetrics BioPerformance does as the technology provider.
Data stewardship and individual sovereignty
RescueMetrics BioPerformance treats two duties as complementary. Stewardship: fire departments, research groups, other public or private employers, and RescueMetrics BioPerformance as their technology provider are responsible for protecting individual and group data — organization isolation, need-to-know access, encryption, audit, and use only for the purposes in this Policy. Agencies administer enrollment and Command Post views for their own members; they do not see other customers' data. Individual sovereignty: the person the data is about retains control over connecting or disconnecting a wearable, viewing their own Shift Pulse record, withdrawing research participation, and requesting export or deletion (see §8). Organizational dashboards do not replace that control.
This is a product and program principle. It is not legal advice, and it is not a claim that every privacy statute applies to every customer.
3. Information we collect
Account and profile
- Name and email address
- Role (e.g., fire fighter participant, agency admin, platform staff)
- Organization / department affiliation and enrollment identifiers
- Agency invite / registration codes used to create a Shift Pulse account (invite-only; not a public consumer signup)
Health, fitness, and wearable data
With your (or your agency's authorized) connection to wearable providers such as WHOOP, Oura, Polar, and Garmin (when enabled), we may receive recovery, sleep, strain/activity, heart-rate–related metrics, workouts, and related timestamps and identifiers needed to sync and display readiness insights.
Apple Health and Android Health Connect
If you choose to connect Apple Health (on iPhone) or Health Connect (on Android) in Shift Pulse, the app reads sleep, heart rate variability, and resting heart rate recorded by your watch, ring, or band, and sends them to your agency's RescueMetrics program. On iPhone only Apple Watch data is read. On Android, entries typed in by hand and data from services that connect to RescueMetrics directly are skipped. Shift Pulse never writes to either store. We do not use this data for advertising, do not sell it, and do not use it to train or improve machine-learning models. You can turn access off at any time in your phone's Health or Health Connect settings; data already sent is kept and deleted under the retention terms below.
Operational / shift context
- Schedule or duty information when an agency connects a staffing or RMS integration
- App usage events needed to operate features (e.g., sync status, errors)
Device and technical data
- Approximate device type, OS version, app version, and diagnostic logs to keep the Services secure and reliable
- Authentication credentials we issue: on Shift Pulse, tokens are stored in the operating system's encrypted storage. On Command Post in a web browser, a signed session token is stored in an HttpOnly cookie (not readable by page scripts) and expires after about two hours, after which you sign in again. We also collect MFA method details (authenticator-app enrollment).
We do not require advertising identifiers for core app functionality. We do not sell personal information.
4. How we use information (consent purposes)
When you use the Services (including connecting a wearable from an agency registration or enrollment link), you agree to this Policy. Shift Pulse account creation additionally records your named acceptance of purposes A, B, and C below (versioned Terms & Conditions). Wearable-only join via QR does not create a Shift Pulse login; that connection is still use of the Services under this Policy. We do not use your data for third-party AI platforms (see §5).
A. Operate the Services
- Provide personal readiness, sleep, and recovery views in Shift Pulse
- Provide agency / research dashboards and exports authorized for that organization — when you connect a wearable, you opt in to authorized Command Post and research roles for your organization viewing those metrics for the program purposes in this Policy
- Authenticate users, protect accounts (including MFA), and prevent abuse
- Sync wearable and operational data you or your agency connect
- Support customers, improve reliability, and meet legal obligations
B. Improve RescueMetrics BioPerformance models
Develop and improve RescueMetrics BioPerformance-owned analytics and machine-learning models (for example sleep-debt, shift-response, or organizational readiness trends) using de-identified or pseudonymized features derived from wearable and duty-context data, only where the applicable wearable partner terms and API agreements allow. WHOOP® and Garmin® API data are excluded from purpose B under those partners' current terms (no training, fine-tuning, or improvement of ML/AI models on that API material). Data read from Apple Health or Health Connect is also excluded from purpose B. Training and scoring that do run use infrastructure we control (e.g., Microsoft Azure). We do not use these models to declare fitness for duty or to make employment decisions.
C. Research and IRB-supporting use
Support authorized wellness programs and research (including IRB-supporting protocols) through agency-configured dashboards and consent-aware exports. Research access is limited to the organization's authorized roles and documented research workflows; it is not a public dataset and we do not market, sell, or license API-obtained wearable data to third parties.
Firefighter-facing insights are for personal performance and recovery support. They are not medical advice, not a diagnosis or treatment plan, and are not intended for employment decisions by RescueMetrics BioPerformance. Always follow your department's policies and seek qualified clinical care when needed.
Human oversight of automated insights
Scores, trends, and suggested sessions (for example shift-aware recovery bands that surface restore / build / push training content) may be produced automatically from wearable and duty-context data. Those outputs inform a firefighter or authorized program viewer; they do not make employment, fitness-for-duty, staffing, or emergency-operations decisions. A person reviews and applies department protocol before relying on any insight for operational action. Adaptive session suggestions are rules on recovery and preference — not an autonomous agent that invents a training program or acts without human judgment.
5. How we share information
We share information only as needed to operate the Services:
- Your agency / research group — administrators and authorized roles for that organization may see participant and operational data configured for that tenant. Agency data is isolated from other customers.
- Wearable and partner APIs — when you connect WHOOP, Oura, Polar, Garmin, or similar services, those providers process data under their own policies; we receive data they return via their APIs. Apple Health and Health Connect data reaches us only from your own phone, through Shift Pulse, after you grant access.
- Infrastructure providers — e.g., Microsoft Azure for hosting, databases, and encrypted storage, under contractual safeguards. This includes compute we use for purpose B (RescueMetrics BioPerformance-owned models), not third-party AI products.
- Legal requests: we disclose information in response to a subpoena, court order, or other legal demand only when legally required, and only what is required. Where the law allows, we first notify the organization responsible for your program (your agency, union, or research group) so it can object. We may also disclose information when needed to prevent serious harm to someone's safety.
We do not sell customer data. We do not market, sell, or license API-obtained wearable data to third parties. Under the Oura API Agreement, we do not redistribute Oura user data to third parties except as that agreement and user consent allow.
No third-party AI (purpose D — not used)
We do not send wearable API payloads, duty-joined physiology, or other personal data to external generative AI or third-party machine-learning platforms (for example consumer LLM APIs) for training or inference. Consistent with Garmin Connect Developer Program and similar partner requirements: we do not share API-obtained data with external AI or data-processing services. Any model improvement under purpose B is limited to RescueMetrics BioPerformance-controlled systems and partner-allowed fields.
Department stewardship. Authorized agency staff should not paste firefighter wearable metrics, duty-joined physiology, exports, or Command Post screens into public or consumer generative AI tools (for example ChatGPT, Copilot, or Gemini). Treat those tools as outside the RescueMetrics BioPerformance tenant boundary. Departments remain responsible for their own acceptable-use rules; this Policy states how we process data inside the Services.
6. Retention
We retain account, sync, and related records for as long as your organization maintains an active deployment or as needed for security, backups, dispute resolution, legal compliance, and (where consented) model-improvement and research purposes described in §4. Access audit records are kept with other security logs for the organization. Agencies may request export or deletion of their tenant data subject to technical and legal limits. Wearable connections can be disconnected; tokens are encrypted at rest.
7. Security
We use industry-standard controls appropriate to our Services, including TLS for data in transit, encryption for sensitive tokens and storage (including Azure AES-256 for platform storage), role-based access, organization-level data isolation, multi-factor authentication for Command Post and Shift Pulse logins (except designated demo environments), and short-lived web sessions (about two hours). No method of transmission or storage is 100% secure.
We keep an access audit of when authorized agency or platform staff open a fire fighter / participant record (actor, organization, participant, action, time, and IP address). This is for security and program accountability. Designated demo organizations may be excluded from that log.
8. Your choices and rights
- Access or update profile information through the Services where available
- Disconnect wearable providers in Shift Pulse (Profile → Wearable), via your agency admin, or in the wearable company's own app — disconnect stops new sync; request deletion under this Policy if you want stored metrics removed
- Withdraw research / Lab participation through Shift Pulse (Profile) or your agency admin — operate dashboards and wearable sync continue unless you disconnect or request deletion
- Request deletion or export via your agency admin or by emailing mike@rescuemetricsbio.com
- Opt out of non-essential communications we control
Those choices are how individual sovereignty is exercised in the product. Depending on your location, you may have additional rights under applicable privacy laws. Contact us to exercise them. We will not discriminate against you for exercising rights we are legally required to honor.
9. Children
The Services are intended for adult fire fighters, EMS personnel, researchers, and agency staff. We do not knowingly collect personal information from children under 13 (or under 16 where a higher age applies). If you believe a child has provided data, contact us and we will take appropriate steps.
10. International transfers
We primarily host the Services in the United States (including Microsoft Azure regions we configure). If you access the Services from elsewhere, your information may be processed in the U.S.
11. Changes
We may update this Policy from time to time. We will post the revised version at this URL with an updated effective date. Continued use of the Services after changes means you accept the updated Policy. Material changes to Shift Pulse terms may also require accepting a new terms version in the app.
12. Contact
Questions or requests: mike@rescuemetricsbio.com
RescueMetrics BioPerformance, LLC
© 2026 RescueMetrics BioPerformance. All rights reserved. RescueMetrics™ is a trademark of RescueMetrics BioPerformance, LLC. WHOOP, Oura, Polar, Garmin, CrewSense, TeleStaff, First Due, Stationwise, ESO, ImageTrend, and other product names and logos are trademarks of their respective owners. Their appearance on RescueMetrics BioPerformance or Shift Pulse does not mean those companies endorse, sponsor, or are affiliated with RescueMetrics BioPerformance unless we say so in writing.

