Privacy Policy
This policy explains how this app ("the app") handles data related to you. The app is provided by AVEM Biopharmaceuticals, LLC ("the developer"). Effective date: 2026-01-01
1. Overview
The app is a free, general-purpose subscription tool: it reads subscription URLs that you add yourself and, based on their contents, sets up a VPN connection on your device. The app has no accounts and provides no network nodes or subscription services. The developer does not operate any subscription or node servers, and the app never sends any of your data to the developer.
2. The developer does not collect or receive your data
· The developer does not collect, receive, or store any data related to you, including subscription URLs, node information, usage time, the websites you visit, and device information. · The app contains no analytics, advertising, or crash-reporting SDKs, and uses no tracking technologies. · The developer commits not to sell or use user data for any purpose, and not to disclose user data to any third party.
3. Data stored on your device
The following data is stored only on your device and cannot be accessed by the developer: · Subscription URLs you add. A URL usually contains an access token and works like a password, so it is stored in the system keychain and restricted to this device; · Node lists and data-usage / expiry information fetched from subscription servers; · Your preferences, such as routing mode, custom routing rules, and favorite nodes; · The node configuration needed to connect (generated from the nodes of the subscription used for the most recent connection), stored in iOS's VPN configuration for the app's VPN extension to read; · Status records, such as tunnel start/stop, memory usage, and automatic recovery — never any address or domain you visit. Except for subscription URLs, this data may be included in your own iCloud or computer backups.
4. Servers the app communicates with
None of the following are servers operated by the developer, and the developer receives no data from any of them: · The subscription servers you add: when you add or update a subscription, the app sends a request to that URL. The request contains the full subscription URL (including any token in it), the client identifier "Mini/<version>" (so the subscription service can recognize the client type), and the standard headers the system networking library adds automatically (such as language preference and accepted compression formats); as with any network request, the subscription server can also see the IP address it comes from. The full subscription URL and token are sent only to the server the URL points to — never to the developer or anyone else; when that server's domain name is resolved, DNS providers see the domain part of the URL (see below). Subscription content (including subscriptions delivered in encrypted form) is parsed on your device. · The node (proxy server) you choose: while connected, your network traffic is relayed through that node, which can see the traffic it relays and the IP address you connect to it from. Nodes are operated by your service provider. · Built-in public DNS: the app has the following built-in public DNS servers, operated by third parties: 223.5.5.5 (Alibaba Cloud Public DNS), 119.29.29.29 (Tencent Cloud DNSPod), 8.8.4.4 (Google Public DNS) and 1.0.0.1 (Cloudflare); 114.114.114.114 (114DNS) and 8.8.8.8 (Google Public DNS) are also included as bootstrap DNS, used only to resolve the domain names of DNS servers themselves. For each domain that has to be resolved on the device, the core sends the query to the first four at the same time. These queries do not go through a node; they are sent directly from your device, so the DNS providers can see the domain queried and your real IP address (that is, the public address of your current network). Domains resolved on the device include: the domain names of node servers; domains reached directly (not through a node) under the routing rules — in Rule mode, mainly sites in mainland China and others that match direct rules, and in Direct mode, every domain you visit; a few lookups that need real results (such as time synchronization, local device names, voice-call NAT traversal, and non-address DNS queries); and, if you turn off "Skip DNS resolution" for an IP-type rule in Custom Routing, domains that reach that rule. For sites accessed through a node, the domain is resolved by the node server and is not sent to these public DNS servers. On IPv6-only (NAT64) networks, the domain names of node servers and of destinations reached directly are resolved by your current network's DNS instead (see the next item). · Your current network's DNS (usually provided by the Wi-Fi or cellular network you are connected to): when you add or update a subscription while the VPN is not connected, the subscription server's domain is resolved by it; on IPv6-only (NAT64) networks, while connected, the domain names of node servers and of destinations reached directly are also resolved by it, so that usable IPv6 addresses can be obtained. That DNS provider may therefore see these domains. · Connectivity and latency checks: an empty request carrying no personal information is sent to www.gstatic.com/generate_204 to confirm the connection works and to measure node latency. · Routing rule sets: in Rule mode, the core downloads open-source routing rule sets from cdn.jsdelivr.net and updates them periodically (about once a day): they are downloaded once when you first connect in Rule mode, and failed downloads are retried automatically. A copy ships with the app, so routing still works if the download fails. · IP location database: only if you add an "IP Region" rule in Custom Routing, the core downloads an open-source IP location database from github.com.
5. No logging of what you access
To decide whether each connection goes direct or through a node, the core reads the destination domain (including TLS SNI) on your device and matches it against the routing rules. This happens only in memory: the app does not log, store, or upload the websites, domains, or traffic content you access, and the core's log level is fixed at silent.
6. Third parties
· Services you choose: subscription service providers and node operators are chosen by you, not designated by the developer. They each handle the data they receive under their own privacy policies, not this one. Please read your service provider's privacy policy before use. · Public services built into the app: the built-in public DNS servers, www.gstatic.com, cdn.jsdelivr.net and github.com listed in section 4 are public network services the app uses to provide its connection features. The developer does not share or exchange any data with the operators of these services and has no data-processing arrangement with them; what they receive is limited to the content of the network requests described in section 4, sent from your device, which their operators handle under their own published privacy policies.
7. Retention and deletion
· The data above stays on your device until you delete it or uninstall the app. · To delete a subscription: on the Subscriptions page, tap "…" next to the subscription, choose Delete and confirm. The subscription URL, its nodes, and favorites that belong only to that subscription are deleted from this device; if the node configuration saved in iOS's VPN configuration came from this subscription, the app also disconnects and clears that node configuration (the VPN configuration entry itself is kept and regenerated the next time you connect). · To delete the VPN configuration: in iOS Settings → General → VPN & Device Management → VPN, delete the app's VPN configuration. · Uninstalling the app: iOS deletes the app's data and the VPN configuration it created. iOS does not remove the subscription URLs in the keychain along with the app, but no other app can read them; if you reinstall, the app clears them automatically on first launch.
8. Consent and withdrawal
When you first connect, iOS asks whether to allow the app to add a VPN configuration, and you can decline. You can withdraw your consent at any time by disconnecting, deleting the app's VPN configuration, or uninstalling the app.
9. Children
The app is not directed at children under 13 and does not collect personal information from anyone.
10. Changes to this policy
Any updates to this policy will be released with a new version of the app, and the effective date above will be updated accordingly.
11. Contact us
If you have any questions about this policy, contact: benedickf@avembio.lol