Single purpose
AI Runtime provides one Chrome extension runtime that lets user-approved web apps and Chrome extensions send AI requests to configured local or cloud AI providers. Its purpose is to help developers add AI features to browser-based apps through a controlled bridge while keeping provider configuration and API keys in the extension instead of exposing them in frontend code.
Who controls the data
The user controls which providers are configured, which websites or Chrome extension IDs are authorized to call the runtime, which model is selected, whether API keys are saved, and whether local audit entries are cleared. The developer does not operate a separate server that collects extension runtime data.
Data the extension may handle
Depending on user configuration and use, AI Runtime may handle these categories of data:
- Authentication information: provider API keys, provider base URLs, selected model names, and provider settings.
- Communications and user-provided content: prompts, chat messages, generated responses, and files or attachments that a trusted caller sends to the runtime for AI processing.
- Website content selected for AI processing: text, images, documents, or other content passed by an authorized web app to the extension.
- Technical metadata: authorized hostnames or extension IDs, provider status, request timing, response status, token or usage metadata returned by providers, and runtime errors.
AI Runtime does not intentionally collect health information, financial or payment information, precise location, browsing history, keystrokes, mouse movement, or unrelated user activity.
Where data is stored
Extension settings are stored in Chrome extension local storage on the user's device or browser profile. This can include provider settings, API keys, authorized caller rules, model preferences, privacy preferences, and local audit metadata.
The local audit log is limited to recent runtime calls and is intended for debugging provider behavior. Prompt and response content is not stored in the audit log by default. If the user enables any optional content logging setting, that content remains in Chrome extension local storage and can be cleared by the user.
How data is used
Data is used only to provide the extension's stated AI runtime bridge functionality: validating trusted callers, selecting a configured provider, attaching provider credentials when needed, sending AI requests, returning responses to the trusted caller, showing provider status, preserving local preferences, and displaying local audit information for troubleshooting.
AI Runtime does not use user data for advertising, user profiling, creditworthiness, lending decisions, resale, or any purpose unrelated to the extension's single purpose.
Sharing and provider processing
AI Runtime does not sell user data. The developer does not transfer extension runtime data to third parties except as needed to provide the user-selected AI provider functionality or to comply with applicable law.
When the user chooses a cloud AI provider, prompts, messages, attachments, selected files, and relevant request options are sent over HTTPS to that provider so it can generate a response. Supported cloud provider adapters may include OpenAI-compatible providers, OpenRouter, Anthropic, Hugging Face-hosted resources, or other endpoints the user configures. Those providers process data under their own terms, privacy policies, and account settings.
When the user chooses a local provider, data is sent to the configured
local endpoint, such as Ollama or LM Studio. Local endpoints may use
local HTTP addresses such as http://localhost. When
WebLLM is enabled, model files may be downloaded from model hosting
sources and inference runs locally in the browser profile.
Permissions used by the extension
AI Runtime requests Chrome permissions only for its runtime bridge purpose:
- storage: saves local provider settings, API keys, authorized callers, preferences, and audit metadata.
- declarativeNetRequest: supports packaged browser request rules needed for compatible local provider traffic, such as Ollama CORS handling.
- offscreen: supports local WebLLM execution in an offscreen extension document when enabled by the user.
- management: helps display information about trusted Chrome extension callers that the user has configured by extension ID.
- host permissions: allow the background runtime to reach user-selected local and cloud AI provider endpoints and allow approved integration pages to communicate with the runtime.
Remote code
AI Runtime does not load or execute remote JavaScript or remote WebAssembly as extension code. Extension code is packaged with the submitted extension. Network requests are used for configured AI provider APIs, local endpoints, and model or provider resources needed by the runtime.
User choices and deletion
Users can remove API keys, disable providers, change provider endpoints, remove authorized websites or extension IDs, clear local audit entries, and uninstall the extension at any time. Uninstalling the extension removes extension storage according to Chrome's normal extension storage behavior.
Security
Cloud provider calls use HTTPS when sent to HTTPS provider endpoints. API keys are stored in Chrome extension local storage and are attached by the background runtime instead of being intentionally exposed to trusted web pages. Users should authorize only websites and extensions they trust, because authorized callers can send content to the runtime for AI processing.
Chrome Web Store Limited Use statement
AI Runtime's use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. AI Runtime uses user data only to provide or improve its single purpose, transfers data only as needed to provide that purpose or comply with applicable law, does not sell user data, and does not use user data for personalized advertising, creditworthiness, lending, or unrelated purposes.
Children
AI Runtime is a developer tool and is not directed to children. The extension does not knowingly collect data from children.
Changes to this policy
This policy may be updated when the extension's providers, permissions, data handling, or published functionality changes. The "Last updated" date will be revised when material changes are made.
Contact
For privacy questions about AI Runtime, contact: gallegofalconpablo@gmail.com.