Kinn is made by Kinn LLC, a company in New York. We decide how the information on this page is used. Email eric@withkinn.ai about anything here.
If you use Kinn
When you use Kinn, we keep:
Your work email, which is how you sign in. Kinn emails you a link. There are no passwords.
Your name, your role and your team. People who sign in with the same work domain, or who are invited, share a team.
Your LinkedIn profile link, if you add it, and what’s public on that profile.
Your message settings: for each of your voices, the tone, how it opens, the sign-off, phrases to avoid and a few examples.
What you do in Kinn: the clients, boards and posts you add, the drafts you write and copy, who you shortlist, skip or contact, who replied, your notes, your corrections to why Kinn suggested someone, what you let Kinn do without asking, and your answers to Kinn’s questions.
What you tell Kinn to remember, as you said it and when: about you, such as how long your messages should be or the days you don’t send, and about a client, such as the level they’re hiring at.
The kind of change you make to a message, such as a length, a tone or a sign-off, and the reason you give when you skip someone, with when. Not the message itself. The same one three times in two weeks is kept like something you told Kinn to remember, and Kinn says so when it does; a skip reason for one client is kept for your team.
Usage events, such as a page opened or a draft copied, kept in our own database. They carry ids and counts, not message text, names, emails or links.
When Kinn gets a chat wrong, a short excerpt of that turn goes to the Kinn team’s internal tools so we can fix it.
We use it to run Kinn for you and your team: to find and rate people for your clients, to write your drafts, and to check that ratings and drafts are right.
Your LinkedIn
Members connect their LinkedIn account to Kinn through a provider called Unipile. Once it’s connected, Kinn reads and keeps:
Your name, photo, headline, account type and InMail credits.
Your connections, and the invitations you’ve sent and received.
The connections you have in common with people on your boards, looked up for people who are ready to contact or whose card you open.
When you ask, the connections of one of your own connections, found through LinkedIn’s search and narrowed to engineers. Kinn keeps the people it finds, which connection they came through, and how many connections you have in common.
Every chat and message on your account: both sides, group chats and InMail, and attachments up to 20 MB. A larger attachment keeps only its name, type and size.
Kinn never posts, sends, accepts or deletes anything on your LinkedIn. Sending is always yours to do.
If you ask, or as you set up your account, Kinn reads the messages you sent in one-to-one chats over the last 12 months, from the ones it keeps, to set up your voices. An AI model picks out the ones about roles and hiring. The result waits for your review, and is deleted once you use or discard it, or after 14 days. The voices and the examples you keep stay.
When someone you contacted replies, an AI model reads their answer to say where they stand, and Kinn keeps that reading.
Your teammates don’t see your messages in Kinn. They see that you contacted someone and whether they replied.
When you disconnect, Kinn removes the connection at Unipile and stops reading your account. What it has already read stays, including your connections, invitations, chats, messages and attachments. To have it deleted, email us.
The browser extension
Kinn’s extension opens a side panel beside LinkedIn in your browser. It reads the LinkedIn page you have open, as the page shows it:
On the feed or a post: each post on screen, with its link, its author’s name, headline, photo and link, its first lines, its reaction and comment counts and when it was posted.
On a profile: the link, name, headline, place and photo, and the About, Experience, Education and Skills sections once the page has shown them, with the logo beside each company in Experience. Kinn fetches each of those logos from LinkedIn’s media server once per company and keeps a copy in a public bucket, shared by every team.
On a company’s page: its name, logo, tagline, industry, size and city from the top of the page. For a company that isn’t one of your clients, Kinn fetches that logo from LinkedIn’s media server once and keeps a copy in a public bucket so it doesn’t expire.
On any LinkedIn page: the faces it shows beside a link to someone’s profile, such as search results, a post’s comments and reactions, the feed and your connections. The extension sends Kinn their profile links to ask which of them Kinn already has with no photo, and sends only those people’s photo links. Kinn fetches each of those photos from LinkedIn’s media server once and keeps a copy in a private bucket. Nothing is kept about anyone else.
It never clicks, scrolls, types or makes requests on LinkedIn, and it draws nothing on LinkedIn’s page. It sends what it reads to Kinn to look people and posts up on your boards. On the feed, an AI model reads the first lines of posts by people at your clients to say whether each is about hiring, someone leaving or a launch; Kinn keeps that answer for your team, not the lines.
Kinn keeps the profile sections it reads for anyone whose profile you view, with your name and the time, and your team uses them to rate that person for a client. From a profile you view, Kinn also works out a short description of the person (role, skills, seniority, companies, place), the same as from a profile it reads another way, and every team’s match for a client reads it; members see tags and a match, not the description. It keeps your chat in the panel, both your words and Kinn’s, including what the panel adds itself, such as the people you walked through and the messages you wrote, so it’s there on another computer. The extension keeps your sign-in and your recent searches in your browser. It records which kind of page was open, the page's language when the extension couldn't read it, and what you did in the panel, without links or names, with the extension’s version. It installs its own updates while the panel is closed or your computer is idle or locked, reading only whether it is idle, and records each update with the versions and how long it waited. Each request it sends Kinn names its version, so Kinn can tell when it is too old to work. When something in the panel breaks, it sends Kinn an error report on its own: which view was open, the version, the request that failed and the turn it happened on, without links, emails, names or message text. Kinn passes it to Sentry and keeps it with that turn so the team can fix it.
If you appear in Kinn
Kinn helps recruiters find engineers who may be open to a new role, starting with people who engaged publicly with LinkedIn posts from the companies they hire for, or from people who work there. If that’s you, Kinn may hold:
Your public profile: your name, photo, headline, location, work history, education and skills.
Your public activity: the posts you reacted to or commented on, when, and what your comments said, and your public GitHub profile when it’s linked to you.
A short description of your work that an AI model reads from your public profile: your role, level, years of work, skills, the areas you’ve worked in, and your companies and schools. Every team sees the same description, through the tags and fit it drives; it holds nothing a team wrote or did.
How well you fit each client’s criteria, worked out from that description or rated by an AI model with a line of evidence for each, and a suggested first message. Only the team with that client sees it.
How you know a member: whether you’re connected on LinkedIn, the connections you have in common, and where you both worked or studied at the same time.
That you were found through someone you’re connected to on LinkedIn, if a member asked Kinn to look through that person’s connections: your name, headline and profile link as LinkedIn’s search shows them, and which connection you came through.
Whether a member shortlisted, skipped or contacted you, any correction they made to why Kinn suggested you, and whether you replied. If that member connected their LinkedIn to Kinn, Kinn keeps your conversations with them.
What a member told Kinn about you, as they typed it, such as when you might move or the work you want, with who typed it and when. Their team sees it, and Kinn uses it in answers and drafts about you. Kinn doesn’t keep personal details a member mentions about you, such as your health or family.
A day a member asked Kinn to bring you back to them, with what they typed. Only that member sees it, and it ends if you reply first.
That a member starred you, and when. Only that member sees it; their team doesn’t.
If someone on a team starred you: your profile and your public posts from the last week, read once a week through Apify, and what a member’s own LinkedIn page showed about you in Kinn’s browser extension (your name, headline and the first lines of a post in their feed, or your profile when they open it). Kept for that team only, and used to tell the member who starred you when you change jobs, turn on Open to work or post about leaving.
Public profiles and posts are collected for us by Apify, a data provider. Profiles also come from the page a member has open in Kinn’s browser extension. Connections and messages come from the LinkedIn account a member connected. Data sourcing explains how.
Kinn also reads the public profiles of people who work at the companies members hire for, to describe what each company looks for and to show who has worked together.
Kinn keeps a copy of each person’s photo it shows, including members and their mutual connections, because LinkedIn’s links to photos stop working. It fetches each photo from LinkedIn once when it reads the person, and the copies are private, shown only to the teams that see that person. A person’s older photos are kept for good beside the newest; a photo that stops showing is hidden, not deleted. It does the same once for a company’s logo, kept in a public copy, and when it reads a profile, once for the logo of each company in the person’s roles, shared by every team. Data sourcing lists every direct request to LinkedIn.
Kinn never contacts you. A recruiter decides whether to reach out, and writes to you from their own account.
Visitors to this site
If you ask for access, we keep your name and your work email, so we can reply.
Kinn keeps you signed in, and remembers small settings, using your browser’s storage. There are no advertising cookies and no third-party trackers, on this site or in Kinn.
Who else sees it
Your team shares boards, ratings, drafts, decisions, notes, notes on clients, contacts and the profiles members viewed, so two people don’t reach out to the same person. LinkedIn messages, and what you tell Kinn to remember about you, stay with the member they belong to.
Other teams see the same description of a person’s public profile (their role, level, skills, companies and the like), shown as tags and used for fit. They never see your team’s notes, messages, replies, decisions, contacts, clients, criteria or fit.
The people who run Kinn can open a team’s boards, read only, to help with a support question, and the Team page says so. To check that answers are read correctly and drafts are good, they can also read the messages behind them. Of what you tell Kinn to remember about you, they see only how many there are, never what they say. Every view is recorded.
Providers run parts of Kinn for us, and use data only for that. Vercel hosts Kinn. Supabase holds the database and files and signs you in, and Resend sends the sign-in emails. Anthropic’s AI models rate fit, write drafts and read messages, and under Anthropic’s commercial terms what Kinn sends isn’t used to train them. Apify collects public LinkedIn posts and profiles, Unipile holds the connection to members’ LinkedIn, and GitHub answers lookups of public GitHub profiles. Sentry receives error reports, with ids and the sender’s IP address and without names in fields, emails, links or message text. Langfuse receives a trace of each turn typed to Kinn in the panel, the box or chat, so we can check its answers: what was typed, what Kinn showed, and the model calls behind it with the facts they were given about the people asked about, kept by member id and never by email. jsDelivr serves a code library to signed-in pages, and photos load from LinkedIn’s own servers.
Anyone else only when the law requires it, or a company that buys Kinn, which would be held to this policy.
We don’t sell personal information, and we don’t use it for advertising.
How long we keep it
Connections in common with someone on your boards: looked up again after 90 days. The newest answer is the one used, and earlier counts are kept until you ask us to delete them.
Messages read to set up your voices: until you use or discard the result, or 14 days.
Something you told Kinn to remember, about you or a client: until you forget it, and then 30 more days before it’s deleted.
Your account: while you’re on a team. If you’re removed, your sign-in ends and your team keeps the decisions you made, under your name marked removed.
Everything else, including your LinkedIn data after you disconnect, access requests, and what Kinn holds about people who appear in it: until you ask us to delete it.
Your choices
Wherever you are, you can ask us to show you what we hold about you, send you a copy, correct it, delete it or stop using it. Email eric@withkinn.ai from any address. We may ask you to confirm who you are, and we’ll answer within 30 days.
If you appear in Kinn and ask to be removed, we delete what Kinn holds about you on every team: your profile, activity, ratings, drafts, decisions and the connection records that name you. We keep your LinkedIn profile link on a list so Kinn skips you from then on. Conversations you had with a member stay with that member’s LinkedIn account in Kinn, unless you ask for those too.
In the EU or UK
We rely on our agreement with members to run Kinn for them. For people who appear in Kinn, we rely on a legitimate interest, ours and our members’, in finding and reaching people for jobs, using public professional information and what members’ own LinkedIn shows. For access requests, we rely on a legitimate interest in replying. You can object at any time, and you can complain to your data protection authority. Kinn’s providers may process data in the United States and other countries.
In California
We don’t sell personal information or share it for advertising. You have the rights above, and using them won’t change how we treat you.
Security, children and changes
Security. Data is encrypted in transit and at rest, only Kinn’s servers can reach the database, and message text is kept out of error reports.
Children. Kinn is for work. It isn’t meant for anyone under 16, and we don’t knowingly hold information about them.
Changes. When this page changes, so does the date at the top.