Privacy Policy

🔒 Privacy Policy

Last Updated: July 2026

✅ Privacy-First 🔐 Local-First Data 🏗️ Built In-House

Welcome to ExtensionHub. Your privacy is important to us. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our Site or use our extensions. Please read this policy carefully. By using ExtensionHub, you agree to the collection and use of information in accordance with this policy.

1. Information We Collect

1.1 Personal Information

We may collect personal information that you voluntarily provide to us when you:

• Contact us via our contact form or email
• Leave comments or feedback on the Site
• Purchase a Monthly Pro subscription (processed by Gumroad — see Section 4)

This information may include your name, email address, and any other details you choose to provide.

1.2 Non-Personal Information

We automatically collect certain non-personal information when you visit our Site, including:

• Browser type and version
• Operating system
• Pages you visit and time spent
• IP address (anonymized when possible)
• Referring website

2. How We Use Your Information

We use the information we collect for the following purposes:

• To provide and maintain our Site — Ensuring ExtensionHub runs smoothly and securely
• To improve your experience — Understanding usage patterns to enhance our content and navigation
• To communicate with you — Responding to inquiries and support requests
• To process subscription purchases — Via Gumroad, our third-party payment processor
• To comply with legal obligations — Meeting regulatory and legal requirements

3. Cookies and Tracking Technologies

ExtensionHub is hosted on Blogger, which may set essential cookies as part of Google's underlying infrastructure to operate the Site. We do not currently run additional analytics or advertising tracking beyond what Blogger's platform sets by default. You can control cookie settings through your browser preferences; disabling cookies may affect certain features of the Site.

🍪 We do not sell or share your personal data with third parties for marketing purposes.

4. Third-Party Services

We use the following third-party services to operate our Site and process payments:

• Blogger/Blogspot — Our hosting platform, operated by Google
• Gumroad — Our third-party payment processor for Monthly Pro subscriptions and license verification. Gumroad has its own privacy policy governing payment and license data.

These third-party services have their own privacy policies, and we encourage you to review them. We do not share your personal information with third parties for their own marketing purposes.

5. Data Security

We take the security of your personal information seriously. We implement appropriate technical and organizational measures to protect your data from unauthorized access, disclosure, alteration, or destruction. However, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.

Extension Privacy Policy

• ExtensionHub extensions do not collect, store, or transmit personal information to our servers, with one exception: verifying a Monthly Pro license key, which sends the license key to Gumroad's servers to confirm subscription status.
• All extensions may store settings and data you enter (such as a trade log or tracked items) locally on your own device to provide the extension's functionality. This local data is not transmitted to us.
• No personal data is sold, transferred, or shared with third parties beyond the Gumroad license check described above.
• Specific data handling for any individual extension is also described in that extension's own guide page.
• If you have questions regarding this privacy policy, contact us through ExtensionHub.app.

6. Your Rights

Depending on your location, you may have certain rights regarding personal information we hold about you — primarily information you've provided directly, such as through our contact form — including:

• Access — Request access to the personal data we hold about you
• Correction — Request corrections to inaccurate or incomplete data
• Deletion — Request deletion of your personal data
• Data Portability — Request a copy of your data in a structured format

To exercise these rights, please contact us.

7. Data Retention

We retain your personal information only for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required or permitted by law. When we no longer need your information, we will securely delete or anonymize it.

8. Age Requirement & Children's Privacy

ExtensionHub is not intended for use by anyone under 18 years of age, consistent with our Terms of Service. We do not knowingly collect personal information from anyone under 18. If we become aware that we have collected personal information from a user under 18, we will take steps to delete that information.

9. International Data Transfers

Your information may be transferred to and processed in countries other than your own, including by our payment processor Gumroad. We take appropriate safeguards to ensure your data is treated securely and in accordance with this Privacy Policy.

10. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date. We encourage you to review this Privacy Policy periodically for any changes.

11. Contact Information

If you have any questions, concerns, or requests regarding this Privacy Policy, please contact us.

