Privacy and permission disclosure

Last updated: 2026-10-26

This disclosure describes Bridgefold, including published 0.7.0 and the 0.7.1/0.7.2 maintenance candidates. The maintenance update does not change the data flows or the optional native integration limitations described below.

Bridgefold is an independently developed browser agent. Its purpose is to carry out tasks you request on a selected browser tab through your chosen AI connection. Bridgefold does not operate advertising or developer usage analytics. AI-provider software and external services have their own privacy and telemetry behavior.

Who is responsible, and on what legal basis

The controller for the limited personal data Bridgefold's maintainer actually receives — support email and voluntary feedback — is Andrei Damashkevich, an independent individual developer based in Cyprus. Contact: the.career.odyssey@gmail.com.

Where the EU GDPR applies, processing rests on these bases:

• Article 6(1)(b) — performance of a contract: running the task you asked for, which means sending your prompt and the page content you selected through the chosen connection to your selected AI provider, and keeping the conversation so the panel can show it back to you.
• Article 6(1)(f) — legitimate interests: answering support requests, acting on voluntary feedback, and keeping the extension and its native host secure and working correctly. The interest is operating and maintaining a free tool; the data involved is what you chose to send, and you can object at any time by writing to the address above.

The maintainer does not automatically receive your local conversations or account keys. Data you send to Cursor is processed under its own terms and privacy policy; configured API endpoints and enabled MCP services are operated by their respective providers. Bridgefold handles local storage and browser actions; each external service is responsible for its own service and data practices.

Data flow

Before you start the first real task from the side panel, Bridgefold asks you to review this data flow and choose Accept and continue. Declining sends no task and keeps your draft. Chrome stores the accepted disclosure version and acceptance timestamp locally; a new disclosure version asks again. Demo mode and connection setup do not require this task consent. API connection verification sends built-in test prompts and a small built-in image to the selected provider; it does not read your page and may use provider credit.

Depending on the pages and prompts you choose, task content can include personal identifiers, private communications, health information, financial information and location details. URLs, page titles and agent interactions are also processed. Blocking sensitive form inputs does not remove sensitive information already visible elsewhere on a page or supplied in a prompt. Avoid including information you do not want your AI provider or enabled integrations to process.

Opening the side panel reads the bound tab’s ID, URL and title to display context and suggest quick actions. Task content is processed when you submit a task, add context, start dictation, or run a finalized routine. It can include:

• active tab ID, window ID, URL, and title;
• selected text or a bounded page-text snapshot;
• accessibility/DOM metadata needed to identify visible controls;
• a viewport screenshot when explicitly attached or requested by the agent;
• recent console or network summaries when the task requires debugging;
• the user's prompt, agent response, routine plan, and routine report;
• microphone audio while the dictation button is active. Chrome's speech-recognition service processes that audio; the extension keeps only the resulting text.

Browser API connection: the visible extension panel sends relevant prompts, page context, tool results and images directly to the HTTPS OpenAI-compatible API endpoint you explicitly configure. You grant access to that exact provider origin before verification or inference. Endpoint URLs cannot contain credentials, query parameters or fragments; redirects are rejected. Connecting checks the model list and makes up to two small tool/result/image compatibility completions with built-in test data. These requests may use API credit. Image acceptance is not a guarantee of image understanding or reliable task completion.

Optional native Cursor connection: Chrome native messaging starts a separately installed host. Its native relay authenticates the local connection using private credentials stored on this computer. The host uses Cursor CLI (ACP), Cursor Agent SDK, or its own configured native API connection. Native Cursor sessions may discover configured MCP servers and skills; enabled integrations may receive relevant task data under their own policies. These native features are unavailable in the browser API runtime. Public companion bootstrap and clean-machine native distribution are not yet qualified for this candidate.

Your selected endpoint's operator and model-service providers process task data under their own terms, privacy policy and account settings. Local browser or host execution does not mean model processing stays on your computer. Review Cursor's privacy policy, or your API provider's policy, and your organization's account controls before sending confidential data. Antigravity is not offered in this public release. Bridgefold's browser-action approvals do not replace the permissions and policies of external tools.

Dictation is opt-in. Chrome's speech-recognition service may send microphone audio to its service provider; Bridgefold retains the transcript, not audio recordings. Actions such as typing or submitting may send task data to the website you chose.

The project does not sell data, use it for advertising, or share it with unrelated third parties.

Credential handling

