Crawler and Bot Policy: FastFindRemoteJobsBot and employer opt-out

Page: https://fastfindremotejobs.com/bot Last updated: [EFFECTIVE DATE]

This page is for employers, recruiters, and anyone who runs a careers site or job board that our crawler visits. It covers who we are, what our crawler does and doesn't do, how to limit or block it, and how to opt your company out.

At a glance

• Our crawler identifies itself as FastFindRemoteJobsBot.
• It reads only public job listings that anyone can see without logging in, and it follows robots.txt.
• It never tries to get past a login, a CAPTCHA, or a bot challenge.
• We keep basic job facts and a link to your posting. We don't republish your job descriptions, and we don't use your logo.
• Every alert sends job seekers to apply on your own site.
• Opting out is free and you can do it at any time. We honor verified opt-outs within 24 hours.
• Questions or problems: bot@fastfindremotejobs.com

1. Who we are

FastFindRemoteJobs (fastfindremotejobs.com) is operated by Conner Strategic Systems LLC, a Pennsylvania limited liability company.

FastFindRemoteJobs is a paid job-alert service for people looking for remote work in the United States. It is not a job board. We have no public job listings, no job search, no public job pages, and no job-data feed for other companies. Each subscriber sets up private alert rules based on employer industries and keywords. When a new remote job matches those rules, we notify the subscriber, who then applies on the employer's own website.

We are not affiliated with, endorsed by, or sponsored by the employers we monitor or their job-board providers. Employers do not pay us.

2. Why we visit your site

We check employers' careers sites and public job feeds to spot new remote jobs soon after they're posted. When a new job matches a subscriber's alert rules, we send that subscriber a short alert with a link to your posting.

We look for fully remote jobs, mainly ones open to applicants in the United States. We don't send alerts for on-site or hybrid jobs.

At launch, we monitor about 500 employers. [UPDATE AS COVERAGE CHANGES]

3. How to recognize our crawler

Every request our crawler makes carries this user-agent string:

