brisaVPN FOR iOS
← Back to Brisa

LEGAL

Privacy Policy

A clear account of the data Brisa stores and the services it contacts.

Last updated November 3, 2026 · Pavel Yakimov

Who is responsible

Brisa is developed by Pavel Yakimov. For privacy questions, contact support@homerstack.app. This policy covers the Brisa iOS client. It does not replace the privacy policies of the servers or services you choose.

No accounts, advertising, or analytics

Brisa does not require an account, display advertising, or include analytics or tracking SDKs. The client does not record browsing history or traffic contents. The developer does not collect, sell, use, or disclose VPN traffic data for advertising, profiling, or other secondary purposes.

Data stored on your device

Brisa stores subscription names and URLs, server configurations and credentials, selected servers, routing preferences, database sources, and app settings. Secret library data is encrypted and protected using the system Keychain. The app and VPN extension share a protected App Group container. Imported routing databases are copied into that container.

Diagnostics contain error codes, connection states, and technical counters, without subscription URLs, tokens, keys, or visited addresses. Latency results include status, duration, and measurement time. QR camera frames are decoded locally; they are not saved or uploaded.

Network requests

Availability checks and Auto

Manual checks support HTTP GET, HTTP HEAD, and ICMP. The selected HTTP endpoint is Google (www.gstatic.com/generate_204), Apple (captive.apple.com/hotspot-detect.html), or Cloudflare (cp.cloudflare.com/generate_204). ICMP sends a network reachability probe. The recipient can see the request and the address from which it arrives. Subscription URLs and VPN credentials are not sent to check endpoints.

Proxy hostname bootstrap uses Cloudflare DNS, including DNS-over-HTTPS fallback at cloudflare-dns.com/dns-query, outside the VPN. This resolves server hostnames, not your browsing destinations. Manual checks and automatic selection can generate additional network requests.

Auto can reuse a recent successful check and confirm a candidate with another request. Automatic switching is off by default. When enabled, it checks connectivity approximately every 30 seconds and may confirm a failure against the Cloudflare endpoint, including while the screen is locked. Auto health checks use their own endpoint settings, independently of manual ping preferences.

See the policies of Google, Apple, Cloudflare DNS, Cloudflare, Quad9, and GitHub, as applicable to your configuration.

Deletion and your controls

You can remove subscriptions and change database sources and settings in the app. Removing a subscription deletes its library entries and prevents restarting a removed server. An existing tunnel continues until you disconnect. A protected last-tunnel configuration may remain until replaced for state restoration. Uninstalling the app does not guarantee removal of every Keychain item.

The developer cannot delete records independently held by your subscription, VPN, DNS, database, or check-endpoint providers. Contact those operators about their retention policies and your data rights.

Support and this website

If you email support, we receive your email address and the information you include to respond to your request. Do not send subscription links, private keys, passwords, or browsing history. You can request deletion of support correspondence by email, subject to applicable retention requirements.

This website does not include analytics scripts, advertising, or application cookies. Its hosting provider may process IP addresses and request metadata to deliver and protect the site.

Policy changes

Updates will appear on this page with a revised date. Contact support@homerstack.app with any questions.