BrainStorm Map Plugin Privacy Policy

1. Who we are

Brainstorm LTD is responsible for personal information processed by the BrainStorm Map ChatGPT app and MCP connectors for Claude, Gemini, and other supported assistants, including anonymous map previews and the handoff to a BrainStorm workspace. This notice explains what the integrations receive, purposes, recipients, retention, and your controls.

Contact privacy@brainstorm-map.com for privacy questions, access, correction, export, objection, or deletion requests. OpenAI and other assistant platforms process your interactions with their own services under their own policies; this policy describes BrainStorm's processing.

Registered in the United Kingdom. Registered office: Suite 4.01, 4th Floor Capital House, 25 Chapel Street, London, England, NW1 5DH.

This notice covers plugin activity and original plugin preview records, including after a workspace copy is saved. The Main Privacy Policy at /privacy covers the website, account, and separate application, including saved workspace copies. Saving does not merge the original preview record with the workspace copy. For the plugin processing described here, this dedicated notice takes precedence over general descriptions in the Main Privacy Policy.

2. MCP integration inputs, processing, and outputs

Conversation mapping: when you ask to map a conversation in ChatGPT, Claude, Gemini, or another supported host, the intended flow is for the host assistant to create a concise outline. It sends Brainstorm the map title, topic labels, details, and nested branches, which may contain personal information derived from the conversation. Brainstorm stores the resulting map structure and a generated map summary. The intended flow does not send raw conversation turns to Brainstorm or require Brainstorm to make a second AI call to create the map.

Source-text mapping: when notes or other source text are explicitly supplied for mapping, the host may send Brainstorm that text (up to 12,000 characters) and an optional title. Brainstorm may send these to a separate AI provider using Brainstorm-owned API credentials to generate an outline. Brainstorm stores the resulting map and generated summary; the original source text is not copied into the map chat. The text is nevertheless processed by Brainstorm, its infrastructure, and the selected downstream provider, and generated topics, details, or summaries may reproduce information from it.

Expansion: expand_node receives share and claim tokens, a node identifier, new topic labels and details, and an optional request identifier. It stores the expanded map, revision, and retry information. The assistant supplies the content; this tool does not itself call another AI model.

Display: render_context_map receives a share token and optionally a claim token to retrieve and display a map. Tool results sent to the assistant include the title, node count, map links, share token, and, where applicable, claim link/token, revision, and changed-node identifiers. The embedded viewer also receives map content and interaction-event identifiers.

The MCP integration is designed not to retrieve other chats, memories, or user files, or request full conversation histories. Conversation mapping is intended to use a concise host-generated outline rather than raw turns or a transcript. A conversationMessageCount of zero means conversation messages were not imported into the map chat; it does not mean no map content or personal information is processed or stored.

3. Account handoff and operational information

Account information: you can create and preview plugin maps without an account. Registering, signing in, or saving a workspace copy involves account identifiers, email, profile and authentication information, and associations between your account and content. Supabase handles authentication.

Technical records: infrastructure processes IP addresses, request times, browser/device information, status codes, and errors to deliver and secure the service. AI usage records include provider/model, token counts, processing duration, success status, and feature used. The plugin text-structuring code does not deliberately log source text, titles, model output, or provider error bodies.

Plugin interaction measurement: we record map views, prompt opening/dismissal, outbound clicks, app arrival, sign-in steps, access restrictions, waitlist steps, map saving, workspace loading, activation, and handoff failures. Records include timestamps, assistant source, session/event identifiers, entry point, requested action, and outcome. A session can be associated with your account when you save a map. This is not limited to anonymous aggregate counts.

These MCP integrations use Brainstorm-owned provider credentials when a separate AI call is needed; you do not need to provide an AI-provider API key to the plugin or connector. Never submit passwords, API keys, government identifiers, protected health information, or other sensitive personal information through the tools. Separate account, billing, and application features are described in the Main Privacy Policy.

4. Purposes and legal bases

We process plugin data to fulfil your requests to create, display, expand, and save maps; verify capability links and permitted account access; and respond to support and privacy requests. Where applicable, this is necessary to perform our contract with you or take steps you request before entering a contract.

Operational records help maintain reliability, detect abuse, investigate failures, and protect users. Our legitimate interests in running and securing the service are balanced against your rights. Interaction measurement helps us understand and improve the journey from the plugin to the workspace. You may object by contacting us. Where consent is legally required for optional tracking or processing, it must be obtained before that processing occurs.

We process records to meet legal obligations, including accounting and lawful disclosure requests. Where processing relies on consent, you can withdraw it without affecting prior lawful processing. Using the service or reading this policy is not blanket consent to all processing.

5. Recipients, sharing, and AI providers

Host assistant: ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), or another MCP client processes the prompts, conversation, notes, and interactions you supply to that host under its own policies and settings. The host sends Brainstorm the tool inputs you request and receives tool responses, such as map links, identifiers, and displayed map content. A host provider may also be the separately called AI provider described below, but those are distinct processing steps.

Separate AI provider for source-text mapping: When host-based routing is enabled, Brainstorm sends source text for the ChatGPT integration to OpenAI, for Claude to Anthropic, and for Gemini to Google. If the client is unrecognised or direct, the default is Google. The route depends on how the client is identified and Brainstorm uses its own API credentials; users do not necessarily choose the downstream provider. Until host-based routing is enabled in the deployed service, Google may receive source text from any integration. The recipient provider processes the text and optional title to return an outline under its applicable terms and data-handling practices. Outline creation and assistant-supplied expansion do not trigger this additional Brainstorm AI call.

