ZMetricsAdd to Chrome

Privacy

Privacy Policy

Last updated: October 18, 2026

This Privacy Policy explains how ZMetrics handles information when you use the Chrome extension and website.

Overview

ZMetrics is a Chrome extension that shows live crypto prices, market caps and 24h changes in a compact popup or floating window. No account is required. This policy describes the information ZMetrics stores locally or in Chrome Sync and the information it sends to CoinGecko to provide market data. In v1.5.0, an optional favorite can also display a compact price in the Chrome toolbar and refresh while the popup and floating window are closed. The version-specific details and controls below apply to v1.5.0; earlier published versions may not include these features.

All data we collect and process

ZMetrics processes watchlist and display preferences; selected asset IDs, currency and market-data requests; search text sent to CoinGecko when you search for an asset; and coin IDs, symbols and icon URLs returned by CoinGecko and selected for a custom asset. Network and service providers may also process ordinary request metadata such as IP address, browser information and request time. ZMetrics does not use this information for personalized advertising or sell it. Version 1.5.0 also processes the optional favorite asset ID, a session-only favorite quote, local Radar viewed-state and the locally accepted public terms version, as described below.

chrome.storage.sync data

The extension stores enabled asset IDs, custom asset IDs, custom symbols, custom icon URLs, removed default asset IDs, asset order and selected currency in chrome.storage.sync. Chrome may synchronize this data across the user's Chrome profile using Chrome Sync. ZMetrics uses it to restore preferences and the watchlist. The extension does not store account credentials or analytics data in chrome.storage.sync. Version 1.5.0 additionally stores favoriteCoinId, the optional favorite cryptocurrency. Favorite selection may synchronize with your other Chrome profiles/devices according to Chrome Sync settings; terms acceptance and favorite quotes do not.

CoinGecko data sharing

To provide prices and market data, ZMetrics sends the selected asset IDs, selected currency and the requested 24-hour price-change field to CoinGecko's markets API. The same request also includes BTC as a comparison benchmark when it is not selected; this does not add BTC to your saved watchlist. Radar analyzes these market responses locally to compare assets and calculate equal-weight watchlist observations. No watchlist analysis or Radar observations are sent to ZMetrics or an AI provider. When you search for an asset, the search text is sent to CoinGecko's search API. CoinGecko responses are processed temporarily in the extension to display prices and search results. Selected search results may be stored as custom asset ID, symbol and icon URL in chrome.storage.sync. Coin images may be loaded from CoinGecko-hosted URLs. CoinGecko may receive normal request metadata under its own privacy policy. In v1.5.0, favorite-price requests also include the favorite asset ID, currency and BTC benchmark and can be sent in the background with both views closed. The requests do not include the local terms-acceptance value or Radar viewed-state. API and image recipients can see your IP address, browser/network details and request time; HTTPS protects the connection but does not hide a request from its recipient. Public market quotes are not your wallet holdings or transactions.

Favorite price and automatic requests (v1.5.0)

Selecting a favorite enables its Chrome toolbar badge and background refresh. With a tracker view open, market data normally refreshes about every 60 seconds using shared caching. With a valid favorite, the service worker schedules a repeating Chrome alarm of about five minutes plus a quote-expiry alarm; startup, preference changes or expiry may cause another request sooner. A still-fresh shared/session quote can avoid a duplicate request. Closing the popup and floating window does not stop favorite refresh. An empty selection with no valid favorite makes no market request. Clear the favorite to stop this background feature; disable or remove the extension to stop extension requests altogether. A favorite synchronized from another device can also enable it after terms have been accepted locally.

Alarm timing and quote freshness (v1.5.0)