Your privacy matters to us. We are committed to protecting your personal information and being transparent about our data practices.

Privacy Policy — UI Context Capture for AI Coders

Last updated: [insert the date you publish this]

This policy describes what UI Context Capture for AI Coders ("the extension," "we," "our") collects, how it's handled, where it's stored, and whether and how it's shared. It's written to describe exactly what the extension's code actually does — not a generic template.

---

1. What data the extension collects

The extension only collects data when you actively use it — clicking the toolbar icon, selecting an element on a page, or configuring a setting. It does not collect anything passively or in the background beyond what's described below.

When you capture a UI element or region, the extension collects:

• A screenshot of the selected region or element, captured from the visible page content in your active browser tab.
• The HTML of the selected element (the outer markup, not the entire page).
• A CSS selector identifying the element's position in the page (tag name, classes, and structural path).
• Computed CSS styles for the selected element.
• Framework and component name, when detectable (a best-effort heuristic check for React or Vue component names — this is not always available and is never guessed if it can't be determined).
• Recent console errors and unhandled promise rejections from the page, captured in a short rolling buffer (recent entries only, not a permanent log of everything the page has ever logged) — since debugging context is often exactly what these captures are for.
• Any custom instruction text you type alongside a capture.

Separately, if you choose to use the optional AI features:

• Your own API key for Anthropic or OpenAI, which you provide and which is used only to authenticate your own requests to that provider.

If you purchase a license, the license key you enter is sent to Gumroad (our payment processor) to verify it — no other captured data is included in that request.

We do not collect: your browsing history, data from tabs you haven't actively used the extension on, your identity, or any information you haven't directly captured or configured yourself.

2. How this data is handled

• All capturing happens only when you initiate it — opening the picker and selecting a region or element.
• Captured data (screenshot, HTML, styles, selector, detected framework, recent console errors) is assembled into a single "capture," which you can view, edit, and copy in the extension's results view before doing anything else with it.
• The anonymize option, if you turn it on, replaces CSS class names in the displayed output with generic placeholders before you copy or share it — this happens locally in your browser and does not change what was originally captured in your history.
• Nothing is transmitted anywhere automatically. The extension's core purpose — producing a clean context block to paste into an AI coding assistant of your choice — requires no network request at all.

3. Where this data is stored

• All captures, your capture history, your saved prompt templates, and your license status are stored using Chrome's built-in local storage (chrome.storage.local and chrome.storage.session) — on your own device, inside your own browser profile.
• We do not operate a server that receives, stores, or has access to any of this data. There is no account system and no cloud sync — everything lives locally, the same way your browser's own bookmarks or history do.
• Your capture history remains on your device until you delete individual entries or clear it entirely from the History page, or until you uninstall the extension, at which point Chrome removes all of the extension's locally stored data automatically.

4. Whether and how this data is shared

• By default, nothing is shared with anyone. A capture stays on your device until you choose to copy it out or use an optional AI feature.
• If you use the "Ask AI" feature, the current capture's content (screenshot, HTML, styles, selector, and any instructions you've added) is sent directly from your browser to the AI provider you configured (Anthropic or OpenAI), using your own API key. This is a direct connection between your browser and that provider — it is not routed through, logged by, or visible to any server we operate. Anthropic's and OpenAI's own privacy policies govern how they handle data you send them through their APIs.
• License verification sends only your license key to Gumroad's license-verification API — no captured content is included in that request.
• We do not sell, rent, or share any of your data with advertisers, data brokers, or any other third party, under any circumstances.

5. Your controls

• View and search all past captures on the History page.
• Delete any individual capture, or clear your entire history, at any time.
• Anonymize class names in a capture's output before copying or sharing it.
• Remove your AI API key at any time from Settings — this immediately disables the AI features until a new key is added.
• Uninstalling the extension removes all locally stored data (captures, history, settings, keys) from your browser.

6. Permissions this extension uses, and why