Browser API credentials: one active connection's key is encrypted with AES-GCM in this Chrome profile's IndexedDB, alongside its connection metadata and a non-extractable Web Crypto encryption key. A plaintext cache in chrome.storage.session is restricted to trusted extension contexts (TRUSTED_CONTEXTS). The API key is not stored in chrome.storage.local or sync, returned in public connection metadata, or included in the task journal. Trusted extension code can decrypt it for the selected connection: this is not an OS keychain, a hardware-security guarantee, or protection against a compromised browser profile. Restarting Chrome restores the saved connection without contacting the provider or resuming tasks. Disconnect/Forget deletes the saved credential and cache; it does not revoke the key at the provider. Removing the extension or clearing its profile storage also removes its saved data. Replacing a key/provider creates a new connection identity; existing chat context is not silently sent to a new connection.

Native credentials: the shared Cursor CLI connection uses the CLI's authentication. Separate Cursor Web/native API accounts use the host's OS credential store: macOS Keychain, Linux libsecret/Secret Service, or Windows DPAPI CurrentUser. These OS-store requirements do not apply to browser API connections. Native keys pass through the authenticated local transport; native Disconnect keeps the saved credential, while Remove saved key deletes it and preserves native metadata/chat bindings. Cursor's own account controls revoke provider keys. Windows keys are bound to that Windows user/installation and macOS keys require an accessible Keychain; no cross-device key synchronization is promised. Windows native distribution remains deferred for this candidate.

The native host stores rotating local pairing credentials, paired extension origin and access choices in ~/.bridgefold-host/config.json with owner-only permissions. The extension retains its native pairing credential locally. Older ~/.cursor-chrome-host state is not deleted automatically. Account display metadata is not a developer analytics identifier.

Local retention

Browser API path: bounded chat messages, run status and whitelisted journal data are stored in chrome.storage.local (bridgefold.browser-api.history). The defaults retain at most 20 runs, 100 messages and 100 events per run, 16,000 characters per text field and 512,000 UTF-8 bytes overall; older content is evicted as limits are reached. Keys and authorization headers are excluded/redacted. History remains on this computer across browser restarts. It contains no executable resume state: panel closure/reload, owner-port loss or a connection change interrupts the run. Unfinished records become interrupted on recovery; they never silently replay. Old chats remain bound to their original connection; a newly connected provider cannot automatically receive that context. Removing the extension removes its extension storage; native host purge commands do not clear browser history.

Optional native path: the following host files and lifecycle controls apply only when that connection is used:

• Conversations are stored in ~/.bridgefold-host/conversations.json; durable run identity and replay events are stored in ~/.bridgefold-host/runs.json.
• Routines and reports are stored in ~/.bridgefold-host/routines.json.
• When native learning is enabled, agent-owned skills and short memory notes from completed or blocked tab runs are stored in ~/.bridgefold-host/agent-learn.json. They are written from the host action ledger, not from page text, and cannot skip approvals or raise access. The packaged uninstaller preserves this file unless you --purge-user-data.
• When enabled, structured native local memory (ongoing goals, observed entities, episodes, user-claim preferences, and consolidation proposals) is stored locally in ~/.bridgefold-host/local-memory.sqlite. When a local Ollama service is reachable on 127.0.0.1:11434, the host may compute local vector embeddings for hybrid memory search; if unavailable, search falls back to local lexical matching. You can disable local memory, inspect or dispute claims, and delete individual memory records from the side panel. The packaged uninstaller preserves this database unless you --purge-user-data.
• Account labels, email addresses, API endpoint/model metadata, selected connection, and task/account bindings are stored in ~/.bridgefold-host/connections.json. Isolated API keys live in the macOS Keychain (com.bridgefold.host.connection), in Linux Secret Service, or, on Windows, in ~/.bridgefold-host/connection-secrets/<id>.dpapi. Isolated CLI configuration and session data are under ~/.bridgefold-host/connections/<id>/.
• The host workspace is under ~/.bridgefold-host/workspace.
• Operational startup and error output is stored locally in ~/.bridgefold-host/host.log with owner-only permissions. New logs do not include the signed-in account email. The host rolls this file to ~/.bridgefold-host/host.log.1 when it exceeds 10 MB and keeps one previous generation; there is no age-based expiry, so both files remain until they are rolled over again, you delete them, or you explicitly purge host data.
• Cursor authentication and agent state are managed by the installed CLI/SDK in their own state directories. Cursor and integration providers control retention of data processed by their services.
• The extension stores pairing credentials, page-access choices, theme/model preferences, tab-to-conversation mappings, a bounded local activity log, and the accepted task-consent version and timestamp in chrome.storage.local.

Deleting a routine from the product deletes its stored reports. The packaged uninstaller preserves conversations, routines, reports, pairing settings, workspace files, and logs by default; it removes only the registered bridge and installer-managed runtime, extension, and companion artifacts. To remove all host-owned state, use the explicit --uninstall --purge-user-data lifecycle action (or stop the host and delete ~/.bridgefold-host). To remove the extension token stored by Chrome, remove the extension or clear its site data in Chrome. Use Cursor's own logout and account controls to remove or revoke Cursor SDK credentials.

