Privacy

Last updated: 2026-07-26

viewbus does not send telemetry, does not phone home, and has no backend servers. Your Azure credentials and connection strings are used by your machine to talk to Azure directly — they never touch any infrastructure operated by viewbus (because there isn't any). The SQLite index, logs, and settings files all live under your user profile on disk.

What's on your machine

• SQLite index — resource metadata (namespace names, queue names, etc.) discovered from Azure or from connection strings you add. Contains no message bodies and no secrets.
  • Windows: %LOCALAPPDATA%\viewbus\viewbus.db
  • macOS: ~/Library/Application Support/viewbus/viewbus.db
• OS keychain entries under service name viewbus — raw Service Bus connection strings you paste in. Stored in the Windows Credential Manager on Windows and the macOS Keychain on Mac. Never written to the SQLite index or log files.
• Settings JSON — your theme, hotkeys, and preferences.
  • Windows: %APPDATA%\viewbus\settings.json
  • macOS: ~/Library/Application Support/viewbus/settings.json
• Custom themes in the themes/ subfolder of the settings directory above — drop a JSON file in and it shows up in Settings on next launch.
• Local API discovery file — while the app is running it serves a small HTTP API on 127.0.0.1 for launcher plugins and scripts (see the developer docs). On each launch it writes the port and a freshly generated bearer token to a discovery file so local tools can find it. The token is regenerated every launch, the listener binds loopback only, and requests carrying an Origin header are rejected so no web page can reach it. Turn the whole thing off with localApi.enabled: false in settings.json.
  • Windows: %APPDATA%\viewbus\local-api.json
  • macOS: ~/Library/Application Support/viewbus/local-api.json
• Log files — daily-rotated plain-text diagnostics via tracing. No PII, no credentials, no message bodies. Attached only if you opt in via the in-app feedback dialog.
  • Windows: %LOCALAPPDATA%\viewbus\logs\
  • macOS: ~/Library/Application Support/viewbus/logs/

What leaves your machine

Only requests you trigger:

• Azure authentication (OAuth flow in your default browser; tokens go directly between Microsoft and your machine). If your account belongs to several tenants, viewbus enumerates them so you can pick the active one — that enumeration is also a direct call to Microsoft.
• Azure Resource Manager + Service Bus REST / AMQP calls (direct to the endpoints in your connection strings — the app's Content Security Policy allows only login.microsoftonline.com, management.azure.com, *.servicebus.windows.net, and the static viewbus.app hosts below).
• An update check on app start that reads https://viewbus.app/latest.json — a static JSON file with the current version number. No query parameters, no identifiers, no user agent beyond what the OS adds. Apps installed from the Microsoft Store are updated through the Store instead.
• An announcements check on app start that reads https://viewbus.app/announcements.json — the same kind of static file. Notices that don't apply to your version are filtered locally; dismissed ones are remembered in localStorage.
• If you send feedback from the in-app dialog, whatever you typed — plus the log file, but only if you tick the box to attach it.

The built-in MCP server doesn't change any of this: it runs locally over stdio and holds no credentials of its own. If you ask an AI assistant to read a message through it, that message goes to whichever AI provider your client is configured with — that's between you and them, and viewbus never sees it. Details on the MCP page.

This website

viewbus.app is a static site hosted on GitHub Pages. There is no analytics script, no tag manager, no cookies, and no third-party embeds — fonts are served from this domain rather than a font CDN, so no request leaves it while you read this.

• Server logs. GitHub, as the host, sees the standard request data any web server sees: your IP address, user agent, and the page requested. That data is GitHub's to handle under their privacy statement; it isn't forwarded to us and we can't query it.
• Browser storage. Two localStorage keys, both set only by your own clicks and never read by anything but this site: viewbus-site-theme (light or dark) and viewbus-mcp-client (which config tab you last looked at). Clearing site data removes them.
• Outbound links. GitHub, the Microsoft Store, and Buy Me a Coffee are ordinary links — nothing is prefetched or contacted until you click.

No third parties

No analytics SDK, no crash reporter, no A/B framework, no affiliate tracking. If a future version adds any of these, it will be opt-in with a clear prompt, and this page will list them.

Who's responsible, and how to reach us

viewbus is made and operated by Håkon Lia, an individual developer in Norway, who is the data controller for anything on this page. There's no company and no support desk; the routes on the support page all reach me directly:

• GitHub issues for anything you're happy to discuss in public.
• The feedback dialog inside the app (Settings → Send feedback), which needs no GitHub account and is the right route for anything you'd rather not post publicly.

Under the GDPR you have the right to access, correct, or erase personal data a controller holds about you, and to complain to a supervisory authority — in Norway, Datatilsynet. In practice there is nothing for us to produce or delete: viewbus operates no servers, no database, and no account system, so we hold no personal data about you at all. Everything the app stores is on your own machine, in the files listed above, and deleting them is entirely in your hands. If you believe that's wrong, get in touch and I'll look into it.