Our requests to your site
JobScanner, at get-me-hired.com, is a job-search service. When it reads anything for its job search (a job feed, an application system's API, or a web page), its requests carry this user agent:
JobScanner/1.0 (+https://get-me-hired.com/bot; support@get-me-hired.com)
Write to support@get-me-hired.com about any of them. It reaches the person who runs the service.
When a member pastes a link to your site
- We read a page of yours for a member only when they paste a link to a job ad on your site, or a link that redirects to one, to add that one job to their own search. Each paste reads the page at most once. We do not crawl, follow the links on the page, or come back to it on a schedule. Our other kinds of request are at the end of this page.
- robots.txt first. Before we request such a page, we read your
/robots.txtand follow it (RFC 9309) for the product tokenjobscanner, or for*when no group names it. If it disallows the page, we do not request it. A robots.txt that answers with a server error, or does not answer, counts as disallowing everything; one that is not there (a 4xx) as no rules. We keep your site's answer for up to 24 hours. - If the page redirects, we follow at most 3 steps, reading each new site's robots.txt too, and make at most 8 requests for one link, robots files included.
- At most one request every 2 seconds to your site, and at most 200 different pages and 600 requests to it in a day (UTC). After a 429 we ask nothing of your site for 60 minutes, and after a request that timed out or went unanswered, for 15 minutes. The server keeps these counts in its memory, so a restart starts them afresh.
- The request carries no cookies, no referrer and nothing from the member's browser. We do not sign in, and we do not try to get past a check meant for people.
- If your page says
noarchive,nosnippetornonein its meta robots tag or itsX-Robots-Tagheader, its text is shown to nobody but the member who added it and the person who checks it.
What we keep
The job's title, employer, place and dates, as the member chose them from your page or typed them, the description the member chose, the page's address, and, for the person who checks the job, what else the page offered and the first words of each paragraph the member left out. Not your page's HTML, and not your robots.txt. A person checks the job before anyone else can see it, and other members are shown it only if the employer's own website vouches for the page: the page is on the employer's domain, or the employer's website links to that exact page or, when the page is on a platform that gives each of its users an address of its own (such as acme.teamtailor.com), to any page at that address. Then the email addresses and phone numbers our scan finds are taken out of its title, employer and description, and they see it, its description included, until the job closes here, at most 30 days after we read the page. Its text is deleted then at the latest, unless a person found the job not genuine, before or after other members could see it: then it is kept, hidden, for 30 days after that decision, the time the member has to contest it.
To stop us
- Add this to your robots.txt, and within 24 hours we stop reading the pages
members paste from your site:
User-agent: jobscanner Disallow: / - Or write to support@get-me-hired.com, and say which page or site. On the day we read your message we take down every job read from it and delete its text, and, if you ask us to stop reading your site, refuse its host from then on for the links members paste: a link to it, or a redirect to it, is refused before any request is made. A job a person had already found not genuine is down already, and its text is kept for the 30 days above.
- Neither your robots.txt nor our refusal of your host stops the checks under Our other requests, below: they do not read robots.txt, and they do not look at the hosts we refuse.
Our other requests
The same user agent is on our scheduled reading of the sources this service collects postings from: public job feeds, application systems' APIs, and the career pages of a few employers, with the job pages those link to. And when the person who runs the service checks a job somebody added here, this server may read an employer's front page and at most 3 more pages of the same site that look like its careers pages, looking for a link to the job or to its employer's job board, and ask IANA, the domain's registry or the certificate log crt.sh how old the page's domain is. Those checks start only when that person asks for them.