Contacts

What a contact is

A contact is a person your workspace has heard from. One row per email address, per workspace. It carries their name, the domain of their address, when you first and last heard from them, every document and data room they have touched, and whatever your team notes or tags about them.

Most contacts are never typed in. LinkDrop makes one the moment a person tells you who they are, and updates it every time they come back. If they give a different name later, the latest one is shown.

The domain is the company part of the address. For a personal mail provider such as Gmail, Outlook or iCloud there is no domain: the list shows a dash and the contact's page shows Webmail, because the address says nothing about where the person works.

How someone becomes a contact

Three moments on your links create or update a contact:

• Introduced themselves: they typed a name and address on a share link or in a data room. See Analytics for how introductions work for your recipients.
• Signed in to read: they opened your link while signed in to LinkDrop, so the account's address is theirs.
• Asked to download: they requested a file and gave an address to send it to.

You can also add somebody yourself, with Add contact on the Contacts page: an address, and a name if you know it. That is for people you already know, like someone you met at a dinner, rather than people who read what you sent. A connected agent can add one the same way. Either way the contact page shows how it arrived, as Added by a teammate or Added by an agent, and the activity feed shows who added it under Contacts, so you can always see where a person came from. Adding an address that is already there makes no second copy; the page says the person was already a contact and records that you added them too.

A reader who never gives an address is not a contact. That visit is still recorded on the document, with nobody attached to it. Your own opens and your teammates' previews never create a contact.

Contacts belong to one workspace. Telling one workspace who you are tells only that workspace.

On every plan

Every contact is shown in full on Free and Pro alike: the people who introduced themselves, readers who signed in or asked to download, and anyone you added yourself, by hand or through an agent.

Search, sort and filter

Open Contacts in the sidebar.

• Search matches a name, an address or a domain.
• Sort by last seen, first seen, name, domain, documents read or visits, in either direction.
• Filter by tag, by how they arrived, or by domain. Clear removes every filter at once.

Every control is in the address bar, so a filtered view survives a reload and can be sent to a teammate as a link.

Download them

Download CSV gives you the rows you are looking at, with the search and filters you have applied, not the whole list. The file carries the name, address, domain, whether the address is confirmed, the first and last dates, the documents and projects counts, the visits, the tags and how they last arrived.

The file opens in a spreadsheet as it is, and imports into anything that reads CSV. It arrives as it is built, so a long list starts downloading straight away instead of making you wait for the whole thing.

One download holds 25,000 contacts. Past that the button reads Too many to download; narrow the list with a search, a tag or how they arrived, rather than getting a file that is quietly missing people.

Tags and notes

Tags work on a person exactly as they do on a document or a project: apply one from the contact's page, and the tag's own page lists the contacts carrying it. "Investor", "passed", "warm", "counsel" are yours to define.

Each contact has one note, up to 2,000 characters, for what the system cannot know. It keeps who wrote it last and when. A cleared note cannot be brought back.

Members, admins and owners can add a contact, write a note and apply tags. Viewers see the list, the contact pages and the download, and change nothing. Roles are explained in Teams and workspaces.

Names and addresses cannot be edited. They are what the person gave, or what was typed when they were added.

Getting there from a reader

You do not have to start at the Contacts page. A reader's page, the one that shows what somebody did with a single document, carries a View contact link beside their address. A visit brief email about one reader carries a View contact button too. Both appear only when that person is a contact, so a link is never a dead end.

What a contact page shows

The person, then the history: every document they read, every data room they entered, and each of the moments they arrived through, under How they arrived. A document row opens that document's metrics, where the readers and the page-by-page detail live. A document you have deleted stays in the list, marked Deleted, for the 30 days it can be restored from Dashboard, then Recently deleted; it no longer opens anything, and it leaves the list once it is purged.

Reading history lists their visits, newest first: what they opened and on which link, when, for how long, how many pages of how many, and whether it was their first visit or a return. Where a visit brief was written, its summary, what caught their attention and the suggested next step are there too. See the whole visit opens that reader's page for the document or data room. Reading the history costs nothing; it shows what was already recorded. It is the same on every plan. Visits to a deleted document or data room are left out.

An address shows as Verified once the person has confirmed it from the link LinkDrop sent them (opening the link shows a Yes, this is me button; only pressing it confirms). Confirmation belongs to the browser that confirmed: someone else typing the same address on another device is treated as unconfirmed and cannot rename the contact. Unconfirmed is normal and means only that: somebody typed it.

