Privacy
What Jobs I Know actually collects, what it does with it, and what it never touches. Last updated November 2026.
Jobs I Know is operated by Mountain Mustang Labs LLC, a Texas limited liability company, 5900 Balcones Drive # 22167, Austin, TX 78731. “We” on this page means Mountain Mustang Labs LLC.
What we collect
- Your email address, to sign you in, let you reset your password, and send the emails you ask for. If you sign in with Google, Google gives us your email; your Google name and photo are never shown.
- A city, used to show you postings nearby and to compute an approximate distance. We store the city, not a street address.
- The interest categories you choose, to filter what you see.
- Companies you say you work at, worked at or interviewed with, if you add them under Your experience, so an insight you share about one says how you know it. Never your name.
- The jobs you save, and the ones you open with Apply, to list them under My jobs. Two weeks after you open one, we ask what happened. Answers only ever show added up, per company, and once a company has enough of them, the link between you and yours is removed.
- Anything you write: a job posting, a message, an insider tip, a report.
- A message you send through the help or contact form, which goes straight to our email inbox. We keep only when you sent it (and, if you weren’t signed in, a scrambled form of your IP address) for two days, to stop spam.
That is the whole list for an account. No phone number, no physical address, no real name is ever required.
Searching with your resume
On the homepage, and on the Search tab once you’re signed in, you can search with your resume or coursework as a PDF. Your browser reads the file on your device; the file itself is never uploaded. Before anything is sent, your browser takes out what look like contact details (email addresses, phone numbers, links, social handles and street addresses) and the line that looks like your name, and our servers check again. The rest of the text, up to 8,000 characters, and anything you typed into the search box (signed in, your saved description) go to our servers and, within a small daily budget, to Microsoft’s Azure AI service in the United States, which sums them up as a short profile (the kinds of roles that fit, your main skills and your level) that we use to find matching jobs. Neither the text nor the profile is stored on our servers: they are used for that one search and then discarded. To limit how many searches one network can make, we count them for a few days under a scrambled form of your IP address.
Signed out, each browser gets one free resume match. For that, your browser keeps a random visitor code and sends it with each resume search; we keep only a scrambled form of the code and when it was used, for 90 days. Signed in, you get five a day, counted with your account.
After a resume search on the homepage, the profile we read, and a description of the job you’re looking for built from it, are kept only in your browser tab until you sign up. Closing the tab removes them. If you sign up in that tab and haven’t saved a description yet, that description is saved to your account as yours, and your search starts from it. Signed in, a resume search works the same way: the description built from it is saved as yours and searched straight away. You can change or clear it any time in the search box.
Sharing through a share link
A share link lets someone tell people starting out what their work is like, with no account. With each share we keep your name and email, the job title, years and kind of workplace you give, your organization and your state if you add them, what you wrote, and a name and link if you ask to be credited by name. All of it is encrypted, and only we can read it. A scrambled form of your email and IP address lets us stop duplicates and spam.
Your name and email are never shown, unless you ask to be credited by name. Your name tells us who sent what, since a share link can be passed on to anyone. We use your email to send you a confirmation, to tell you when your share is live, and to show your shares under My insights once you sign in with that same email and confirm it. What goes on the Insight Feed is what you wrote, credited by your job title, years and kind of workplace (and your organization, if you named it), or by the name you chose. You can change or withdraw a share from My insights any time.
How you appear to others
Every account gets a generated, pseudonymous handle, like quince-0264. Postings, messages, and profiles show that handle, never your email or your real name, unless you explicitly choose to add contact details to a posting you create.
Insights you share about a job show only that handle and how you said you know the company. Anyone reading one can open a small profile card for it: your handle, when you joined, and how many insights and openings you’ve shared. If you turn on Open to messages (or I can refer people here), people can write to you about it in your Jobs I Know inbox; your email is never shown. Before an insight appears, its text is checked automatically by Microsoft’s Azure AI service for names, contact details and abuse. Only the insight and the job it’s about are sent, never who wrote it. Deleting your account deletes your insights.
Expert picks
Some people who know a field rank a few open jobs for others starting out in it. They don’t need an account: we send them a private link. For each one we keep the name and title they approve (copied from their public LinkedIn profile, which we check but never show), their picks, and when they agreed to publish them. If they choose to stay anonymous, only a short description like “Nurse Manager, 30 years, Dallas” is ever shown. Notes they add are checked by Azure AI the same way insights are. They can change or remove their picks any time from their link.
People you can connect with
Beside your matches we show people in that kind of job, so you know who to reach out to on LinkedIn. They’re public LinkedIn profiles found through Exa’s search. We never contact them, and we never write or send messages for you.
For each person we keep their name, profile link and location, and their current and up to three earlier job titles and employers. To find people by the kind of work they do, Microsoft Azure AI turns their job titles (never their names) into numbers, which we keep with them. We delete all of it 180 days after the person last comes up in a search.
If you’d rather not be shown, write to contact@jobsiknow.com with your profile link. We delete what we keep about you and keep only a scrambled form of the link, so you’re never shown again.
People we invite from LinkedIn
We invite some of our own LinkedIn connections to share what they know. For that we keep what LinkedIn’s export of our connections lists for each one: name, profile link, company, title, the date we connected, and an email address if they share it with their connections, plus our own notes. It’s encrypted, only we see it, and none of it is ever shown on the site. If you’re one of them and want yours deleted, write to us.
Messages
Conversations happen inside the app. A message never gets forwarded to your personal email address, and the other person never sees your email either.
Ads
A job’s history can show an ad first, from an advertiser who made it with us and that we reviewed before it ran. There are no ad networks and no tracking scripts. We count how often each ad is seen and clicked; the note of which ad was shown to you is deleted within a day. Nothing about you goes to the advertiser.
If you advertise, we keep what you put in your ad (your website, names, description and messages) and show it to job seekers once we’ve approved it. Your reports show totals only: how many times your ad was shown and clicked, for how long, on which days, and with jobs in which fields. Never who saw it. Your email, from your account, is how we tell you about your ad, and is never shown.
Who else sees anything
We do not sell data. A handful of service providers process it on our behalf, strictly to run the service:
- Firebase (Google), for sign-in, the emails that confirm your address or reset your password, and hosting the backend.
- Cloudflare, which hosts the website. Its Workers AI service (Clef) also reads your saved job description beside each of your matches, to put the closest matches first. It receives the description and the job, never who you are, and Cloudflare doesn’t train its models on them.
- Neon, for the database that stores postings and messages.
- Exa, to find public LinkedIn profiles of people to connect with. It receives the role, employer and city searched (and, for people with a path like yours, the kind of work you did before), never who you are.
- Resend, which sends our other emails (the daily summary, share confirmations) and brings your help and contact messages to us.
- Google reCAPTCHA, to tell a real visitor from a bot before a request reaches our servers.
- Google Places, to find your city as you type it. Our servers send it what you type, nothing else about you.
- Google Safe Browsing, to flag a posted link that looks unsafe. The check runs against the link itself, not against you.
- Microsoft Azure AI (in the United States), to check the text of an insight, or an expert’s note on a job they picked, before it appears. It receives the text and the job it’s about, never who wrote it. It also writes our short job summaries from employers’ public listings, which contain nothing about you. When you search with your resume, it receives the resume’s text with your contact details and name taken out, and anything you typed into the search box, to sum it up for that search, and nothing else about you. To find jobs by meaning, it also turns the job you describe in the search box into numbers. It receives those words alone, never who wrote them. We keep the numbers, not the words: signed in, with your saved description until you change or clear it; signed out, for a few days under a scrambled form of the search.
On your device
Firebase keeps you signed in using your browser’s storage. We keep a few small things there too: your email on the sign-in page if you ask us to remember it, when you last visited (to show what’s new), whether the sidebar is tucked away, notes you’ve dismissed, and an unsent share as a draft until you send it. None of it leaves your device, except the random visitor code for your free resume match, which goes only with a resume search. There are no tracking cookies.
Where the jobs come from
The jobs themselves come from employers’ own career sites, from USAJOBS for federal jobs, and from people who post them. Nothing about you is sent to any of them. Jobs I Know isn’t operated, sponsored, approved or endorsed by USAJOBS or the U.S. Office of Personnel Management. What we take from each, and how, is on Where our jobs come from.
Deleting your account
Account settings has a delete option that removes, for good, your account and everything tied to it: your postings, messages, insights, saved jobs, the companies you added, and any contact details. An opening you posted stays in a job’s history only as a record of the opening, never as yours, and answers about what happened after you applied stay only as anonymous counts.
Shares sent through a share link aren’t tied to your account. Withdraw them from My insights before you delete it, or write to us and we’ll remove them.
Questions
Write to contact@jobsiknow.com.