Effective date: 28 October 2026
Applies to: Fixnetworks Chat Manager, version 0.2.4.
Who provides the extension
Fixnetworks Chat Manager is provided by Fix Networks Ltd (Company No. 12378975, registered in England and Wales), 42 Epworth Road, Isleworth, Middlesex, TW7 5BN. For privacy questions or requests, contact [email protected] or use our contact page and identify your message as a privacy request.
This policy covers the extension. Visiting fixnetworks.co.uk or contacting support involves separate website or support processing, described below. It does not replace your AI providers' or Google's privacy notices.
What it does with your information
The extension helps you search, organise, review, export and manage AI conversations. Its main library is stored in your browser profile. It does not include a Fixnetworks conversation server, advertising, analytics SDK, tracking pixel or automatic diagnostic uploader. You do not need a Fixnetworks account or a separately billed AI API key.
“Local-first” does not mean “no network.” Connected account operations use your AI provider, optional organisation sync uses Google Chrome Sync, and features you request may contact other destinations as explained below. Fixnetworks does not receive a copy of your library through an extension backend.
Information accessed or stored
| Information | Purpose and storage |
|---|---|
| Conversation text, titles, message roles, available dates, model labels, source links and available image references | Local search, preview, indexing, imports, exports, bookmarks, context insertion and activity estimates. History loading initially obtains metadata; indexing obtains available message content. |
| Project identifiers/names, membership, available native links and verification results | Project filtering, overview and user-directed Project changes; local colours are saved against the Project and account/workspace. |
| Folders, tags, prompts/chains, bookmarks, notes, saved searches, selections and settings | Local organisation and page tools. These fields may contain information you enter about yourself or other people. |
| Account/workspace identifiers, a selected tab identifier and connection display information | Select and revalidate the intended provider account. An identifier can be an email address if the provider does not supply its usual user ID. Some connection metadata is stored locally. |
| Operation results/errors, pending Project actions and locally calculated activity counts | Progress, verification and troubleshooting. There is no automatic upload of these records to Fixnetworks. |
| Local page-tool cache and auxiliary records | Saved prompts, bounded context excerpts, message timestamp/label metadata, settings, pending captures/bookmarks, sidebar selections and per-conversation collapse preferences. Some records include conversation URLs. |
Information comes from supported AI pages and accounts, files you choose to import, and information you enter. Conversations can contain sensitive personal information, including health or financial details. The extension processes their contents for its features rather than deliberately seeking those categories for a separate purpose.
On supported domains with permission, including X when enabled, the extension's page tools read available page content to recognise messages and editors, provide counts/estimates and navigation, and detect response activity. Those reads can happen while the page tools are active, before you request a capture. Capturing a conversation or bookmarking a message saves available page content locally. The extension does not request the browser History API or collect a general browsing-history feed; it does handle supported-page URLs and titles needed for its features.
When information leaves your browser
Connected ChatGPT operations. The extension accesses your existing signed-in session in the selected ChatGPT tab and makes account-checked requests to ChatGPT to load history/messages/Projects and carry out requested moves, archive/unarchive or deletion. Connecting or loading history may also read Project names/membership automatically. Session access tokens are used transiently for these requests and are not deliberately written to extension storage. The extension does not ask you to give Fixnetworks your provider password. Creating or renaming a Project uses the normal website form, which you confirm in ChatGPT, followed by result verification. Provider services process these requests under their own terms and privacy notices.
Prompts and saved context. Inserting a prompt or an excerpt from another locally indexed conversation places it into the selected provider's page editor. A confirmed prompt chain can send its steps automatically. Ordinary inserted text is sent when you submit it. This can disclose content from one provider's conversation to a different provider you choose. Review inserted text and the target account before sending. Page tools cache saved prompts and excerpts from up to 100 locally indexed conversations for use on enabled AI sites. This cache is not separated into per-provider or per-account stores; check the material and target account before inserting it. Inserting this material into a website makes it available to that site’s editor/scripts.
Optional manual Chrome Sync. Choosing Upload organisation in Settings sends folders, saved prompts/chains, tagging rules, saved views and settings to Google's Chrome Sync service, associated with your Chrome profile/account. This is separate from the default local library. The upload object does not include conversation collections, bookmarks, account-session tokens or the Project catalogue/Project colour collection. However, prompts, folder names, keywords and saved-search fields can themselves contain sensitive text or account/Project identifiers. Review them before uploading. Sync is not an encrypted backup supplied by Fixnetworks: its chunk encoding and integrity hash do not provide application-level encryption. Google and Chrome control service storage, synchronisation and retention. The extension does not automatically upload organisation changes.
Downloads, links and read-aloud. PDFs, text exports, archives and backups are generated locally using bundled libraries/fonts, then written or downloaded to the location you choose. A cloud-backed download folder may separately sync those files. Requesting image downloads contacts the HTTPS image URLs found in the available chat data; requests omit explicit fetch credentials, but destination services can receive ordinary connection/request information. Opening original conversations or other links contacts those destinations. Browser read-aloud uses voices offered by your browser/operating system, which may include an online speech service; an online voice may send the selected text to its provider. The extension does not select a separately billed speech API or guarantee that every browser voice works offline.
Support and website visits. The extension does not automatically submit a support ticket or diagnostics. If you contact us or send a screenshot/report, we receive what you choose to send and the contact information supplied by that channel. We use the details you provide to answer your enquiry, investigate the reported issue and keep an appropriate support record. Access to extension support material is limited to the business owner and people authorised to resolve the request. The website contact form sends messages through Resend. Email for the fixnetworks.co.uk domain routes through Microsoft 365; these are separate services. The form has no attachment-upload field. Please initially describe the problem without sending conversation content or sensitive personal information. Visiting these documentation pages contacts our website hosting and delivery services, which receive ordinary connection information such as your IP address and requested page. These four documentation pages do not load Google Analytics. Other pages on the website have separate analytics/cookie disclosures in the website privacy policy. The documentation website is not an extension conversation-storage endpoint.
Permissions
- Storage: save the local library, settings and page-tool cache; support the optional manual organisation transfer through Chrome Sync.
- Scripting: run page tools, obtain account-checked provider data and prepare native Project forms in supported tabs.
- Required site access:
chatgpt.comand the legacychat.openai.comdomain for the ChatGPT connector and page tools. - Optional site access:
claude.ai,gemini.google.com,grok.comandx.com. The current Enable other AI sites control requests these sites together. Their current features are visible-page capture/page tools and local use, not full remote history or bulk account management.
The extension identifies accessible supported tabs to let you choose a connection and open the manager or original chat. Its current manifest does not request the browser History, Cookies, Downloads or broad Tabs permissions. This does not mean it cannot inspect the URLs/titles of supported tabs through granted site access or create browser downloads.
Retention, removal and your controls
Local library records remain in the extension's browser storage until you change/reset them, remove the extension's stored data, or uninstall it. There is no automatic age-based expiry. There is no application-level encryption/password vault for the library or exported backups; protect your device, browser profile and files.
- Clear local data in Settings resets the main local library/settings and saved connection reference, and rewrites the page-tool cache. In version 0.2.4 it does not purge every auxiliary extension-storage key: for example, pending inbox/selection records and per-page collapse preferences may remain. Do not treat this control as a complete erasure of the browser profile's extension data.
- To remove extension-local storage more comprehensively, remove the extension and review your browser's extension-data controls. Device backups or other copies are outside this control.
- Downloaded files and organisation previously uploaded to Chrome Sync are separate copies. Delete exported files yourself and manage synced data using Chrome/Google account controls. There is currently no dedicated Delete synced organisation button in this extension.
- Archiving/deleting a chat remotely is separate from deleting the local library. A remote deletion can leave a locally retained conversation marked as deleted and an operation journal until the library is reset or its stored data is removed. Local reset/uninstall does not delete provider-side chats.
- You can stop using connected features and revoke site permissions through Chrome. Revocation prevents further site access but does not itself erase saved local data or provider-held information.
From this policy’s effective date, we retain ordinary extension support enquiries for up to two years. Diagnostic attachments and screenshots supplied for troubleshooting are deleted within 30 days after resolution, unless they are needed for an ongoing issue or a legal obligation. Where an exception applies, we restrict use to that purpose and retain the material only as long as necessary.
Support and website service providers may process information outside the UK. Resend’s Data Processing Addendum describes its US processing and transfer arrangements, including standard contractual clauses and the UK addendum. Microsoft describes its processing and transfer arrangements in the Microsoft Products and Services Data Protection Addendum. These provider documents describe their arrangements; they do not mean that we promise UK-only storage or that every enquiry uses the same processing location. Contact the privacy address above for information about the providers and safeguards relevant to your request. Your AI provider and optional Chrome Sync also have their own processing locations and privacy notices.
Your rights and legal information
Fix Networks Ltd determines how it handles enquiries and support records it receives. We use those records for our legitimate interests in responding to requests, investigating problems and maintaining the extension, taking account of the impact on the people concerned. We may also retain information where necessary to meet a legal obligation. We do not use support enquiries for unrelated marketing.
We do not receive the local conversation library through the extension. If you use the extension for an organisation or client, you remain responsible for having authority and an appropriate legal basis to handle their information, including any additional conditions required for sensitive information. Do not send sensitive conversation content to support; a redacted description is normally sufficient. Contact us before sharing material that needs special handling.
Where applicable, you may have rights to access, correct, erase, restrict or port your personal information, and to object to certain processing. You may object to processing based on legitimate interests where that legal basis applies. Where processing relies on consent, you can withdraw that consent without changing the lawfulness of earlier processing. These rights depend on the circumstances and applicable law. Contact [email protected] or use our contact page for a privacy request. We cannot retrieve a local-only conversation library from a Fixnetworks server or delete information held independently by your AI provider or Google.
You can also raise a concern with the UK Information Commissioner's Office or your relevant local supervisory authority. The extension does not implement solely automated decisions about legal or similarly significant matters; local tagging, excerpts and activity estimates support your own review.
Limited Use and changes
Our use of information accessed through the extension is limited to its disclosed conversation-management features. We do not sell extension user data or use it for personalised advertising, data brokerage, creditworthiness or lending decisions. We do not operate a service that gives staff access to your local conversation library. If you choose to send support material, access must be limited to the authorised support purpose and the material you provide. Our use and transfer of extension user data adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.
If features or handling practices change, we will update this notice and its effective date. Changes will be published on this page with a revised effective date. Material changes to extension data access or sharing will also be explained in the release notes supplied with the affected update, with any additional permission or consent obtained where required. Review the notice before installing an update; this page does not itself enable new permissions or retrospectively authorise new uses of information.