Treat profiles like credentials
A Swift Tunnel configuration can contain details that are private to you or your team. That may include server addresses, authentication material, subscription URLs, or routing settings. Handle it with the same care you would give a password.
Avoid common leaks
Do not paste an unredacted configuration link into a public support request, chat room, screenshot, or issue tracker. QR codes can also contain the full profile, so blur or remove them before sharing screenshots.
Avoid storing profiles in notes or shared documents that other people can access. If a subscription link is exposed, ask its original provider whether it should be replaced.
Use trusted sources only
Import profiles only from a provider, administrator, or system you trust. Before connecting, check that the profile name, server information, and intended use make sense. An unknown configuration is not harmless just because it imports successfully.
Keep Swift Tunnel organized
Name profiles clearly, remove obsolete profiles, and use the app's current version. A small set of current profiles is easier to inspect and much less likely to lead to accidental use of an old or unknown configuration.
For more setup basics, see the Swift Tunnel import guide.