Loupe ("the extension") is a browser extension for pixel-perfect UI inspection. This policy describes what data the extension handles and how.
Summary
Loupe runs no analytics and no telemetry, and the developer never receives your inspection data or browsing activity. Everything you inspect is processed on your device. Data leaves your device in only three cases, all described below: your email address when you buy or sign in to Loupe Pro (handled by our payment provider), and — only at your explicit request, using credentials you supply yourself — the optional Figma and AI integrations.
Data disclosures
For clarity, these are the only categories of data that ever leave your device, matching the disclosures on our Chrome Web Store listing:
- Personally identifiable information — your email address, if you start a trial, sign in, or purchase Loupe Pro. Collected by our payment provider ExtensionPay for license verification and receipts.
- Authentication information — your own Figma personal access token and/or Anthropic API key, if you choose to use those integrations. Stored on your device and transmitted only to the service each one belongs to.
- Website content — if you request an AI explanation of a design difference, the element's CSS selector and label, the matched Figma layer name, and the specific CSS property differences are sent to Anthropic using your own API key. Nothing is sent unless you click to request an explanation.
We do not sell or transfer any of this data to third parties, do not use it for anything unrelated to Loupe's single purpose, and never use it for creditworthiness or lending purposes.
Data storage
- All extension state (active tool, grid settings, recent colors, per-tab on/off state) is stored locally in your browser using Chrome's extension storage. Session-scoped state is deleted automatically when the browser closes.
- If you use the optional Figma comparison feature, the Figma personal access token you enter is stored in Chrome's local extension storage on your device only.
- If you use the optional AI explanation feature, the Anthropic API key you enter is stored in Chrome's local extension storage on your device only.
- Tokens are never transmitted anywhere except to the API they belong to (see below). You can delete them at any time from the extension's Design panel, or by removing the extension.
Network requests
Loupe makes network requests only in these cases, always initiated by you:
- api.figma.com — when you connect your Figma account and fetch a frame for design comparison, using your own Figma personal access token.
- api.anthropic.com — when you request an AI explanation of a design difference, using your own Anthropic API key. The request contains only what is needed for the explanation: the element's CSS selector and label, the matched Figma layer name, and the differing CSS property values. No page text, screenshots, or full page source are sent.
- Your team's own servers (Design System Profiles) — if you import a design-system profile that declares an update URL, Loupe re-fetches that profile JSON from that URL (a plain GET, no user data attached) about once a day to stay current. If the profile declares a reporting endpoint and you click "Send to team" after an audit, the audit result is POSTed to that endpoint: rule findings (CSS selectors, offending class names, colour values), the page URL, the profile id, and the extension version — never tokens, API keys, cookies, or page text. Reports are only ever sent on your explicit click, and both URLs are declared by the profile you imported — Loupe operates no server and receives nothing.
No other network requests are made, except license verification (below). Page content you inspect is processed entirely on your device.
Payments and licensing
Loupe's Pro features are sold through ExtensionPay (extensionpay.com), with payment processing by Stripe. When checking your license status, the extension contacts extensionpay.com with an anonymous installation identifier; if you sign in or purchase, ExtensionPay associates that identifier with your email address for license lookup and receipts. Payment card details are handled entirely by Stripe and never reach the extension or the developer. No page content, inspection data, or browsing information is ever included in license checks. See ExtensionPay's privacy policy and Stripe's privacy policy.
Permissions
- Access to websites (
<all_urls>) — required so the inspection overlays (box model, rulers, measurements) can run on whatever page you choose to inspect. Loupe does nothing on a page until you enable it for that tab. debugger— used exclusively for device emulation: Responsive Mode (viewport, touch, and user-agent emulation applied to the tab you choose) and breakpoint comparison (temporarily reflowing the page to each breakpoint width). Chrome displays a visible notice while this is active, and the session ends when you exit. No page data is read through the debugger.tabs,storage,sidePanel— used for per-tab enablement, saving your settings locally, and showing the inspection side panel.alarms— schedules the daily design-system profile refresh described under "Network requests". No data leaves your device on that schedule beyond the plain GET of the profile URL you configured.
Data sharing and sale
Loupe does not sell, share, or transfer user data to third parties. The developer receives no inspection data, page content, or browsing history at any time. The limited data described under "Data disclosures" is handled only by the service it is sent to — ExtensionPay/Stripe for licensing, and Figma or Anthropic for the integrations you choose to enable with your own credentials.
Uninstalling
When you remove Loupe, Chrome opens a short feedback page on getloupe.org asking why. The request carries no identifiers, no query parameters, and nothing about your install or browsing — it is an ordinary page visit, covered by the website section below. Answering is entirely optional (it composes an email in your own mail app); closing the tab is a complete answer.
The getloupe.org website
This website (getloupe.org) uses Google Analytics to measure page visits — standard, aggregate web statistics such as page views and referrers. This applies to the website only: the Loupe extension itself contains no analytics or tracking of any kind, as described above. The licence-delivery page never sends its payment session reference to Google.
Changes
Any material change to this policy will be published at this URL with an updated effective date.
Contact
Questions about this policy: contact@getloupe.org