The removal of the Trusted Networks feature from F-Secure VPN on iOS has made the user experience wo

vmvm

The removal of the Trusted Networks feature from F-Secure VPN on iOS has made the user experience worse.

Users should be able to define their own trusted Wi-Fi networks where the VPN does not start automatically. The current “Turn on VPN automatically” option does not solve this issue, because the VPN remains active even on trusted home networks.

The previous behavior was better: the VPN could automatically activate on public or unknown networks while staying disabled on user-defined trusted networks.

Please consider bringing back a Trusted Networks / trusted Wi-Fi network feature for the iOS VPN app. This kind of user control is important for people who want automatic protection without having the VPN running unnecessarily at home or on other trusted networks.

Ukko

just as an addition to your another topic:

so, this discussion: Trusted Networks option missing (IOS) and solution for kind of 'both points' are outdated now? As well as for Android (community.f-secure.com/en/discussion/129438/where-is-trusted-network-setting).

I mean, the change from a bit of direct "Trusted Networks" to "Wi-Fi Protection" feature is not a fresh one situation.

The current “Turn on VPN automatically” option does not solve this issue, because the VPN remains active even on trusted home networks. The previous behavior was better: the VPN could automatically activate on public or unknown networks while staying disabled on user-defined trusted networks.

Is this something fresh? Introduced recently? Or did this design already exist back when mentioned above topics were current?

Thanks!

JOnes

@Ukko , this does not appear to be a newly introduced change. F-Secure already confirmed in May 2025 that the separate Trusted Network option on iOS had been removed and replaced by the more integrated Wi-Fi Protection feature. Therefore, the earlier discussions are still relevant to the underlying issue.

@vmvm , I agree with the main point of your request. Automatic Wi-Fi classification is not equivalent to allowing users to define their own trusted networks.

The required use case is quite straightforward:

• VPN starts automatically on public, open or unknown Wi-Fi networks.
• VPN remains disabled on explicitly selected home or other trusted networks.
• The user, rather than the application alone, decides which networks are trusted.

There also appears to be a documentation inconsistency. F-Secure’s current iOS instructions indicate that a trusted network can be added to bypass automatic VPN use, and the iOS version 26.3 release notes mention a fix related to changing trusted networks. This seems to conflict with both the earlier official statement and the application behaviour described here.

Could an F-Secure representative therefore clarify the following for the current iOS version?

1. Are user-defined trusted Wi-Fi networks currently supported?
2. If they are supported, where exactly is the setting located?
3. Which application version and subscription type include the feature?
4. If the feature has been removed, why do the current instructions and release notes still refer to trusted networks?
5. Does Wi-Fi Protection use only automatic security classification, or can the user override the classification for a specific network?

If manual trusted-network selection is no longer available, I support restoring it. “Turn on VPN automatically” alone does not provide the same functionality or level of user control.

Ukko

F-Secure’s current iOS instructions indicate that a trusted network can be added to bypass automatic VPN use, and the iOS version 26.3 release notes mention a fix related to changing trusted networks. This seems to conflict with both the earlier official statement and the application behaviour described here.

I think most of official statement(s) align with the current iOS guides (found on the Online Help portal / maybe in the app's built-in Help as well). But trying to use "trusted networks" (as 'old' feature) is surely conflicting with current "Wi-Fi protection" (as 'new' feature).

As you wrote - per documentation - it should still be possible to 'choose' a trusted network.

I mean, it says ""You can set the app to automatically use VPN when you connect to a WiFi network that is not trusted."" While allowing the option to skip this for "manually" selected trusted networks.

And per mentioned topic - maybe - if kind of global "Turn on VPN automatically" option is enabled, then it will enable VPN even for trusted networks.

So, you should disable this option; then define Wi-Fi Protection for only 'untrusted'/'unsafe' ones. Thus the design is like turn on vpn automatically for unsafe/public/untrusted Wi-Fi connections (in contrast to turn on always for any network). Where you can still choose/mark a trusted one.

This, probably, does not cover automatically mobile data (but it is still possible to enable VPN manually).

// I did not see any mentions for 26.3 iOS release. But for 26.2 indeed: ""Fixed Wi-Fi Protection stopping after changing trusted networks"" (dated to 12.03.2026)

// and, as I understand it, this knowledge base article states: """once WiFi Protection is enabled, unsafe Wi-Fi is automatically detected, and the user is prompted to turn VPN ON to encrypt their traffic""" like autodetection is only about unsafe rather than 'safe' ones (which you manually choose; or which 'anyhow' automatically treated as safe).

JOnes

Summary: (personally)

The VPN feature should follow the same principles on Windows, macOS, Android, and iOS.

Users should be able to:

• keep the VPN disabled on trusted networks;
• choose separately whether the VPN is used on mobile data;
• clearly see why the VPN was activated or remained disabled.
• VPN should be able to handle rapid network changes if the device moves from one network technology to another (managing multiple simultaneous network interfaces)

Automatic network classification should assist the user, not replace the user’s own choices. Setting names, functionality, and documentation should be as consistent as possible across all platforms.

This would maintain strong security on public networks while preventing the VPN from unnecessarily reducing usability, connection speed, or access to local devices on trusted networks.

vmvm

@JOnes , Exactly!