export default { async fetch(request) { const url = new URL(request.url); if (url.pathname === "/privacy" || url.pathname === "/privacy/") { return new Response(` Privacy Policy – Timezoner

Privacy Policy for Timezoner

Effective Date: March 8, 2026

Timezoner ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how our Chrome Extension collects, uses, and safeguards your information.

Because Timezoner is designed for sales professionals and operates on Customer Relationship Management (CRM) platforms, we have engineered the extension with a "local-first" architecture to ensure maximum data privacy and compliance.

1. Information We Collect and How We Use It

We only collect the minimum amount of data necessary to provide our services.

A. Local Page Scanning (No Data Leaves Your Browser)

To function, Timezoner requests permission to read the text on the web pages you visit.

The extension scans the page locally for area codes, phone numbers, and ZIP codes to calculate the correct timezone.

Zero Payload: This scanning happens entirely offline within your browser using local databases. We do not transmit, log, or store any names, phone numbers, emails, CRM data, or personal information from the websites you browse.

B. External API Requests (Pro Users Only)

If you are a Timezoner Pro user and have the "Live Weather" feature enabled, the extension must contact our external servers to fetch weather data.

When this happens, the following specific data points are sent to our secure Cloudflare servers:

Your License Key: To verify your active Pro status.
An Anonymous Device ID: A randomly generated string (UUID) created by your browser to lock your license to your specific hardware and enforce usage limits.
Geographic Query: The specific State abbreviation (e.g., "FL") or ZIP code needed to fetch the weather. We never send full phone numbers or lead data to our weather API.

C. Local Browser Storage

Timezoner uses your browser's native chrome.storage (both local and synced) to save your personal preferences. This includes:

Theme settings (Dark/Light mode).
UI preferences (e.g., 24-hour time, emoji visibility).
Feature toggles (e.g., enabling/disabling ZIP code scanning).
Domain blocklists (websites where you have disabled the extension).

This data is stored locally on your machine and/or synced via your Google account. We do not have access to this data.

2. Information Sharing and Disclosure

We do not sell, rent, or trade your personal information or browsing data to third parties. We do not use third-party analytics trackers (like Google Analytics) or advertising pixels within the extension.

3. Data Retention

Server Data: License validation checks and API request logs on our Cloudflare servers are transient and used strictly for rate-limiting and abuse prevention.

Local Data: Your settings and preferences remain in your browser's local storage until you uninstall the extension or clear your browser data.

4. Security

We take reasonable measures to protect your information. API communications between the Timezoner extension and our validation servers are encrypted via HTTPS.

Furthermore, our extension architecture strictly isolates injected CSS and JavaScript to prevent cross-site scripting conflicts.

5. Your Choices and Controls

You have full control over how Timezoner operates:

Disable on Specific Sites: You can disable the extension on specific domains from the popup.
Toggle Features: You can disable phone scanning, ZIP scanning, or weather fetching in settings.
Uninstall: Removing the extension deletes all locally stored preferences and the anonymous Device ID.

6. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. If significant changes occur, we will notify users via extension updates or our website.

7. Contact Us

If you have questions about this Privacy Policy or our data practices:

Email: support@verileads.net
Website: verileads.net

`, { headers: { "content-type": "text/html; charset=UTF-8" } }); } return new Response("Not found", { status: 404 }); } };