Privacy Policy

Last updated: October 14, 2026.

The Chrome store package supports conversation, shared screens, selected-page assistance, attachments, and local scientific tools. Where separately deployed and enabled, its cloud computer runs approved commands on copied files in a temporary remote Linux workspace. Native desktop control, local terminal/Codex tasks, Monid specialist calls, and image editing are not part of that package. Optional connected-app workflows use account APIs and the providers described below. Separately enabled web or pilot features have the additional handling described below.

The waste-heat recovery API processes the engineering inputs, operating bins and financial assumptions you submit. It stores the normalized decision basis and result under your account for retrieval and safe retries. This deterministic endpoint does not send those inputs to an AI provider. Raw CSV uploads are parsed into operating bins and are not stored as separate files.

Results are available for retrieval for 30 days. Older records are purged on your next assessment request; this is not a scheduled physical-deletion guarantee. You can delete an individual result and its normalized inputs using the API DELETE endpoint. A content-free retry digest and usage count remain for the retry window. Account deletion removes API keys, results and API usage. API keys are stored as cryptographic digests; the complete key is returned only at creation.

Typed prompts, spoken requests, transcripts, replies, and tool results are used to answer you and carry out your current task. With microphone access enabled, audio is sent through Exergy to OpenAI for speech and transcription or to Google Gemini in enabled Gemini voice modes. Both paths can receive conversation context. You can use text without enabling the microphone.

Screen sharing sends repeated images of the screen, window, or tab you choose while sharing and a session are active. Shared pixels, attached images, PDF page images, and browser screenshots can reach Google for image understanding or visual targeting and OpenAI for reasoning. The transfer is not limited to a text description of the image. Sharing a whole screen may include other apps, notifications, or private information visible there.

Browser assistance can list eligible open tabs with their URLs and titles to find the requested page. After browser access is enabled and a tab is selected, it can read page text, controls, field and selection information, screenshots, and action results. This data is sent to Exergy and the model providers needed for the task. Chrome's debugger permission enables reading and input on that tab. Screen sharing and browser control are separate controls; either can expose page content.

When you send an attachment, names, file metadata, extracted text, images, or local inspection results may be sent to Exergy and model providers. Supported document originals are held in the extension's local session file workspace; Python can read copies and return excerpts, calculations, or generated files to the assistant. This is not a promise that the file's contents stay local. Uploading an original to a website sends it to that website after the destination review.

The assistant can generate Python and run it automatically in an isolated browser worker to calculate results or inspect and create file copies. There is not a separate code-approval prompt for every run. The worker has no browser-control APIs, host filesystem, or credentials, and its external network access is blocked. Supplied inputs and file copies are available to that run; its returned output may be sent back through Exergy to model providers.

Running code is not independent scientific verification. Local processing still handles your data, and the surrounding conversation uses cloud services.

Where deployed and enabled, the assistant can run Bash, Python and Node commands in a temporary Linux workspace hosted separately from your device and the Exergy web server. Before each run, you review the exact command, the selected copied file names and sizes, and requested output files. Browser or screen-sharing permission does not authorize this transfer. Declining leaves the command unstarted.

Exergy and the operator's dedicated computer host receive the approved command and selected file copies. Standard output, error text and selected output files return through Exergy; relevant results can enter the assistant's model context. The reviewed image supplies the tools. This version has no outbound network access, package installation, inherited browser cookies, or access to your host filesystem. It does not publish, deploy software or change connected accounts.

The computer has separate command, workspace, resource and daily runtime limits. A successful process exit proves only that the process exited successfully, not that its output is correct or scientifically verified. Stop, a replacement task or End session requests cancellation; the interface must distinguish confirmed termination from an unknown cleanup outcome.

Temporary inputs and outputs are removed when the cloud workspace is closed or expires, subject to cleanup failure. The host retains bounded job receipts and a hashed account identifier with daily runtime reservations for admission and security. Hosting logs, backups and downloaded copies have separate lifecycles. Before this feature is enabled, the publisher must identify the actual hosting operator, region, retention and data terms in this policy and confirm them for the deployed service; prepared code alone does not establish those facts.

