In 30 seconds
- Lookups go directly from your browser to the provider you configure — there is no SenderFinder server in the lookup path.
- Keys, cache and history stay on this device, in the extension's storage and your browser's IndexedDB. You can export them or wipe them in one click.
- A provider receives the address you look up, the display name from the mail header and the company domain. Nothing else.
- The mail body never leaves your browser: the signature scan runs locally.
- Usage counts are on by default: one anonymous daily summary of counts, outcomes, spend, version and language plus a random installation ID, sent to the project’s statistics service. One switch in settings turns it off and deletes the installation ID. Never an address, name, domain, profile field, key or message text.
- You control which providers to configure and which people to look up. You can disable statistics, revoke LinkedIn access, and export or delete local data; the policy below explains what each feature reads and where it goes.
Who runs SenderFinder
SenderFinder is an open-source Chrome extension. Lookup requests go directly from your browser to the data provider you configure; there is no SenderFinder server in the lookup path. A separate statistics service receives one anonymous daily summary, on by default and switchable off in the settings page. The data controller for those statistics is Tony Li, maintainer of astonysh/SenderFinder. For privacy requests, contact tony@senderfinder.com.
What the extension reads and keeps
In Gmail or Outlook on the web, the extension reads the open message’s sender and participants. It scans the message body locally to find a LinkedIn profile URL, for example in a signature. The body is not stored and is not transmitted. Lookup history, results, settings and provider keys are stored locally in the extension or browser. Cached results expire after 90 days by default, with a limit of 5,000 entries; you can export or delete them in Settings.
What data providers receive
When a lookup runs, the selected person’s email address, display name and company domain are sent directly to the provider you configured, using that provider’s API key. Some providers are aggregators and may forward the request to their listed downstream services; their terms and privacy policies apply. SenderFinder does not receive lookup addresses or provider results. Professional profile fields returned by a provider are kept locally; phone numbers and personal email addresses are discarded.
Anonymous usage statistics
Usage statistics are on by default. Once a day the extension posts one summary of the previous day to our Cloudflare Worker, which stores it in Cloudflare D1. The summary includes the date, extension version, interface language, lookup totals and outcomes, provider-step counts, mail-client totals, rounded spend and a random installation ID. The ID identifies an installation, not a person. One switch in the settings page turns the summary off and deletes the installation ID and anything unsent; the preview button next to it shows exactly what would be sent.
The summary contains no email address, name, company domain, LinkedIn URL, profile field, provider key or message text. You can preview the exact payload in Settings. Turning statistics off stops future sends and deletes the local installation ID and unsent summaries. To request deletion of previously received summaries, contact tony@senderfinder.com with the installation ID shown in the preview.
If you enable a LinkedIn feature, the extension asks for the optional linkedin.com permission on first use; you can revoke it in settings at any time, and it only applies to tabs the extension opens itself. With it, the extension uses your own LinkedIn session to request the connection degree, any pending invitation, the profile photo and the associated company links for the profile you are reading. It reads the JSESSIONID authentication cookie locally as the CSRF value for those requests; the cookie is sent only to LinkedIn, never to SenderFinder or an enrichment provider. Results are cached on your device and sent to no one. When you choose Connect, the extension opens the selected profile and, in the invitation dialog, clicks “Add a note” once and fills your editable template. It never clicks Connect or Send.
Your choices and Chrome Web Store policy
You choose which data providers and API keys to configure, and which people to look up. You can remove keys, switch statistics off, revoke LinkedIn access, export or clear local history, or uninstall the extension. SenderFinder uses mailbox data only to display and perform the lookup you request. Email body text is processed locally only to find a LinkedIn profile link; it is not used for advertising and is not sent to SenderFinder or a provider.
Cookies and local storage
This section describes the SenderFinder website, not the extension. The extension sends one anonymous daily usage summary, on by default and switchable off in its settings. The website itself uses local browser storage as described below.
Today this website sets no cookies. Two entries in your browser's localStorage are used, both only because you asked for them: el-theme remembers the Light or Dark choice from the header, and sf-notice remembers that you closed the notice at the bottom of the page. Neither is ever sent anywhere, and clearing site data in your browser removes both.
Website analytics. If analytics is added to this site, this paragraph will name the tool, say what it counts and how to opt out, and the notice at the bottom of the page will ask for consent where the law requires it. Until then no analytics script, font or image from a third party is loaded here.
The site is hosted on Cloudflare Workers Static Assets. Cloudflare processes the technical data of a request, such as the IP address, to deliver pages and to protect the service against abuse, under its own privacy terms.
Cloudflare Web Analytics, Zaraz and similar injection features are not enabled for this site. If that changes, this section changes with it.
This website and contact
This website is static and sets no cookies or analytics. For questions or privacy requests, contact tony@senderfinder.com or open an issue at GitHub.