Consensus Room by CUSP42 Labs
Last updated: June 13, 2026 · Support: cusp42@gmail.com
Consensus Room is designed as a local-first Chrome extension for user-controlled multi-AI discussions. This policy explains what information the extension uses, where it is stored, and how third-party AI services may receive content when you choose to use them.
Consensus Room may store the following information locally in Chrome extension storage on your own device:
This local storage helps the extension preserve your room state, generate reports, and improve your workflow.
When you use Web Mode, you control which AI web tabs are used. The prompts, room context, and discussion content you send to those tabs may be processed by the third-party AI services you are logged into.
Those third-party services are governed by their own privacy policies and terms. Consensus Room does not control how third-party AI services process content after you send it to them.
When API Mode is available, content sent through provider APIs will be processed by the API providers you choose. Provider API charges, usage limits, and data policies may apply. Optional local models running on your own machine communicate only with your own device.
Consensus Room requests only the permissions it needs to operate the participants and discussions you set up:
| Permission | Why it is used |
|---|---|
tabs | To identify and bind user-selected AI web tabs as Consensus Room participants. |
activeTab | To work with the specific AI web tab you select, alongside tabs and scripting. |
scripting | Used only when needed to support user-controlled interaction with the AI web tabs you bind (typing your prompt and reading the visible answer). |
storage | To save local room state, preferences, participant settings, transcripts, and reports on your device. |
sidePanel | To display the Consensus Room interface in Chrome's side panel. |
notifications | For user-visible extension notifications, such as when an agent needs attention or the final report is ready. |
alarms | For a scheduled local heartbeat so a running discussion reliably resumes if Chrome suspends the extension's background worker. |
declarativeNetRequestWithHostAccess | For one local rule that adjusts the request Origin header so the optional local model integration works. It applies only to the local model endpoint on your own machine (localhost:11434). |
| Host permissions | Limited to the compatible AI assistant pages you select and the API endpoints needed for user-configured workflows, so Consensus Room can coordinate user-controlled AI discussions in Web Mode and future API Mode. Local host access covers optional local model servers. |
Consensus Room uses extension permissions only to provide its single purpose: helping users run user-controlled multi-AI discussions and export consensus reports.
We do not use or transfer user data for advertising, retargeting, interest-based advertising, or unrelated purposes.
We do not allow humans to read user content unless the user voluntarily sends it to us for support.
We do not sell user data.
Consensus Room is designed to keep room data local to your browser unless you choose to send content to third-party AI services. Please remember that any content you send to AI services is subject to those services' own terms and privacy policies.
If API keys are stored locally, users should protect access to their device and Chrome profile.
You can delete locally stored extension data using the extension's "Reset All (Clean Start)" function in the sidebar, or by removing the extension from Chrome. Removing the extension may delete locally stored extension data, depending on Chrome's storage behavior.
Consensus Room is not specifically designed for children. Users should follow the age requirements and terms of the third-party AI services they use.
We may update this Privacy Policy from time to time. The updated version will be posted on this page with a revised "Last updated" date.
For privacy questions or support, contact: cusp42@gmail.com