Browser Extension Privacy Policy

The extension has one purpose: when you are on a single job posting, it lets you save that job to your private Hirelayer added jobs (Add job) and, where Hirelayer can apply on that application system, have Hirelayer tailor your résumé and apply for you (Apply). It does nothing else, and it shows nothing on pages that are not a job posting.

To decide whether a page is a single job posting, the extension looks at the page itself, in your browser:

• The page's web address.
• Structured job data the page publishes (schema.org JobPosting markup).
• The page's title heading, company name and apply buttons, to read the job title and company and to find the page's apply link.

This detection happens entirely in your browser. Visiting a page sends none of it anywhere. On pages that are not a job posting the extension shows nothing and looks again only when the address changes.

The extension talks only to Hirelayer's own servers, and only while you are signed in:

• When it shows its widget on a job posting: it checks your sign-in state, loads the list of your résumés so you can pick one, and sends the posting's web address (and, where the page has an apply link, that link's address) to ask whether Hirelayer can apply on that application system. Nothing else about the page is sent.
• When you click Add job: it sends the posting's web address, or the employer's job page address that the posting's apply link leads to. Hirelayer then reads the posting from that address on its own servers and saves the job to your account.
• When you click Apply: it does the above and then asks Hirelayer to start an application for that job with the résumé you chose. From there the application is handled by Hirelayer exactly as one started in the web app, under the Hirelayer Privacy Policy.

The extension never sends the text of pages you visit, your browsing history, or anything from pages that are not the job you chose to save.

Job boards such as LinkedIn and Indeed often send applicants to the employer's own job page. So that Hirelayer saves and applies to the right page, the extension finds where the job page's apply control leads. This happens only when you click Add job or Apply, never on its own:

• If the apply control is a link, the extension follows it to its final address. Your browser makes that request as if you had clicked the link, including any cookies you have for that site, and only the final address is kept.
• If the apply control is a button, the extension clicks it for you, reads the address of the tab it opens, and closes that tab. If nothing opens within a few seconds, there is nothing to resolve.

The address found this way is sent to Hirelayer in place of the job board's address. The content of the employer's page is not read by the extension.

The extension does not ask for a password. It uses the session you already have with the Hirelayer web app, read from Hirelayer's sign-in cookie through Clerk, our authentication provider. That session token is sent only to Hirelayer's servers, to identify your account. Signing out of the web app signs the extension out too.

• The status of each job you added or applied to from the extension (added, application started, or the error it hit), so revisiting a posting shows it. These are tied to your account and never shown to another account on the same browser.
• The résumé you last picked, so it is preselected next time.

Nothing is stored while you are signed out. This data lives in the extension's own storage in your browser; removing the extension deletes it. It is not synced between devices and not sent to Hirelayer.

• Read and change data on all websites: job postings live on thousands of employer and job-board sites, so the extension must be able to detect a posting on any of them, and, when you click Add job or Apply, follow its apply link to wherever it leads. It reads only what sections 2 and 4 describe and changes nothing on the page apart from showing its own widget.
• Cookies: to read your Hirelayer sign-in session (section 5). No other site's cookies are read.
• Storage: to keep the job statuses and résumé pick described in section 6.
• Active tab and scripting: so the toolbar popup can check whether the tab you clicked it on is a job posting. This grants access to that tab only, and only when you click the extension's icon.

The extension does not request access to your browsing history, tabs, downloads, or any other browser data, and it loads no code from outside the extension itself.

• It contains no analytics, tracking or advertising code and sends no usage data to anyone.
• It never collects your browsing history. Only the job you choose to save leaves your browser.
• It never fills in or submits a form on a website. Applications are made by Hirelayer from its own servers, after you click Apply.
• We never sell your data or use it for advertising.

• Clerk: authentication, as in the web app.
• Hirelayer's servers, hosted on Microsoft Azure: everything in section 3.
• The job sites you visit: only when you click Add job or Apply, as in section 4.

Hirelayer's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data the extension collects is used only to provide the features described here, is never sold, and is never used for advertising, for determining creditworthiness, or for any purpose unrelated to saving and applying to jobs.

• Removing the extension from your browser deletes everything it stored on your device.
• Jobs and applications you saved through the extension appear in your Hirelayer account and can be edited or deleted there like any other.
• You can delete your Hirelayer account and its data at any time, as described in the Hirelayer Privacy Policy.

Questions about this policy or the extension? Reach out:

We may update this policy when the extension changes. If we do, we'll revise the date above, and a change to what the extension collects will be reflected in its Chrome Web Store listing before it ships.