You tapped something in a VPN app, and iOS answered with a dialog you did not expect: the app would like to add VPN configurations, with Don't Allow and Allow underneath. That dialog is the system's routing permission, and it appears once per configuration the app tries to install. Allow it when you opened the app and meant to connect; tap Don't Allow when the request arrived while you were doing something else, then work out what put it on screen. Nothing in the wording tells you whether the provider deserves trust — it only records that iOS is about to hand part of the network stack to this app.

What iOS is asking you to approve

An ordinary app cannot touch the packet path. A VPN client has to be built against Apple's NetworkExtension framework and signed with the Personal VPN entitlement; when it wants a tunnel it creates a configuration object and asks the system to save it, and that save call is what raises the prompt. The phrasing shifts between releases — recent versions say add VPN configurations, older ones add a VPN configuration — but the meaning is fixed: an app you installed wants a persistent entry in Settings > General > VPN & Device Management.

The entry is persistent by design. It outlives app crashes and reboots, it can reconnect while the app is closed, and it can carry on-demand rules that bring the tunnel up when you join a network. That is exactly why iOS asks instead of just doing it, and why the answer is stored rather than requested again on every connect.

Read the dialog before you tap Allow

Treat the prompt as a claim you can check in a few seconds. Stop at the first item that fails.

  • The name in the dialog matches an app you installed. A prompt credited to something you do not recognise is a reason to tap Don't Allow and keep looking, not a thing to test.
  • You were inside that app when it appeared. First-run setup and connect buttons are the normal triggers.
  • The app has not just been updated or reinstalled without you. A new version can add a configuration and ask again.
  • Nobody is asking for your Apple ID, a card number or a code from a message. The VPN prompt never wants those, so a dialog that does is a different dialog.

When all four hold, Allow is a fair answer for a provider you picked on purpose. If you are unsure, tap Don't Allow; the app will ask again the next time it saves, and you lose nothing by waiting an hour.

Verify the configuration after you allow

Approval starts the check, it does not finish it. Open Settings > General > VPN & Device Management and look at the VPN block. You should see one row named after the app or the profile it installed, with a status line and an info button. Tap that button to read the server address, the account name if there is one, and whether Connect On Demand is switched on.

Then decide whose row it is. A personal VPN you created from an app is yours to edit and delete; a row that says it is managed by an organisation is not, and its removal runs through whoever enrolled the device. Seeing both means two different authorities share the device, and you should know which one is carrying your traffic right now.

Last step: connect once and confirm traffic really follows the tunnel. Load a page that echoes your public address and check that the address belongs to the provider, not to your home connection. If the row says Connected and the address has not changed, the configuration is installed but not routing, and the fix is in the settings on that info screen rather than in the app.

What approval does and does not cover

Allow hands the app the ability to route traffic under its configuration. That is a large permission in one direction and a narrow one in the other. The app can send your packets through its servers and it can see the metadata attached to them: which addresses you contacted, when, and how much moved. It cannot read the inside of an HTTPS session, and it does not gain your photos, messages, microphone or Apple ID.

Coverage is narrower than everything, too. A configuration may route all traffic or only some destinations, and per-app tunnelling — where only named apps use the tunnel — is arranged by a device manager, not by tapping Allow. iOS keeps one personal VPN connection active at a time even when several configurations are listed, so a second app cannot quietly take over from the first while it is connected.

Revoke it properly when you stop using the service

Deleting the app is not a dependable way to remove the configuration. Check the VPN list yourself and delete the row from its info screen if it is still there. On a device you are retiring, do the account side as well: sign out in the provider's dashboard or revoke the device there, because a deleted local row does nothing about a session the server still treats as valid.

Managed devices are the exception. When the row says an organisation installed it, a local delete either fails or is undone at the next check-in, and only the organisation's own removal process will stick.

When the prompt keeps coming back

A repeat prompt usually means the configuration is being created again, not that the first approval failed. The common causes: the app writes a fresh configuration on every launch and iOS treats it as new, an on-demand rule dropped the old entry, a profile was reinstalled by a device manager, or several configurations exist and the app is asking about one you never noticed.

Count the rows first. If the list grows each time you open the app, the app is not reusing its configuration and the fix belongs to the developer or to a clean reinstall. If the list stays at one and the prompt still returns, look for a management profile reinstalling it — that is a policy question, not a bug you can tap away.

Before you move on, confirm three things: the row in Settings is the one you approved, the address you see while connected belongs to the provider, and the account side is revoked if you are finished with the service. Those three cover what the prompt granted, what it is doing now, and what it will keep doing after the device leaves your hands.

Artaigilean co-cheangailte