1. Scope
This policy applies to the LockedIn browser extension for Chrome and Firefox. LockedIn has one purpose: when you visit LinkedIn’s feed, it redirects that visit to LinkedIn Jobs. It also provides a local redirect counter, a temporary toolbar badge, and optional browser notifications confirming redirects.
LockedIn is an independent extension and is not affiliated with, sponsored by, or endorsed by LinkedIn.
2. Information the extension accesses
LinkedIn page addresses
The extension receives access to page addresses on
linkedin.com
through its LinkedIn host permission. It checks only the hostname
and path needed to recognize LinkedIn’s /feed and
/jobs routes. This enables both normal navigations and
client-side navigations inside LinkedIn to be handled. Full page
addresses are not saved.
Local redirect count
After a confirmed redirect, LockedIn stores one number: the total number of redirects since installation. The number is stored in the browser’s extension-local storage. It is not synchronized to an account and is not sent anywhere.
Private-browsing status
LockedIn checks whether the redirected tab is private or incognito solely to exclude that redirect from the saved counter. It does not store private-browsing activity.
Notification permission state
LockedIn checks whether you have granted its optional notification permission so the interface can show the correct setting and the extension can decide whether to display a redirect notification.
3. Information LockedIn does not collect
LockedIn does not collect, store, or transmit:
- LinkedIn profile details, messages, posts, or page content;
- form entries, search terms, keystrokes, or credentials;
- cookies, authentication tokens, or account identifiers;
- your general browser history or activity on other websites;
- IP addresses, location, device identifiers, or diagnostics;
- analytics, advertising identifiers, or crash reports; or
- financial, employment, or other sensitive personal data.
4. How information is used
LinkedIn page addresses are processed temporarily and locally only to decide whether a redirect is required and whether it completed. The redirect count is used only to display the “redirects since install” total in the popup. Permission state is used only to operate the notification toggle and optional notifications.
LockedIn does not create a browsing profile, infer interests, evaluate employment activity, or use information for advertising, analytics, credit, eligibility, or automated decision-making.
5. Storage, retention, and deletion
The redirect count remains in extension-local browser storage until you clear the extension’s data or uninstall the extension. Pending redirects and toolbar-badge timers exist only in memory while the extension’s background process is running. LockedIn has no developer-operated database, account system, backup, or cloud storage.
Because no information is sent to the developer, there is no server-side copy for the developer to access, correct, export, or delete.
6. Browser permissions
- LinkedIn host access
- Allows LockedIn to recognize the relevant LinkedIn routes and perform redirects. Access is limited to LinkedIn.
- Declarative network request with host access
- Lets the browser apply a packaged rule that redirects the LinkedIn feed to LinkedIn Jobs without injecting code into the LinkedIn page.
- Storage
- Stores the local redirect count. LockedIn uses local storage, not synchronized storage.
- Notifications (optional)
- Displays a native confirmation after a redirect only when you explicitly enable this permission. Feed blocking and the toolbar badge continue to work without it.
LockedIn does not request broad browser-history, cookie, clipboard, identity, download, or page-content scripting permissions.
7. Native notification privacy
If notifications are enabled, LockedIn asks the browser and operating system to show the text “LinkedIn feed blocked. Jobs opened.” Depending on your operating-system settings, that message may be visible on a lock screen or to someone near your device. Notification display, history, and lock-screen behavior are controlled by your browser and operating system, not by LockedIn.
You can disable notifications at any time from the LockedIn popup or onboarding page without disabling the redirect feature.
8. Network activity, sharing, and third parties
LockedIn does not contact a developer server or analytics service.
Its only navigation change sends your existing LinkedIn tab to
https://www.linkedin.com/jobs. Your resulting interaction with LinkedIn is governed by
LinkedIn’s own terms and privacy practices.
LockedIn does not sell, rent, share, disclose, or monetize user information. It contains no advertisements, tracking pixels, affiliate links, remote configuration, or remotely hosted code.
9. Security
LockedIn minimizes data access by limiting its host permission to LinkedIn, keeping its redirect rule and application code inside the signed extension package, avoiding page injection, and retaining only a local numeric count. Browser extension isolation and your browser’s local-storage protections provide the underlying storage security.
No software can guarantee absolute security. Keeping your browser and extension updated helps ensure you receive current platform and dependency security fixes.
10. Your choices
- Leave optional native notifications disabled.
- Disable notifications later from the LockedIn popup.
- Revoke LinkedIn site access in browser extension settings, which prevents the core redirect feature from operating.
- Clear LockedIn’s local extension data or uninstall the extension to remove the saved redirect count.
11. Children’s privacy
LockedIn is not directed specifically to children and does not knowingly collect personal information from anyone, including children.
12. Policy changes
If LockedIn’s data practices change, this page and its effective date will be updated, and any disclosures or consent required by the browser stores will be provided before the changed practice is used. An update will not retroactively transmit locally stored information without a clear disclosure and any required consent.
13. Contact
Privacy questions can be sent through the developer support contact shown on the official browser-store listing from which you obtained LockedIn. Because the extension sends no information to the developer, support requests contain only the information you choose to provide.
14. Open-source components
LockedIn includes open-source software and fonts. Their copyright and license texts are available in the bundled third-party notices. These components run locally and do not receive user information from LockedIn.