The Safeguard Safari extension on iPhone and iPad is confirmed to ship inside the iOS app and to be enabled in Settings. Its feature behavior is not described on the pages we reviewed, and the App Store notes say a workspace administrator must enable it. Ask before you roll it out.
What is confirmed?
- The extension is included in the Safeguard.sh iOS app, per the download page.
- You turn it on under Settings, Apps, Safari, Extensions, or Settings, Safari, Extensions before iOS 18.
- The app is free, runs on iPhone and iPad from 16.4 and needs a Safeguard account, per the App Store listing.
- The listing's privacy label says the developer does not collect data from the app, and Apple notes it has not verified that label.
What is not stated?
The browser extension docs we read cover the Chrome, Edge and Firefox side panel and sidebar. They do not describe the Safari extension. The download page and the App Store give install and enable steps only. So we do not describe what it shows on a page, which sites it runs on or which permissions it requests in Safari.
That is a limit of what we could verify, not a fault in the extension. If your team needs those details, ask Safeguard for them.
Who turns it on?
The 2.0.3 version notes say new features, including the Safari extension, must be enabled by the workspace administrator. For a company rollout, that makes two switches: the admin side and the device toggle in Settings.
Questions to ask before rollout
- Which Safari permissions does the extension request, and for which sites?
- Does it read page content, and when?
- What does the privacy label cover, given Apple has not verified it?
- Can our admin turn it off per workspace?
- Which iOS versions have you tested, given the 2.0.3 fix for iOS 27?
How to test it yourself
Install it on one test device. In Settings, open the extension's entry and read the permissions Safari shows for it. Safari lets you see which websites an extension can access. Compare that with what Safeguard tells you.
How does this compare with the other browsers?
For Chrome, Edge and Firefox the docs state the design: a thin wrapper around the search page with minimal permissions. For Safari we have no equivalent statement, which is why the questions above matter more here than elsewhere.
What to do
- Pilot on one iPhone and one iPad.
- Get the admin switch on for the pilot group.
- Read the extension's permissions in Settings.
- Send your questions to Safeguard and keep the replies with your rollout notes.
Quick check
Does the Safari extension work without a workspace admin?
The App Store notes say the Safari extension must be enabled by the workspace administrator. Check with your admin if it is not available.
Is the privacy label verified by Apple?
The listing states the developer collects no data from the app, and notes that Apple has not verified that label.
Sources
Last reviewed: 18 October 2026.
