←   Back to FlowWell
PRIVACY, IN PLAIN LANGUAGE

Your day is yours.
Here’s what the code shows.

This overview is based on the FlowWell extension manifest and implementation reviewed on October 22, 2026. Items marked “Needs confirmation” require the publisher’s input before this is a complete policy.

IN SHORT

FlowWell saves planner records in browser storage and uses Chrome alarms and notifications for reminders. The code reviewed does not show app-initiated requests to an external service.

01

Information FlowWell stores

FlowWell stores preferences in Chrome local storage under flowwell.preferences. Planner data—including routine details, scheduled and completed occurrences, and focus sessions—is stored in a browser IndexedDB database named flowwell.

Routine records may include a title, category, optional notes, selected days and time, time zone, duration for movement or meditation, and completion state. Focus records include the task name, session times, and duration. These are fields used by the extension code; they are not sent to an account service in the code reviewed.

02

Where the data goes

We found no app-initiated fetch, XMLHttpRequest, WebSocket, or beacon calls in the extension source reviewed. The storage and reminder implementation uses Chrome local storage, IndexedDB, Chrome alarms, and Chrome notifications.

The marketing website loads fonts from Google Fonts and includes Vercel Web Analytics for page-view statistics. This is separate from the extension and does not send planner records. Vercel describes its analytics as aggregated and says it may process the page URL, referrer, filtered query parameters, approximate geolocation, and browser, operating system, and device details. Review Vercel’s Web Analytics privacy details and confirm this disclosure meets your policy requirements.

03

Permissions

  • storage: saves FlowWell preferences in Chrome local storage.
  • alarms: schedules routine reminders and focus-session timing.
  • notifications: displays reminder and focus completion notifications.
  • activeTab (optional): declared as an optional permission in the manifest; we did not find use of it in the implementation reviewed.

The content script is configured for HTTP and HTTPS pages. It can display the floating notch on those pages, read FlowWell state through the extension messaging layer, and is suppressed for domains the user has hidden. The code excludes Chrome extension pages.

04

Your controls

FlowWell settings let you hide the notch, choose its position, and list domains where it should not appear. The implementation also includes a delete-all-data action that clears routine, occurrence, and focus records and scheduled alarms and notifications.

05

Retention and contact

Needs confirmation: The reviewed code does not specify a data retention period or explain whether removing the extension removes all extension data under every Chrome configuration. Confirm the deletion behavior and retention language you want to publish.

Needs confirmation: Add the legal publisher or data controller name, a working privacy contact, and any applicable jurisdiction-specific details.

Privacy contact: [Add a privacy email or contact link]

06

Policy details to confirm

Before publication, confirm whether any analytics beyond Vercel Web Analytics on the marketing website, crash reporting, customer support, or third-party services operate; identify the publisher and contact method; and set the policy’s effective date.

This is a code-based overview, not a legal determination. Last reviewed: October 22, 2026.

Questions about FlowWell?Visit Support ↗