Privacy Policy

Effective: 2026-09-27 · Last updated: 2026-09-27 · Version 1.2

Flowboard is operated by TG11 LLC, doing business as VulpFin. This page says what the service stores, why, who else can see it and how to get rid of it. There is no advertising here and nothing is sold to anyone.

1. What we store

• Account: email address, username, display name, and either a password hash or a link to your TG11 account. Never a password in the clear.
• Preferences: timezone, working hours and day length, board defaults, and the model you picked as your default.
• Your work: boards, tasks, estimates, notes, reflections, activity history, invitations and membership.
• AI provider credentials, if you add them: encrypted with AES-256-GCM under a key held by the server, bound to your account and the provider. They are decrypted only to make a request you asked for, and never shown back to you in full.
• Calendar connections, if you make them: the account label available from the provider, the calendar you chose, and OAuth tokens — stored encrypted the same way — plus a 15-minute cache of busy time intervals so the planner does not re-fetch them constantly.
• AI usage records (model, token counts, cost estimate, timestamps) so you can see what the assistant cost you. You can turn this off in settings.
• Operational data: IP address, user agent, and server logs of requests and errors.
• Support messages you send us, with the version and page you sent them from.

2. What leaves the server

This is the part worth reading carefully.

• AI providers. When you use the assistant, the board content that request needs — task titles, notes, estimates and dates — is sent to the provider you chose (OpenAI, Anthropic, Google, Groq, OpenRouter, or whichever you configured), using your key. What they do with it is governed by their policy, not ours. If that is not acceptable for a piece of work, do not run the assistant on it.
• Calendars. When you push a task, its title, notes, and time are sent to Google or Microsoft as an event. Calendar lists and busy-time intervals come back the other way.
• Email. Digests, invitations and password mail go out through our mail provider.
• TG11 Accounts. Signing in with TG11 exchanges an identity token; Flowboard never sees your TG11 password, and no other TG11 service can read this one's database.
• Calendar feed links. An .ics feed URL contains a secret token: anyone who has the link can read that board's dated tasks. Rotate or revoke it in board settings.

Nothing else is shared, except where the law requires it or to protect the service and its users.

3. Google Calendar and Google API Services

Google Calendar is optional. Flowboard accesses Google Calendar data only after you choose to connect Google Calendar and only to provide the calendar features you request.

Google user data we access

Flowboard requests https://www.googleapis.com/auth/calendar.readonly to identify calendars you can access and retrieve busy time ranges. It requests https://www.googleapis.com/auth/calendar.events to create, update, or delete a Google Calendar event when you explicitly perform that action from a Flowboard task. Flowboard receives calendar-list metadata (including calendar names and identifiers), busy interval start and end times, and OAuth access and refresh tokens. It does not import Google Calendar event titles, attendees, descriptions, or other event content as Flowboard tasks.

How Flowboard uses Google user data

Flowboard uses this data only to let you choose a calendar, show availability, avoid scheduling work over busy time, and perform the create, update, or delete action you explicitly requested. Flowboard does not use Google user data for advertising, profiling, credit decisions, data brokerage, surveillance, or any unrelated purpose.

Sharing, transfer, and disclosure of Google user data

Flowboard does not sell, rent, or share raw Google Calendar data with third parties. It does not send Google Calendar event titles, attendees, descriptions, calendar identifiers, or OAuth tokens to AI providers. When you explicitly ask Flowboard's assistant to schedule work, Flowboard may send the AI provider you selected with your own credential derived daily busy-minute totals solely to provide that requested scheduling feature. Those totals do not include event content, calendar identifiers, or OAuth credentials. Google user data may also be disclosed if required by law or necessary to protect the service and its users.

Storage, retention, and deletion

Flowboard stores the selected calendar list and caches busy time intervals for up to 15 minutes. Google access and refresh tokens remain only while the connection exists and are encrypted at rest. Disconnecting deletes Flowboard's local connection, tokens, availability cache, and event links, and makes a best-effort request to revoke the Google credential. Disconnecting does not delete events that already exist in Google Calendar.

Flowboard does not use Google Workspace API data, whether raw or derived, to develop, improve, or train generalized or foundation AI or machine-learning models.

The use of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. Cookies

One signed session cookie to keep you logged in, and a CSRF token to stop other sites acting as you. That is the lot — no advertising or analytics cookies. Your browser may also keep small local preferences, like a collapsed column.

5. Who can see your work

Your boards are private to you and to the people you invite, at the role you gave them. Operators of this server can technically reach the database — that is true of every hosted service — and we look only when it is needed to fix a fault or answer a support request you raised.

6. How long we keep it

• Boards, tasks and account data: while the account exists.
• Server and access logs: a short operational window, then rotated away.
• Backups: on a rolling schedule, so deleted content can persist in a backup for a short time after it disappears from the live service.
• AI usage records: until you clear them or the account is deleted.
• Support email: kept with the correspondence it belongs to.

7. Deleting things

• Tasks, boards, reflections, AI credentials and calendar connections can all be deleted from inside the app, and deleting a connection deletes its stored tokens.
• There is no self-serve "delete my account" button yet. Ask through support and we will delete the account and its boards within 30 days, backups ageing out on their own schedule after that.
• Ask the same way for a copy of your data and we will send you an export.

8. Security

Passwords are hashed, sessions are signed, provider credentials and calendar tokens are encrypted at rest, and the service is served over HTTPS. Tokens are never written to logs. No service can promise perfect security, and we will not pretend otherwise — if something does go wrong in a way that affects you, we will tell you.

9. Children

Flowboard is not intended for anyone below the minimum age for digital consent where they live.

10. Where it runs

Flowboard runs on servers in the United States. If you use it from elsewhere, your data is processed there.

11. Changes

The version and date at the top change when this policy does; material changes are called out in the changelog.

12. Contact

Privacy questions, export requests and deletion requests: [email protected].