What we collect, and what we don't

The extension only reads page content on the applicant-tracking-system (ATS) domains listed below, and only on a job's application page. When you open an apply form on one of these sites, the extension reads:

• The page title and visible text of the current job posting — so we can match it to the role you saved and tailor your application to it.
• The form field labels on the apply page (e.g. “First name”, “LinkedIn URL”, “Years of experience”) — so we know which of your saved profile fields to fill into which box.

The ATS domains the extension is permitted to act on:

• job-boards.greenhouse.io / boards.greenhouse.io (Greenhouse)
• jobs.lever.co (Lever)
• jobs.ashbyhq.com (Ashby)
• apply.workable.com (Workable)
• jobs.smartrecruiters.com (SmartRecruiters)
• *.myworkdayjobs.com (Workday)
• ats.rippling.com (Rippling)

A single lightweight script also runs on other pages for one narrow purpose: it checks whether the page's own URL carries our ?jobbot_autofill=1 launch flag (set when you click “Apply” from your jobhigh5 dashboard). If the flag is absent — which is the case on every ordinary page you browse — the script does nothing and reads no page content whatsoever. It never inspects the text, forms, or contents of pages outside the ATS domains above.

To match a posting and fill a form, the extension sends the following to the jobhigh5 backend (api.jobhigh5.com):

• A scoped extension token — a credential issued only to your extension after you pair it from the dashboard. It identifies your account to our API and nothing else. It is not your password and cannot be used to log into the website.
• The URL of the job posting you're applying to.
• The parsed text of that posting (the same posting text described above), so the role can be matched and your documents tailored to it.
• The profile fields the extension fills in — your name, email, phone, links, and similar details. These are the values you already gave jobhigh5 at sign-up and in your settings; the extension fetches your own saved profile to fill the form. No new personal data about you is collected by the extension beyond the posting it's looking at.

The extension never collects, transmits, or stores:

• Your keystrokes.
• Your browsing history.
• Data from other tabs or windows.
• Passwords or any credentials you type into other sites.
• The content of any page outside the declared ATS domains listed above.

We do not sell your data, we do not use it for advertising, and we do not share it with anyone except the single processor named below.

jobhigh5 uses exactly one third-party processor that ever sees your application content:

• Anthropic, PBC — when you ask jobhigh5 to tailor your application, we send the job posting text and your resume to Anthropic's Claude API to draft a tailored resume and cover letter. That is the only data sent, and Anthropic is the only third party that receives it. Anthropic processes it to return the result and does not train its models on it. See Anthropic's privacy policy.

We also rely on standard infrastructure providers (hosting, our database, and email delivery) that process data solely to operate the service on our behalf and never receive your data for their own use.

Your account and profile live in our database. Your resume text is encrypted at rest. Connections to our servers use HTTPS. The extension token is stored only in your browser's extension storage and is revoked when you unpair the extension or delete your account.

You can permanently delete your account and everything tied to it — profile, resume, saved searches, matches, tailored documents, notifications, and any paired extension — at any time:

• Go to Settings → Danger zone and choose Delete account. Deletion is immediate and irreversible.
• To remove just your resume while keeping your account, use Settings → Resume → Delete.

If you can't sign in, email privacy@jobhigh5.com and we will delete your data on request.

Questions about this policy, or requests to access or delete your data, go to privacy@jobhigh5.com.

If we change how we handle data, we'll update this page and the “last updated” date above. Material changes will be communicated before they take effect.