To set up Safeguard in Firefox, open the add-on listing from safeguard.sh/download, add it, open the sidebar from the toolbar icon and approve the browser from your Safeguard account. You need Firefox 113 or later and a Safeguard account. Setup takes a few minutes.
What do you need before you start?
- Firefox 113 or later, per the browser extension docs.
- A Safeguard account. The add-on does not work without one.
- A few minutes to check the listing before you click Add.
Step 1: Get the real listing
Start from safeguard.sh/download, not a search result. Lookalike extensions that borrow a security vendor's name are a known habit, so the link source matters. The download page points Firefox users to addons.mozilla.org, under the add-on name Safeguard-sh.
On the listing, check three things. The publisher should read Safeguard.sh Inc. The current version should be 1.0.4, as the listing showed on our check. The package is small, about 226 KB, so a very large download would be a reason to stop.
Step 2: Read the data section before installing
The listing separates permissions from data collection. It shows optional access to data for all websites. It also shows that the developer declares collection of authentication information, website activity and website content. The docs, for their part, say the extension collects no data and makes no Safeguard API calls of its own. We cannot reconcile those two statements from the pages alone, so read both and decide with your own security team. The limits post in this series goes deeper.
Step 3: Add it and open the sidebar
Add the extension. Firefox shows a toolbar icon titled "Open Safeguard". Click it and the sidebar opens next to the current page.
Step 4: Sign in by approval
You do not type a password into the extension. You approve the browser from your Safeguard account, in a flow the listing likens to the Safeguard CLI. Signing out revokes the session.
Step 5: Verify it works
The docs give a simple test. The panel should show the login page first, then the search page after sign-in. Search results should render. Then close Firefox completely and reopen it.
That last test matters because the docs name a known limitation. The web app's session cookie uses SameSite=Lax, which can stop login persisting across a browser restart inside the panel. The docs say the fix is server side. Until then you may need to sign in each session.
Step 6: Try a real question
Ask something whose answer you know. Then open the same thread at app.safeguard.sh, since the listing says conversations are shared with the web app.
What about a team rollout?
Test with two or three people and keep the notes. Record the version you approved, since the listing shows 1.0.4 today and will change. Tell people to ignore any other link, and to report any extension that uses the Safeguard name from a different publisher.
What to do
- Open safeguard.sh/download and follow the Firefox link.
- Confirm publisher and version.
- Review the optional all-websites permission and decide.
- Sign in by approval and test across a restart.
- Tell your team which link is the approved one.
Quick check
Why do I have to sign in again after restarting Firefox?
The docs describe a session cookie setting that can prevent login from persisting in the panel. They say the fix is on the server side, so for now you may sign in each session.
Does the add-on need a password?
No. You approve the browser from your Safeguard account, and no password is entered in the extension.
Sources
Last reviewed: 18 October 2026.
