Extension Permissions Explained
On this page
The HyperApply Chrome extension needs certain permissions to work alongside job listings and generate tailored CVs.
This page explains permissions in plain language.
> HyperApply is designed for individual job seekers and does not auto-submit applications.
Core permission categories (why they exist)
1) Access to job listing pages (limited to where you use it)
HyperApply needs to read the job listing content you can see in your browser so it can:
- extract role requirements
- suggest relevant skills
- generate a tailored CV
See: /docs/how-hyperapply-reads-job-descriptions
2) Storage (to remember your settings)
The extension may store:
- your preferences (template, writing mode)
- session information needed to keep you signed in
3) Network access (to call the HyperApply backend)
HyperApply must communicate with the backend service to:
- process CV generation
- store and retrieve your documents
- enforce plan usage limits
What the extension does *not* do
- It does not read unrelated websites “in the background.”
- It does not send bulk messages or mass-apply for jobs.
- It does not bypass the normal job platform UI.
If you want to review or change permissions
You can inspect extension permissions in:
- `chrome://extensions/` → HyperApply → Details
If you disable required permissions, some features may stop working.
FAQ
Does HyperApply scrape my LinkedIn account?
HyperApply reads job listing content you can see in your browser to generate your CV. It is user-initiated and designed for manual job applications.
Can I uninstall anytime?
Yes. You can uninstall the extension and stop using HyperApply at any time.