Nexoniq is built so that what's on your network stays on your network. This policy describes exactly what happens on your Mac, what leaves it, and what is never collected.
What stays on your Mac
All your monitoring data lives locally on your Mac, inside the app's sandboxed container, under ~/Library/Containers/. Nothing is transmitted to a Nexoniq server at any point during normal use, because there is no Nexoniq server.
- Discovered devices. IP addresses, MAC addresses, hostnames, vendor lookups, and the device type Nexoniq decided on.
- Networks. The router identity used to tell your networks apart, so devices and history stay scoped to the right one.
- Configured services. The URLs and host:port endpoints you chose to monitor.
- Uptime history. Which devices and services answered, and when, sampled every 15 minutes and kept for 7 rolling days.
- Alerts. Your per-device alert settings and the record of what has fired.
- Preferences. Sweep interval, quiet hours, category order, renamed devices, your notes.
MAC vendor lookups use the IEEE registry bundled inside the app. No vendor query is sent over the network.
What Nexoniq doesn't collect
Nexoniq contains no analytics, trackers, third-party SDKs, advertising identifiers, or crash-reporting services.
I have no idea how many devices you monitor, which alerts fire, how long you keep the app open, or whether you opened it today. There are no accounts, so there is nothing to associate with you in the first place.
This is verifiable. Nexoniq's App Privacy label on the Mac App Store shows "Data Not Collected" across every category. Apple enforces this label; if Nexoniq contained a tracker, it would show up there.
What Nexoniq sends
For Nexoniq to work, your Mac must send packets on the local network and HTTP requests to configured service endpoints. Specifically:
- ICMP and TCP probes on the IP ranges you've configured. These stay on your local network.
- HTTP/HTTPS requests to monitored service URLs. The service host sees your IP address and a standard request, just like a browser. Nexoniq is not a middleman.
- TCP connect attempts to monitored host:port endpoints. The destination receives a connection attempt, no more.
- Discovery and identification traffic. mDNS and SSDP go out on the local link only. NetBIOS, SNMP and the HTTP, TLS, SSH and SMB probes are aimed at devices on your own network.
Nothing in this list leaves your local network except the requests to the service endpoints you configured yourself. There is no Nexoniq server to talk to.
When you send feedback
Nexoniq does not contain a feedback form. If you'd like to send a comment, bug report, or feature request, send a regular email to hello@nexoniq.app using whichever email program you prefer.
The address is the only way to reach the author. Your email lands in a personal inbox and is usually answered within a few days.
If you'd like to include diagnostics, you may attach the debug log nexoniq-debug.txt from the app's container (structural events only; it contains no monitored hostnames or IPs). Attaching anything is entirely your choice; Nexoniq does not collect or upload diagnostics on its own.
Children's privacy
Nexoniq does not knowingly collect any information from anyone, including children. The app has a 4+ age rating on the Mac App Store, has no accounts or social features, and contains nothing directed at children.
Changes to this policy
If this policy changes materially, the updated version will be posted here with a new "last updated" date. Because Nexoniq does not have your email address or any way to contact you, I cannot notify you directly. You're welcome to bookmark this page and check back now and then.
Contact & support
Questions about this policy, or about anything else? hello@nexoniq.app
Bug reports, feature requests, and general feedback all go to the same address. The author reads every message personally.
Nexoniq is a personal hobby project by Antti, a private individual based in Finland. Full legal identity and mailing address are available on written request to the same address, for formal GDPR data subject requests.