Chrome controls alarm delivery; these are approximate schedules, not a real-time price feed or an exact request every five minutes. Network conditions, API limits and Chrome/device suspension can delay work. The favorite controller accepts provider quotes less than five minutes old and normally schedules expiry 30 seconds before that age limit. Missing, stale or failed refreshes clear the numeric badge when the controller runs. Alarms do not wake a sleeping device, so an old badge may remain visible while Chrome or the device is suspended. The tooltip shows the provider quote time; it is not a trading guarantee.

Local Radar viewed-state (v1.5.0)

Keys beginning zmetrics_radar_seen_v1: store true-only flags for viewed observation types, asset IDs and directions. They keep Radar observations from being repeatedly presented as new. They contain no full price history, timestamps or user identifier. ZMetrics does not transmit these flags or synchronize them through Chrome Sync. They remain locally until extension data is cleared or the extension is removed, subject to Chrome behavior.

First-use terms acceptance and existing users (v1.5.0)

Before market/search requests, v1.5.0 asks you to review its bundled Terms and Privacy and select Accept terms and continue. This also applies on first opening after an upgrade from v1.4.8, which did not store this acceptance. It does not erase your existing watchlist, currency or Radar viewed-state. The key zmetrics_terms_accepted_version stores only the accepted public terms version, currently 1.5, in chrome.storage.local, without a timestamp or user identifier. It is not synced or transmitted. Reopening either view in the same profile does not ask again while that version remains accepted; another profile/device or clearing local extension storage requires acceptance there. If you do not agree, close or remove the extension; market/search requests stay blocked. The local Terms and Privacy pages require no website visit. Following an external provider, privacy or social link is a separate user-requested website visit.

Marketing tracking

External publication links may attribute visits to a specific campaign. After validating a signed campaign token, zmetrics.net stores a random temporary session ID and campaign attribution in sessionStorage for the current tab's session. This attribution follows navigation between website pages without cookies, fingerprinting or IP-derived identifiers. Supabase stores the campaign link ID, event type (website visit or Add to Chrome click), random session ID, website page path and timestamp. We count each session's visit once and use unique sessions that click Add to Chrome to calculate campaign conversion. Multiple clicks may be recorded for the same session. Direct visitors without a valid campaign token do not generate campaign events. Buttons link directly to the official Chrome Web Store, even when tracking fails. This system uses no Google Analytics or Google Tag Manager and sends no telemetry from the extension. Historical redirect records may also contain a source, campaign, timestamp and referrer; those records are kept separately from session-based campaign analytics.

Website storage and cookies

Campaign attribution uses sessionStorage, not cookies, and normally clears when the tab's session ends. Attribution tokens also expire after a maximum of seven days. Browser session restoration may preserve sessionStorage. The website repository includes a separate sidebar interface preference cookie; it is not used to identify visitors or attribute marketing campaigns. This policy does not claim that all website functionality or infrastructure is cookie-free.

Vercel and website logs

When you visit zmetrics.net, Vercel and other website infrastructure providers may process standard operational metadata such as IP address, user agent, request time, status and network information. The Chrome extension does not send telemetry or marketing tracking requests to zmetrics.net or Supabase. Each provider controls its own operational logs under its applicable settings and privacy policy.

Chrome Sync and local browser processing

ZMetrics uses chrome.storage.sync for watchlist and display preferences. It uses chrome.storage.session to remember the ID of its floating window while the browser session is active, with chrome.storage.local as a fallback when session storage is unavailable. It uses the chrome.windows API to create, find and close the floating tracker window; this does not require a separate windows permission. It uses chrome.tabs.create only to open user-requested Chrome shortcut settings and X links; it does not declare the tabs permission and does not read tab URLs, browsing history or page content. The api.coingecko.com host permission is used for market prices and searches. There are no content scripts. Version 1.5.0 also uses the alarms permission to schedule favorite refresh and quote expiry. It stores the favorite quote only in chrome.storage.session, with no persistent local fallback for that quote. Local Radar viewed-state and terms acceptance use chrome.storage.local.

Information we do not collect

