Loupe / Browser extension
Loupe privacy policy
Loupe is a browser extension for previewing images, video, audio and galleries. Keion Davis operates Loupe from Florida, United States, and is responsible for the practices described here. This policy covers the extension, Loupe Pro purchases and key delivery when offered, support communications, and this privacy-policy page.
Overview
The extension does not send browsing history, preview activity or usage analytics to the developer. It contains no advertising or analytics service and does not require a Loupe account. It does process website content and media addresses to provide previews. Media providers receive the requests needed to load their content; browser sync, purchases, support and visits to this website involve separate data handling described below.
Extension data and storage
- Page content and media detection. Loupe reads media links, images, video sources, captions and related page content to find larger media. Some site integrations inspect page-provided media data or relevant network responses, which can contain search terms, public profile information and surrounding content. From version 2.17.3, the broad Google, Lemon8 and Sogou captures are reduced to media records; known authentication and contact fields are filtered from the shared response bridge. Detection and caching can happen while a page loads or changes, before you hover. This processing takes place in your browser; Loupe does not upload these page contents to the developer.
- Media and provider requests. Previews and downloads request files or metadata from the relevant website, media provider, its API or delivery network. Requests can reveal your IP address, browser/request headers, requested media address and, where permitted by the browser, referrer information. Some integrations read page-accessible cookies or request tokens, or use your existing signed-in session with that provider. These are used to resolve that provider’s media, not to sign you in to Loupe. Providers process these requests under their own policies. Hover preparation, gallery navigation and optional preloading may request content before a preview appears.
- Settings and local caches. Loupe stores settings, site allow/pause lists and shortcut preferences using browser extension storage. It also keeps media addresses, captions, metadata and some relevant page/API data in memory to avoid repeated lookups. From version 2.17.3, shared resolver and page-bridge caches use bounded memory rather than the site’s session storage: each cache holds at most 64 entries, with estimated string-data limits of 1 MiB total and 256 KiB per entry. Entries expire after 90 seconds and are not returned after expiry. Cleanup is scheduled every 15 seconds, but the browser can delay background timers. Pausing capture or leaving the page clears those shared caches. Media references already attached to page elements and provider-specific in-memory lookup state can remain until the page closes. Older versions may have left resolver data in site session storage; clear the site’s stored data through your browser if you want that removed. This also affects the site’s own stored data. Browser-managed media caches and restored pages follow browser controls. Settings use Chrome storage.sync; Chrome may synchronize them through your Google account when sync is enabled. The developer has no access to your browser’s settings store.
- Pro keys.A Loupe Pro key contains an identifier, issue date and, for some keys, a display name. The extension checks its signature locally without contacting an activation server. The key is stored separately in Chrome storage.sync and may sync through your browser account. Ordinary settings backups, imports and Restore defaults do not remove it. The signed-key format does not require a customer name or email. Separately issued keys may have a display name; automated delivery uses a derived purchase identifier and date, without a customer name or email in the key.
- Hidden images and backups. If you permanently hide an image, its address is saved in extension local storage so Loupe can skip it. Clear that list in Settings → Privacy. Exporting settings creates a file or text containing your preferences, including any saved site list; you control where you save or share it. Settings exports do not contain your Pro key or hidden-image list.
Permissions and your controls
Chrome’s website-access permission lets Loupe inspect pages and load media across the sites where you permit it to run. The bundled network rules adjust selected media request/response headers so previews can load. Loupe does not request general browser-history or download access on installation.
- History: if you grant the optional history permission and enable the setting, Loupe adds previewed media URLs to your browser history. That history can be synchronized or retained by your browser according to its settings.
- Downloads: if you grant the optional downloads permission, Loupe saves media when you use its save action, including Pro gallery saving. The browser manages downloaded files and download records. Turning this permission off does not delete files already saved.
Turn the history and downloads switches off in Settings → Privacy to revoke those optional permissions. Pause previews for a site, use an allowed-site list, or turn Loupe off. From version 2.17.3, pausing Loupe also disables page-response capture, clears the shared temporary caches and blocks new extension media fetch/Ajax/broker requests; supported in-flight fetch/Ajax requests are aborted. Requests already sent, downloads already started, and the website’s own requests may still finish. Page-level wrappers can remain loaded, but do not retain new response data while paused. Use Chrome’s extension site-access controls, disable the extension or uninstall it to prevent further page access. Browser controls determine whether an extension runs in private/incognito windows; enabling it there does not make provider requests anonymous.
When you use a copy shortcut, Loupe asks the browser to write the media or its address to your clipboard. If you enable the optional “use clipboard text as the filename” setting, its save path may request clipboard text. Browser permission and gesture restrictions apply. This is not continuous clipboard monitoring. Clipboard contents or filenames are not sent to the developer by the extension.
Pro purchases and key delivery
When Loupe Pro is offered, Stripe Checkout with Managed Payments handles checkout, payment, receipts and related billing/tax information under Stripe’s privacy policy. Stripe acts as merchant of record for eligible Managed Payments transactions. The seller can receive normal order details such as customer name or email, order/product identifiers, purchase amount/status and billing or tax details made available by the platform. We use these records to fulfill purchases, help customers, handle refunds/disputes and meet accounting or other legal obligations. The extension does not collect payment-card details. A checkout account, if required by Stripe or its payment services, is separate from Loupe.
The automatic key-delivery service verifies completed purchases with Stripe, issues a signed offline Loupe key, and provides it on the confirmation page and by email. It runs at pro.keiontdavis.com in the maintainer’s Cloudflare account, using Cloudflare Pages/Workers with purchase records in Cloudflare D1. The service processes Stripe account, payment, product and order identifiers and payment/refund/dispute status; it stores the Checkout Session identifier, a derived entitlement identifier, customer email, signed key, purchase date and email-delivery timestamps. These purchase records are kept for ongoing lifetime-key delivery, recovery and support, subject to the removal requests and legal retention needs below. Temporary rate-limit records include counts, expiration times and hashed recovery-email addresses and are deleted after expiration. Resend sends the key emails and receives the recipient address, key, message contents and delivery information. Hosting and email providers also receive ordinary connection information and may retain operational/security logs under their own policies. The service does not store payment-card details or billing addresses. The extension does not send it browsing or preview activity.
Support
If you email support, we receive your email address, message and attachments, and any purchase details you provide. We use them to answer you, investigate the reported issue and administer your purchase. Please send only what is needed and redact sensitive page contents, passwords, session cookies and payment details. A screenshot or diagnostic file you deliberately send can include personal information even though the extension sends no automatic diagnostic reports.
Retention and removal
Extension preferences and hidden-image addresses remain until cleared, reset or removed through browser controls. Remove a Pro key in Loupe Pro settings; Restore defaults does not remove it. Current shared media caches expire and clear as described above. Data left in site session storage by older versions follows the site tab/session lifecycle, and browser restore features can retain it; clear site storage through browser controls if you want it removed. Clear extension data and manage Chrome sync separately where needed. Uninstalling Loupe does not delete downloaded files, browser history entries, exported backups, provider records or emails.
Purchase and support records are retained only for the purposes above, including unresolved support, fraud/disputes and applicable accounting or legal requirements, and then deleted when no longer needed. Provider-controlled billing, hosting, email and browser-sync records follow the relevant provider’s retention rules. We cannot delete records that exist only on your device or at a media provider; the controls and request routes above let you manage them.
Use and disclosure
We do not sell personal information, use it for targeted advertising, or transfer browsing/preview activity to data brokers. Data is used to provide the features you choose, fulfill purchases, provide support, secure the service and comply with applicable legal requirements. We use the browser/media providers, payment platform, hosting and email services needed for those purposes. Information may be disclosed where legally required or necessary to address fraud or security incidents. These exceptions do not authorize unrelated uses of extension data.
This website and other services
This policy page is hosted by Webflow and loads site assets and remotely hosted fonts/scripts, including Google-hosted font resources. Those services receive ordinary web-request information, including your IP address and browser headers, and may process operational logs under their policies. The website can use browser storage for its own display preferences. The extension itself does not load this policy page, its fonts or portfolio scripts automatically. Other websites you visit, including media sites and checkout, have their own privacy practices.
Security and international processing
We restrict the information handled to the purposes described and keep the Pro signing private key out of the extension and public source. Purchase validation uses HTTPS. From version 2.17.3, the background broker rejects requests carrying known credential/token headers or query fields, or request bodies, over plaintext HTTP and prevents redirects on sensitive requests; anonymous background requests omit cookies and the browser referrer by default. Media playback URLs still follow browser security rules, so Loupe does not promise that every third-party image/video address uses HTTPS. Browser storage and sync security depend on the browser, device and account settings. No online service or storage system can promise absolute security. Service providers may process information in the United States or other countries where they operate; their applicable privacy and transfer terms also apply.
Legal bases where applicable
Where EU or UK data protection law applies to our processing, we use the legal basis appropriate to the purpose: performing a contract or taking steps you request before a contract for a Pro purchase and necessary delivery/support; legitimate interests for answering general enquiries, maintaining service security and preventing fraud, subject to your rights; a recognized legal obligation where that basis applies to required records; and consent for optional processing where the law requires consent. A browser permission or acceptance of this privacy policy is not treated as blanket consent to unrelated processing. If required information is not provided, we may be unable to complete a purchase, deliver a key or resolve a support request. The extension’s core previews do not require sending us an email address or creating a Loupe account.
Your privacy choices and rights
Depending on where you live and the law that applies, you may have rights to access, correct, delete or receive a copy of personal information we hold, restrict or object to processing, withdraw consent where processing relies on consent, and complain to a privacy regulator. Contact us using the address below. We may ask for information reasonably needed to verify and fulfill a request, and may retain records we are legally required to keep. For data held only by Chrome, a media provider or Stripe, use that provider’s controls or contact it directly; we can help identify the appropriate route. We do not use personal information for automated decisions with legal or similarly significant effects.
Children
Loupe Pro purchasing and support are not directed to children under 13. If you believe a child has provided personal information to us, contact us so we can address it under applicable law. This statement does not replace parental or browser controls over websites, media or extension use.
Chrome Web Store User Data Policy
Our use of information handled by the extension adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. We use website content and browsing-related data only for the disclosed extension features and permitted operational purposes, not for unrelated advertising or profiling.
Changes
We will publish changes to this policy at this address with an updated date. If a change requires additional notice or consent under applicable law or Chrome Web Store policy, we will provide that notice or obtain consent before the new practice starts. New purchase/key-delivery services must have their actual providers and data practices disclosed before launch.
Contact
Keion Davis is the operator of Loupe, based in Florida, United States. Send privacy requests and questions to keiontdavis.apps@gmail.com.