No accounts or logins
Launch a breathing session immediately. We do not collect names, email addresses, or any authentication data.
Privacy commitment
Your privacy comes first
Remember to Breathe is designed to work without accounts. It uses local storage for your practice history and Google Analytics for usage measurement. This page outlines the information we process, the rare cases where we store data, and how to contact us with questions.
What we collect (and what we do not)
The app focuses on quick relaxation, so the only insights we gather are aggregated usage trends that help us improve the breathing experiences. Each commitment below is active today—not planned or future work.
Minimal analytics only
Google Analytics 4 runs with privacy-conscious defaults so we can understand general usage trends such as popular techniques and device types.
Everything runs in your browser
Breathing visuals, timers, and language settings execute locally so you keep control of your data.
Local storage usage
The breathing app keeps preferences on your device so you can pick up where you left off. Clearing your browser data will remove these items immediately.
- Language preference
- Stored in localStorage under the key "breathing-app-language" so the app opens in your preferred language.
- Practice preferences and history
- Your last technique, duration, and up to 100 completed practices are stored on this device under breathing-app-practice-v1. Records include completion time and practice duration. They are not synced across devices. Clearing browser site data removes them.
Analytics details
We monitor high-level trends so we know which breathing patterns are helpful and which devices to optimise for. Practice events are linked by a random practice identifier so we can measure completion rates.
Google Analytics 4 (gtag.js)
Google receives page views and practice events (start, completion, or early stop), including technique, duration, entry page, and a random practice identifier. GA4 may use cookies and device identifiers. We do not send names, email addresses, or the full locally stored practice history. Advertising personalization and Google signals are disabled in our tag configuration.
Need to reach us?
Have a privacy question or spotted an issue? Open a discussion in our GitHub repository and we will follow up quickly. You can also request additional details about how we handle analytics events.