Infrastructure providers: Supabase provides the MCP database, Edge Functions, and authentication. It processes tool inputs as needed to run the service and stores maps, generated summaries, access tokens, and related operational records. Google Cloud hosts the marketing website and processes requests to that website. Infrastructure providers receive the information necessary to operate their services under their applicable agreements and policies.

If you choose to sign in or save a workspace copy, Supabase processes authentication and the account association needed for that action. The separate BrainStorm application may use additional AI, payment, and communication providers under the Main Privacy Policy. Using this plugin does not by itself send map content to every provider used by that separate application. Support and service-message providers may receive the contact details and message content needed to respond to your requests.

Anyone with a valid share link can view the map without signing in. A claim token enables supported expansion of an unclaimed map and saving to an eligible signed-in account. The account holder who claims it receives a workspace copy. Keep claim links confidential; share the view link for view-only access.

Authorised personnel access information as needed for support, security, and administration. We may disclose information as legally required, to protect rights and safety, or during a business transfer subject to applicable safeguards.

We do not sell personal information or share it for cross-context behavioural advertising. This does not exclude the service disclosures described above. Third-party retention and model-training practices depend on the applicable provider agreements and settings; we do not promise universal zero retention or training opt-out across providers.

6. Retention and deletion

Plugin preview maps: links are configured to expire 30 days after creation. After expiry the preview is unavailable and an unclaimed map cannot be claimed. Expiry is an access limit, not automatic erasure. Map records, generated summaries, tokens, and expansion/retry records can remain in the database until deleted. Contact us to request deletion of an unclaimed or expired map.

Saved maps and accounts: workspace copies remain until deleted or the account is closed, subject to legal obligations. Saving creates a separate workspace copy. Deleting that copy or an account should not be assumed to erase the original plugin preview. Include the preview link in a request to remove both.

Plugin interaction sessions and events: the configured daily cleanup removes sessions older than 90 days and their associated events. Records may remain until the next daily cleanup after reaching 90 days. Event-submission expiry does not erase earlier events.

Source text: original supplied text is used to generate the outline and is not saved in the map chat. Generated topics, details, and summaries can reproduce information from the source and remain with the map. The AI provider's separate retention terms apply to text it receives.

Operational, AI-usage, support, and security records remain for administration, troubleshooting, security, and handling requests. We have not established a single automatic deletion deadline for all such records. Contact us for deletion or further information; legal and security obligations may limit erasure.

Backup copies can outlast deletion from active systems until the relevant backup is rotated or expires. Link expiry is not backup deletion. Records subject to a legal preservation obligation may be held for the required period. Contact us for retention information relevant to your data.

7. Your controls and rights

Choose what to send: ask your host assistant to create a concise outline and use outline-based mapping if you do not want Brainstorm to send source text to a separate text-to-map AI provider. Review the topics and details supplied; these can still contain personal or sensitive information. Do not include material you lack authority to share.

Keep claim tokens private. Sharing a link permits anyone who obtains it to access the map until expiry or removal. Saving a workspace copy does not revoke the preview link. To request preview removal or revocation, email privacy@brainstorm-map.com with its view link. Do not email passwords or API keys. We may verify your authority before acting.

Contact privacy@brainstorm-map.com to request access, correction, export, deletion, restriction, objection, or consent withdrawal. Identify the account or map and requested action. Account settings may also offer controls for saved content. You do not need to create an account to submit a privacy request about an unclaimed map.

Disconnecting BrainStorm from ChatGPT, Claude, Gemini, or another host stops future use through that connection. It does not delete maps or records held by Brainstorm, or copies held by the host, AI providers, or other recipients. Request deletion from each relevant organisation separately.

You may object to personal interaction measurement and request deletion of existing records by email. The plugin currently has no dedicated in-widget analytics opt-out switch. Cookie controls do not disable server-side events.

We respond within the period required by law, normally one month for UK/EEA requests, explaining any permitted extension. Your rights depend on your location and may include portability, objection, and complaint to the UK Information Commissioner's Office or your local data-protection authority. California residents may exercise applicable access, correction, and deletion rights without unlawful discrimination.

8. Browser storage and security

The map viewer and workspace handoff can use browser session storage to preserve a pending action. Signing in to the separate application also uses authentication storage. Browser controls can clear or block local/session storage and cookies, which may affect sign-in or handoff. Cookie controls do not disable server-side measurement. There is currently no dedicated in-widget measurement opt-out switch.

ChatGPT and other host platforms use their own browser storage under their policies. When you visit this policy or other marketing pages, Google Fonts requests expose your IP address and request/device information to Google, as described in the Main Privacy Policy.

We use access controls and secure connections to protect information. No online service guarantees absolute security. Keep capability links private and report suspected unauthorised access to support@brainstorm-map.com.

9. International processing and children

Our providers may process information outside your country, including in the United States. Where data-protection law requires transfer safeguards, appropriate safeguards must apply, such as an applicable adequacy decision or contractual mechanism. Contact us for provider, processing-location, and safeguard information relevant to your data.

The service is not intended for children under 16, except that users aged 13–15 in the United States may use it with parental or guardian permission. Do not submit personal data about children through the plugin. Contact us if a child has supplied information without required permission.

10. Updates and contact

We update this policy when practices change and show the actual revision date above. Material changes will be highlighted in the service or otherwise notified where appropriate. Where a change requires consent, we seek it rather than treating continued use as consent.

Data controller: Brainstorm LTD. Privacy requests: privacy@brainstorm-map.com. Service assistance: support@brainstorm-map.com.