Privacy Policy
Last updated: June 19, 2026
At JD Saver, we take your privacy seriously. This Privacy Policy details how our Chrome Web Store extension and landing page handle data. Our design philosophy is simple: **you own your data, and we do not want it.**
1. Local Storage First (Extension)
All job descriptions, metadata (salaries, workplace locations, types), applicant statistics, network contact cards, interview round details, and resume text blocks are stored exclusively inside your browser's local sandbox database using the chrome.storage.local API.
This means your job applications history remains 100% offline, local, and private. We do not maintain user databases, servers, or trackers to harvest your applications.
2. Content Script Scoping
The JD Saver extension requests host permission access restricted exclusively to https://www.linkedin.com/jobs/*. This is the narrowest possible scope required to read page details when you actively click the extension icon. The extension will never monitor or inject scripts into other browser tabs or websites.
3. Pro Features Data Flow (Notion Syncing & Cloud Backup)
If you choose to purchase JD Saver Pro and enable Notion Syncing or Cloud Backup, data is handled with maximum privacy:
- The extension communicates directly with official Notion APIs (
https://api.notion.com) and Google APIs using your own authorization tokens. - For subscription validation, the extension queries our Cloudflare Worker endpoint (
https://jd-saver-backend.garamsoftwares.workers.dev/check-subscription) using an anonymous license key or your checkout email. No personal job search content or browsing history is ever transmitted to this endpoint. - Our Cloudflare Worker operates statelessly with encrypted KV storage strictly for verifying subscription active states and license validity.
4. Third-Party Payments
Pro purchases (both Monthly Subscriptions and Lifetime Licenses) are processed securely through certified PCI-DSS compliant providers: Razorpay and PayPal. JD Saver never collects, records, or stores credit card numbers, CVVs, or bank details.
5. Changes to This Policy
We may update this Privacy Policy to reflect security changes. Any updates will be posted on this page with an adjusted date.
6. Contact Us
If you have any questions or security feedback regarding this Privacy Policy, please visit our Contact page.