Legal

Privacy Policy

Last updated: August 1, 2026

This policy describes what information PulseForm collects across the PulseForm iOS app and the PulseForm Web Portal, how that information is stored, and the controls available to you. PulseForm is a training and simulation platform for medical instruction — it is not for clinical or diagnostic use, and it is not directed at children.

Accounts and sign-in

The PulseForm app uses Sign in with Apple. The PulseForm Portal supports Sign in with Apple and Google Sign-In. Both use Firebase Authentication (a Google Cloud service) to manage your session. PulseForm stores the identity information your sign-in provider gives it — a stable account ID, and an email address or display name if the provider supplies one. PulseForm does not collect or store passwords.

Training content and Performance History

Lanes (training scenarios you author), Vitals Presets, and folders are stored locally on your device by default. Completed training sessions ("LaneRuns") and their Timeline event records are also local-only by default.

If you turn on Performance History (also called Platform Participation in-app), completed LaneRuns and their Timeline events are additionally saved to a private, per-user location in Cloud Firestore. This data is scoped to your account — Firestore Security Rules restrict it to you alone, and PulseForm does not analyze, aggregate, or share it.

Separately, if you turn on Cloud Sync (Optional Cloud Backup), your authored Lanes, Vitals Presets, and folders are backed up to a private, per-user location in Cloud Firestore so they can be restored on another device. This is a separate setting from Performance History — turning one on does not turn on the other.

Organization and Small Group data

If you join a PulseForm Organization (for example, through the SG Tracker feature), your role, small-group assignment, and related roster fields are stored in Cloud Firestore, scoped to that organization. This data is visible to that organization's administrators and instructors as needed to run the program, and is managed through the PulseForm Portal.

What PulseForm does not collect

PulseForm does not use analytics, advertising, or crash-reporting SDKs of any kind, and does not sell or share your data with advertisers or data brokers. The only outside services involved are described below.

How data is stored and secured

Cloud data is stored in Cloud Firestore (Google Cloud infrastructure) under the same Firebase project used for authentication. Firestore Security Rules enforce that your private training records are readable only by you, and that organization data is readable only by members of that organization with the appropriate role.

Data retention

PulseForm does not automatically delete or expire your data on a schedule. Local data remains on your device until you remove it or uninstall the app. Cloud data you have opted into remains stored until you remove it yourself in-app, or until a deletion request you submit is processed — see Account Deletion for exactly what each control does.

Your choices and controls

  • Turn off Performance History at any time — this stops future syncing; records already saved to Firestore are not deleted by this action alone.
  • Turn off Cloud Sync at any time — this stops future backups; a backup already saved to Firestore is not deleted by this action alone.
  • Delete a single completed training record from Command's Recent Runs.
  • Delete your Cloud Backup entirely.
  • Sign out, which ends your session on that device only.
  • Request full account deletion — see Account Deletion.

Third-party services

PulseForm relies on: Firebase (Google) for authentication and cloud data storage; Apple for Sign in with Apple; and Google for Google Sign-In on the Portal. Each provider's own privacy policy governs the identity data it passes to PulseForm during sign-in.

Children's privacy

PulseForm is built for licensed and trainee medical personnel and is not directed at, or knowingly used by, children.

Changes to this policy

If this policy changes, the updated version will be posted at this same URL with a revised "Last updated" date.

Contact

Questions about this policy or your data can be sent to .