Last updated: 28 August 2026
Core PACEme Care data
Daily check-ins, heart-rate records, HRV, steps, sleep, Pace Points, suggestions, Care Log entries and settings are stored locally on the Android device by default. They are not automatically uploaded to a PACEme account or server.
Optional AI Pacing Coach
The AI Coach is off until you configure a provider and request an analysis. When you use it, PACEme sends a bounded recent pacing summary and your message directly to the AI provider you selected. Depending on what is available, that summary can include recent check-in answers, heart rate recorded by PACEme, and sleep, steps and HRV read from Health Connect. The provider's own privacy and retention terms apply.
PACEme does not send this information merely because an API key is saved. The app shows a notice before first use. You can use the core pacing features without the AI Coach.
Optional weather and location
Weather is off by default. If you enable it, PACEme sends either an approximate device coordinate or the place you search for to Open-Meteo to retrieve a forecast. Raw device location is not stored; a manually selected place remains on your device until weather is turned off.
On Android 11 and earlier, Android also requires Location permission to scan for Bluetooth heart-rate monitors. PACEme does not use Bluetooth scan results to determine your location.
Research Feed and Research key
The public feed, Daily Summaries and available individual article summaries can be viewed without an account. A free Research key is required only to save articles, sync read/saved state across devices, or request generation when an individual summary is not yet available.
The service stores the email used to issue the key, the key record, verification codes while active, and the identifiers of articles marked read or saved. It does not receive your Care check-ins or pacing history through the Research Feed.
Website forms and early access
The Android beta form asks for the email connected to your Google Play account and your agreement to be contacted about testing. PACEme stores that email, the consent time, waitlist status and email-delivery status in Firebase so an application is not lost if a notification fails. It is used only to manage beta invitations and testing correspondence.
Waitlist, support, bug, feedback and case-study forms send the email address and information you choose to enter to PACEme. Email delivery is handled through Brevo. Beta waitlist records are retained until the beta programme ends or you ask for deletion. Please do not include health information that is not needed for your request.
App support diagnostics
The Android app keeps a bounded diagnostic event log on the device to help explain calculation, suggestion and app-workflow problems. The full log is not uploaded automatically and can be viewed, exported or cleared from App Settings.
When using Report a Problem, you can separately choose to include a smaller filtered technical extract. The preview identifies what will be sent. The extract excludes raw heart-rate history, notes, AI conversations, credentials, web addresses, location, Patrick-only private-sync events and detailed engine trace. Nothing is attached unless you select the option and submit the form.
Firebase Crashlytics automatic collection is disabled. After an unexpected app close, a technical crash report is held locally until PACEme asks whether to send it to Firebase or delete it. This separate report contains app/device details and the crash stack trace, not PACEme's diagnostic log, check-ins, notes or heart-rate history. The Android app does not include Firebase Analytics.
Hosting and browser storage
The website and feed backend use Google Cloud and Firebase. Their infrastructure may process ordinary technical records such as IP address, request time, device/browser information and server logs for delivery, security and fault diagnosis.
PACEme does not currently use advertising or analytics cookies. If you link a Research key, the site stores it in this browser's local storage so you remain signed in. Choosing Logout removes that local copy.
Exports, source links and retention
PDF and structured ZIP exports remain on your device until you choose where to share them. ZIP exports are not encrypted. Opening a research source takes you to the source website, whose own privacy terms apply.
Local app records remain until you delete them, clear app storage or uninstall the app. Server records are retained for the feature and support purpose for which they were supplied, subject to operational, security and legal needs.
Questions or requests
Use the support form to ask what PACEme holds about your Research key or website submissions, or to request correction or deletion where applicable.
Contact PACEme Support