Privacy Policy for WhoLeakMyName
Effective Date: October 24, 2026
WhoLeakMyName ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how our browser extension processes data. Unlike traditional cloud services, WhoLeakMyName is built on a privacy-first, on-device architecture.
Core Privacy Philosophy
We believe your email tracking habits and data leak history belong solely to you. WhoLeakMyName is designed to function locally inside your browser sandbox. We do not operate central data harvesting databases, and we do not sell, rent, or monetize your personal information or browsing history.
Information We Process (Local Scope)
All critical operations are computed on your local device. The extension interacts with the following data types strictly within your browser environment:
Core Configuration Data: Your primary email address, tagged first/last names, and generated tracking codes are stored directly on your machine using the browser’s isolated local storage api (chrome.storage.local).
Browsing Context & Hostnames: In order to automatically fill registration boxes or generate site-specific tags, the extension checks the domain name of the website you are actively visiting. This context remains isolated inside your running browser tab and is never transmitted out.
Gmail Metadata Headers: For users opting into the automated Leak Alerts feature, the extension uses the authorized "gmail.metadata" permission to check incoming email envelopes (To, From, Delivered-To, and Subject lines) at 15-minute intervals. This loop runs locally inside the service worker. Your email bodies are completely unread, and your communication logs never leave your system.
Information We Collect (External Transmission)
The extension minimizes external network traffic. Transmission only occurs under the following narrow condition:
License Key Verification: When upgrading from the Free Tier to the Pro Tier, the extension sends your entered license activation key to our validation server (https://api.example.com). This request is used solely to confirm your subscription status and does not attach your email data, generated tracking records, or web browsing logs.
Third-Party Access and Authentication
WhoLeakMyName integrates with Google OAuth2 services to fetch temporary operational tokens required for background metadata checks. These tokens are saved securely within the browser runtime. We have no visibility into your Google account credentials, passwords, or primary cloud assets.
Data Security & Storage Controls
Because your data is stored locally in your browser workspace, it is protected by your device's native security systems. You maintain total control over your records. You can instantly wipe all stored domains, aliases, and historical alert logs by using the clear cache features or by uninstalling the extension from your browser manager.
Changes to This Policy
We may update this Privacy Policy from time to time to align with store framework updates. If any future modification introduces structural changes to our data handling, we will notify users clearly through store release updates.
Contact Us
If you have any questions regarding this Privacy Policy or local data boundaries, contact us at: solvemyproblems007@gmail.com