FastFindRemoteJobsBot/1.0 (+https://fastfindremotejobs.com/bot; bot@fastfindremotejobs.com)

The version number may change over time. The name FastFindRemoteJobsBot will stay the same, so use that name in robots.txt or firewall rules.

Our crawler runs on Google Cloud servers in the United States. We don't currently publish a fixed list of IP addresses. [IF A STATIC OUTBOUND IP ADDRESS IS ADOPTED, LIST IT HERE.] Anyone can copy a user-agent string. If you see traffic using our name that doesn't behave the way this page describes, it may not be us. Please tell us at bot@fastfindremotejobs.com.

Occasional visits in a normal browser. When we add an employer to our list, we may also look at its careers site in an ordinary web browser, the way any visitor would, sometimes with the help of an AI browsing assistant. We do this to confirm the site's address and whether a login is needed to see jobs. These occasional visits don't use the crawler's user agent, but they follow the same rules: public pages only, no logins, and no attempts to get past a challenge.

4. Where we look

• Public job feeds and job-board pages. Most are run by applicant tracking systems (ATS) such as Greenhouse, Lever, Ashby, SmartRecruiters, Workable, Teamtailor, Personio, Recruitee and Workday. These names are trademarks of their owners, and we are not affiliated with them.
• Only pages and feeds that anyone can see without logging in.
• Today we monitor only job boards that offer a public job feed. We plan to add some careers sites that don't have one. We'll check those less often (every 30 to 60 minutes) and under the same rules, and for some of them we may use an AI model to read the public careers page and pick out the job facts listed in section 5. We'll update this page before we start.

How we find employers. We identify companies that hire remotely from remote-job listings published elsewhere, such as on other job sites. Later we may add other sources, such as public lists of companies. We then find and confirm each company's own careers site. Our alerts are always based on what we find on the employer's own careers site or job feed, never on another job site's listing.

5. What we collect

About each remote job, we keep only these facts:

• the job title
• the company name
• the location and remote status, including any location limits (for example, "Remote: Texas residents only")
• the dates the job was posted or updated, when the listing shows them
• the salary or pay range, if the posting publishes one
• the posting's web address (URL) and ID
• whether the job is new, edited, reopened, or closed.

If we add other basic facts of the same kind (for example, employment type), we'll update this list.

About each company, from public information: the company name, website domain, careers-site address, which job-board platform it uses, whether a login is needed to see its jobs, its industry (one of our 34 industry categories), its headquarters location, and whether it is a staffing agency.

For on-site and hybrid jobs, we keep only the job's ID on your board, so that we can tell which jobs are new. The one exception is the training sample described below.

How we handle job descriptions. To decide whether a new job is remote and whether it matches a subscriber's keywords, our software reads the full text of the posting. We don't store that text for display, and we never show it to subscribers. What we keep is a scrambled (hashed) word index that can't be turned back into readable text, and we delete it after about 4 days. There are two limited exceptions:

• AI checks on public data. We may send public posting text to an AI model (Google Gemini, through Google Cloud), for example to double-check whether a "likely remote" job really is remote, or to help label the training sample described below. We also use AI to work out an employer's industry from public company information. These models receive only public job and company information, never information about our subscribers.
• A training sample. We keep a limited internal sample of postings, including their text, to train and test the software that decides whether a job is remote. Only we and people working on our behalf use this sample, and it is never shown to subscribers or published. [OWNER TO CONFIRM HOW LONG THE SAMPLE IS KEPT.]

How long we keep job facts. We keep job records for about 30 days, and a hashed "fingerprint" of each job for up to 45 days so we can recognize reposted jobs. Subscribers see a match on their private dashboard only while the job is within 72 hours of when we first detected it.

What we don't collect. We don't collect any information about your applicants or candidates. We don't extract the names or contact details of your recruiters or employees.

6. What we never do

On your careers site or job board, our crawler and our team never:

• log in, create accounts, or use anyone's credentials, on your site or on your job-board platform;
• try to get past a CAPTCHA, bot challenge, paywall, or other access control. That includes switching IP addresses or networks, disguising our user agent or browser, and using CAPTCHA-solving tools or services. If our crawler runs into a challenge, it stops requesting pages from that host, and the host is flagged for review by a person;
• submit job applications or fill in any other form.

With your job information, we never:

• store, display, or republish the text of your job descriptions (section 5 lists the two limited exceptions);
• copy or use your logo, images, or other brand artwork without your written permission;
• say or suggest that you endorse, sponsor, or partner with us;
• sell, license, or give your job data to other companies. The only exceptions are sending alerts to our own subscribers and sharing data with service providers that help us run FastFindRemoteJobs, such as our cloud host;
• publish your postings on our website. We have no public job pages, so your listings never appear on our site, and search engines can't find them through us.

7. How often we visit and how we limit our load

	Current setting
How often we check each board	About every 5 minutes. Careers sites without a feed (planned): every 30 to 60 minutes.
Requests per check	Usually one. It is a conditional request, so your server can answer "304 Not Modified" when nothing has changed. When a new job appears, we may make one more request for that job's details. On Workday sites we read up to 3 short pages per check, stopping at the first job we've already seen.
Maximum rate per host	Between 1 and 5 requests per second for each job-board platform host, depending on the platform, shared across all the employers on that host. For a single employer's board, that works out to a few requests every 5 minutes. On Workday: no more than 1 request per second for each employer's site. On careers sites without a feed (planned): no more than 1 request every 5 seconds.
robots.txt	Read before we request pages on a host, then cached for up to 24 hours (see section 8).
Compression	We ask for compressed (gzip or Brotli) responses.

When your server signals trouble:

• "429 Too Many Requests" or "503 Service Unavailable": we wait for the time given in your Retry-After header (up to 10 minutes). We also halve our request rate to your host for 10 minutes, then raise it slowly.
• Repeated errors: after 5 failures in a row, or a high error rate, we pause that host automatically for 5 minutes. We then send a single test request before resuming. Boards that keep failing are checked less and less often, down to once an hour.
• A challenge page (such as a CAPTCHA): we stop requesting pages from that host and flag it for review by a person (see section 6).
• A block (such as "403 Forbidden"): we back off as described above. We never try to get around a block or challenge.

We may lower these limits at any time. If we ever need more than the limits above on a shared job-board platform, we'll contact that platform first. If you'd like us to check your site less often, email bot@fastfindremotejobs.com and we can slow down our checks of your boards.

8. robots.txt: how we follow it and how to block us

We follow the Robots Exclusion Protocol (RFC 9309):

• We check robots.txt on each host before we request pages there, and we re-read it at least every 24 hours. Changes you make can take up to 24 hours to reach us.
• We follow the group for FastFindRemoteJobsBot. If there isn't one, we follow the * group.
• If your robots.txt doesn't exist (a 404 or other 4xx response), we treat the site as open. If it returns a server error (5xx) or can't be reached, we treat the whole site as closed to us until we can read it.
• [OWNER TO DECIDE: Crawl-delay isn't part of RFC 9309. Either state "We also honor Crawl-delay values of up to [N] seconds" or "We don't use Crawl-delay; see section 7 for our limits".]

To block us from your whole site:

User-agent: FastFindRemoteJobsBot
Disallow: /

To block us from part of your site:

User-agent: FastFindRemoteJobsBot
Disallow: /internal-jobs/

If a job-board platform hosts your jobs: the robots.txt that applies is the one on the host we actually contact. That is often your platform's domain (for example, boards-api.greenhouse.io), not yours, and you probably can't edit it. Use the opt-out in section 10 instead. It covers your boards wherever they're hosted.

If you need us to stop right away: robots.txt changes can take up to 24 hours to reach us. For immediate relief, block our user agent at your server or firewall (for example, by returning a 403 or 429 response). Our crawler slows down when it gets those responses and pauses automatically if they continue. It never tries to get around a block. Then email bot@fastfindremotejobs.com with "Urgent" in the subject line, and we'll pause our checks of your boards.

9. How our alerts send applicants to you

• Every job in our alert emails and on subscribers' dashboards has an "Apply on employer site" link that goes straight to your posting, on your site or your job-board platform's page.
• Text-message alerts link to the subscriber's private dashboard, which then links to your posting.
• Subscribers apply through your own hiring process. We don't apply for them, and we never see their applications.
• Each subscriber sees only the jobs that match their own rules. A match stays on their dashboard only while the job is within 72 hours of when we first detected it.
• If it looks as though a job has been taken down, we label it "May be closed" on dashboards.
• [OWNER TO DECIDE: whether links carry a referral tag such as utm_source=fastfindremotejobs, so employers can see our traffic in their analytics. If adopted, say so here.]

10. Opt out of monitoring

Opting out is free, and you don't need an account.

What an opt-out does

You choose the scope:

• All job boards: we stop checking every job board and careers page we monitor for your company, and we won't add new ones for your company.
• Specific URLs: we stop checking only the boards or pages you list.

Within 24 hours after your request is verified, we:

1. stop our crawler's requests to the boards in scope;
2. cancel any alerts for your jobs that are waiting to be sent;
3. email you a confirmation.

What an opt-out doesn't change:

• Alerts we sent before the opt-out can't be recalled.
• Matches already on subscribers' dashboards drop off within about 72 hours of when we first detected the job.
• Job records we already hold expire within about 30 days, and hashed fingerprints within about 45 days.
• Postings of yours that are already in our internal training sample (section 5) [OWNER TO DECIDE: are removed from it when the opt-out takes effect / stay in it].
• An opt-out doesn't affect other websites, and it doesn't stop job seekers from finding your jobs on their own.

We keep a record of your request (company, domain, contact email, scope, how it was verified, and the relevant dates) for as long as the opt-out is in effect, so that we can keep honoring it. [OWNER TO CONFIRM any added period after an opt-out is reversed, matching the Privacy Policy §7.]

How to ask

Use the opt-out form on this page, or email bot@fastfindremotejobs.com with the same information. The form asks for:

Field	What to enter
Company name	Your company's name.
Company domain	Your company's main website domain, for example example.com.
Contact email	Your work email. An address at your company's domain is the fastest to verify.
Scope	"All of our job boards and careers pages", or "Only these URLs" (one per line).
Message (optional)	Anything else we should know, for example other domains or brands, or a recruiting agency that runs your careers site.

How we verify a request

We verify requests to make sure only the company itself can opt out. You need to complete one of these:

1. Email at your company's domain (automatic). If your contact email is at your company's domain (for example, jane@example.com for example.com), we email you a confirmation link. Clicking it verifies the request. The link expires after [7] days. If you email bot@ instead of using the form, we'll reply with the same kind of link.
2. A DNS TXT record. If your email is on a different domain, add the TXT record we give you to your domain's DNS. We check for it automatically [every hour for 7 days]. You can delete the record after you receive our confirmation email.
3. Manual review. If neither of those works (for example, an agency runs your careers site), tell us in the message, and we'll review the request ourselves. We may ask you for more information. We aim to finish manual reviews within [2] business days.

If the domain or URLs in a request don't match our records for that company, we review the request manually. If we can't verify a request, we'll email you to say why and what else we need.

Changing your mind

To reverse or change an opt-out, email bot@fastfindremotejobs.com. We'll verify the request the same way.

11. Report a problem or correct our information

Email bot@fastfindremotejobs.com. To help us respond quickly, include:

• your domain and the URLs involved;
• the dates and times, with your time zone;
• what happened (for example, request volumes or status codes);
• a sample log line showing our user agent and the IP address.

Please also tell us if something we show about your company or jobs is wrong: for example, a hybrid job labeled remote, the wrong industry, or a closed job that's still showing. We'll review it, and if it's wrong, we'll correct or remove it.

We aim to reply within one business day. If our crawler is causing a problem for your site right now, put "Urgent" in the subject line.

Other contacts:

• abuse@fastfindremotejobs.com to report misuse of our service or our name;
• privacy@fastfindremotejobs.com for questions about personal information (see our [Privacy Policy] [LINK]).

12. Changes to this page

This page describes how our crawler works today. Before any material change to these practices takes effect, we'll update this page and its "Last updated" date.

13. Contact

FastFindRemoteJobs, operated by Conner Strategic Systems LLC [MAILING ADDRESS]

• Crawler questions and opt-outs: bot@fastfindremotejobs.com
• Privacy: privacy@fastfindremotejobs.com
• Abuse: abuse@fastfindremotejobs.com