Effective date: August 14, 2026

DayFlow is a browser extension that replaces the new-tab page with a personal Kanban task board, clock, and local weather display. This policy explains what information DayFlow handles and why.



Task titles, priorities, column positions, appearance preferences, and cached weather results are stored locally in the browser using chrome.storage.local (or equivalent browser extension storage). A background image selected by the user is optimized and stored locally as a Blob using IndexedDB. This information is used only to provide DayFlow's task-board and appearance functionality and synchronize DayFlow tabs in the same browser profile.

DayFlow does not transmit task content, appearance preferences, or uploaded background images to the developer or to third parties.


If the user chooses Enable weather in DayFlow's consent prompt, DayFlow contacts one of the following IP-based geolocation services:

• ipwho.is
• get.geojs.io

These services receive the network information needed to process the request, including the user's IP address, and return an approximate city, latitude, and longitude. DayFlow then sends the approximate latitude and longitude to api.open-meteo.com to retrieve current temperature and weather conditions.

DayFlow does not make these requests before the user enables weather. The user's choice is saved locally in browser extension storage and can be changed later from the weather control. On Firefox, enabling weather also requests the browser's optional location-information data permission. Disabling weather stops future weather requests, removes that optional Firefox permission, and deletes the locally cached city and weather result. If weather is enabled, weather data is refreshed when the local cache is older than approximately 30 minutes and periodically while a DayFlow tab remains open.

This information is used exclusively to provide the visible weather feature. DayFlow does not use it for advertising, analytics, profiling, or tracking.


Weather functionality depends on these independent services:

• ipwho.is
• GeoJS
• Open-Meteo

Their handling of requests is governed by their own terms and privacy practices. The DayFlow developer does not operate these services or receive the location and weather requests sent to them.


DayFlow does not:

• Require an account or login.
• Collect names, email addresses, payment details, or authentication credentials.
• Read or transmit browsing history, visited URLs, page content, bookmarks, or cookies.
• Transmit task content.
• Upload user-selected background images to a server.
• Use analytics, advertising, tracking pixels, or profiling.
• Sell user information.

DayFlow requests only the permissions needed for its current features:

• Storage: saves tasks, appearance preferences, uploaded background images, and cached weather information in the browser.
• Access to ipwho.is and get.geojs.io: obtains an approximate location for the weather display.
• Access to api.open-meteo.com: retrieves current weather for that approximate location.
• Optional location information (Firefox): allows DayFlow to transmit approximate location information only after the user enables weather; the permission is removed when weather is turned off.

Tasks remain in browser extension storage until the user deletes them, clears the extension's stored data, or removes the extension. Appearance preferences remain until they are reset, the extension's stored data is cleared, or the extension is removed. An uploaded background remains in IndexedDB until the user selects Use default, clears the extension's stored data, or removes the extension. Cached weather information remains locally stored until it is replaced by a newer result, the extension's stored data is cleared, or the extension is removed.

DayFlow does not maintain a developer-operated server or remote database containing this information, so the developer has no remotely stored DayFlow user data to retrieve or delete.


All external weather and approximate-location requests use HTTPS. Task information is not sent over the network. Browser extension storage is managed by the browser and may not be encrypted on the user's device.


DayFlow is a general-purpose productivity tool and is not directed specifically to children. It does not knowingly collect personal information from children.


This policy may be updated if DayFlow's features or data practices change. Material changes will be disclosed before the updated practices take effect, as required by applicable browser-store policies.


Questions or privacy concerns can be submitted through the DayFlow GitHub Issues page.