Privacy Policy

Last updated: October 19, 2026

Overview

OpenWrt Manager ("the App") is a tool for managing your own OpenWrt router, on your local network or remotely. We are committed to protecting your privacy. This policy explains what data the App handles and how it is stored.

Data Collection

The App's router-management features talk directly to your router — on your local network, or remotely through an address or remote-access method you set up yourself (see Remote Access). Your router traffic never passes through servers we operate. Beyond your router, the App only contacts the optional cloud push service, Apple's purchase services, and downloads.openwrt.org when you check for firmware updates, as described below.

• No analytics or tracking SDKs are included (no Firebase, no Google Analytics, no Crashlytics).
• No user accounts or registration are required.
• Personal data is not sold. Limited data is shared with service providers only where needed to deliver features you use.
• No advertising identifiers are read.

Two optional features — cloud push notifications and the OpenWrt-side notification agent — upload a minimal, scoped data set to a backend we operate. Those flows are described in the Cloud Push (Optional) section below. Purchase and subscription validation is described separately under Purchases and Subscriptions.

Data Stored on Your Device

The following data is stored locally on your device only:

• Router address and connection settings — stored in SharedPreferences to allow quick reconnection.
• Router password — if you choose to save it, the password is stored in the platform's secure storage (iOS Keychain / Android Keystore). It is never transmitted anywhere other than directly to your router.
• Cloudflare Access service tokens — if you save any, the name and Client ID are stored in SharedPreferences and the Client Secret in secure storage (iOS Keychain / Android Keystore). They are sent only as request headers to the router address you use them with.
• Traffic history — hourly and daily bandwidth statistics are stored locally in SharedPreferences for display purposes.
• App preferences — theme mode, language, device nicknames, groups, and notification preferences.
• Notified MAC list — when "New device alerts" is enabled, a list of MAC addresses already alerted on is kept locally to avoid duplicate notifications.

Notifications (Local)

• The App can send you a local notification when a previously-unseen device joins your network. This feature is opt-in and can be toggled in Settings → Notifications.
• The first time you enable it, the system prompts you for notification permission. You may revoke this permission at any time from your device's system Settings.
• Notifications are generated entirely on your device by comparing the current device list with locally stored MAC addresses. No notification content or device information is sent to our servers or any third party in this mode.

Cloud Push (Optional)

If you want push notifications to arrive even when the App is closed (for example: an unknown device joins your home Wi-Fi while you are at work), you can enable cloud push. This adds a second delivery path on top of local notifications. It is off by default. Enabling it is a deliberate action: tapping the "New device alerts" toggle plus tapping "Install router agent" in Settings.

What gets uploaded, by whom, and to where

• The App sends our backend an APNs device token (an opaque identifier issued by Apple, scoped to this App on this device — not a tracking ID), your language preference (e.g. en, zh), and a randomly generated device key + agent token. The agent token is the bearer credential the OpenWrt-side script will later use to authenticate.
• The OpenWrt-side notification agent — installed onto your router only after you tap "Install router agent" — uses the agent token to send our backend a small JSON event when something you asked to be told about happens: a previously-unknown device joins your network; a device you chose to watch comes online or goes offline; a device exceeds the hourly traffic threshold you set; the internet connection comes back after an outage; or the router restarts. Each event carries only the event type, the device's mac, ip and name (where it applies), your router label, and where relevant one number (data used in the hour, or outage length). No traffic content, no browsing history, no logs.
• To deliver one router's alerts to every phone that subscribed to it, the backend also keeps a random router ID and router token, and which device keys are subscribed to it.
• The backend is a Cloudflare Worker we operate at openwrtpush.yzinf.com. It stores your registration in Cloudflare KV and uses Apple's APNs service to deliver the notification to your iPhone. No third party other than Cloudflare and Apple is involved, and we do not use any analytics SDK, ad SDK, or tracking SDK.
• Storage retention: registrations expire after 90 days of no re-registration. The backend also keeps a 30-minute deduplication cache so the same event isn't pushed repeatedly. Both are automatically purged.
• The notification body that Apple delivers to your phone contains the device's name and IP. We do not log notification deliveries on the backend.

