SkieDoes Skie keep Chrome Safe Browsing on for managed devices?
Yes. Skie keeps Chrome Safe Browsing on as a device owner rule, so students keep Google's warnings about phishing, malware and deceptive pages and cannot disable them. It is a security layer, separate from the content filter, and it is on by default.
Safe Browsing is Google's service that flags pages known for phishing, malware or harmful downloads. It protects against a different problem from adult content. A student could be tricked into a fake login page just as easily as stumble across something unsuitable.
On a managed device Skie sets it through Chrome policy, so the toggle in Chrome's privacy settings cannot be switched off. It applies to Chrome stable, beta, dev and canary alike.
It works alongside the other layers. The filtering DNS blocks categories of risky domains, the safe-sites filter checks page content, and Safe Browsing warns about known bad pages. Downloads from unknown sources are separately blocked at the Android level, which means a student who clicks past a warning still cannot install an app from a website.
From the admin side there is nothing to maintain. The setting is read back after every apply and counts toward the device's compliance score. If a device somehow reports it as not enforced, it shows up in the breach centre with the exact device named.
Practical tip: when you brief staff on what the filter does, separate the two ideas clearly. Content filtering is about what a student should see. Safe Browsing is about what could harm the device or the account. Teachers often mix the two when a page is blocked, and the distinction speeds up support requests.