Monlet Privacy Policy
Last updated: 11 November 2026
Monlet is operated by Michael Olsen. This policy covers Monlet for Mac, iPhone and iPad, and monlet.app. The apps do not require a Monlet account and include no advertising, tracking or app analytics code. We do not operate an app telemetry, History or purchase server. Network checks contact the destinations needed for those checks. Optional sharing sends selected Mac data to paired devices or alert records to your private iCloud database. Apple’s separate diagnostics and reporting, website hosting and support email are explained below.
Data on your devices
Monlet stores settings, saved targets and device choices locally. Depending on the features you use, local records can include network and device names and addresses, Wi-Fi details, ping and check results, diagnostic events, alerts and History. On Mac, Monlet can read CPU, memory, disk and thermal values for the health items you enable. It saves readings to Mac History only while History saving is on; watched items can also generate alerts when their thresholds are crossed. Disk space alerts stay on the Mac and are excluded from Mac-link sharing, iCloud delivery, History exports and diagnostic snapshots, including old saved disk events.
Local network discovery communicates with devices on your network. Bonjour features advertise or discover services that other local devices can see. Live Mac sharing advertises a service name such as “Monlet Mac” with an identifier. Wake-on-LAN sends a packet containing the target device’s hardware address. Saved results and choices stay local unless included in sharing you enable.
If you enable the Mac’s incoming-connection listener, it records source addresses and connection attempts. On HTTP ports, it reads at most the first request byte to show that the connection is being recorded. It does not read request bodies or parse Authorization headers. The Honeypot does not ask for or save passwords.
Mac History uses a local database. Saving is on for new installations; existing choices are kept. Default retention is 30 days for raw results and 365 days for summaries and events, with a 1,024 MB storage limit. You can change these choices and delete saved History. Storage limits can remove older records sooner, and cleanup runs during app maintenance. Turning saving off does not erase earlier records.
iPhone and iPad check History uses local files, with 30-day retention by default or a selectable 90-day option. Expired check records are pruned when the store is used. Saved Room Walks are separate: they have no age-based expiry, with a limit of 100 saved walks. Delete saved walks individually. Deleting check History does not delete saved Room Walks, settings, pairing credentials or tip records. iCloud alert setup and syncing records follow their own lifetime rather than the check-History age limit.
Mac History exports write a file to a destination you choose and may contain network identifiers, but exclude disk events. You control where you keep or share that file.
Location permission is used to access Wi-Fi network and access-point details where the operating system requires it. Route maps may use a recent location already available from the operating system when permission is allowed. Monlet does not request ongoing location updates for these maps.
Network checks and outside services
Checks send network traffic to targets you configure or built-in services. A destination can receive your source IP address as seen by your network or VPN, along with request data such as a hostname, IP address, DNS question or requested URL. These requests perform the checks; they are not app analytics. A VPN, network or destination may affect what address is visible.
- Ping, connection and web checks: traffic goes to the selected target. Built-in internet targets include Cloudflare, Google and Quad9. Web and connectivity checks can contact Apple, example.com and Google’s gstatic.com, as well as URLs you configure. Mac IPv4/IPv6 comparisons also make TCP connection checks to Cloudflare and Google on port 853, without sending DNS questions.
- DNS checks and comparisons: questions go to your system or router resolver, or selected public resolvers including Cloudflare, Google, Quad9, OpenDNS, AdGuard DNS, CleanBrowsing, Comodo Secure DNS, Yandex and Vercara. Mac comparisons also support DNS over HTTPS through Cloudflare, Google and Quad9. Comparisons use public site names and fresh randomized names under google.com; those are DNS questions, not visits to those websites. Resolvers may contact upstream and authoritative DNS services. IPv6 checks use system DNS and Cloudflare and Google DNS-over-HTTPS services, with numeric-address fallbacks and short pings. Normal certificate checks may involve operating-system trust services.
- Speed checks on iPhone and iPad: the app downloads test data from speed.cloudflare.com by default, or from a direct HTTPS endpoint you choose, while pinging your selected target. The download request includes a size parameter and a fresh random request value. It uses network data and does not upload your saved History.
- Public IP: Public-IP lookups ask FreeIPAPI (and ipify if that fails) over the internet. Providers may keep request logs under their own policies. Results stay in memory on the device. Route-map locations come from bundled DB-IP. FreeIPAPI can return the address, approximate city/region/country and provider; ipify returns an address only. They see the connection’s source IP and normal request metadata. Lookups run when a feature needs them, such as Wi-Fi details or an online route-map start point. See FreeIPAPI’s privacy policy and ipify’s service information.
- Names and registry lookups: reverse lookups use DNS. On Mac, identifying public IP owners can fetch a registry directory from data.iana.org and query the relevant registry with the IP address. Whois/RDAP lookups send the domain or IP address you enter to rdap.org, which can redirect the request to a relevant registry.
- Route maps: online maps on Mac, iPhone and iPad load Apple Maps over the internet. The displayed area can include a recent device location. If one is unavailable, an online map can request your public IP through the services above to place its starting point. Hop locations use bundled IP-location data; hop addresses are not sent to an online geolocation service. Offline maps use bundled map data and a device location or public IP already known to the app, without loading online maps or making a new public-IP request for the map.
Outside services handle requests under their own policies. Monlet does not control their logging, retention, processing locations or onward use and does not promise how long they keep requests.
Mac-to-iPhone and iPad link
Mac pairing uses a QR code or equivalent setup text, then an eight-digit number displayed only on the accepted iPhone or iPad and typed on the Mac. The setup token works once within three minutes; a wrong number ends the window. Camera access is requested only for scanning. Camera images are processed on this device and are not saved or sent to the developer. Setup text, tokens and numbers are not sent to analytics or cloud. Copies pasted outside Monlet can remain after expiry.
The link uses TLS 1.3 with AES-256-GCM and checks a SHA-256 pin of the peer certificate’s public key. Both devices require Secure Enclave; private identity keys are nonexportable and device-only. The phone uses a separate key for each pairing. Locking the phone ends live access.
Pairing credentials are saved in the device Keychain. The Mac can accept a paired device over any network route that can reach it, including supported direct-address and VPN routes; firewall and routing rules affect reachability. The link is not limited to the local network.
On iPhone or iPad, Forget removes the pairing from the phone at once and attempts to delete its key, then tries once to tell the Mac. It does not retry. The Mac may still retain its pairing if it does not receive or confirm the request. Forget does not stop same-account iCloud alerts or recall copies already taken.
Your Mac can send live status and panels, alerts and the History you request to your paired iPhone or iPad. View only can see status, graphs, targets, alerts, up to 30 days of saved History, network and device names and addresses, Wi-Fi information, public IP, and security and pairing events. It cannot change Mac settings. Full control also allows supported changes to Mac settings. The iPhone or iPad sends its device name, requests and authorised commands back to the Mac. Disk space alerts stay on the Mac; other Mac health alerts can be shared.
The iPhone or iPad keeps a local cache of received Mac data with size and record limits. Status, panels and alerts use a seven-day window; cached History expires seven days after it was loaded. Cleanup runs when the cache is loaded or saved, so files can remain until the app next performs cleanup.
Optional iCloud alerts and push
iCloud alerts are optional. When enabled and set up on your devices, your Mac saves alert records in your Apple Account’s private CloudKit database so your iPhone or iPad can receive them away from the local network. This uses your Apple iCloud account; it does not create a Monlet account. A device on the same Apple Account can receive alerts even when it is not paired with the Mac. Disk space alerts are excluded. Push delivery uses Apple’s push notification service.
Alert details use encrypted CloudKit fields. Record identifiers, expiry times and notification flags are outside those encrypted details. Local-link and iCloud previews follow the Mac’s Hide names and addresses setting (off by default) for target names and addresses. iCloud alerts also have a separate optional Show Mac name on alerts setting. Enabling the iCloud receiver allows detailed previews; unavailable details fall back to generic text. Delivered notifications are also kept under the operating system’s notification controls.
Cloud alert records have a seven-day expiry. The Mac deletes expired records when it next completes cloud cleanup; expiry does not guarantee immediate deletion from Apple’s systems. Turning alerts off does not by itself erase records already saved. Mac History deletion asks cooperating paired devices to clear cached copies when connected or next connected. It cannot guarantee recall of other copies, including exports, screenshots, delivered notifications or iCloud records.
Voluntary tips
Optional tips use Apple’s In-App Purchase through StoreKit and unlock no features. Monlet uses StoreKit’s verified transaction result and keeps a local record of processed transaction identifiers, whether you have tipped and your tip-reminder preference. This record is separate from network History and stays on your device. The apps do not send us a list of tippers; any purchase reports available to us come from Apple. Removing the local record does not refund a tip or erase Apple’s purchase records. Monlet does not ask you to enter payment-card details.
Apple diagnostics and reports
If you choose to share diagnostics with app developers through Apple’s system settings, Apple can make crash and energy reports and aggregated usage or performance information available to us. Apple also provides App Store Connect metrics, such as downloads and purchases; usage metrics depend on users’ sharing choices. These are Apple’s reporting services, separate from the apps’ network checks. The apps do not include a separate developer crash-upload service. You can manage diagnostic sharing in your device’s Analytics and Improvements settings.
Email and this website
Support and idea links open your email app. If you send a message, we receive your email address, message and any attachments you choose to include. The app’s support links do not automatically attach logs. Please leave out passwords, pairing codes and private information you do not want to share. We keep support emails unless you ask us to delete them. To request deletion of personal information we hold about you, including support emails, contact support@monlet.app. We will respond without undue delay and within the timeframes required by applicable law. We may retain information where legally required or otherwise lawfully necessary, such as to resolve legal claims, and will explain any limits on deletion. Email passes through outside mail services, so we can't control copies they keep, including in their backups.
This website has no contact form, login or advertising. Its own page code does not set tracking or analytics cookies, download third-party fonts or embed outside services. Local scripts support feature filtering and screenshot appearance controls; they do not send analytics. Loading a page sends an ordinary web request, including your IP address and requested page, to our host, Cloudflare. Cloudflare processes requests to serve and protect the site and can make traffic statistics or request information available to us through its hosting tools. Hosting information is separate from app History. Its availability and retention depend on Cloudflare’s services and account settings.
Keeping and deleting data
Use the apps’ History controls to remove saved History, delete saved Room Walks separately, and use Clear saved Mac data on iPhone or iPad to remove received Mac caches. Remove a pairing on both devices if it remains after Forget. The Mac also offers Remove all data and quit. It removes local History, settings, app support files, caches, its notifications and supported Keychain keys, including its local tip record when present, then turns off Start at login and quits. Every supported key is attempted; reported failures can leave data. Some helper/shared-container metadata, system logs and older Keychain items can remain. Other copies, including exports, screenshots, data on other devices, delivered notifications, iCloud records and old backups, need separate cleanup. Removing an app does not promise to remove its Keychain items. Privacy permissions remain in System Settings. Resetting settings or deleting History does not remove pairing or tip records.
The iPhone and iPad apps attempt to exclude preferences, History, saved room measurements, Mac-link caches and the local tip record from device backups, and show an error if exclusion cannot be completed. Exclusion can fail and does not control operating-system data outside the app’s stores. Deleting app data does not alter older backups or files you have exported.
Contact and changes
For privacy questions, email support@monlet.app. You can also find contact details on Support.
Read the Third-party notices bundled with Monlet 1.0.1 and later.
Changes to this policy will be posted here with an updated date.
Monlet