Route what you choose.

Most VPN interfaces start with a country or server list. FiestaVPN starts with the thing the user wants to route.

The product design includes built-in profiles for:

• Telegram.
• YouTube.
• WhatsApp.
• Instagram.
• Facebook.
• LinkedIn.
• Slack.
• Discord.
• All Connectivity.
• Custom application and destination profiles.

Only one profile is active at a time, so the connected state remains understandable.

A selective profile is intended for the moments when a person needs one application or service to use a private route but does not want unrelated banking, work, local, gaming, or general device traffic to follow it.

The connected screen says what is active and what happens to everything else.

Example:

VPN active for Telegram. Everything else is using your normal internet connection.

The product never uses selective-profile language while silently routing the whole device.

All Connectivity is an explicit full-device profile. It installs a default-route VPN policy, routes eligible IPv4 and IPv6 traffic and DNS through the gateway, shows the gateway and public IP, and exposes local-network and kill-switch behavior.

The first-use flow makes that scope clear before connecting.

Example:

All Connectivity is active. All eligible traffic on this device is using FiestaVPN.

This is a different product state, not just a broader selective rule.

A custom profile can be created for an installed Android application and/or defined destinations such as domains, wildcard domains, and optional IP ranges.

The builder is designed to:

• Show installed applications where the platform supports it.
• Validate domains and network ranges.
• Warn about broad, local, private, or conflicting rules.
• Explain consumer-iOS destination-based behavior.
• Offer a route test before connection.
• Save and version the profile safely.

The goal is advanced control without requiring a user to understand package identifiers, CIDR notation, DNS matching, or tunnel routing internals.

Service applications and content-delivery networks change over time. FiestaVPN profiles are designed as signed, backend-managed rule sets so the product can update identifiers, destinations, protocol requirements, and gateway policy without waiting for a full application release.

The app rejects expired, invalid, or incompatible rules and explains when a reconnect is required.

A generic green shield is not enough. Diagnostics identify whether the intended traffic scope is actually working.

Checks can include:

• Active profile and traffic scope.
• Exact or known-destination route mode.
• Application installation and permission.
• Service-rule version and freshness.
• Gateway health and latency.
• UDP support for voice and video.
• DNS behavior.
• Public IP and full-device route verification.
• Direct behavior for non-selected traffic.
• Kill-switch or strict selected-service behavior.
• Subscription and credential state.
• Recent connection events.
• A sanitized support report.

The default experience stays plain. Advanced detail remains available when needed.

The product design requires:

• No payload-content decryption.
• No message-content logging.
• Short-lived session credentials.
• Signed route profiles.
• Scope-aware failure behavior.
• Sanitized support reports.
• Privacy-preserving telemetry.
• Clear notification and foreground-service behavior.
• No green “protected” state when the selected traffic is not actually routed.

Product-specific privacy notices define exactly what connection metadata is collected, for what purpose, for how long, and in which regions.

AI can help FiestaVPN improve diagnostics, recognize recurring failure patterns, prioritize support guidance, assist rule-quality review, and recommend a suitable gateway based on product-approved signals.

That intelligence does not require reading private message content or browsing payloads. It also never changes the visible traffic scope without the user’s explicit action.

• People who need one supported service to use a different route.
• Users who want to keep unrelated device traffic on the normal connection.
• People who sometimes need a familiar full-device VPN mode.
• Power users creating a route for a work portal, application, site, or service.
• Teams that value visible routing scope and useful diagnostics.

• Selective mode is not full-device protection.
• Consumer iOS does not provide exact arbitrary third-party-app-only routing.
• A route profile cannot guarantee recognition of every future service destination.
• Connection quality still depends on the local network, gateway health, service behavior, capacity, and platform limitations.
• FiestaVPN does not inspect or decrypt application content to decide what a user is saying or viewing.