Chrome extension “Aisle — AI Shopping Assistant” (Manifest V3). Last updated:
.
This page describes how the Aisle extension handles data. It is not legal
advice; you may adapt it with counsel for your situation.
Data collection
No Aisle backend for end users. There is no Aisle
account, telemetry pipeline, or central database of your browsing operated
by this extension’s publisher for normal use of the extension.
API keys are stored only in the extension’s
chrome.storage.local on your device (Chrome’s extension
storage). They are not written into web pages, shared with other
extensions, or logged by Aisle.
Page content (URLs, titles, extracted product cards, and
similar snapshot text) may be included in prompts sent
directly from the extension’s service worker to
Anthropic or OpenAI over HTTPS,
depending on which provider and model you select. That data is subject to
the provider’s privacy policy and retention rules.
Third parties
Anthropic (api.anthropic.com) when you choose Claude and save an Anthropic API key.
OpenAI (api.openai.com) when you choose OpenAI and save an OpenAI API key.
No other remote endpoints are required for core functionality. Optional
custom shopping sites use host access only for URL
patterns you add in Settings, after you grant permission in Chrome.
User control
You may replace or delete API keys at any time in Settings.
You may stop a research run, clear custom sites, and uninstall the
extension (which removes local extension storage managed by Chrome).
Remote code
The extension does not download or execute remote code.
Application logic ships inside the packaged extension bundle (Manifest V3).
Contact
Use the support email or URL shown on the
Chrome Web Store listing
for this extension (replace this sentence with your published support link
if you host this file elsewhere).