This Privacy Policy explains how the Email Finder browser extension (“Extension”, “we”, “us”) handles information when you install and use it. By using the Extension, you agree to this policy.
1. Summary
The Extension helps you extract email addresses that appear in Google Search results you run from the side panel, and (if you enable it) from web pages linked in those results. Most data stays on your device. We do not sell your personal information.
2. Data the Extension processes
Depending on your settings, the Extension may process:
- Search inputs you type (keyword, optional site filter, page count, Google domain, options).
- Public web content rendered in tabs the Extension opens or updates (Google Search pages, and optionally destination sites opened from results).
- Derived contact data: email-like strings detected in visible page text and links, plus contextual fields shown in the UI (for example page title, result URL, snippet).
The Extension does not read your email inbox, passwords, or unrelated tabs you do not direct it to open as part of the workflow.
3. Where data is stored
By default, the Extension stores your preferences, in-progress state, and collected results in Chrome local storage under your browser profile. Uninstalling the Extension or clearing extension data removes that local information (unless your browser keeps backups according to its own settings).
4. Network transmissions (remote servers)
The core extraction workflow can run entirely on your device. However, your build may include features that contact servers, for example:
- Account / subscription / payments (for example ExtensionPay or a custom API) if enabled by the publisher. Those services receive only what is needed to authenticate, bill, or enforce plan limits, subject to their own policies.
- Your publisher’s backend, if you connect an account using a token or similar mechanism.
If your installed package does not include such integrations, the Extension may not transmit personal data to our servers for basic usage.
5. How permissions are used
- Side panel: user interface for searches, progress, and exports.
- Tabs: open/update the Google Search tab; optionally open background tabs for result URLs when you enable that mode.
- Scripting: run a small script on permitted pages to read visible content and detect email addresses.
- Storage: persist local settings and results.
- Host permissions (as declared in the manifest): limit which sites the Extension may automate; typically Google Search-related origins plus any API origin required for membership features.
6. Legal basis and acceptable use
Email addresses can be personal data. You are responsible for collecting and using them only where permitted by law (including consent or legitimate interest where applicable), honoring website terms, and complying with anti-spam and marketing rules. Do not use the Extension for harassment, unauthorized scraping contrary to site rules, or sending unsolicited bulk email.
7. Google Search
The Extension automates Google Search navigation that you start. Google may present security checks. Complete them in the browser tab when prompted. Your use of Google is also governed by Google’s terms and policies.
8. Third-party websites
Search results may link to independent sites. We do not control those sites and are not responsible for their privacy practices.
9. Children
The Extension is not directed to children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children.
10. Changes & contact
We may update this policy; the “Last updated” date will change. Continued use means you accept the updated policy.
Privacy questions: privacy@example.com
Publisher page (optional): https://YOUR_GITHUB_USERNAME.github.io/YOUR_REPO/privacy-email-finder.html
Appendix — Chrome Web Store “Privacy practices” (reference)
Use this table as a guide when completing the store questionnaire. Adjust checkboxes if your shipped build differs (for example if you add analytics or a backend).
| Topic | Typical answer for this Extension |
|---|---|
| Does it collect user data? | Yes — it processes email addresses and related context found in pages you choose to load; stored locally. Remote collection only if you enable account/payment features. |
| Data types (examples) | Contact info (email strings), user-provided search parameters, technical state needed to run the workflow. |
| Purpose | App functionality — to display and export addresses you asked the tool to find. |
| Sale of data | No sale of user data by the publisher (state your practice accurately). |
| Encryption in transit | Any optional API calls should use HTTPS in production builds. |
| User control / deletion | Users can clear extension data or uninstall; account deletion depends on your backend if applicable. |