Privacy
FlowState pages are static HTML. This policy describes typical data flows if you host them yourself or embed third-party analytics — written for transparency, not legal advice.
What this site collects by default
The files themselves do not require accounts or form submissions. Your browser still sends standard HTTP data (IP address, user agent, referrer) to whatever server hosts the files.
| Data type | Source | Typical use |
|---|---|---|
| Server logs | Web host | Security and uptime |
| CDN metrics | Optional CDN | Latency and cache stats |
| No FlowState database | N/A | This bundle has no backend |
Example — cookie categories counted for disclosure table
Input: essential = 1, analytics = 1, marketing = 0
Calculation: total disclosed categories = 1 + 1 + 0 = 2
Output: "Policy lists 2 active cookie categories"
Input: essential = 1, analytics = 1, marketing = 0
Calculation: total disclosed categories = 1 + 1 + 0 = 2
Output: "Policy lists 2 active cookie categories"
Cookies and local storage
- First-party cookies: only if you add them (for example session on a separate app).
- Analytics cookies: if you embed a provider, follow that vendor’s consent rules.
- Local storage: these HTML files do not write local storage unless you extend them.
Marketing line: “Straightforward static privacy story — easy compliance copy blocks.”
Basic analytics explanation
Common analytics measure page views, session duration, and traffic sources at aggregate level. They generally do not need to know your habit numbers unless you send custom events — avoid sending personal productivity notes to analytics endpoints.