Privacy Policy
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:
-
Live DOM & Box-Model Inspection: Element hover targeting, open Shadow DOM traversal,
keyboard DOM navigation, and box-model measurement run locally via an isolated Shadow DOM overlay
(
#tokenpeek-root). -
Hidden
about:blankBaseline CSS Diffing: Computed styles are compared locally against browser default styles from a temporary, hiddenabout:blankiframe and parent inherited styles, alongside same-origindocument.styleSheetsrules for:hoverstate extraction. - Tailwind v4 & AI Prompt Formatting: Conversion of clean CSS and component subtrees into Tailwind v4 utility classes, HTML/JSX markup, and compact AI coding prompts is performed purely via local rule-based logic — nothing is sent to any AI provider or cloud API.
-
Color Clustering & Design Token Exports: Perceptual color clustering
(
ΔE < 2.5), HEX/OKLCH/HSL conversions, WCAG AA/AAA contrast calculations (viaculori), and exports to W3Ctokens.json, Tailwind v4@themeCSS, and Figma Variables JSON run locally in memory. -
Client-Side Brand Styleguide PDF Generation: Vector PDF styleguides are compiled entirely
inside your browser using
pdf-liband saved directly to your device. If a Pro user selects a custom PNG or JPG agency logo (up to 2 MB) for white-label PDF export, the image is read strictly in ephemeral browser memory to embed into the PDF and is never uploaded or persisted to storage.
2. Data We Do Not Collect
TokenPeek does not collect, log, store remotely, share, or transmit any of the following:
- Webpage DOM content, text, images, stylesheets, extracted design tokens, or generated PDFs
- Website URLs, hostnames, tab titles, or browsing history
- Personal identifying information (name, email address, account credentials, or hardware fingerprints)
- Browser cookies, session tokens, form inputs, or clipboard contents
- Usage analytics, telemetry events, crash dumps, or third-party advertising trackers
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.
-
Stateless Proxy Architecture & Background Isolation: When you activate, validate (every
24 hours), or deactivate a Pro license key, TokenPeek's Manifest V3 background service worker sends an HTTPS
POSTrequest to our minimal, stateless Cloudflare Worker proxy (/v1/activate,/v1/validate, or/v1/deactivate). The worker attaches our server-side API credential and forwards the request to Creem's License API (https://api.creem.io/v1/licenses/...). Our proxy has no database, performs no request logging, and never receives or stores webpage content, URLs, or personal data. -
Minimal Payload: Requests transmit strictly two fields required by Creem's license lifecycle:
-
/v1/activate: your licensekeyand an anonymous, non-personal browser labelinstance_name(such asChrome · macOS · a7f3). -
/v1/validate&/v1/deactivate: your licensekeyand the opaqueinstance_idreturned by Creem during activation.
-
- Payments & Merchant of Record (Creem): All Pro purchases, invoices, VAT/sales taxes, and refunds are processed exclusively by Creem as Merchant of Record. TokenPeek never receives, processes, or stores your payment card details or billing address. Please review Creem's Privacy Policy for details on how Creem handles purchase transaction data.
- User-Initiated Links: Clicking checkout buttons inside the Pro modal, the optional one-time Chrome Web Store review banner, or legal documentation links simply opens the destination URL in a new browser tab at your explicit request.
6. Chrome Web Store User Data Policy & Limited Use Compliance
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:
- Access to active-tab DOM and CSS data is strictly limited to providing the user-facing CSS inspection, Tailwind v4 conversion, Design Token extraction, and local PDF export features you explicitly invoke.
- No webpage data or browsing data is ever transferred to third parties (the sole external transmission is your voluntarily entered license key and anonymous browser instance ID sent through our stateless proxy to Creem to activate, validate, or deactivate Pro entitlement).
- No data is ever used or sold for personalized advertising, retargeting, data brokerage, or determining creditworthiness or lending eligibility.
- No human (including the developer) reads or receives any webpage content you inspect with TokenPeek.
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:
-
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. -
Delete All Local Extension Data: Open
chrome://extensions, locate TokenPeek, and click Remove. Chrome immediately and permanently wipes the entirechrome.storage.localsandbox for TokenPeek (includingpdfExportCount,cssCopyCount,reviewPromptDismissed, andtokenpeekLicense). - 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.