HireRoom
Extension · permissions and data access

Exactly what the extension can see and do.

The HireRoom Chrome extension (v0.4.5) assists with two jobs: saving a job posting into your workspace, and filling supported application forms from your verified profile. It works only on Greenhouse, Lever, and Ashby application pages, and only when you open it and click. It is not autonomous: nothing fills, submits, or sends anything without a click from you, and you stay responsible for every application submitted under your name.

Supported systems: three, no more

  • Greenhouse · supported in v0.4.5
  • Lever · supported in v0.4.5
  • Ashby · supported in v0.4.5

Behavior can differ between employer implementations of the same system. Two companies can run Greenhouse with different custom fields, so the fill result is never identical from posting to posting. SmartRecruiters, Workable, and BambooHR adapters were pulled from production because they were not verified against real postings; the extension says so on those sites instead of guessing. Workday support is deferred to a future release and the extension shows a placeholder there today.

Every permission, explained

This is the complete list from the extension manifest, with what each one is for. If the manifest ever gains a permission that is not explained here, our own test suite fails the build.

  • activeTabrequired
    Why it exists
    Lets the popup act on the one tab you deliberately open it on. There is no access to any other tab.
    When it runs
    Only when you click the HireRoom toolbar icon, and then Preview or Fill.
    What it can access
    The URL and page content of the current tab, at the moment you click.
    Can it modify anything
    Form-field values on that page, and only after you click Fill.
    Is data sent to HireRoom
    Nothing by itself. Data only moves through the actions described below.
    Is anything retained
    Nothing.
  • scriptingrequired
    Why it exists
    Runs the field mapper inside the apply page so your profile values land in the right boxes.
    When it runs
    When you click Preview (a dry run that changes nothing) or Fill.
    What it can access
    The apply form's structure: labels, fields, existing values, and the job details on the page.
    Can it modify anything
    The supported fields it can confidently map, only on Fill.
    Is data sent to HireRoom
    Nothing by itself.
    Is anything retained
    Nothing.
  • storagerequired
    Why it exists
    Keeps your API token and endpoint preference on your device so you paste them once, not every time.
    When it runs
    Read each time the popup opens; written when you save the popup's Settings tab.
    What it can access
    Only the extension's own storage area. It cannot read other extensions' or the browser's data.
    Can it modify anything
    Only its own storage area. No page data.
    Is data sent to HireRoom
    Nothing.
    Is anything retained
    Your token, locally, until you clear it or remove the extension. It is stored as plain browser extension storage; it is not separately encrypted by the extension.
  • greenhouse.io (all subdomains)required
    Why it exists
    Greenhouse application forms live on company-specific subdomains. The detector script runs here to recognize Greenhouse pages.
    When it runs
    The detector loads automatically at page idle; field mapping runs only when you click Preview or Fill.
    What it can access
    Page structure, form labels, existing field values, and job details on Greenhouse pages.
    Can it modify anything
    Supported form fields, only on Fill.
    Is data sent to HireRoom
    Only the actions you trigger: saving a clipped job, and the fill log entries.
    Is anything retained
    Clip and fill-log records in your HireRoom account, described below.
  • job-boards.greenhouse.iorequired
    Why it exists
    The current Greenhouse job-board host. Same behavior as the other Greenhouse patterns.
    When it runs
    Same as greenhouse.io.
    What it can access
    Same as greenhouse.io.
    Can it modify anything
    Supported form fields, only on Fill.
    Is data sent to HireRoom
    Only the actions you trigger.
    Is anything retained
    Clip and fill-log records in your HireRoom account.
  • boards.greenhouse.iorequired
    Why it exists
    The legacy Greenhouse board host, still in use by some employers. Same behavior.
    When it runs
    Same as greenhouse.io.
    What it can access
    Same as greenhouse.io.
    Can it modify anything
    Supported form fields, only on Fill.
    Is data sent to HireRoom
    Only the actions you trigger.
    Is anything retained
    Clip and fill-log records in your HireRoom account.
  • jobs.lever.corequired
    Why it exists
    Lever application forms. The detector script runs here to recognize Lever pages.
    When it runs
    Detector at page idle; field mapping only on Preview or Fill.
    What it can access
    Page structure, form labels, existing field values, and job details on Lever pages.
    Can it modify anything
    Supported form fields, only on Fill.
    Is data sent to HireRoom
    Only the actions you trigger.
    Is anything retained
    Clip and fill-log records in your HireRoom account.
  • *.ashbyhq.comrequired
    Why it exists
    Ashby application forms. The detector script runs here to recognize Ashby pages.
    When it runs
    Detector at page idle; field mapping only on Preview or Fill.
    What it can access
    Page structure, form labels, existing field values, and job details on Ashby pages.
    Can it modify anything
    Supported form fields, only on Fill.
    Is data sent to HireRoom
    Only the actions you trigger.
    Is anything retained
    Clip and fill-log records in your HireRoom account.
  • hireroom.techrequired
    Why it exists
    The popup calls the HireRoom API from here: fetching your profile and resume, saving clipped jobs, and writing fill logs.
    When it runs
    When you open the popup and use Clip JD, Preview, or Fill.
    What it can access
    The HireRoom API, authenticated with your token.
    Can it modify anything
    Your HireRoom data only: saving a clipped job and writing fill logs. It cannot delete or alter your profile.
    Is data sent to HireRoom
    This is HireRoom itself.
    Is anything retained
    On HireRoom's servers, per the privacy policy.
  • www.hireroom.techrequired
    Why it exists
    The canonical HireRoom host. Same API behavior as hireroom.tech.
    When it runs
    Same as hireroom.tech.
    What it can access
    The HireRoom API, authenticated with your token.
    Can it modify anything
    Same as hireroom.tech.
    Is data sent to HireRoom
    This is HireRoom itself.
    Is anything retained
    On HireRoom's servers, per the privacy policy.
  • hireroom.vercel.apprequired
    Why it exists
    The pre-launch preview host, kept so installs pointed at it keep working during the transition.
    When it runs
    Only if your popup endpoint is still set to this host.
    What it can access
    The HireRoom API, authenticated with your token.
    Can it modify anything
    Same as hireroom.tech.
    Is data sent to HireRoom
    This is HireRoom itself.
    Is anything retained
    On HireRoom's servers, per the privacy policy.
  • ATS hosts (optional declaration)optional · unused today
    Why it exists
    The manifest also declares the three ATS domains as optional host permissions, reserved for a future per-site consent flow.
    When it runs
    Never today: no code in the extension requests optional permissions at runtime.
    What it can access
    Nothing beyond the required hosts above.
    Can it modify anything
    Nothing beyond the required hosts above.
    Is data sent to HireRoom
    Nothing.
    Is anything retained
    Nothing.
  • ATS hosts (optional declaration)optional · unused today
    Why it exists
    Same optional declaration as above.
    When it runs
    Never today.
    What it can access
    Nothing beyond the required hosts above.
    Can it modify anything
    Nothing beyond the required hosts above.
    Is data sent to HireRoom
    Nothing.
    Is anything retained
    Nothing.
  • ATS hosts (optional declaration)optional · unused today
    Why it exists
    Same optional declaration as above.
    When it runs
    Never today.
    What it can access
    Nothing beyond the required hosts above.
    Can it modify anything
    Nothing beyond the required hosts above.
    Is data sent to HireRoom
    Nothing.
    Is anything retained
    Nothing.

