Last changed 4 November 2026
Nameclick privacy
Nameclick finds work contact details when you press for them, and keeps as little about you as it can to do that.
This page covers the Nameclick browser extension, the service at api.nameclick.co, the MCP server at mcp.nameclick.co and the LinkedIn email finder on sourcey.com. It has two parts: what Nameclick keeps about the people it finds, and what it keeps about you when you use it.
The people Nameclick finds
Nameclick keeps professional contact details of people who never signed up for it: name, job title, employer, work email and whether it was checked to take mail, public profile addresses, work history, a general location and their employer's company record. These come from a contact-data provider, currently Apollo.io, and from the person's own public GitHub profile. Nameclick does not keep personal email addresses, phone numbers or home addresses of the people it finds.
Sourcey is responsible for these records. They are kept on the basis of legitimate interest: helping people reach someone at work about their work. Each record is kept so the next person who asks is answered from it, rather than buying the same record again.
If you are in it, you can ask to be removed. You do not need to give a reason. A link goes to your work address, and when you follow it your record, the provider's replies about you and your identifiers are deleted at once. A one-way fingerprint of each identifier is kept so Nameclick never looks you up again.
What the extension reads
- On LinkedIn: the profile's address, to know whose profile is open. Nothing from the page itself.
- On any other page, only when you press: the name you selected, its sentence and paragraph, the page title and the links in that paragraph, trimmed. They are sent once to work out who you meant, and never stored.
- On GitHub: the login in the page's address.
- Never: your other tabs, history, feeds or messages, or anything before you press.
What is sent, and where
A press sends what the extension read to api.nameclick.co. To answer, the service may ask the contact-data provider about that person, and to work out who a selected name means it sends the passage to Google's Gemini API. For a GitHub profile it reads the public profile from GitHub.
What is kept about you
- Your account, when you sign in: the number Google gives your Google account, never your name or email address, when you signed in, and a key only your browser holds, kept as its digest. Signing out ends the key.
- Your lookups: who you looked up and when, so the people you found open again for free and your monthly lookups are counted. The passage of a selected name is never kept.
- Agent keys: each kept only as its digest.
- Usage counts, which carry identifiers only: a random install ID, the kind of press (LinkedIn, a selection, GitHub, the finder, an agent) and how it ended. Never a name, an address, selected text or a page address. Settings turn them off.
- On the web finder: nothing is tied to you. The number of lookups from an address is counted in memory for the day, and the address is not stored.
What Nameclick does not do
It does not sell data about you, show ads, or look people up in bulk. It never sends email for you, and never reads a page you have not pressed on.
Who handles data for Nameclick
Amazon Web Services runs the service and its database, and Cloudflare carries its traffic. Apollo.io supplies contact records. Google signs you in, and Google's Gemini API works out selected names. Nitrosend sends the removal confirmation. Stripe will take payments when plans open.
Questions
Write to hello@nameclick.co, including to have your account and its lookups deleted.