A short list we can prove in code.

The negative spec for this build. Each clause maps to a storage or network boundary in the repository.

• Prompt text in analytics. The extension ships no analytics SDK. Server operations store token counts, not content.
• Your whole page. The adapter reads the editor; optional selection context is limited to the selected text.
• API keys. Model credentials exist only in backend environment variables.
• Email addresses on install. Nothing is requested at install time.
• Browsing history. Only chatgpt.com is permitted, and the extension does not query tabs.
• Your history to our server. History stays in local extension storage and can be cleared.