TaskFlow Privacy
This page describes the account, workspace, browser, and service data involved when using TaskFlow. TaskFlow is maintained by Pratik Dhandare (Code2WithPratik).
Information stored by TaskFlow
When you register, TaskFlow stores the name and email address you provide and a bcrypt password hash; the application does not store your password in plain text. When you use the service, it stores workspace information you submit, such as project names and descriptions, task details, assignments, due dates, comments, notifications, and project membership. The API stores this application data in its configured PostgreSQL database.
If a project administrator connects GitHub, TaskFlow stores installation and repository-link information needed for that integration. Depending on the features used, the application reads repository metadata, issues, pull requests, and check status from GitHub to connect engineering work to tasks.
Authentication and browser storage
TaskFlow keeps the short-lived access token in application memory in the browser. The refresh token is sent in an HttpOnly cookie scoped to the authentication routes. In production the cookie is Secure and uses SameSite=None for the separate frontend and API origins; local development uses SameSite=Lax. Logging out revokes the active refresh token and clears the cookie. The light or dark theme preference is stored in browser local storage under the taskflow-theme key.
Hosting, analytics, and integrations
The published deployment guide configures Vercel for the frontend and Render for the NestJS API and PostgreSQL database. The operator may change hosting providers or deployment settings. The frontend includes Vercel Web Analytics and Speed Insights to measure site activity and performance. Vercel processes data under its own privacy terms; review Vercel's privacy policy for details.
When you choose to connect GitHub, GitHub processes authentication and repository access under GitHub's terms and privacy statement. TaskFlow's GitHub integration is optional and project members should only connect repositories they are authorized to use.
Retention and requests
TaskFlow does not currently publish a fixed data-retention schedule or provide self-service account deletion. To ask about account data, access, correction, or deletion, contact the maintainer using the method on the Contact page. A request may need enough information to identify the account, but do not send passwords, tokens, or other authentication secrets.
Updates to this notice
This notice describes the application's current behavior and configured integrations, not a promise that every deployment uses the same infrastructure. If the data collected or service providers change, this page should be updated to reflect those changes.