Flow beta privacy notice

Updated November 2026. This notice describes the current Flow beta operated by Del Carmen Ventures.

Your account and content

Flow uses your email to create your account and deliver account messages. Your profile, tasks, checklists, notes, goals and Flow events are saved so you can open them on another device. Supabase provides account authentication and stores this content. Flow is hosted using OpenAI Sites and Cloudflare infrastructure.

Access rules separate each user’s workspace. Content is not end-to-end encrypted: the services operating Flow process it to provide the app. This beta is not a private encrypted vault.

Google Calendar

Connecting Google is optional. Flow requests your Google account identity, permission to list your calendars, read events on calendars you can access, and manage events on calendars you own. You choose which calendars appear in Flow. The current interface sends event changes only to your primary calendar; selected secondary calendars, including Runna, are view-only in Flow. Google events are fetched when your calendar refreshes.

Flow stores your connected Google account identity on the server to maintain the connection. Access and refresh tokens, together with your selected calendar identifiers, are stored in an encrypted server-side payload. Your calendar selection belongs to your Flow account and is available when you sign in on another device. Tokens are not included in the workspace returned to the app or ChatGPT. Flow saves separate copies of calendar events only when you choose to copy them. You can review the date range and choose whether to include descriptions and locations.

Disconnecting asks Google to revoke access before removing the saved connection from Flow. Google revocation can affect all clients in the same Google project. If revocation cannot be confirmed, Flow pauses calendar access, retains encrypted credentials only to finish revocation, and offers Retry disconnect. You can also remove Flow’s permission in your Google account. Requests already sent to Google may finish; disconnect does not reverse them. Disconnecting does not delete events in Google or the separate copies you chose to save in Flow. If Google sign-in returns credentials that Flow cannot accept, Flow retains them encrypted and unused for reviewed cleanup. It does not automatically revoke an existing working connection after a failed reconnect. Unknown credentials or unconfirmed revocation need review through Google Account and support; the interface does not let a browser assertion clear that uncertainty.

Limited use of Google data

Flow uses Google data only to provide the visible calendar and optional assistant features you choose. Flow does not sell Google data, use it for advertising or credit decisions, or use it to train generalized AI models. Transfers to service providers are limited to providing these features with your consent, security, legal requirements, or a business transfer with your prior consent. Human access is limited to your affirmative permission for specific data, security investigation, legal obligations, or appropriately aggregated internal operations.

Flow’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. This is Flow’s data-use commitment, not a claim that Google has verified or approved the app.

Built-in Flow assistant

When you send a request in Ask Flow, Flow sends that request and bounded workspace context to the OpenAI API. Context may include task and note titles, checklist items, goal totals and saved Flow event times. Note bodies, Google credentials and weather preferences are not included. Requests are sent with response storage disabled. OpenAI may retain API data under its applicable policies. Flow stores account-scoped request identifiers, request hashes and results to prevent duplicate changes; a prepared change may be retained when a result is uncertain. These records are removed through the account-deletion process. The assistant uses a shared monthly spending cap and needs only your Flow account.

Before a new Google connection, Flow shows a separate, optional AI-sharing checkbox. It is preselected and explains that connecting with it checked allows calendar sharing with OpenAI for calendar requests. You can uncheck it before connecting. Flow saves the choice with your Google connection and uses it across devices; existing saved choices are preserved. When enabled, Ask Flow can send a limited set of event identifiers, titles, dates, times and editing restrictions from your primary Google calendar and saved Google copies to OpenAI for calendar requests. Changing “Google Calendar with AI” in Ask Flow or the setting in Settings updates that saved choice. Turning it off keeps it off for future requests and follow-ups until you enable it again. Requests already sent may finish; changing the choice cannot retract data already sent. Disconnecting Google clears the saved choice. Existing Google event descriptions and locations are not included in this model context. You can use the calendar editor without sending calendar context to OpenAI. Creating or editing a Google event requires you to review the proposed change and choose Confirm Google Calendar change. Planning advice and ordinary follow-up answers do not confirm a Google change. Flow stores the proposed fields and provider metadata in your account-scoped request record for confirmation and recovery. Protected events and secondary calendars remain view-only.

Deleting a saved Flow item through Ask Flow requires a separate deletion preview and confirmation. Local deletions move the item to Deleted items for restoration. Deleting a supported primary Google event requires its own Google preview and confirmation. For a recurring Google event, you must explicitly choose this occurrence or the entire series before reviewing that preview. Entire-series deletion includes past and future occurrences and exceptions; concurrent changes to individual exceptions cannot be locked atomically with the series. Flow retains the reviewed target, account identity, versions and exception fingerprint in the request receipt to recover uncertain results without choosing a different target. Google deletions do not enter Flow’s Deleted items. Protected events and unsupported recurrence scopes must be managed in Google Calendar.

