Official Chrome Web Store Privacy Policy

Privacy Policy

Effective Date: November 2026  ·  Product: TokenPeek (Chrome Extension, Manifest V3)  ·  Contact: noxielabs@gmail.com

100% Local-First Architecture — Summary

TokenPeek runs entirely inside your browser. All DOM inspection, CSS diffing, Tailwind v4 conversion, AI prompt formatting, color clustering, Design Token extraction, and Brand Styleguide PDF generation happen locally on your device. TokenPeek has no user database, no analytics, no telemetry, and no tracking. If you use the Free tier, TokenPeek makes zero outbound network requests.

1. 100% Local-First Processing

Every inspection and export feature in TokenPeek executes exclusively on your local machine inside the active Chrome tab:

2. Data We Do Not Collect

TokenPeek does not collect, log, store remotely, share, or transmit any of the following:

3. Extension Permissions & Why Each Is Required

TokenPeek follows the principle of least privilege. It intentionally does not request <all_urls>, tabs, cookies, history, or persistent host-page background scripts. Below is every permission declared in TokenPeek's Manifest V3 configuration:

Permission Scope Purpose
activeTab Current tab only, upon click Grants temporary access exclusively to the active tab when you click the TokenPeek toolbar icon so the extension can inspect DOM elements and styles on demand. TokenPeek cannot read other tabs or run in the background on pages you visit.
scripting On-demand injection Dynamically injects TokenPeek's isolated Shadow DOM HUD (/content-scripts/content.js) into the active tab via chrome.scripting.executeScript when clicked, and toggles it off cleanly on a second click or when pressing Esc.
storage Local browser profile only Persists lightweight local state inside chrome.storage.local (free Brand PDF export count, one-time review banner dismissal state, and cached Pro license validation state). No data is synced to external servers.
host_permissions:
https://*.workers.dev/*
(narrowed to TokenPeek's dedicated proxy origin in production builds)
TokenPeek License Verification Proxy only Permits TokenPeek's Manifest V3 background service worker to communicate exclusively with our stateless Cloudflare Worker license proxy when a user voluntarily activates, validates, or deactivates a Creem Pro license key, without host webpage CSP or CORS interference. No other external host is contacted.

4. Local Data Stored in chrome.storage.local

TokenPeek stores only the following minimal state locally inside Chrome's extension storage area (chrome.storage.local) on your device:

Storage Key What Is Stored Why It Is Stored
pdfExportCount Non-negative integer (e.g., 0–3) Tracks how many of the 3 complimentary Brand Styleguide PDF exports have been used on the Free tier.
cssCopyCount & reviewPromptDismissed Integer counter & boolean flag Shows a one-time, non-intrusive Chrome Web Store review banner after your 3rd successful "Copy CSS" action and permanently hides it once clicked or dismissed.
tokenpeekLicense Pro license record (isPro, licenseKey, Creem instanceId, tierLabel, activationLimit, lastValidatedAt timestamp, and optional revokedReason) — populated only while Pro is activated Caches your Pro status locally so Pro features unlock instantaneously, supports silent 24-hour background validation with a 7-day offline grace window, and enables 1-click remote device-slot release when you deactivate TokenPeek on a browser. Cleared immediately upon deactivation or revocation.

5. Optional External Network Requests (Creem Pro Licensing)

TokenPeek makes no network requests at all unless you voluntarily enter a Pro license key.

6. Chrome Web Store User Data Policy & Limited Use Compliance

Limited Use Disclosure

TokenPeek's use and transfer of information received from Google APIs and Chrome Extension APIs strictly adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Specifically, TokenPeek guarantees that:

7. Data Retention & How to Delete All Data

Because TokenPeek stores no user data on remote servers, you have immediate and complete control over all local extension data:

  1. Deactivate & Release Your Pro License: Open TokenPeek on any webpage, click PRO ✓ in the floating control bar, and click Deactivate on this browser. TokenPeek releases the browser slot via Creem's API and immediately wipes your stored license key and instance ID from chrome.storage.local.
  2. Delete All Local Extension Data: Open chrome://extensions, locate TokenPeek, and click Remove. Chrome immediately and permanently wipes the entire chrome.storage.local sandbox for TokenPeek (including pdfExportCount, cssCopyCount, reviewPromptDismissed, and tokenpeekLicense).
  3. Purchase & Billing Records: To access or delete billing records held by Creem, use your Creem order receipt or contact Creem under Creem's Privacy Policy.

8. Policy Updates & Contact

If we update this Privacy Policy to reflect new features or regulatory requirements, we will publish the revised version at [GITHUB_PAGES_BASE_URL]/privacy.html with an updated effective date. We will never weaken our core local-first privacy commitment without clear notice.

Questions about privacy, permissions, or data handling? Contact us at noxielabs@gmail.com.