Permission rationale

• sidePanel — presents the product next to the current page.
• storage — stores encrypted browser API credentials in this Chrome profile with a trusted session cache, bounded browser chat history locally, and native pairing credentials, page-access decisions, preferences, tab mappings and activity.
• tabs — captures and displays the chosen tab and resolves finalized routine targets.
• tabGroups — labels tabs actively controlled by a Bridgefold task so they are visible and recoverable as a group.
• debugger — uses Chrome DevTools Protocol for bounded inspection and interaction on the explicitly targeted tab.
• scripting — injects packaged page helpers (agent-cursor.js, page-ax.js, page-overlays.js) on demand with chrome.scripting.executeScript into the top frame after an origin grant. The packaged extension has no static content_scripts.
• activeTab — captures a visible screenshot fallback only after the user invokes the extension.
• notifications — reports completed routines and approval requests when the panel is closed.
• nativeMessaging — starts and authenticates the packaged local host without exposing host credentials to page scripts.

The Chrome Web Store build declares no required host_permissions. Browser API requests use HTTPS directly from the extension; the optional native connection reaches its host through native messaging. optional_host_permissions is exactly http://*/* and https://*/*; those origins are not granted at install. Chrome prompts per origin for task-page access and for the API provider endpoint. A snapshot never requests that grant on its own. The extension does not request <all_urls> or microphone.

The release declares no static content scripts, so installing Bridgefold does not grant it script access to every site. Three packaged page helpers are injected on demand with chrome.scripting.executeScript into the top frame for user-requested tasks or context capture: agent-cursor.js draws the visible agent-cursor overlay, page-ax.js collects an accessibility snapshot after a task-page origin grant, and page-overlays.js supports element and screenshot selection. Chrome enforces the scripting permission for the targeted page. These helpers ship inside the package; they are not downloaded or automatically injected on every page.

Chrome still shows a broad debugger warning because the debugger permission is powerful; the product cannot suppress or weaken Chrome's own warning text.

Safety boundaries

Password, payment-card, and one-time-code inputs are blocked. Sensitive interactive actions require approval, and scheduled runs skip them. A task can still send non-sensitive text to the page named in the user's instruction, so users should review the pinned target and the action log before approving consequential work. Native Cursor cloud research is a separate execution mode and never silently falls back to the live-tab agent. Browser API mode has no cloud, routines, memory or MCP execution.

Limited Use

Bridgefold's use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. User data is used only for the disclosed browser-agent features and related security/operation; it is not sold or used for advertising, data brokerage, creditworthiness or lending. The developer does not receive your transcripts automatically. If you send diagnostics to support, inspect them first and include only the information needed to resolve your issue.

Questions

Bridgefold is a personal project owned and maintained by Andrei Damashkevich, an independent individual contributor. Contact: the.career.odyssey@gmail.com. It is not affiliated with, sponsored by, or endorsed by Anysphere, Inc. Cursor is a trademark of Anysphere, Inc.

Where applicable, you may also request restriction of processing, portability of the personal data you supplied, and object to processing. You may withdraw consent for processing based on consent and lodge a complaint with your competent data-protection supervisory authority. These rights apply subject to their legal conditions; they do not give the maintainer remote access to your device or to your separate provider accounts.

Cursor may use model providers including OpenAI, Anthropic and Google; actual routing depends on its services and your configuration. See Cursor's trust and privacy documentation, current subprocessors, and privacy policy. Provider processing may take place outside your country, including in the United States; consult those disclosures for locations and transfer safeguards. Bridgefold does not independently promise EU-only processing or zero provider retention.

You can contact the address below to request access to, correction of, or deletion of information you have sent directly to Bridgefold support. The maintainer does not automatically receive your local conversations, account keys or browser history and cannot erase those files remotely; use the local removal controls described above. For information processed by Cursor, Chrome speech recognition or another integration, use that provider's privacy and account controls. Applicable privacy rights depend on your jurisdiction.

The public Bridgefold information and download website is hosted on Vercel. Requests to that website are processed by the hosting provider, including ordinary connection/request metadata. The site does not embed an analytics SDK or collect extension transcripts.

Contact Bridgefold support at the.career.odyssey@gmail.com. The public support page and Chrome Web Store listing use the same contact address.

Bridgefold is free and has no paid features. Your selected AI provider may charge for usage, including connection verification, under its own terms and limits. Use of the extension and its native host is also subject to the terms of use, which disclaim warranties and limit liability.

Voluntary feedback

The feedback form sends the message, category, and any optional email address and extension version you provide through FormSubmit to the.career.odyssey@gmail.com. No conversations, page content, or account credentials are attached automatically. Do not include passwords or API keys. FormSubmit processes submissions under its privacy policy. Bridgefold does not process payments and has no paid features.