Cookies should solve a product problem, not create a trust problem.
TaskFlow uses a small set of cookies to make the web app usable. If a cookie is there, it should have a concrete job: keep you signed in, keep your app state stable, or preserve context you would reasonably expect us to remember.
A cookie is a small piece of browser data tied to your use of the site.
Cookies can be essential, functional, or optional depending on what they do. TaskFlow keeps that footprint intentionally small.
This Cookies Policy explains the cookies used by the TaskFlow website and web app today. If our cookie usage changes in a meaningful way, we will update this page.
Current cookie use is centered on sessions and notes.
Essential session behavior
TaskFlow uses a session cookie so authenticated parts of the app know which signed-in user is making a request.
Notes context memory
The app stores the last note you opened and a scope-based note map so the notes view can restore where you left off.
HttpOnly protection
The note-context cookies set by the app are marked HttpOnly and SameSite=Lax, which helps reduce casual client-side access and some cross-site risks.
No ad cookie stack today
TaskFlow is not currently presented as using cross-site advertising cookies, social ad retargeting pixels, or third-party behavioral ad trackers.
Here are the product cookies we can describe clearly today.
| Name | Purpose | Type | How long it lasts |
|---|---|---|---|
|
Flask session cookie |
Keeps authenticated requests tied to your signed-in account so protected app pages can work. | Essential | Usually until you sign out or the browser session ends, depending on browser behavior and session settings. |
| Remembers the most recent note you opened so TaskFlow can restore note context when you come back. | Functional | 30 days | |
| Stores a small scope-to-note map so the notes area can remember the last opened note for different views. | Functional | 30 days |
Some third-party features may involve their own cookies or storage rules.
If you choose a third-party sign-in method, such as Google sign-in, that provider may use its own cookies or browser storage as part of its authentication flow. Those providers control their own cookies and policies.
If TaskFlow adds analytics, measurements, or other optional cookie categories later, we will update this page and any consent flow that is legally required before relying on them.
You can control cookies from your browser, but some product behavior depends on them.
- You can delete TaskFlow cookies through your browser settings at any time.
- You can block cookies entirely, but that may prevent sign-in sessions from working correctly.
- If you remove the note-context cookies, the app may stop remembering the note you last opened or the notes scope you were using.
- If you use a shared device, signing out when you are done is still the safest habit.
If our cookie use changes, this page should change with it.
We will update this Cookies Policy when TaskFlow adds, removes, or materially changes how cookies are used.
If you have questions about cookies or browser storage in TaskFlow, email hello@taskflow.io and include "Cookies" in the subject line.
Related pages
If you are looking for the rest of the legal and trust information, start here.