← Nameclick

Last changed 6 November 2026

Nameclick privacy

Nameclick finds work contact details when you press for them, keeping as little about you as it can to do so.

This page applies to 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 contact details about people who have never signed up for it. These are their name, photo, job title, employer, email address and whether it was checked to take mail, public profile addresses, work history, a general location and their employer's company record. The details come from a contact-data provider, the person's own public GitHub profile and, for a photo, the public profile someone looked them up on. Nameclick does not keep phone numbers or home addresses for the people it finds.

Sourcey is responsible for these records. They are kept on the basis of legitimate interest: helping people contact someone at work about their work. Each record is retained to answer the next person who asks, rather than buying the same record again.

If you are in these records, you can ask to be removed without giving a reason. A link is sent to your work address. Following it immediately deletes your record, the provider's replies about you and your identifiers. Nameclick keeps a one-way fingerprint of each identifier so that it never looks you up again.

What the extension reads

  • On a profile, only when you press: It reads what the open profile shows about who the person is and where they work, to find them and check their record. If their record has no photo, the address of the one on the profile is kept with it.
  • On any other page, only when you press: It reads the name you selected, its sentence and paragraph, the page title and the links in that paragraph, trimmed. With nothing selected, it reads the page's title, headings, main text and the profile links on it, trimmed. These are sent to identify who you meant, and the text is not kept.
  • On GitHub: It reads the login from the page's address.
  • Never: It never reads your other tabs, history, feeds or messages, or anything before you press.

What is sent, and where

When you press, what the extension read is sent to api.nameclick.co. To answer, the service may ask the contact-data provider about that person. To identify who you meant, it sends what it read from the page 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: Nameclick keeps the number Google assigns to your Google account, never your name or email address; when you signed in; and the digest of a key held only by your browser. Signing out ends the key.
  • In your browser: the people you have found, their photos and your lookups left stay in your browser, so they open at once without asking the service. Signing out removes them, and someone no longer on your list leaves it the next time the extension reads it.
  • Your lookups: Nameclick keeps who you looked up and when, so you can reopen people you found for free and your monthly lookups can be counted. It never keeps the text it read from a page.
  • Agent keys: Nameclick keeps each key only as its digest.
  • Usage counts, which carry identifiers only: These include a random install ID, the kind of press (LinkedIn, a selection, GitHub, the finder, an agent) and how it ended. They never include a name, an address, selected text or a page address. You can turn them off in Settings.
  • On the web finder: Nothing is tied to you. The number of lookups from an address is counted in memory for the day. The address is not stored.

What Nameclick does not do

Nameclick does not sell data about you, display ads or look people up in bulk. It never sends email for you or reads a page you have not pressed on.

Who handles data for Nameclick

Amazon Web Services runs the service and its database. Cloudflare carries its traffic. A contact-data provider supplies the contact records. Google signs you in, and Google's Gemini API identifies selected names. Nitrosend sends the removal confirmation. Stripe will take payments when plans open. Stripe takes payments for plans: your card details go to Stripe and never reach Nameclick.

Questions

To have your account and its lookups deleted, or for other questions, write to hello@nameclick.co.