Privacy Policy
Last updated: December 2025
Quick Summary
FlowClock stores your timer data locally on your device only. We don't collect, transmit, or share any personal information.
Information We Collect
FlowClock collects and stores the following data locally on your device:
- Timer Sessions: Start times, durations, and session types (focus/break)
- Daily Summaries: Aggregated focus and break time totals by date
- Settings: Your preferences for notifications, custom presets, and sound settings
- Current Session State: Active timer information to maintain continuity
How We Use Your Information
Your data is used exclusively to:
- Track your focus sessions and break times
- Display daily productivity summaries
- Maintain timer state across browser sessions
- Remember your custom settings and preferences
- Send break completion notifications
Data Storage and Security
- Local Storage Only: All data is stored locally in your Chrome browser
- No Cloud Sync: Your data never leaves your device
- No External Servers: FlowClock doesn't communicate with any external servers
- Device-Specific: Data is tied to your specific browser installation
Data Sharing
We do not share, sell, or transmit your data to any third parties. Since all data remains on your device, there is no data sharing involved.
Permissions Explained
FlowClock requests the following Chrome permissions:
- Storage: To save your timer data and settings locally
- Notifications: To alert you when break timers complete
- Alarms: To manage background timers when the popup is closed
Data Control
You have complete control over your data:
- Clear Data: Use the "Clear All Data" button in Settings
- Uninstall: Removing the extension automatically deletes all data
- Browser Reset: Clearing Chrome's extension data removes FlowClock data
Contact
Questions about this privacy policy can be directed through the support page or Chrome Web Store developer contact information.
Compliance
This privacy policy complies with Chrome Web Store Developer Program Policies, GDPR principles, and CCPA requirements.