Ideaflow PRIVACY · AGENT CONNECTIONS

Your data through the Ideaflow connector

One connection can give your chosen agent access to OpenChat, Unlinked and Thoughtstream Vision. You choose the apps and whether to allow writes.

Updated October 9, 2026. This supplement explains the shared connector operated by Ideaflow (IdeaFlow, Inc.). Read it with our company privacy policy and terms of service. Your agent host and each source app also have their own data controls.

This page covers the shared connection for all three apps, including private as well as shared app data. The separate Ideaflow notes and folders connector has its own privacy notice. App content is not automatically public; its permissions and your chosen sharing actions determine its audience.

What passes through the connection

Account and permissions. Your Ideaflow account ID, connected app identity, agent/client name, selected permissions and connection timestamps establish and manage access. The account-check tool returns your account ID and your name and email when present.
Requests and results. The agent sends the tool name and arguments, such as a search query, conversation or note ID, message text or proposed change. Ideaflow returns the requested results allowed by your app permissions. The gateway does not retrieve your entire conversation with the agent host.
OpenChat. Results can include conversations, participant and author information, messages, shared Context and Stream posts and replies, and associated IDs and timestamps. Shared Context is visible to conversation participants; quiet delivery does not make it private. Agent-private Stream entries are excluded from the shared conversation-content tool. With the matching permission, the agent can also search, read, record and correct your private people notes and relations (for example “knows” or “sister of”, including about Unlinked profiles); these stay visible only to you, are shown in OpenChat and on Unlinked person and contact pages, never notify the people they are about, and are labelled with the name the agent registered so you can tell its entries from yours.
Unlinked. Results can include your connections, professional profiles and published people, connection requests, notifications and relevant account information. Search may process professional information from your accessible network.
Thoughtstream Vision. Results can include note text, metadata, links, groups, author information and sharing settings within your permissions.
Service and security data. Sign-in uses authentication records and session cookies. Service infrastructure processes request URLs, IP addresses, browser/user-agent information, times, response status and diagnostics to operate the service, prevent abuse and investigate failures. IP-based sign-in rate limits are stored in the identity database; the connector also uses short-lived in-memory request counters.

We use these data to authenticate you, enforce permissions, carry out requested reads and changes, maintain the connection and protect its operation. Sign-in credentials belong in the Ideaflow sign-in flow; do not place passwords, API keys or other authentication secrets in tool arguments.

Who receives the data

Your agent host receives tool results. For example, when you connect through ChatGPT, OpenAI receives the returned data; a different host receives it when you use that host. Its storage, model processing and sharing settings apply to those copies. Granting read access permits data to leave the source app for that host.

Ideaflow services and infrastructure process requests. The gateway sends the requested operation and a short-lived account authorization to the selected Ideaflow app. Google Cloud hosts the gateway, identity database and operational logs; Vercel provides the public domain's edge routing. Authentication may involve Google or Apple when you choose their sign-in option, and Resend delivers requested account verification or password-recovery emails. These providers process the information needed for their respective services.

Some app tools have additional recipients. Unlinked's AI search sends the query and selected professional candidate fields, such as names, roles, companies, skills and connection dates, to the OpenAI API for ranking. Its request disables saved response storage, but this is not a promise of zero provider retention; OpenAI's API data controls describe provider handling. Ordinary list operations do not require this AI-ranking step. Vision's send-feedback tool publishes the submitted title, details and account attribution on the public World Issue Tracker board. Message, Context and note-sharing tools deliver content to their selected recipients or audience. These actions require the corresponding write permission.

The gateway itself does not call a model to generate answers. Separate source-app AI and automation features have their own operation and consent controls; connecting this plugin does not opt you into hosted Context generation.

Storage and retention

Connection records and token hashes: We store your account-to-agent grant, client identifier and label, permissions, creation/revocation times and token hashes. Access tokens expire after 1 hour; refresh tokens expire after 30 days and are replaced when used. Expiry stops a token working; it does not delete the stored record. Grant and token records currently have no scheduled age-based deletion and can remain after disconnect for security and replay checks. Deleting the identity account removes its associated grants and token records from the live database.
Temporary authorization data: Authorization codes expire after 60 seconds. A code's stored record is removed when exchanged; expired code records are cleared on later code creation. Per-request app authorizations last 45 seconds. These expiry periods are validity limits, not promises that infrastructure logs or backups are erased at the same time.
App content and host copies: The gateway processes tool inputs and results in memory and does not keep a separate archive of app result bodies. Source apps retain their own content, changes and diagnostics; your host may retain the results it receives. Their retention and deletion controls apply independently.
Operational logs: The gateway's Google Cloud application/request log bucket is configured for 30 days; required infrastructure audit logs for 400 days. Vercel edge logs and source-app logs follow their provider/account settings; this supplement does not promise a single deletion period across those services. Gateway errors use fixed categories, but infrastructure URLs and source-app diagnostics can contain request-related information.
Identity database backups: The Google Cloud identity database is configured to retain the latest 7 successful automated backups by count and 7 days of point-in-time recovery logs. Seven backups is not a fixed seven-day deletion promise. Data removed from the live database may remain in these recovery copies until they expire or are replaced. The gateway and identity database are deployed in Google's US Central region; routing, agent-host and other provider processing is not limited to that region.
Sign-in records: Your browser also keeps a 30-day last-used sign-in method hint: email/password, Google, Apple or passkey. This cookie contains no account identity or credential and does not change permissions; clearing it removes the hint. Ideaflow ID maintains your account, authentication and session records separately from the connector. Sessions have a 30-day validity period with renewal during use; expiry is not a general account-data deletion schedule. Disconnecting an agent does not delete your Ideaflow account or sign you out of every app.

Your choices and controls

Review the account and app permissions on the connection screen. Write access starts unchecked. Existing app ownership, membership and sharing rules still apply.
Visit Connected agents to disconnect a grant. This immediately stops future token authentication and refresh for that grant; it does not undo a request already accepted, delete app content, revoke separate app API keys or erase host copies.
To change permissions, disconnect and reconnect with the intended scopes. Use the source app to edit or delete its content and the host's controls to manage copies there.
For access, correction or deletion requests, contact pleasecontact@ideaflow.io. Identify the account and affected service, without including passwords, tokens or unnecessary private content. We may need to verify account ownership. Account deletion is separate from disconnecting.

Back to agent connections