To display usage and administer the assistant, Exergy stores account-linked session identifiers, start/end times, duration, numeric quota usage, provider/model names, numeric billing units, pricing-version identifiers and provider cost estimates. These accounting records are kept in the active database for up to 90 days. Estimates are not charges to you or reconciled provider invoices. Unavailable costs remain unavailable; quota credits are not converted into dollars.

Optional task performance analytics is off by default. In the extension's Settings, you can affirmatively enable fixed task outcomes, tool counts, retries, model names, error categories and timings for new sessions. These records measure and improve the assistant's performance and reliability and are retained for up to 30 days. The choice expires after 90 days. A released answer means runtime review permitted delivery; it does not prove your goal was achieved.

Neither record set includes prompts, transcripts, screenshots, URLs, page titles, file names or contents, tool arguments/results, authentication tokens, or raw provider responses. They are sent to Exergy and stored with our existing Render and Neon hosting/storage services. They are not sent to Google Analytics, advertisers, data brokers or model-training services. We do not sell them or use them for advertising, profiling, lending or unrelated purposes.

Settings shows your recent sessions and lets you export your records. Turning task analytics off disables collection and deletes existing optional analytics from the active database; billing/quota records remain until their retention limit or account deletion. Deletion and late reports are serialized so an old report cannot recreate deleted analytics. Removing the extension does not delete server records. Hosting logs, backups and provider records have separate lifecycles. Automated cleanup runs hourly while the gateway is running; a backlog or outage can delay physical removal, and expired records are excluded from reads.

Session records are owner-scoped. We do not provide staff with a per-user analytics dashboard. Human access is limited to your explicit consent for specific support data, necessary security investigations, legal obligations, or aggregated and anonymized internal operational reporting, in accordance with Chrome Web Store Limited Use requirements.

We receive account information such as your name, email address, authentication details, plan, and company settings. The web workspace stores projects, uploaded files, conversation history, analysis runs, reports, feedback, and usage records. Saved company context can be included across eligible projects to answer your requests.

Square handles payment card details on its hosted checkout. Exergy stores billing identifiers and subscription status, not card details. Early-access signups include your email, referral source, and when you agreed to receive email.

Operational records can include timestamps, IP or connection information, browser details, usage counts, error diagnostics, and security events. We use these to provide and secure the service, enforce limits, administer billing, send requested or transactional email, and diagnose failures.

xAI receives microphone audio and bounded dialogue or approved answer text for Grok voice dialogue and speech. OpenAI receives audio for request transcription and speech readback, and conversation and task context for reasoning, including relevant image pixels; enabled legacy OpenAI voice modes also use OpenAI speech. Google receives images and task context for Gemini perception and visual targeting, and audio and conversation context in enabled Gemini voice modes. Answer and action screening can send bounded request, draft, target, or execution-result text to OpenRouter and Inception's Mercury model, or to a configured Jev service. This screening is not independent verification.

Search terms and public-page URLs can be sent to Exa, OpenAlex, or Crossref to find and read sources. Requested analyses, including the Chrome assistant's full-analysis tool and the general web workspace, can use configured text, document, or specialist providers, including DeepSeek, Moonshot, Alibaba's DashScope, Google, OpenAI, and Z.ai models reached through OpenRouter. Render hosts the service, Neon provides database storage, Cloudflare provides network and operational services, Resend sends email, and Square handles billing.

These services have their own data terms and account settings. We do not promise that every provider retains nothing, permits no human review, or never uses data for model training. A request setting such as “store: false” is not proof of those conditions. Do not share data whose handling requires assurances that have not been confirmed for your feature.

If you connect an app in the extension or an enabled web or pilot feature, Composio and that app's provider handle authorization and tool requests. Depending on the permissions you grant, returned data may include email, files, calendar entries, spreadsheets, or other app records. Requested content and results can enter the assistant's model context. Exergy retains connection identifiers and authorization records; Composio manages the connected credentials. Review the app's consent screen before granting access.

Where available, native Companion features use a separately installed local program. Authorized window content, screenshots, app data, selected files, or command results can enter the cloud assistant. A separately approved Codex task sends the selected project code and coding request to OpenAI. These are not required for the Chrome store package.

Approved image editing sends resized pixels and instructions through Monid to Alibaba. We request deletion of the temporary origin upload after processing and retry interrupted cleanup. The issued input link may remain accessible from provider caches for up to one hour; this does not establish deletion of provider processing records or generated output. Other enabled Monid specialists receive the query or inputs identified for that task.

