DashyNMS Desktop privacy policy
Last updated 1 November 2026
The short version
DashyNMS Desktop talks to the LibreNMS server you sign in to, and to Graylog and Unimus if you set them up. There’s no DashyNMS account, no advertising and no tracking, and nothing about your network is ever sent to DashyNMS. From version 2.0, you can choose to share error reports and usage measurements with DashyNMS; both are off until you turn them on. If you use Intelligence, your questions go to OpenAI through your own ChatGPT plan.
This policy covers DashyNMS 2.0 on Windows, macOS and Linux. Version 1.x doesn’t share error reports or usage. The full technical detail is in PRIVACY.md in the app’s repository.
Who the app talks to
- Your LibreNMS server, the one you sign in to. Everything you see comes from there. Your API token is only ever sent to that server: if it redirects DashyNMS somewhere else, the token isn’t sent along.
- Your Graylog and Unimus servers, only if you set them up in Settings.
- GitHub, to check for and download new versions of DashyNMS, at start-up and every 6 hours.
- GitHub, for sensor definitions, which give state readings names and colours. They’re on by default and are checked at most once a day, from the official repository or another public one you choose. You can turn them off in Settings → Sensor definitions.
- OpenStreetMap’s tile servers, for the backgrounds of the geographical map, unless your LibreNMS server or Settings names a different tile server. As with any map website, the tile server sees which parts of the map are loaded.
- OpenAI, only if you sign in to Intelligence with your ChatGPT account (see below).
- Sentry, only if you choose to share error reports or usage (see below).
The requests to GitHub carry nothing about you or your network, only what any download sends. Nothing else is contacted. What happens to data on your own servers is up to whoever runs them.
Signing in with LibreNMS
If you choose Sign in with LibreNMS, your server’s own sign-in page opens in a window inside DashyNMS, using your system’s browser engine: Microsoft Edge WebView2 on Windows, WebKit on macOS and WebKitGTK on Linux. It works as it would in your browser: if your server sends you to a single sign-on provider, that provider sees the sign-in, as it would anywhere else.
DashyNMS doesn’t read or keep your password. Once you’re signed in, it creates an API token on your server and keeps only that. Each sign-in uses a private browser session, so no cookies are left behind. If you paste an API token instead, none of this applies.
Intelligence
Intelligence answers questions about your network using your own ChatGPT Plus or Pro plan. You sign in to ChatGPT in your browser, so DashyNMS never sees your ChatGPT password.
Your questions, and what DashyNMS looks up to answer them, such as device names, addresses, alerts, ports and log lines, are sent to OpenAI to be processed. Passwords, tokens and SNMP communities are never sent. Configuration backups are summarised unless you choose otherwise in Settings → Intelligence. If web search is on, search terms may be sent to search providers; you can turn it off in Settings. Intelligence tells you this before your first question, and again if what’s sent changes. OpenAI’s privacy policy covers what OpenAI does with it.
Saved chats stay on your computer, encrypted. Exporting a chat saves a file where you choose and sends nothing anywhere.
Error reports and usage, if you choose
The first time you open DashyNMS 2.0, it asks whether to share error reports, and separately usage and performance measurements. Both start off. Closing the question without choosing leaves them off and asks again next time; a choice you make is remembered. You can change either one at any time in Settings → Diagnostics. Turning one off deletes anything for it that hasn’t been sent yet.
What you share is sent to DashyNMS through Sentry, a service for collecting app errors and measurements:
- Error reports, when something goes wrong in DashyNMS: the app version, operating system, processor type, the time, the kind of error, and where in DashyNMS’s own code it happened (method names, and file names and line numbers within the app’s source code).
- Usage and performance: how often the app starts; how long start-up, screens and requests to your server take, and whether they succeeded; how responsive the app is; how much memory DashyNMS itself uses; how updates went; and how often a few features are used, such as opening Maps or Intelligence or editing the dashboard. Each comes with the app version, operating system and processor type. Counts are added up on your computer before they’re sent, and timings are sampled.
- How each session ended, only if you share both: whether each time the app was open ended normally, with an error, or with a crash, under a random ID that’s new each time. If you chose to share before this was added, DashyNMS asks again before including it.
They never include your server’s address, device or other names, IP addresses on your network, API tokens or passwords, error messages, anything from your network or your Intelligence chats, file paths on your computer, or anything you type. There’s no user or install ID. Demo mode never reports.
When something is sent, Sentry sees your computer’s IP address, as any website would, so we don’t call these reports anonymous. DashyNMS sends them to Sentry’s EU servers, and Sentry deletes them after the retention period set for that project. They’re used only to find and fix problems and to see which parts of the app are used, never for advertising or tracking, and they’re never sold or shared.
While you’re offline, reports wait on your computer for up to seven days. Crashes in the operating system or other native code below the app aren’t covered, and no memory contents or crash dumps are ever collected.
What the app keeps on your computer
Everything stays on your computer, in your user account: your server address and settings, dashboards and map layouts, any certificate you’ve chosen to trust, saved Intelligence chats, downloaded updates, reports waiting to be sent, and log files kept for 14 days. Map tiles are cached for a week.
- on Windows, in
%APPDATA%\DashyNMS, with map tiles in%LOCALAPPDATA%\DashyNMS - on macOS, in
~/Library/Application Support/DashyNMS - on Linux, in
~/.config/DashyNMS, with map tiles in~/.local/share/DashyNMS
Your LibreNMS API token, Graylog password, Unimus token and Intelligence chats are encrypted so only you can read them: by Windows for your Windows account, or with a key in your macOS Keychain or Linux keyring. You can turn off saving the LibreNMS token entirely.
Your logs are never sent anywhere, and they’re never attached to error reports. Signing out removes everything apart from the logs and downloaded updates. On Windows, uninstalling asks whether to remove the rest too. The user guide explains how to remove it on macOS and Linux.
Notifications
Alert notifications are created on your computer from the app’s own alert checks. They don’t pass through any push service or third-party server.
Reporting a bug
Report a bug in Settings → Diagnostics opens a new GitHub issue in your browser with the DashyNMS, operating system and LibreNMS version details filled in. Nothing is sent until you submit it, and you can change anything first. The app only shows you where your logs are; it never uploads them.
Children
The app isn’t aimed at children and doesn’t knowingly collect anything from anyone.
Changes
If this policy changes, the new version will be posted here with a new date.
Contact
Questions? Email dashynms@pckp.net, or open an issue on GitHub. For a security problem, see the security policy.