• activeTab and scripting — to inject the picker only into the tab you're actively using, only when you click the toolbar icon. There is no persistent, always-running content script watching your browsing.
• storage — to save your captures, history, and settings locally, as described above.
• Host permissions on the pages you use the picker on — required so the picker can read the DOM, styles, and console state of the specific element you select. This is not used to read or transmit anything outside of an active, user-initiated capture.

7. Children's privacy

This extension is a developer tool intended for use by software developers and is not directed at children. We do not knowingly collect data from children.

8. Changes to this policy

If what the extension collects or how it handles data changes in a future update, this policy will be updated accordingly, with the "Last updated" date above reflecting the most recent revision.

9. Contact

Questions about this policy or how your data is handled can be sent to [insert your contact email or contact page URL here].

Japanese Font Inspector — Privacy Policy Content

What data this extension collects

Japanese Font Inspector only processes data when you actively use it — clicking the toolbar icon and then clicking an element on a page. It does not run in the background or collect anything passively.

When you inspect an element, the extension reads:

• The text content of the element you clicked (up to 60 characters).
• Its declared CSS font stack, computed style (size, weight, style, line-height, letter-spacing, color, writing mode), and the page's root font size.
• Which script types are present in the text (Kanji, Hiragana, Katakana, Latin, numbers, punctuation, emoji) — computed from standard Unicode character ranges, not sent anywhere for analysis.
• Which @font-face web fonts have finished loading on the page, via the browser's own document.fonts API.

If you use the Pro full-page audit, it additionally reads every text-containing element on the page to build a font-usage report (font name, how many elements use it, and whether it contains Japanese and/or Latin text).

If you use the Pro web-font service detection, it checks the page's own script and stylesheet URLs against a short list of known font-service domains (Google Fonts, Adobe Fonts, TypeSquare, FONTPLUS) to identify which one, if any, the page is using.

We do not collect: your browsing history, data from tabs you haven't actively inspected, your identity, or anything beyond the specific element or page you choose to inspect.

How this data is handled

• All analysis — script classification, fallback-font estimation, style extraction — happens entirely in your browser, on the page you're inspecting. None of it is sent to us or to any third party.
• The fallback-font estimation uses a canvas width-comparison technique to estimate which font in a stack is likely rendering. This is computed locally and never transmitted anywhere; only the final estimate is shown to you.

Where this data is stored

• Inspection results and your history (up to the last 100 inspections) are stored using Chrome's built-in local storage (chrome.storage.local) — on your own device, inside your own browser profile.
• We do not operate a server that receives, stores, or has access to any inspected page content, text, or history. There is no account system and no cloud sync.
• Your history remains on your device until you clear it yourself (a "Clear History" control is available on the History page) or uninstall the extension, at which point Chrome removes all of its locally stored data automatically.

Whether and how this data is shared

• Nothing you inspect is ever shared with anyone. No page content, text, or font data is transmitted off your device, to us or to any third party, at any point — including with the Pro features.
• The only network request this extension ever makes is license verification: if you enter a license key, that key (and nothing else) is sent to Gumroad's license-verification API to confirm it's valid. No inspected content is included in that request.
• We do not sell, rent, or share any data with advertisers, data brokers, or any other third party, under any circumstances.

Your controls

• Uninstalling the extension removes all locally stored data (history, settings, license status) from your browser.
• Settings let you control the UI language, unit preferences, and detection sensitivity — all stored locally and changeable at any time.

Permissions this extension uses, and why

• activeTab and scripting — to read the DOM, computed styles, and font information of the specific tab and element you choose to inspect, only when you click the toolbar icon. There is no persistent, always-running content script.
• storage — to save your inspection history and settings locally, as described above.
• Host permissions on the pages you use the inspector on — required so the inspector can read the font and style information of the element you select. Never used to read or transmit anything outside of an inspection you initiate yourself.

Children's privacy

This extension is a developer/design tool and is not directed at children. We do not knowingly collect data from children.

← Back to ExtensionHub