Reader profile

Who they are is the contact's reader profile: who the person is, from public professional sources, and their history with you. A profile is made only for a reader who introduced themselves by typing a name and email on one of your share links or project links, and research runs after they confirm that email with the link LinkDrop sends them. A reader who only opened a link while signed in to LinkDrop, a contact you or an agent added, and an anonymous reader are never profiled. A reader whose browser sends a Global Privacy Control signal is not profiled either, and the card says so.

Once someone has introduced themselves and confirmed their email (a few minutes after the introduction at the earliest), LinkDrop searches the public web for them and writes the profile, both with OpenAI, which receives their name and their email's company domain (never the full address, which is never searched), their approximate location, browser language and time zone, and the titles and stored summaries of the documents they opened (never the documents' text, their IP address or the site they came from):

• Who they are: their name, role and company, with how the match was made and a confidence. If LinkDrop cannot tell them apart from someone with the same name, it says so and shows nothing rather than a guess.
• About their company, their Role, a short Background and their Public profiles.
• At Advanced only, and only where public sources have it: their Career history (earlier roles and companies, with years when a source gives them), Recent news from the last 12 months (talks, posts, articles, funding, launches), their company's stage and funding, and specific ties between their background and the documents they read.
• Fit with what they read: how they are likely to relate to the documents they opened, by title.
• Location: always "around" a city, region and country, with where the estimate came from (their network location, a work location a public page states, such as their office or their company's headquarters, both, or a disagreement between the two) and a confidence. It is worked out from the location LinkDrop's host derives from their connection, their browser's language and the time zone the share page reports. LinkDrop never looks up or shows where someone lives, and nobody sees their IP address.
• History with you: first and last seen, visits and returns, the documents they opened and the last few brief headlines. This part comes from LinkDrop's own records, not from the web.
• Suggested approach, and the numbered Sources every fact came from.

It is AI research and it can be wrong: check before you rely on it. An address marked Email not confirmed has not had its confirmation link clicked yet, so the address may not be theirs. It is not researched automatically until it is confirmed; if the workspace owner clicks Research this person anyway, confidence in who they are is capped and the summaries of what they opened are left out of the web search. The research never signs in to a site, never uses LinkedIn, other sites behind a login or people-search sites as a source, and never keeps health, religion, politics, family or other sensitive details.

What it costs: 3 credits at Standard or 6 at Advanced, once per reader. An owner or admin picks the level and can turn automatic profiles off in the Profile each reader row on the dashboard Automations tab; it is on by default. Updates to their history after later visits are free. A reader is researched again automatically at most every 30 days, when they come back. The workspace owner can click Refresh research on the card at any time for the level's price; within 30 days of the last research it asks first. If the research fails, the credits go back. Automatic profiles come out of included, starter and pack credits only, never on demand, on every plan, and one link can start at most 5 a day (the workspace as a whole, 50); a click on Pro may use on demand. On Free it comes out of your starter credits and any credit packs, never on demand; if the workspace is out of credits, the card says so and nothing is charged.

A profile is shared with everyone in the workspace, and a locked data room's reading is never part of it. Contacts summarized before profiles arrived may still show their Earlier reader summary until they have a profile.

Privacy and deletion

A contact is another person's data, held by your workspace. Deleting your account erases the contacts of the workspaces that go with it. Deleting a workspace takes its contacts out of reach with it, the same as its documents and its analytics. See Privacy and security for what deleting removes and when.

There is no button to delete a single contact. If a recipient asks you to remove them, contact support with the address and the workspace, and it is one row per workspace rather than a scatter. Removing a contact removes its reader profile too. A person can also ask LinkDrop directly, at support@lnkdrp.com, to delete a reader profile about them; LinkDrop deletes it in every workspace without asking the workspace first, and does not profile that address again.

LinkDrop does not sell, share or cross-reference contacts between workspaces, and a contact is never used to mail that person anything.

Agents

An agent connected over MCP can read your contacts and one contact's history, and add a contact by address, with a name if it has one. That is all it can write. It cannot write a note or tag a person: a note is a judgement and a tag on a person is a claim about them, which is a person's call. A contact an agent adds is marked Added by an agent, and the activity feed shows the addition as the agent's. See Connect your agent, or start at /agents.