Privacy notice
Last updated: September 15, 2026
Scope
This notice covers the antifyapp.com website, the Antify macOS app, and the system extension the app installs. Antify provides no proxy server and has no accounts, so your traffic never passes through us. Each section below says what is collected or stored where.
Your traffic
Antify handles your traffic entirely on your Mac. The system extension reads a connection’s destination (domain or IP, and port) and the server name in the TLS handshake to match the rules you set; the traffic itself is relayed unchanged, never decrypted and never stored — Antify installs no root certificate.
The entries on the Connections screen live in memory only, at most 1,000 in the system extension and 1,000 in the app, and are gone once it quits. Antify does not write them to a file and does not send them to any server.
The system extension that carries your traffic contains no analytics or crash-reporting components; the Firebase services described below run only in the app’s interface process.
Proxy server and passwords
You bring your own proxy server; Antify only hands it the traffic of the apps you choose. Proxy passwords are stored in the macOS Keychain and are sent only to the proxy you configured, to authenticate with it. Proxy addresses, rules, and configurations stay on your Mac.
Website analytics
antifyapp.com uses Firebase Analytics to understand website usage: it writes cookies or local storage in your browser and automatically records events and user properties such as page visits, device information, and general usage context; the exact fields are described in the official Firebase documentation. The website does not require an account.
App diagnostics
The Antify macOS app includes Firebase Analytics and Firebase Crashlytics. The app defines no custom analytics events and sets no user identifier, so Analytics collects what the SDK gathers automatically; Crashlytics reports stack information for crashes and non-fatal errors, along with the device and operating-system details needed to diagnose stability issues.
Device identifiers
On first launch, Antify records an installation identifier and your Mac’s hardware UUID to tell which version you first installed and how many days you have used it. Both stay on your Mac; no code in the app sends them anywhere.
Automatic updates
The app checks for updates through Sparkle, which periodically asks our server for version information. That request carries no system profile, as Sparkle’s system-profiling option is not enabled. You can turn “Check Automatically” off in Settings → General.
Location permission and Wi-Fi names
The app asks for location permission only when you use automatic configuration switching by Wi-Fi: macOS requires that permission to read the name of the current Wi-Fi network, which is an OS-level restriction. Antify does not collect, store, or transmit any location data, and the Wi-Fi names you enter are saved in your local configuration. If you do not use Automation, the permission is not needed.
Diagnostic files and configuration backups
The diagnostics file produced by “Collect Logs” and any exported Configuration Backup are saved where you choose; Antify never uploads them on its own. In the diagnostics file, proxy addresses, ports, usernames, and passwords are redacted, while destination domains, IP addresses, and process paths are kept; a configuration backup contains proxy addresses, ports, usernames, the program paths your rules refer to, and Wi-Fi names, but not proxy passwords.
Third-party services
Firebase Analytics and Firebase Crashlytics are provided by Google. See the official Firebase documentation and Google Privacy Policy for information about how those services process data.
Feedback and contact
You can file bugs and feature requests in the feedback repository on GitHub; the feedback entry in the app attaches your app version and macOS version. Either way, we receive only what you choose to submit.
For privacy questions, email [email protected].