Privacy

Last updated: 2026-06-01

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.
• 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.

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.