The Chrome extension does not collect or transmit browsing history, visited domains, active page content, cookies, form data, wallet addresses, balances, payment information, GPS/device-location coordinates, contacts, files, page titles, email addresses, passwords or authentication tokens. It does not create analytics identifiers or send telemetry. Website campaign attribution records only the campaign events described above, not browsing activity outside zmetrics.net, and does not profile users across websites. This does not mean that no data leaves your device: CoinGecko receives the requests and network metadata described above, and Google may process synchronized preferences. ZMetrics does not derive your geographic location or monitor your activity on other websites.

Data retention

Preferences and custom watchlist data remain in chrome.storage.sync until you change them, clear the extension's stored data or remove the extension, subject to Chrome Sync behavior. The floating-window ID is kept only for the active browser session when chrome.storage.session is available, with a local fallback if necessary. CoinGecko and website infrastructure providers retain request or operational data according to their own settings and policies. ZMetrics does not control those provider retention periods and does not make a fixed retention promise for them. In v1.5.0, the favorite quote is session-only: its asset ID, currency, price, provider/fetch timestamps and ordering value may survive service-worker suspension but clear according to the Chrome session-storage lifecycle, including browser restart, extension reload/update or disabling. Invalidated quotes are removed as the controller processes changes or expiry. Radar viewed-state and the accepted public terms version remain in local extension storage until that data is cleared or the extension is removed, subject to Chrome behavior. Shared market-response caches in worker/view memory are temporary, not a durable market-history database.

User deletion rights and choices

You can remove locally stored preferences and the floating-window ID by clearing the extension's stored data or removing the extension, subject to Chrome Sync behavior. You can also remove or change individual watchlist and display preferences from the extension settings. To ask about data controlled by ZMetrics, contact support@zmetrics.net. Deletion from CoinGecko, Chrome Sync, Vercel or other third-party systems is subject to the relevant provider's systems and policies and may require a separate request to that provider. In v1.5.0, clear the favorite using its star control, or disable/remove the favorite asset, to clear its displayed quote and stop its favorite background refresh schedule. Market requests can still occur while a tracker view is open. Clearing local extension data also resets Radar viewed-state and terms acceptance; acceptance is then required again before market/search requests. Chrome Sync copies and provider logs may require separate deletion steps; uninstalling is not a promise to erase all copies held by Google or providers.

Campaign data retention

Browser attribution is temporary and session-based, but server-side campaign event records and historical redirect records are not removed when you close a tab. No automatic deletion period is currently configured for these records. For questions or deletion requests, contact support@zmetrics.net. We do not use campaign session IDs to identify a named person.

Data security

ZMetrics sends market-data and search requests over HTTPS. The extension contains no account credentials, authentication tokens or analytics service credentials. No passwords or authentication tokens are sent to CoinGecko or any analytics provider. No security measure can eliminate all risk, so users should keep their Chrome profile secure.

Chrome Web Store Limited Use compliance

ZMetrics complies with the Chrome Web Store User Data Policy and Limited Use requirements. User data is used only to provide, secure and maintain the extension's single purpose, quick cryptocurrency price tracking. ZMetrics does not sell user data or use it for personalized, retargeted or interest-based advertising. Data is transferred only when necessary to provide the extension or comply with law and security requirements.

Contact

For privacy questions, access or deletion requests, contact support@zmetrics.net. Please do not send passwords, authentication tokens or other sensitive credentials by email.

Changes to this Privacy Policy

We may update this Privacy Policy when ZMetrics changes or when additional clarification is needed. We will update the date shown on this page and describe material changes here. If an update materially changes how the extension handles user data, we will provide an appropriate prominent notice in the extension or its store materials before applying the new practice where required. Your continued use of the extension after an update means the revised policy applies to future use. This website policy does not replace the bundled service terms: v1.5.0 explicitly requires local acceptance of those terms before market/search requests. Continued website use is not recorded as extension terms acceptance.