Last updated: 2026-07-21
The ApplyGuide browser extension scores a job posting on the page you are viewing against the resume in your ApplyGuide account. It sends job-posting content to our servers when you click Analyze, Save Job, or Tailor. It does not read or transmit content from pages you have not acted on. The extension also sends install and product-analytics events, described below.
The main ApplyGuide privacy policy at /privacy.html covers the rest of your account (resume, billing, deletion). This page only covers what the extension itself does.
api.applyguide.net together with your auth cookie so we can score it against your resume.client_id) generated by the extension on first launch. Persisted in chrome.storage.local.us.i.posthog.com.ApplyGuide can help you fill out job application forms. This is off until you turn it on, and it never runs by itself.
You turn it on. "Interactive mode" is off when you install the extension. You switch it on at the top of the extension window (or in the sidebar settings). While it is on, ApplyGuide adds fill buttons on job application pages. While it is off, there are no fill buttons and nothing is read for filling.
Nothing fills until you press a button. Opening a page never fills anything. Filling only starts when you press Quick Fill or Pro Fill.
Quick Fill stays on your device. Quick Fill uses the profile details and resume you already saved to your account and fills the fields it can match. It does not send the page or your answers to a server, and it does not use AI.
Pro Fill uses AI. When you press Pro Fill, ApplyGuide first fills what it can on the device, then sends only the questions still left unanswered, plus the parts of your resume and profile that could answer them, to ApplyGuide's servers and to OpenAI. The AI drafts answers for those questions and Pro Fill writes them into the form for you to review. We send only the leftover questions and the matching resume/profile details. We do not send the whole page, and we do not send the answers listed under "Answers you choose to save" below.
Answers you choose to save (work authorization and similar). You can optionally save answers to eligibility and demographic questions: work authorization, sponsorship, disability, veteran status, gender, and race or ethnicity. These are voluntary. You can answer "prefer not to answer," and you can edit or delete any of them at any time. We use them only to fill applications you start, we never use them to make a decision about you, and we never send them to the AI. A form field for one of these topics is filled only from your own saved answer, or left blank for you to handle.
Answers we remember for next time. When you fill in something we could not, ApplyGuide can save it so the next form is easier. Standard details (like your address) go into your profile. Other question-and-answer pairs are kept as notes that help Pro Fill answer similar questions later. You get a "Saved for next time" note with an undo the moment it happens, you can delete saved answers, and they are included when you export or delete your account data. Answers about the sensitive topics above are only saved after you tap to confirm, and they are stored with your other saved answers, never as AI notes.
What filling never does. ApplyGuide never types a password, never checks a consent, agreement, or "I certify" box, never solves a CAPTCHA, never attaches a file (including your resume), and never submits an application. You always submit yourself.
Deleting this data. Everything above is stored under your account. When you delete your account, all of it is deleted with it, including your saved answers, your remembered answers, and the records of forms you filled.
chrome.storage.local)latest_analyze: the most recent analyze result, used for a brief 30-second window so the popup can re-render without a network call.resume_status_cache: a short cache of whether your account has a resume uploaded.hidden_hosts: sites where you have dismissed the sidebar.ag_active_tab: which sidebar tab was open last.applyguide_ph_client_id and applyguide_ph_distinct_id: the PostHog install UUIDs.We do not store your authentication token in chrome.storage.local. The previous version of this policy said we did. That was wrong; sign-in is now cookie-based (see Section 5).
When you use Pro Fill, we keep a short, redacted record of the form session so we can run the daily limit and support the feature: which site (by domain), how many fields were filled, declined, or skipped, and how many tokens the AI used. These records do not store your answers, the form's questions, or your resume text. They are deleted with your account.
When you sign in on applyguide.net, our web app sets an HTTP-only cookie (auth_token) scoped to the .applyguide.net domain. The extension reads this cookie via the Chrome cookies API only to check whether you are signed in and to attach the cookie to authenticated API calls.
The token never appears in chrome.storage and is not readable by JavaScript on web pages (it is HTTP-only). Signing out on the web app clears the cookie, which the extension detects within a few seconds and reflects in its UI.
| Permission | Why we need it |
|---|---|
activeTab |
Lets the popup read the active tab when you click the toolbar icon, so we can show whether the current page looks like a job posting. |
scripting |
Used as a cold-load fallback: if you click Analyze on a tab where the content script had not yet loaded, we inject the extractor to read the visible job description. |
storage |
Stores the small set of cached values listed in Section 4 on your device. |
cookies |
Reads the auth_token cookie on .applyguide.net to check sign-in state and detect sign-out from any tab. |
https://*.applyguide.net/*: our API and web app.https://us.i.posthog.com/*: product-analytics endpoint.Only pages on applyguide.net and www.applyguide.net can send messages to the extension. This lets the web app tell the extension things like "you just upgraded to Pro" so the sidebar UI updates without a refresh.
<all_urls>)The extension's content script matches all URLs, but it is gated to do nothing on pages that are not job postings. Here is what actually happens on a page load:
document_idle (after the page has finished loading).JobPosting object in LD+JSON.We use the broad match because new ATS templates, careers pages, and SPA route changes appear constantly. A narrow allow-list would miss them. The cost of the broad match is that the script briefly runs on every page; we pay that cost so you don't have to copy-paste job descriptions.
The extension itself talks to a small number of third parties. Each is also listed on the full subprocessor page.
| Provider | What gets sent | Why |
|---|---|---|
| ApplyGuide servers (AWS) | Job description text, page URL, page title, resume identifier, your auth cookie | To score and tailor against your resume |
| OpenAI (via our servers) | The job description text, plus the parsed resume content we already hold | To generate the fit score, verdict, and tailored bullets |
| PostHog | Event names, install UUID, fit score, verdict, host name of the analyzed page, extension version, and your email on identify when signed in | Product analytics |
| logo.dev | Company name or domain string (e.g. "Lyft") as an image URL path | To display the employer's logo on Saved Jobs cards |
If you installed the extension after clicking one of our ads, we also report that install to the ad platform you came from (currently Meta), sending a scrambled version of your email, your IP address, browser info, and the ad click ID so we can tell which ads work.
Wipe local state: right-click the toolbar icon → Manage Extension → uninstall, or sign out from the extension to clear the local caches.
Erase account data on our servers: deletion is account-wide and lives on the main app. Open applyguide.net → Settings → Manage Account → Delete Account. See the main privacy policy for what is deleted and on what timeline.
For questions about this policy or to report an issue, use the bug-report form:
Contact us