Chrome Extension · works with Greenhouse

Privacy Policy

GreenMaxing Toolbar — exactly what data the Extension touches, where it goes, and what your rights are.

Last updated: July 3, 2026

GreenMaxing Toolbar ("the Extension," "we," "us") is a browser extension that adds a docked productivity panel to Greenhouse recruiting pages. This policy explains, in plain English, exactly what data the Extension touches, where it goes, and what your rights are. It is written specifically for this Extension — not a boilerplate template.

The Extension is not affiliated with, endorsed by, or sponsored by Greenhouse Software, Inc. "Greenhouse" is used only to describe the site the Extension works on.

1. Who is responsible for your data (controller / processor)

The Extension is a tool operated by a recruiter or employer, running inside that person's own browser and their own authenticated Greenhouse account.

Because the Extension has no server, we (the developer) cannot see, collect, sell, or retain any candidate data at any time.

2. Where the Extension runs

The Extension only activates on Greenhouse pages, inside your own logged-in Greenhouse session:

It reads data the same way your browser already does — using the session cookie you are already signed in with. It never logs you in, never stores your Greenhouse password, and never accesses Greenhouse on your behalf when your browser is closed. It performs no background network activity of its own.

3. What data the Extension accesses, and why

All of the following is read from the Greenhouse pages/endpoints you are already viewing, and is used only to render the panel and power the features you invoke:

DataWhy it is accessed
Candidate name, source, tagsShown in the candidate snapshot; name is used to personalize AI-drafted emails.
Candidate contact details (email, phone, LinkedIn URL)Shown in the contact card; email is the recipient when you send a rejection/other email.
Résumé (PDF link and extracted text)Shown as a one-click résumé link; résumé text is the primary input to AI scoring.
Screening-question answersDisplayed to you in the dashboard so you can read them. These are stripped out before anything is sent to an AI provider (see Section 4).
Salary, work-authorization, and similar application fieldsDisplayed in the dashboard snapshot for your review.
Job description and your role criteria (need-to-haves, dealbreakers, soft negatives)Sent with the résumé to the AI provider so the score reflects the role's bar.
AI scores, summaries, and evidence snippets you generateStored locally so scores persist between visits; optionally written back into the candidate's Greenhouse record as a private note/tag.

The Extension does not access data from any non-Greenhouse site (other than opening LinkedIn and calling the AI endpoints described below), and does not track your browsing.

4. What is transmitted to third-party AI providers

The AI features — candidate scoring and rejection-email drafting — are opt-in. They do nothing until you enter your own AI API key and enable them. Nothing leaves your machine for AI purposes unless you invoke one of these features.

When you use an AI feature, the Extension sends the following, and only the following, to the AI provider you selected:

Screening-question answers are removed before this request is made. No contact details, salary, work-authorization, or Greenhouse identifiers are included in the AI request.

It goes to your provider account, under their terms

The request is sent directly from your browser to the AI provider's API, using your own API key. It is billed to your own account. We never receive a copy, and your API key is stored locally and is never sent to us or to any Greenhouse page.

Whichever provider you choose becomes a sub-processor of that data, and the data is subject to that provider's retention and model-training policies, not ours. Please review your chosen provider's terms:

As of this writing, the API services of these providers generally do not train their models on data submitted through the API, but you are responsible for confirming the current terms and configuration of the account and key you use.

Automated decision-making

AI scores are produced by an automated model and, at your option, written into the candidate's Greenhouse record as a note or tag. This is an automated-processing artifact (relevant to GDPR Article 22 and CCPA). As the controller, you remain responsible for any decision about a candidate; the score is a decision-support signal only, and a human (you) makes the final call.

5. Where data is stored, and for how long

We recommend leaving Debug mode off for routine use, since it retains the most sensitive content locally.

6. How to clear your data

You can remove locally stored data at any time by:

  1. using the Extension's "Clear stored scores & debug data" control in settings,
  2. removing the Extension from chrome://extensions, which deletes its local storage, or
  3. deleting your API key from the settings panel to stop all AI transmission.

To have candidate data deleted from an AI provider, use that provider's data-deletion process on your account. To delete data from Greenhouse itself, use Greenhouse's own tools — the Extension does not control Greenhouse's records beyond notes/tags you explicitly write.

7. Children's data

The Extension is a workplace tool for professional recruiters and is not directed to children. It does not knowingly access or process data of anyone under 16, and it has no age-gated or consumer-facing features. This section is included for completeness; in normal use the Extension handles adult job-applicant data only.

8. Your rights (GDPR / CCPA/CPRA)

Because candidate data stays between you (the controller), Greenhouse, and your chosen AI provider, data-subject requests should be directed to the controller (the employer/recruiter using the Extension) and, where relevant, to the AI provider.

Depending on where the data subject lives, they may have the right to:

The Extension developer holds no candidate data and so cannot fulfil access/deletion against a central store — there isn't one. We will, however, help you understand exactly what the Extension transmits and stores so you can respond to a request. Contact: bretfeig@gmail.com.

9. Our certifications

10. Changes to this policy

We may update this policy as the Extension changes. Material changes will be reflected by updating the "Last updated" date above and, where significant, noted in the Extension's store listing or release notes. Continued use after an update means you accept the revised policy.

11. Contact

Questions about this policy or the Extension's data handling:

Email: bretfeig@gmail.com