Brain-Based Workplace, LLC ("we," "us," or "our") operates Flow State (available at myflowstate.ai). This Privacy Policy explains how we collect, use, store, and protect your personal information when you use our service.
By using Flow State, you agree to the collection and use of information in accordance with this policy.
1. Information We Collect
Account Information
When you create an account, we collect your email address and an encrypted password. If you sign up via a third-party provider, we receive the profile information that provider shares, such as your name and email.
Task and Productivity Data
Flow State stores the content you create within the app, including:
Tasks, next actions, and their priorities
Weekly priorities and progress tracking
Projects and project information
Context Library items and folders
Notes and other user-generated content
Meeting recordings you make with Flow State — the transcript, notes, summaries, and any actions extracted from them
AI Chat Messages
When you use the AI Coach, Plan My Week, Plan My Day, or other AI-powered features, we collect the messages you send and the responses generated. These messages are used to provide the service and to build your personal memory and pattern analysis.
We may review AI chat conversations to evaluate the quality of AI responses and improve the service. Flow State is run by a single founder, and this review is conducted only internally by us; conversation content is never shared externally or used for advertising.
Memories and Patterns
Flow State analyzes your usage patterns to provide personalized coaching insights. This includes patterns about your work habits, preferences, and productivity trends. These memories are stored in your account and are only accessible to you.
Google Account Data (Calendar, Gmail, Drive, and Docs)
If you choose to connect your Google account, Flow State requests access to the Google services below. Each one powers a specific in-app feature, and we request only the access those features need. When you disconnect Google from Settings, we request that Google revoke Flow State's access. You can also review or revoke access directly at any time from your Google Account permissions page.
Google Calendar (read and write) — we read your events, including titles, times, attendees, and metadata, to show your schedule, find free time, and detect conflicts, and we create or update events when you ask Flow State to schedule something.
Gmail (read, compose, and send) — if you turn on email features, we read recent messages and threads to help you track items you are waiting on and surface emails that may need a reply, and we draft and, only when you choose to send, send follow-up replies on your behalf. We read message content solely to provide these features.
Google Drive (read-only) — when you prompt the AI chat to do so, it will search your recent Drive files and read the contents of documents you reference so the AI can use them as context when helping with a related task.
Google Drive (app files) and Google Docs — we create and update documents when you ask Flow State to generate or save a document for you.
We do not use your Google data for advertising, and we do not sell it. How we handle this data is described further in our Google User Data — Limited Use section below.
Microsoft Account Data (Outlook Mail and Calendar)
If you choose to connect a Microsoft account instead of, or alongside, Google, Flow State requests the following access through the Microsoft Graph API. As with Google, each permission powers a specific feature and you can revoke access at any time.
Outlook Mail (read, write, and send) — to read recent messages and threads so Flow State can surface open loops and commitments, to create draft replies for you to review, and to send a message once you have chosen to send it.
Outlook Calendar (read and write) — to read your events so Flow State can show your schedule, find free time, and detect conflicts, and to create or update events when you ask it to.
Basic profile — your name and email address, to identify the connected account.
We do not use your Microsoft data for advertising, and we do not sell it. It is used only to provide the features described above. If you turn on email access for connected AI tools, Flow State shares limited details of Outlook messages it has sorted with the AI tool you connected, at your direction (see Connected AI Tools). It never shares the full email or attachment contents.
Usage and Analytics Data
We collect anonymized usage data to improve the service, including page views, feature usage, and performance metrics. This data is collected via PostHog and does not include your task content or chat messages.
If you accept analytics cookies, we may also collect session recordings — anonymized replays of how you navigate the app, with text inputs masked by default — to identify usability issues and improve the experience.
2. How We Use Your Information
We use your information to:
Provide, maintain, and improve Flow State
Power AI coaching features such as weekly planning, daily planning, and chat
Build personalized memory and pattern insights for your account
Sync with your Google Calendar for scheduling features
Send service-related communications, such as password resets
Analyze aggregate usage trends to improve the product
Legal Basis for Processing (GDPR)
If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, we process your personal data under the following legal bases:
Contractual necessity — processing your tasks, priorities, projects, AI coaching messages, and calendar data is necessary to provide the Flow State service you signed up for.
Legitimate interest — we use anonymized analytics via PostHog to understand how the product is used and to improve it. You may opt out of analytics cookies at any time.
Consent — optional features such as connecting a Google or Microsoft account, and the desktop Context Engine, are only activated with your explicit consent. You may withdraw consent by disconnecting these integrations in your settings, or by disabling the Context Engine.
3. AI Processing
Flow State uses Anthropic's Claude API for some AI features. When a feature is powered by Claude, your messages and relevant context are sent to Anthropic's servers for processing.
Important: Your data is not used by Anthropic to train its AI models. Anthropic processes your messages solely to generate responses for your session. Anthropic may retain API inputs and outputs for up to 30 days for trust and safety purposes, after which they are deleted. Please refer to Anthropic's Privacy Policy for details on how API data is handled.
OpenAI. We use OpenAI's API for AI Coach chat, profile generation, calendar analysis, email classification and task or invitation drafts, text-assistant replies, Help and Feedback replies, capture triage of spoken and highlighted text, Weekly Preview quadrant judgments, daily prioritization, Context Engine hourly, daily and weekly summaries and profile-pattern analysis, meeting preparation, notes, and meeting coaching. The messages and context those features need pass through Vercel AI Gateway to OpenAI for processing. OpenAI does not train its models on data submitted through its API, and retains API inputs and outputs only for a limited period for abuse monitoring before deleting them. See OpenAI's Privacy Policy for details.
Google AI models. We may use Google's Gemini models through Vercel AI Gateway for an AI feature if we enable that route. As of 30 September 2026, no Context Engine task uses a Google AI model. If one is enabled later, the text and context needed for that feature would be sent to Google.
4. Data Storage and Security
Your data is stored in a PostgreSQL database managed by Supabase. All data is encrypted at rest and in transit using TLS. We use Row Level Security policies to ensure that each user can only access their own data.
To support offline workspace use, Flow State also stores a device-local copy of your weekly priorities, tasks, projects, and project-board columns in your browser's IndexedDB, together with pending changes and conflict records. This copy is scoped to your account on that browser profile and is not shown without a matching signed-in identity. It is removed after a successful sign-out, when you delete your account, or when you clear the browser's site data, and may also be evicted by the browser or operating system.
Google OAuth tokens for Calendar, Gmail, Drive, and Docs access are stored encrypted using AES-256-GCM encryption. We never store your Google account password.
While we implement industry-standard security measures, no method of electronic storage is 100% secure. We cannot guarantee absolute security of your data.
5. The Context Engine (Flow State for Mac)
Flow State's desktop app for macOS includes an optional feature called the Context Engine. When you turn it on and grant the macOS permissions it asks for, it observes what you do on your computer so that Flow State can describe your day back to you and connect your work to your tasks. This is the most privacy-sensitive thing Flow State does, so we describe it in detail.
The Context Engine runs only in the macOS desktop app. It is not part of the website or the mobile web app. It does nothing until you enable it, and macOS additionally requires you to grant Screen Recording and Microphone permissions before any capture can occur. You can revoke those permissions in macOS System Settings at any time.
What it captures
Screen contents. While the Context Engine is running, Flow State takes a screenshot roughly every 4 seconds when your Mac is on power, and roughly every 12 seconds on battery. Where possible the screenshot is limited to the window you are actively using; where the app cannot determine that window, it captures the full screen. Each screenshot is converted to text on your device using Apple's built-in text-recognition framework. The screenshot image is then deleted and never stored. Only the recognised text is kept.
Clipboard contents. Flow State checks your clipboard about twice a second and records new text you copy. Very short items, bare web addresses, plain numbers, and clipboard contents that are nothing but a single credential the filter recognises are discarded rather than stored. Everything else is kept, with any credentials the filter recognises replaced by [REDACTED] — see below. A password copied out of a password manager is usually a single token that matches no known format, so expect it to be stored and redacted only if it happens to match one.
Meeting and call audio. When you record a call, Flow State captures two audio streams: your microphone, and your Mac's system audio, which contains the voices of the other participants. Both are transcribed into text on your device. Flow State can detect calls in Zoom, Microsoft Teams, Slack, FaceTime, WhatsApp, Google Meet, Discord, and Webex. If you enable automatic call detection, Flow State notices a call and shows a notification saying recording will begin shortly; recording then starts on its own unless you dismiss it. Your obligations to the other people on the call are described in the next section.
6. Recording Other People
When you record a call, you are recording everyone on it. Flow State captures your Mac's system audio, which carries the other participants' voices, and transcribes what they say. Those people are not Flow State users, have no account with us, and have not agreed to this policy.
Obtaining their consent is your responsibility, not ours. In many jurisdictions — including a number of US states and several European countries — it is unlawful to record a conversation unless every participant has consented, and in some places it is a criminal offence. The rules differ by jurisdiction, and the relevant jurisdiction may be the other person's rather than yours. Before you record, tell everyone on the call that you are recording, and get their agreement.
We want to be clear about what Flow State does and does not do here, because it would be easy to assume more:
Flow State does not announce the recording to other participants. It plays no tone, shows them no banner, and posts no message in the meeting. If your conferencing tool has its own recording indicator, that indicator will not appear, because Flow State records the audio your Mac is already playing rather than using the tool's recording feature.
Flow State cannot verify that consent was obtained. When the live meeting notepad opens, it shows you “Ensure you have others' consent when recording” for five seconds, then fades the message away. That message is shown only to you and neither records nor verifies consent. If you turn on the recording-consent reminder in Settings, Flow State also shows you a notification when a recording starts and records whether you confirmed that everyone consented. That separate reminder is off unless you turn it on, it is shown only to you, and your confirmation is your own assertion — Flow State has no way to check it with the other participants.
Flow State does not notify participants afterwards, and does not give them a way to request deletion from us. Because the recording and transcript live on your Mac, any such request has to be honoured by you.
By recording a call with Flow State, you confirm that you have obtained whatever consent or notice the law requires from every participant, and that you have the right to record and transcribe what they say. As between you and us, you are responsible for the consequences of recording without that consent. If a participant asks you to delete a recording, you can do so directly in the app's meeting page for that meeting.
7. Google User Data — Limited Use
Flow State's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
We only access, use, and store your Google user data to provide and improve the user-facing features described in this policy.
We do not use your Google user data for advertising, and we never sell it.
We do not transfer your Google user data to others except as needed to provide or improve these features, for security purposes, to comply with applicable law, or as part of a merger or acquisition with appropriate notice to you. When Flow State sends Google data, such as an email, calendar event, or document, to Anthropic or OpenAI to generate a draft, summary, or suggestion, the provider processes it solely to produce that result and does not use it to train its models. If you turn on email access for connected AI tools, Flow State shares limited details of Gmail messages it has triaged with the AI tool you connected, at your direction, so that tool can answer your requests: the sender, subject, received date, Flow State's summary, type and urgency labels, and attachment names. It never shares the full email or attachment contents. Once shared, the AI tool's own privacy policy and terms apply.
We do not allow humans to read your Google user data unless you give explicit consent to read specific messages or files, it is necessary for security purposes, it is required to comply with applicable law, or the data has been aggregated and anonymized for internal operations. Routine AI-conversation quality reviews do not include the contents of your Gmail or Drive data.
The Google permissions we request, and why
Calendar — to read your upcoming meetings so Flow State can prepare briefs and plan your week, and to write events you ask it to create.
Gmail — read, modify, and send (gmail.modify) — to read the messages needed to surface open loops and commitments, to create draft replies and meeting agendas for you to review, to apply labels, and to send a message once you have reviewed it and chosen to send it. Flow State does not send email you have not approved, and this scope does not permit permanent deletion of your mail.
Drive — read-only (drive.readonly) — to read the specific documents you reference or attach to a meeting, so Flow State can use them as context. Flow State does not browse or index your whole Drive on its own.
8. International Data Transfers
Flow State is operated from the United States by Brain-Based Workplace, LLC. If you are located outside the United States, including in the EEA, the UK, or Switzerland, your personal data will be transferred to and processed in the United States by us and by our service providers.
The service providers who process personal data on our behalf, and the region in which they process it, are listed on our subprocessors page, which we keep current. In summary, our database and authentication (Supabase), application hosting and file storage (Vercel), abuse-prevention request counters (Upstash), AI processing (Anthropic and OpenAI), transactional email (Resend), product analytics (PostHog, US region), error monitoring (Sentry, US region), payments (Stripe), and SMS and WhatsApp message delivery (Twilio) all process data in the United States. Where you connect a Google or Microsoft account, that provider processes the data in its own global infrastructure under your account terms with them.
For transfers of personal data out of the EEA, the UK, or Switzerland, we rely on the Standard Contractual Clauses adopted by the European Commission (with the UK International Data Transfer Addendum for UK transfers), which each of these providers makes available as part of its data processing terms, or another safeguard approved under Chapter V of the GDPR. Several of them additionally self-certify under the EU–US Data Privacy Framework. Every provider listed on our subprocessors page is covered by a data processing agreement — either signed with us directly, or incorporated into the terms under which we use the service.
One transfer is worth stating plainly. When the desktop Context Engine sends text read from your screen or clipboard, or a call transcript, for AI processing, that text passes through our servers to Anthropic or through Vercel AI Gateway to OpenAI, depending on the feature. The providers process it in the United States under our data processing agreements on the terms described in Sections 3 and 5. A Google AI model is not currently active for Context Engine; if enabled later, relevant text would pass through Vercel AI Gateway to Google under the applicable processing terms.
You can request a copy of the relevant transfer safeguards by contacting us at jack@brainbasedworkplace.com. By using Flow State, you acknowledge that your data will be processed in the United States.
9. Data Sharing
We do not sell your personal data to third parties.
We share data only with the following service providers, solely to operate Flow State:
Supabase — database hosting and authentication
Anthropic — AI processing (Claude API)
OpenAI — AI processing for AI Coach chat, profile generation, calendar analysis, email classification and task or invitation drafts, text-assistant replies, Help and Feedback replies, capture triage of spoken and highlighted text, Weekly Preview quadrant judgments, daily prioritization, Context Engine hourly, daily and weekly summaries and profile-pattern analysis, meeting preparation, notes, and meeting coaching
Vercel — application hosting and AI Gateway routing
Google — Calendar, Gmail, Drive, and Docs integration for the features you connect, and AI processing if a Google model is enabled later
Microsoft — Outlook Mail and Calendar integration, if you connect a Microsoft account
PostHog — anonymized product analytics
Sentry — error monitoring and performance tracking
Resend — transactional email delivery
Stripe — subscription payments and billing
Twilio — sending and receiving SMS and WhatsApp messages to and from the phone number you provide, if you use the text assistant. Messages you send in and relevant task context are processed by Anthropic or by OpenAI through Vercel AI Gateway, and can create or change your tasks and priorities.
A current list of these providers, what each one is used for, and where each one processes data is maintained on our subprocessors page. Each of them acts as a processor on our instructions under a data processing agreement, and none of them is permitted to use your data for its own purposes.
We may disclose your information if required by law, such as in response to a valid subpoena or court order.
10. Connected AI Tools
You can connect an AI tool such as Claude, Claude Code, ChatGPT or Codex to your Flow State account through the Model Context Protocol (MCP). The connection is made only after you sign in to Flow State and click Allow on the Flow State approval screen. Setup steps are on our Connect your AI page.
A connected tool can read and change the data that Flow State's MCP tools expose: your tasks and recurring tasks, weekly priorities, projects, Context Library folders and items, workflows, your profile, and your planning and display settings. It can also see the calendar meetings Flow State has synced, upcoming and past, with their prep, and the recaps and coaching of meetings you transcribe with Flow State: titles, times, locations, join links and calendar descriptions; the organizer's and attendees' names, email addresses and responses; desired outcomes, agendas (including your private facilitation notes), prep briefs, recaps and coaching. It can update a meeting's desired outcomes and agenda, edit the text of a recap, turn a recap action item into a task, and hide a meeting from your upcoming meetings and from connected tools. It cannot send email or invitations, and it cannot see meeting transcripts or recordings, which stay on your computer.
If you turn on email access in Settings, a connected tool can also see the emails Flow State flagged as needing you and your Email Digest from the last 30 days: sender name and address, subject, received date, Flow State's short summary, the type and urgency labels Flow State gave it, and attachment names. It cannot see the full text of your emails or open attachments. It can turn an email into a task, mark it handled in Flow State (this does not change your mailbox), and save a reply draft in Gmail or Outlook addressed to the original sender, but it cannot send it. Email access is off until you turn it on, and turning it off stops access immediately. Subjects and summaries come from what other people wrote to you, so only turn this on for AI tools you trust with that information.
Through this connection, Flow State sends data to the tool only in response to requests the tool makes on your behalf, such as when you ask it to list your tasks. Flow State's own AI features, which send data to AI providers separately, are described in Section 3. Once the tool has received data, that provider's own privacy policy and terms apply to it.
Access tokens for a connection expire after one hour. Refresh tokens last up to 30 days and are replaced each time they are used, and reusing an old refresh token revokes the connection. We store only hashed copies of these tokens, and we record when each connection was last used.
11. Cookies
Flow State uses the following cookies:
Authentication cookies (Supabase) — essential for keeping you logged in. These are strictly necessary and cannot be disabled.
Analytics cookies (PostHog) — used to collect anonymized usage data to help us improve the product.
We do not use advertising or third-party tracking cookies.
12. Data Retention and Deletion
We retain your data for as long as your account is active. You may:
Export your data — request an export of the task, priority, context, chat, daily-plan, and change-history categories listed in the export in JSON or CSV format.
Choose meeting data retention — by default, your meeting transcripts, notes, summaries, recaps, briefs, and coaching are kept for as long as your account is active. You can instead choose a 1-year retention period on the Meetings tab in Settings; with that setting, meeting content older than one year is deleted automatically each day and permanently removed from our systems within 30 days. Meeting titles, dates, attendees, and agendas are kept either way.
Delete your account — request complete deletion of your account and all associated data. Upon deletion, your data will be permanently removed from our systems within 30 days.
Flow State keeps structural facts about task and daily-plan changes while your account is active. Raw old and new field values in that history are automatically redacted after 90 days. Data exports include only change history owned by your account, and account deletion removes that owner-scoped audit history with the rest of your account data.
You can export your data from Settings at any time. To delete your account, use the "Delete Account" option in Settings > Data, or contact us at jack@brainbasedworkplace.com.
13. Your Rights
Depending on your jurisdiction, you may have the right to:
Access the personal data we hold about you
Request correction of inaccurate data
Request deletion of your data
Object to or restrict processing of your data
Request a portable copy of your data
Withdraw consent you previously gave, at any time
To exercise any of these rights, please contact us using the information below. We will respond within one month, as required by the GDPR, and we do not charge for a first request.
If you are in the EEA, the UK, or Switzerland, you also have the right to lodge a complaint with your national data protection authority if you believe we have handled your personal data unlawfully. You may do so without contacting us first, though we would rather hear from you and put it right. A list of EEA authorities is published by the European Data Protection Board; in the UK the authority is the Information Commissioner's Office.
14. Minors
Flow State is not intended for use by anyone under the age of 18, and our Terms of Service require every user to be 18 or older. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us with personal data, please contact us so we can delete it.
15. Changes to This Policy
We may update this Privacy Policy from time to time. When we make material changes, we will notify you by updating the "Last updated" date at the top of this page. We encourage you to review this policy periodically.
16. Contact Us
If you have any questions about this Privacy Policy or our data practices, please contact us:
Captured material is stored in a folder in your macOS home directory (~/.flowstate), readable only by your macOS user account. It is stored as ordinary files and a local database, which Flow State does not itself encrypt — it is protected by macOS file permissions and by whatever disk encryption you have enabled. If this archive matters to you, turn on FileVault. We want to be precise about the boundary, because it is easy to overstate:
Screenshot images, audio recordings, and the raw capture files never leave your computer. We never upload them, and we cannot access them.
Text extracted from your screen and clipboard and text from your call transcripts leave your computer. To produce hourly summaries, the desktop app sends the relevant extracted text through Flow State's servers and Vercel AI Gateway to OpenAI. For daily and weekly summaries and meeting features, the relevant text is sent through our servers to Anthropic or OpenAI, depending on the feature. Our servers authenticate your installation, forward the text to the selected provider, and return the result. We do not store or log the text sent this way — we record only which model was used and how many tokens it cost, so we can meter usage. This processing is covered by our data processing agreements with Anthropic and OpenAI. Neither uses data submitted through its API to train its models; their retention terms are described in Section 3. No Context Engine task currently uses a Google AI model; if one is enabled later, relevant text may also be sent to Google through Vercel AI Gateway.
The resulting summaries sync to our servers. The written summary, its topic tags, the model used, and the number of underlying entries are stored in our database so the AI coach on the web and on your phone can see your recent activity. These summaries describe your activity in prose; they are derived from your captures, not copies of them. Access is restricted to your account by database-level row security.
Automatic redaction, and its limits
Before anything is stored, Flow State scans captured text for credentials and sensitive identifiers — private keys, access tokens, database connection strings, API keys from common providers, payment card numbers, US Social Security numbers, and IBANs — and replaces them with [REDACTED]. This filter is on by default and applies to screen text, clipboard text, and call transcripts. You can turn it off in Settings.
This filter reduces risk; it does not eliminate it. It recognises well-known formats, plus labelled secrets written in English and Portuguese. Sensitive information that is labelled in another language, or that has no recognisable format — the substance of a medical record, a legal document, or a private message — will not be detected and will be stored. If you work with material you do not want captured, use the exclusions described below, or pause the Context Engine.
Your controls
Turn it off. The Context Engine can be disabled entirely, and is off until you enable it.
Pause. You can pause capture from the menu bar or with ⌘+\. A pause lasts five minutes by default; when the pause notification appears you can extend it to 10, 15, or 30 minutes, an hour, or a day. Capture resumes automatically when the interval runs out, and is on again the next time you launch the app. There is no indefinite pause — to stop capture until you decide otherwise, disable the Context Engine in Settings.
Exclusions. You can exclude specific applications, website addresses, or window titles from capture. No exclusions are configured by default — until you add them, password managers, banking sites, and health portals are captured like anything else. We recommend setting these up when you enable the feature.
Retention. You can set how long captured data is kept, from 7 days to 10 years. By default, captured data is kept indefinitely until you choose a window or delete it yourself.
Automatic pauses. Capture stops on its own when your screen is locked and after about a minute of inactivity.
Deletion. Because the archive is a folder on your Mac, you can inspect or delete it directly at any time. Deleting the app's data folder removes the captured material permanently. The summaries that synced to our servers are separate from that folder: you can delete them at any time in Settings > Context Engine, and they are also deleted along with the rest of your data when you delete your Flow State account.
Legal basis
If you are in the EEA, the UK, or Switzerland, we rely on your consent (GDPR Article 6(1)(a)) for the Context Engine, given by enabling the feature and granting the macOS permissions it requires. You may withdraw that consent at any time by disabling the feature or revoking the permissions; withdrawal does not affect processing already carried out. Where captured material happens to include special-category data within the meaning of Article 9 — for example health information visible on your screen — we rely on your explicit consent under Article 9(2)(a), and we ask you not to enable capture over material you are not free to record.
In data-protection terms: for material about other people that stays on your own Mac and is used for your own purposes, you are the controller of that material and we do not process it. For any part of it that reaches our servers — for example a meeting summary you sync or share — we act as a processor on your instructions, and you are responsible for having a lawful basis for the participants' personal data it contains.
Drive app files and Google Docs (drive.file, documents) — to create and update documents when you ask Flow State to generate or save one. drive.file is limited to files Flow State itself creates or that you explicitly open with it; it gives us no access to the rest of your Drive.
We request these scopes because the features above cannot work without them. If you would rather not grant a scope, you can decline it or disconnect Google entirely in Settings; the features that depend on it stop working and the rest of Flow State continues to work. You can also revoke our access at any time from your Google account permissions page.
Data received from Google APIs is stored only for as long as needed to provide these features, is never used to train any AI model — ours or anyone else's — and is deleted when you disconnect your Google account or delete your Flow State account.
A distinction worth stating
The commitments above govern data Flow State receives from Google APIs. Separately, if you use the desktop app and enable the Context Engine described in Section 5, and you have Gmail, Google Calendar, or a Google Doc open on your screen, that content may be captured as screen content like anything else on your display. That capture comes from your own screen rather than from Google's APIs, but we mention it so the boundary is not misunderstood. You can exclude Gmail, Drive, or any other site from capture in the Context Engine's settings, and the Context Engine is off unless you enable it.
You can disconnect a tool at any time in Settings → Integrations → Connected apps. Disconnecting revokes its access immediately.
Some tools connect with a Flow State API key instead. These tools skip the Allow screen and do not appear under Connected apps. To cut one off, delete its key in the API Keys window, which you open with the key icon in the Context Library drawer.
What happens when a connected tool deletes something depends on what it deletes:
Tasks go to the Trash. You can restore them for 30 days, after which they are permanently deleted.
Projects are archived. You can restore them from the Archived view at any time.
Weekly priorities are archived, not erased. Flow State support can restore them.
Context Library items are kept for 30 days, during which Flow State support can restore them. After that they are permanently deleted.
Stopping a recurring task removes its future occurrences that have not been changed or completed. Past and completed occurrences stay in your history. This cannot be undone.
Hiding (archiving) a meeting keeps its prep, recap and coaching; Flow State support can restore it.