If the assistant asks a follow-up question, Flow keeps the original request, your short answers and the questions in an account-scoped server record. A continuation can use up to four prior clarification turns and 8,000 characters, with a one-hour validity period starting from the first question. Relevant retained conversation is sent to OpenAI with your next answer. The browser sends a record identifier rather than its own copy of the conversation. Answering a follow-up retires the prior record’s stored request history; a new unfinished question can retain the conversation needed to continue. Cancel or Start over clears the conversation from the current interface. Cancellation and the one-hour expiry do not promise immediate deletion of stored records.

Existing ChatGPT connections

External ChatGPT setup is deferred for this release. The following still applies if you previously authorized a connection. When authorized using your Flow account, ChatGPT can receive workspace information and make requested changes through Flow’s tools. Tools retrieve one requested category at a time: limited task details, note titles, list names and requested checklist items, goal totals or saved Flow event times. They do not return note bodies, descriptions, event locations or live Google events. Task and event dates, titles and other returned fields are shared with ChatGPT when requested. Write tools accept the fields needed for the change, rather than a copy of your conversation. Google Calendar changes through ChatGPT are not available in this beta. Your Flow content remains subject to your ChatGPT account settings when shared with ChatGPT.

You can remove this connection under Settings in Flow. Expand Connected app access, then choose Check connected apps. This stops further access through the connection; it does not delete information already shared in your ChatGPT conversations.

Selected email invitations

Automatic inbox capture is not enabled. Under Settings you can choose calendar invitation (.ics) files saved from email. Flow reads the selected files in your browser, without connecting to an inbox, fetching attachments or sending their contents to AI. Unconfirmed candidates remain in memory only while the panel is open. Only after your separate confirmation does Flow save the reviewed title, date, times, location, Flow time zone and a derived invitation identifier as a local Flow event. Raw invitation files, descriptions, attendees and source email contents are not saved by this feature. These events are separate from Google Calendar. Repeated invitations do not overwrite existing events or recreate deleted ones; updates, cancellations and recurring invitations require manual review.

Weather and location

Weather is optional and currently covers the United States. You can enter a ZIP code or choose to share your device location. Flow rounds device coordinates to roughly a kilometer before sending them through its server to the National Weather Service. ZIP codes are sent to Zippopotam.us to find an approximate forecast area. These providers receive the lookup information. Flow saves your weather choice and optional ZIP code to your private account, but does not save GPS coordinates. With device permission, location updates while Flow is open and when you return; it does not track location while closed. the displayed forecast stays in the current page until you leave it or it expires. Weather is forecast data, not a live sensor reading. Clothing suggestions are based on the available forecast, and missing measurements are identified.

Forecasts are provided by the National Weather Service. ZIP lookup data is provided by Zippopotam.us / GeoNames.

Beta usage measurement

To learn which features work for testers, Flow records when a signed-in account first opens its workspace and observes saves from the editors and Ask Flow. Each observation includes the account identifier, signup and activity dates, feature, entry point, a request identifier, and whether the save succeeded, failed or could not be confirmed. This measurement excludes what you typed, item titles, calendar details and locations. Del Carmen Ventures uses aggregate counts to improve Flow. These account-linked records are kept until account deletion.

How long information is kept

Who processes information

Flow uses Supabase for account authentication and workspace storage; OpenAI Sites and Cloudflare for hosting and connection services; Resend for account emails; and Google when you choose to connect Calendar. ChatGPT receives the tool inputs and outputs used in a connected conversation. The National Weather Service and Zippopotam.us receive the weather lookups described above. These services process the information needed for the functions you use.

Browser storage and service logs

Your browser stores sign-in information and appearance preferences. The current browser tab also keeps unfinished assistant request information scoped to your Flow account so that a reload can offer Check result without creating a new request. These records can contain request text and confirmation decisions; they do not contain Google credentials or API keys. Hosting and account providers may process network and security logs needed to run their services. Avoid putting sensitive information in support screenshots.

Your choices

You can edit or remove individual saved items and disconnect integrations. Removal from the active workspace does not guarantee immediate removal from service backups or logs. For account deletion, access or other privacy requests, email gerardo@delcarmenventures.com from your Flow account email. We verify ownership before acting on account requests.

Return to Flow