How to disable / delete

• Disable in-app: Settings → Notifications → toggle "New device alerts" off. The App will call our backend to remove your registration immediately.
• Disable on the router: Settings → Notifications → "Install router agent" again writes the latest config; conversely, the agent can be removed via SSH with /etc/init.d/openwrt-manager-notify stop && rm /usr/bin/openwrt-manager-notify.sh /etc/init.d/openwrt-manager-notify.
• Even after disabling locally, you may email us to request deletion of any residual registration tied to your APNs token.

Purchases and Subscriptions

The App may offer a monthly auto-renewing subscription, a yearly auto-renewing subscription, and a lifetime non-consumable purchase for premium features. Product names, subscription lengths, prices, and renewal terms are shown in the App before purchase.

• Payments are processed by Apple. The App does not receive or store your name, full Apple ID, payment card number, or other payment credentials.
• The App uses Apple's StoreKit framework directly to retrieve products, validate signed transactions, restore purchases, and determine whether premium features are available.
• Purchase and subscription information is handled by Apple under Apple's privacy policy. StoreKit may provide the App with product identifiers, transaction status, purchase dates, expiration dates, and renewal status needed to unlock premium features.
• The App stores only a local cached premium-access status and legacy paid-version status for offline access. It does not upload purchase receipts or entitlement data to a developer server.
• This information is used only to provide and maintain purchase entitlements, restore purchases, and respond to purchase support requests. It is not used for advertising or tracking and is not sent to a third-party purchase service such as RevenueCat.
• Subscription cancellation and refund handling are managed through Apple. The related terms are described in our Terms of Use.

Network Communication

• The App's primary communication is with your OpenWrt router via the ubus HTTP/JSON-RPC API — directly on your local network, or at the remote address you entered.
• If HTTPS is available on your router, the App supports it to encrypt this traffic.
• When you check for firmware updates, the App reads the public list of OpenWrt releases from downloads.openwrt.org. Speed tests and package installs are run by your router itself, which then contacts speed.cloudflare.com or the OpenWrt package servers.
• When cloud push is enabled, the App communicates with openwrtpush.yzinf.com, our Cloudflare Worker.
• The App communicates directly with Apple's App Store through StoreKit to load products and maintain purchase entitlements. Apple services may be contacted even if you have not completed a purchase.

Remote Access

You can reach your router from outside your home through a public address, a tunnel you already run, or one of the remote-access methods the App can set up on your router at your request:

• Cloudflare Tunnel — the App installs cloudflared on your router with a tunnel token from your own Cloudflare account. Traffic to your router then passes through Cloudflare's network under your account and Cloudflare's privacy policy. If you protect it with Cloudflare Access, the service token you save is sent with each request.
• Tailscale — the App installs Tailscale on your router and opens Tailscale's sign-in page so you add it to your own tailnet. Connections are end-to-end encrypted; Tailscale's coordination service is governed by Tailscale's privacy policy.
• WireGuard — the App configures a WireGuard server on your router. Your phone or other devices connect to it directly; no third-party service is involved. Peer keys and configs are created on your router and shown to you for import.

None of these routes traffic through servers we operate, and we receive no information about your remote connections. You can switch each method off, or remove it, from Tools → Remote Access.

Password Security

• Your router password is used solely to authenticate with your OpenWrt device.
• Saved passwords use the OS secure storage mechanism, encrypted at rest.
• We recommend saving passwords only on personal devices. Anyone with physical access to your unlocked device may be able to connect to your router through the App.

Children's Privacy

The App is not directed at children under 13. We do not knowingly collect any information from children.

Changes to This Policy

We may update this privacy policy from time to time. Any changes will be reflected on this page with an updated date.

Contact

If you have questions about this privacy policy, purchases, or subscriptions, please visit the Support page. For subscription terms, see the Terms of Use (EULA).