1
Local-first by design
The app stores its settings and session history on the device so an interrupted resuscitation can be resumed and recent sessions can be reopened later.
Privacy policy
Your CPR timeline stays with the care team.
CPR Logger is a local-first bedside tool for logging resuscitation events. The app does not require user accounts, does not include analytics or advertising SDKs, and does not send CPR session data to the developer.
- 0accounts required
- Localsession storage
- Usercontrolled sharing
This page applies to the current CPR Logger app configuration in this project and is effective as of June 24, 2026.
Overview
CPR Logger is designed to help clinicians capture a resuscitation timeline quickly and clearly. Privacy follows the same principle: keep data close to the bedside and under the team's control.
2
No built-in tracking
This version of CPR Logger does not contain sign-in, advertising, analytics, or a backend service that receives your CPR session data.
3
You control exports
Reports are created locally as PDF files. Data leaves the app only when you intentionally share or move a file using your device's own tools.
What CPR Logger stores on your device
To support the clinical workflow, the app keeps certain information locally on the device. That storage may include personal or patient-related information if you choose to enter it.
App preferences
The app stores a small set of configuration values needed for daily use.
- Language selection.
- Reminder settings such as the adrenaline interval.
- UI preference for whether the start disclaimer is shown.
Active and recent sessions
The app keeps the current session plus up to 20 recent completed sessions so work can be resumed or reviewed on-device.
- Session timing such as start time, end time, and rhythm-check timers.
- Timeline events including rhythms, shocks, medications, interventions, and notes.
- Post-ROSC assessment fields such as ABCDE entries, vitals, and free text.
Exported PDF reports
When you export a report, CPR Logger creates the PDF locally on the device.
- Generation is local and does not require sending the report to us.
- Stored files may remain in the app's local documents area until removed.
- Shared copies may also exist in other apps or destinations you choose.
Device backups
CPR Logger itself does not upload your session data to the developer. However, operating system backup features may copy locally stored app data depending on your device settings.
- Apple or Google backup services may include app data if enabled on the device.
- We do not operate or receive those backups ourselves.
- Backup behavior can vary based on platform, device policy, and account settings.
Important: CPR Logger does not ask for patient identity fields, but free-text
notes and exported reports can still contain sensitive information if users choose to enter it.
Permissions and device behavior
The current mobile app configuration keeps permissions narrow and focused on the resuscitation workflow.
A
No camera or location access
The current app configuration does not request runtime access to camera, microphone, location, contacts, or photo-library style personal data permissions.
B
Screen stays visible in active use
During a live session, the app may keep the screen awake and temporarily increase app brightness so the timeline remains readable under pressure.
C
Preview and export are local
PDF preview uses local files on the device, and export functions are designed to run without transmitting data to the developer.
Retention, deletion, and security
Because the app is local-first, day-to-day privacy also depends on how the device itself is protected.
Retention
- Active session data remains on-device until the session is completed or discarded.
- Recent sessions remain locally available until deleted, with the list capped at 20 items.
- Exported PDFs may remain on the device or in chosen destinations until removed there.
Deletion and security
- In-app deletion can remove active or recent session data stored by the app.
- Shared copies must be deleted from the destination app or storage service separately.
- Device safeguards such as passcodes, MDM controls, and encrypted backups remain important.
Changes and contact
This privacy policy may be updated as CPR Logger changes. The version published on this page should be treated as the current policy for the corresponding release.
Questions about privacy
If you have questions about this policy or want to report a privacy concern, contact:
Policy scope
This page describes the app behavior visible in the current CPR Logger project as of June 24, 2026, including on-device storage, PDF export, and manual sharing behavior.