Privacy Policy
Fetch and the Fetch Scout browser extension · Last updated 1 October 2026
This policy explains what information Fetch (fetch-hq.vercel.app) and the Fetch Scout extension for Chrome collect, why, and what we do with it. Fetch is a recruiting tool: it helps recruiters find job postings and candidates. We don’t sell data, show ads, or track your browsing.
Your account
When you create an account we store your name and email address to sign you in. Sign-in is handled by Clerk, our authentication provider. If you’re invited to a team workspace, we store the invitation and your role, and send the invitation email through Resend.
What you search for
When you search — by job description, job keywords, or a person’s name and company — the search text is sent to our servers, which turn it into web searches and pass those to our search providers (Serper, Exa and Apify) to find matching public LinkedIn profiles and job postings. We keep a record of each search’s cost for workspace usage limits, and the job searches you choose to save. To understand a job description and rate how well each result fits, the job description and the public profile text in the results are sent to an AI service (OpenAI or Google Gemini). We don’t keep the job descriptions you paste into Fetch Scout.
People in search results
Results contain information people have made public on LinkedIn, as it appears in web search results: name, headline, location, profile link and, where available, profile photo. Results are shown to you and not stored, unless you choose Save, which adds that person’s name, headline, location, profile link, photo link, match score and matched skills to your shortlist, along with any status and notes you add. You can remove saved candidates at any time.
The Fetch Scout extension
- It keeps a sign-in token in your browser’s extension storage so you stay signed in, and holds your current search results in memory until the browser closes. It keeps nothing else between sessions.
- It sends your searches only to Fetch’s servers. To show profile photos in results, it loads those images directly from LinkedIn’s and Google’s image servers, as a web page would.
- It doesn’t read, record or change the web pages you visit, including LinkedIn, and never uses your LinkedIn account.
- The token is linked to your Fetch account, stops working after 30 days without use, and is revoked when you sign out of Fetch or disconnect the browser on Fetch’s Extension page.
- Share → Gmail (optional): if you choose it, you sign in with Google and allow Fetch Scout to manage drafts (the
gmail.composepermission). It uses that only to create the one draft you asked for — the candidate report as a Word attachment — and opens it for you to address and send. It doesn’t read, send, change or delete any email. The Google access token stays in your browser’s session storage, goes only to Gmail, never reaches Fetch’s servers, and expires within an hour. The report itself is built in your browser. You can remove access at any time at myaccount.google.com/permissions. - Fetch Scout’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Who processes data for us
Vercel (hosting), Supabase (database), Clerk (sign-in), Resend (email), Serper, Exa and Apify (web and people search), and OpenAI and Google Gemini (reading job descriptions and rating how well search results match them). Each receives only what it needs to provide its service.
How long we keep it
Account information and your saved candidates, jobs and searches are kept while your account exists. Search cost records are kept for workspace usage reporting.
Your choices
You can delete saved candidates and searches in Fetch. To get a copy of your data, correct it, or delete your account and everything linked to it, email founder@yellocode.app. If you appear in someone’s search results and want to ask about that, write to the same address.
Changes
If this policy changes, we’ll update this page and the date at the top.