What the extension can read
The Chrome permissions, ATSReady host access, and page data the extension inspects when it detects or saves a job posting.
On this page
The ATSReady extension reads page data to detect job postings and prepare a cleaned job payload when you save. The size ceiling on that payload is on File types and size limits.
Chrome permissions
| Chrome access | Why ATSReady uses it |
|---|---|
| Local extension storage | Save sign-in state, plan access, preferences, and recent-save state |
| Current tab access | Work with the page you are viewing |
| Tab lookup | Check the active tab and its URL |
| Chrome sign-in | Complete the Google sign-in flow through Chrome's identity service |
| Background refresh alarms | Refresh preferences and recover pending polls |
| Side panel access | Open the ATSReady side panel |
| Page interaction support | Run the page logic needed for detection and save flows |
Network scope
Each build of the extension can call one ATSReady API host:
- development:
https://api-dev.atsready.ai/* - staging:
https://api-staging.atsready.ai/* - production:
https://api.atsready.ai/*
It does not request wildcard access to all atsready.ai subdomains.
Page-reading scope
The content script is registered against every page you open, in every frame, minus a fixed exclude list built into the extension. ATSReady's own site is on that list, along with search, mail and document tools, video and social networks, large retail and reference sites, and common chat and communication tools.
Being registered on a page is not the same as acting on it. On every page the script runs the detection checks described in why the extension stayed quiet, and on pages that do not look like postings it removes its control and does nothing further. On candidate job pages it reads the DOM to detect title, company, structured data, and main content. Page content leaves your browser only when you save.