JACX — Job Application Control eXtension • Last Updated: October 11, 2026
All data processed by JACX remains exclusively within your local browser sandbox:
Information handled by JACX is stored exclusively in your browser’s local IndexedDB and chrome.storage.local:
JACX complies with Google’s Minimal Permissions Policy. Each permission serves an essential user-facing function:
| Permission | Purpose & Justification |
|---|---|
sidePanel |
Opens a side-by-side workspace within Chrome so you can review and control application autofill without leaving the job page. |
storage |
Persists your profiles, encrypted vaults, and application records on your computer. |
activeTab & tabs |
Detects navigation to job application pages and keeps tracker records synchronized. | offscreen |
Generates PDF cover letters and performs document processing securely within an offscreen browser document. |
<all_urls> (Host) |
Job application portals span thousands of distinct domains (Greenhouse, Lever, Workday, Ashby, and company career portals). Broad host access enables form detection across any career site. The extension only executes on detected job postings. |
Default Offline Mode: By default, JACX functions completely offline using heuristic matching, rule-based algorithms, and local semantic parsing.
Optional BYOK (Bring Your Own Key): If you choose to configure external AI model providers (such as OpenAI, Anthropic, or a local Ollama instance):
You retain absolute control over your career data:
.appvault archive of your entire workspace at any time, or export standardized candidate profiles adhering to the open Applicant Profile Protocol (APP v1.0.4) standard.For questions or feedback regarding this privacy policy:
Author: Caglar Orhan
LinkedIn: https://www.linkedin.com/in/caglarorhan
GitHub: https://github.com/caglarorhan
Protocol Standards: https://app-protocol.org/
Support: support@jacx.dev