Keep focus data close to the user.
FlowQuest is designed so focus sessions can work without turning task content into a surveillance feed. Optional account features should add sync, not change ownership.
Trust boundary
FlowQuest is built around visible progress, not hidden monitoring. Here is how the marketing site and product direction treat privacy.
Trust principles
Team focus works when the system clarifies presence, ownership, and recovery without collecting more context than the loop needs.
FlowQuest is designed so focus sessions can work without turning task content into a surveillance feed. Optional account features should add sync, not change ownership.
This marketing repo does not include screen recording, keystroke logging, or employee-monitoring scripts. Team focus should create presence, not a manager dashboard.
When sync or paid account features are used, the user should understand what leaves the device and why. Offline-friendly workflows remain part of the product promise.
The site only loads Google Analytics when a measurement ID is configured, and CTA events are scoped to page and destination context.
Questions
These answers describe the marketing repo and the product stance. Legal policy pages remain the source of truth for rights and deletion paths.
FlowQuest should not need document names, browser tabs, screen content, or keystrokes to run a focus session. The marketing site does not collect that content.
This marketing repo contains no screen capture, keystroke logging, or session-recording code. FlowQuest is positioned as a timer and RPG progress layer, not surveillance software.
Only if NEXT_PUBLIC_GA_MEASUREMENT_ID is configured for the deployment. Without that environment variable, the analytics script is not loaded.
Account deletion should remove account-scoped data according to the current legal policy and product controls. Local-only browser data can be removed from the device by clearing site data.
The legal policy pages are the source of truth for rights, exports, and deletion requests. For privacy questions, contact privacy@flowquest.io.
The product direction is offline-friendly focus sessions. Any cloud sync should be additive and explicit rather than required for the core timer loop.
The product stance is that focus data belongs to the user. Legal policy and account controls should make export and deletion paths clear.
FlowQuest should not sell focus session content. The business model presented on this site is Free plus Pro subscriptions.
For the legal details, see the Privacy Policy and Terms of Service.
Start with one session and keep the product boundary clear.