Not requested, at all

  • cookies · Not requested. The extension never reads browser cookies; your token is pasted by you, not harvested.
  • tabs · Not requested as a full permission. Only activeTab, scoped to the tab you open the popup on.
  • webRequest · Not requested. The extension cannot observe, block, or rewrite your network traffic.
  • background service worker · The manifest declares none. Nothing runs when the popup is closed.
  • clipboard, downloads, history, bookmarks · None of these are requested.

Information used during autofill

When you click Preview or Fill, the popup fetches your profile from the HireRoom API with your token. The API returns your name, contact details, profile links, current company and title, years of experience, work-authorization answers, visa status, school, degree, graduation year, and your skills list, plus the label of your latest resume. Your resume PDF is fetched separately, only when you click Fill. The field mapper then uses your identity, contact, link, current-role, and work-authorization values for form fields, and your resume PDF for the upload slot. Nothing else in your account is touched.

What it reads on the page

On supported application pages the extension reads form labels, field names, existing field values, page structure, job details, and application questions. It reads them to map your profile values to the right fields and to show you the preview list. It does not read pages outside the three supported systems and the HireRoom site itself.

What it writes on the page

On your click, it populates the supported fields it could map confidently and attaches your resume to the upload slot when it can find one. Fields it cannot map are listed as skipped, not guessed. There is no guarantee every field fills correctly on every employer’s form; that is what the review step is for.

Information leaving your browser

  • Profile and resume fetch. When you use Preview or Fill, the popup downloads your profile fields and resume from the HireRoom API into the extension, authenticated by the token you pasted. This is your own data coming to your own browser.
  • Saving a clipped job. When you click Save on the Clip JD tab, the posting URL, title, company, and description text are sent to your HireRoom account.
  • Fill logs. Each Preview and each Fill records a log entry in your account: the system, the page URL, which fields were filled (field labels and truncated values), which were skipped and why, any errors, and the extension version. These rows back the fill history you see in the product, and they are not shared with anyone else.
  • No AI provider sees the form. Filling runs entirely between your saved profile and the page. No application form content is sent to Anthropic, OpenAI, or any other model provider by the extension.

You stay in control, and responsible

  • · Preview shows exactly which fields will be filled, with each value’s source, before anything changes.
  • · After Fill, you review the populated form. You are responsible for the correctness of what goes out under your name.
  • · The extension contains no code that submits an application form. The company’s own submit button stays yours.
  • · No CAPTCHA solving or bypass, in any form. If a challenge appears, you complete it yourself.
  • · No bulk or scheduled filling, and no background submission of any kind.
  • · Unsupported fields and unsupported systems are left for you, visibly, rather than guessed at.
  • · Filling a field with something you could not honestly claim would violate the same honesty floor the rest of HireRoom enforces. The extension fills from your verified profile; it does not invent.

Storage

Your API token and endpoint preference live in the extension’s local browser storage so you paste them once. The token is stored as plain extension storage; the extension does not add its own encryption layer. Anyone with access to your browser profile could read it, which is why the token can be rotated (below) and why it authorizes only profile reads, resume reads, job clips, and fill logs. On HireRoom’s side, your profile data is stored per the privacy policy.

Removing access

  • · Disable or remove the extension at chrome://extensions. Its local token storage goes with it.
  • · Rotate your token at /settings. The old token stops working immediately, everywhere it was pasted.
  • · Sign out of HireRoom to end your web sessions. Deleting your account removes the server-side data per the privacy policy.

Store status, honestly

The extension is not listed on the Chrome Web Store today. It installs by sideloading in Developer Mode, which is normal for a beta and not the final experience. A Chrome Web Store listing is planned; this page will change when it is live. Install instructions live on the extension page.

Report a problem

If the extension fills a field wrong, reads something it should not, or behaves in a way this page does not describe, open a ticket at /support. A fill that invents content is a bug and will be treated as one.