Hosted TabPFN analysis sends prepared table features and targets to Prior Labs only with the feature's external-transfer authorization. Exergy Vault processes the source document in your browser; selected claims and evidence excerpts are sent if you request backend verification.

Exergy Lab will handle extension user data in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. This applies to raw data and data aggregated, anonymized, or derived from it, including browsing data and automatically gathered page content.

We limit use to providing or improving the extension's disclosed technical-assistance purpose and its related operation, security, and reliability. We transfer data only as needed for that purpose, to comply with law, to prevent fraud or abuse, or in a business transfer with your explicit prior consent. We do not sell it, share it with data brokers, use it for personalized advertising, or use it to determine creditworthiness or lending eligibility.

Human access is limited to your explicit consent to read specific data, necessary security investigations, legal requirements, or aggregated and anonymized data used for internal operations as permitted by the policy. These restrictions also limit the permissions granted in our Terms of Service; accepting those terms is not blanket consent to read private content.

Exergy Lab's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Connected Google data is used for the visible features you authorize, with transfers limited to the permitted purposes above and your consent where required. We do not use this data to train generalized AI models. This statement is not a claim of Google OAuth verification or Chrome Web Store approval.

Opening the extension creates or reads a local Free-account credential and contacts Exergy for enrollment and numeric allowance information, before conversation consent. Declining that consent blocks task content and capture, not these account and usage checks. The extension stores this credential, the cloud-consent choice, and interface choices in browser storage. Session storage holds active session identifiers and bounded browser-operation receipts across extension-worker restarts, but not browser restarts. Conversation text, audit events, attachment copies, and download links also live in panel memory. Exported transcripts and downloaded files remain wherever you save them.

Clear text clears the visible conversation and its download links. It does not end the session, erase the panel's audit history, withdraw grants, cancel running work, or delete provider records. Turning off the microphone stops new microphone capture; stopping screen sharing stops new shared frames. Turning off browser control revokes that control, not other sharing.

End session stops capture and local workers, revokes session control, clears local session attachment copies, and requests cancellation and cleanup of the temporary Exergy live workspace. Live workspace and conversation context are held in server memory rather than saved as ordinary account projects. Cleanup can be delayed or fail. Session and numeric usage records remain for accounting and security. Ending a session does not erase visible text, saved downloads, provider records, or changes already made on a website.

In Settings, Reset cloud consent ends the current session, clears panel conversation, audit history, temporary inputs, and download links, and removes the saved cloud-consent choice so the next conversation asks again. It does not delete your account, exported files, Exergy records, or provider records.

Removing the extension or clearing its browser storage removes local data, not Exergy or provider records. For a local Free identity, contact us before clearing storage if you need help identifying backend records for a privacy request. Disconnect apps in connection settings or revoke access in the app's security settings; stopping a conversation does not revoke those account connections or undo completed actions.

Web account and workspace records are kept while needed to provide the service. You can delete projects or request account deletion in Account Settings. Account deletion removes owned workspace content and de-identifies the account; some billing and security records may remain for transaction integrity, fraud prevention, disputes, or legal duties. It is not automatic deletion of connected-provider accounts or copies they hold. Backups, logs, and provider records have separate lifecycles; we do not promise a fixed deletion deadline for them.

We use owner-scoped access, signed sessions, encryption for sensitive saved company and memory text, rate limits, and monitoring. No service can guarantee absolute security.

You can update profile and company information, remove saved company context, delete projects, cancel subscriptions, and request account deletion from settings. Contact us for access, correction, export, or deletion requests, including local Free-account requests. We may need information to confirm which records belong to you.

Optional website analytics uses Google Analytics 4 for page visits and early-access signup events, not assistant conversations or browsing content. The site does not send signup email addresses or form contents to Analytics. Change this choice using Cookie settings in the footer. You can leave the early-access list or opt out of non-essential email by replying or contacting us; necessary transactional messages may still be sent.

Providers may process data outside your country. Exergy Lab is intended for adults and is not directed to children under 18. We will post policy updates here and provide additional notice where required for material changes.

For privacy questions or requests, email info@exergy-lab.com.