Privacy

hiringfeed has no accounts, sets no cookies and shows no ads. This page covers what we collect, who else handles it, how long we keep it, and how to reach us. Last changed October 22, 2026.

Up to 30 daysIn the feed
Days 30 to 45Kept, not shown
Day 45Deleted

Every post we keep runs on the same clock. It can appear in the feed for up to 30 days and is deleted on day 45, or sooner if its author deletes it on X or asks us to remove it. After that, we keep only the short records described below.

Posts and profiles from X

Every 15 minutes we search X for public posts that look like job openings. For each post we keep, we store:

the post as published: its text, links, links to its pictures, posting time and the IDs of earlier versions
the post it quotes, and job links the author adds in their own thread or replies, with the text around each link
the author's public profile: name, @handle, profile photo, bio, website, verified badge, company badge, follower count and the date the account was created
the same public profile for the author of a quoted post, and for company accounts linked from the post or the author's profile
what we work out from these: the role, company, location, seniority, whether pay is mentioned, whether each job link still works, and spam signals

We use the profiles to show posts the way X requires and to find the company behind an opening. An account younger than 30 days, fewer than 50 followers or a default profile photo is recorded as a spam signal. We never try to infer anything sensitive about an author.

We also keep a short record of every post we check, including ones we skip, such as a job seeker's post, spam or a post from a blocked account. It holds the post's ID, its posting date, usually its author's numeric ID, and what happened to the post: kept, expired, deleted or hidden on X, removed, or skipped. Except for kept posts, it also says why, which for a skipped post can be the model's label. The record has no end date and stays after the post itself is deleted. It stops us from processing the same post twice and lets us spot accounts that post too often. A skipped post leaves nothing else behind unless a post we keep quotes it, takes job links from it, or reads it as part of its author's thread. Profiles we fetched for skipped posts are deleted at the next daily cleanup unless a post we keep still needs them.

What a model reads

We send new posts that pass our first spam and block checks to Grok, xAI's model, which tells us whether each one is a job opening and picks out the role, company and place. We send a post again when it or a post it draws on is edited, and when the author's replies add job links for its roles. The request carries the post's ID, text and links, the titles X gives those links, short snippets of text around links in the author's thread and replies, and the post it quotes or the start of its thread. It carries none of the author's profile fields, so any names or @handles in it come from the posts or from the titles of the pages they link to. It carries nothing about you. xAI handles the request under its own API terms.

What we share with X

Once a day we send X the IDs of the posts we keep, the posts they quote, the thread and reply posts we take job links from, and every account whose profile we store. X tells us which were deleted, made private, suspended or edited, and we delete or update them.
Profile photos and pictures in posts load straight from X's servers. X receives your IP address and browser details, which pictures your browser loads, and that the request came from hiringfeed.
Job links go through t.co, X's link service, as X requires. Opening one tells X which link you opened before it sends you on to the employer's site. Message, Profile and View on X open x.com.
Links you open from hiringfeed send no referrer, so the site you land on isn't told which site or page you came from.

We send X nothing else about you.

If you use the removal form

The form stores what you enter: the post link, profile link or @handle, whether to remove one post or every post by the account, and the reason and contact if you give them. It also stores the time and a keyed hash of your IP address, not the address itself, which lets us limit one network to 10 requests an hour.

The contact field is optional. We use it only to reply about your request, and we never share it or add it to a list.

We keep every request, including ones we decline and ones still waiting for a decision, with no set end date. To have your contact details or reason deleted from a request, email hello@hiringfeed.app.

What we count

PostHog, a US analytics service, counts page views, time on page and how fast pages load. Requests go through our own domain, and the text of your searches is removed before anything is sent. Click tracking, heatmaps, session recordings and error reports are off.

PostHog sets no cookies and stores nothing in your browser. To count unique visitors, it hashes your IP address and browser details together with the date, so the count starts over every day, then drops your IP address before it stores the event. Each event keeps the page and its title, the site that linked you here, how far down the page you scrolled, your time zone and language, and your browser, operating system, device type, and screen and window size. PostHog keeps events for one year.

What stays in your browser

The site keeps three things in your browser's storage: your theme, the time of your last visit so it can mark new posts, and the job links you opened so it can mark them as opened. They never leave your device. Opened links older than 30 days are cleared the next time you open a job link, and clearing this site's data in your browser removes all three.

Where it lives, and for how long

Vercel hosts the site and runs the jobs that read X. Like any web host, it receives your IP address and browser details with each request. Supabase hosts the database.

Posts, pictures and job links: Deleted 45 days after posting, and shown in the feed for at most 30 of those days. Deleted sooner at the next daily check after the author deletes or hides the post on X, or when a removal request is carried out.
Quoted posts: Kept while any post we keep quotes them, then deleted at the next daily cleanup.
Profiles: Deleted at the next daily cleanup once we store no post by the account, quoted from it, or naming it as the company.
Records of checked posts: No end date. Each holds a post ID, its posting date, usually its author's numeric ID, and what happened to the post. The IDs of posts we quote and of the author's thread and replies we read, with their earlier versions, are kept the same way.
Removal requests and blocks: No end date, including declined and waiting requests. A blocked account is stored as its numeric ID and @handle.
Analytics events: One year, at PostHog.
Your browser's storage: Until you clear it. Opened links older than 30 days are cleared the next time you open one.

What we don't do

We don't sell or rent any of this, show ads, build profiles of readers, or match anyone's X account to information from outside X.

Questions and requests

Email hello@hiringfeed.app to ask what we hold about you, to correct it or to have it deleted. To take a post or an account off the feed, use the removal form. If this page changes, the date at the top changes with it.