Campus Command app icon Campus Command

Privacy Policy

Effective date: 23 July 2026

Campus Command is an independent mobile application (available for iOS and Android), with a companion smartwatch app on supported platforms, created by Matthew Notley. This Privacy Policy explains how Campus Command handles information when you use the app on a supported phone, tablet, or companion smartwatch.

Summary

Campus Command does not sell or rent personal information, use it for tracking, or share it other than as described under Casting. The app does not require an account and does not send configuration data to Matthew Notley or to any external server controlled by Matthew Notley.

Information entered into the app is stored locally on the user's device and is used only to operate the app's audio control and announcement features. The Google Cast software development kit collects and sends limited information to Google.

Information Entered Into The App

Users may enter configuration details such as:

This information is used by the app to communicate with the devices configured by the user.

Local Storage

Campus Command stores configuration data locally on the device. Sensitive values such as API keys, passwords, and PIN-related data are stored using the operating system's secure storage mechanisms where applicable. Non-sensitive app preferences and settings, such as appearance, refresh interval, and accepted policy version, are stored using standard on-device storage provided by the operating system.

The app does not upload this configuration to Matthew Notley, to a Campus Command server, or to any third-party analytics service.

Configuration Export And Import

Campus Command allows users to export and import configuration files. Exporting is initiated by the user.

Exported configuration files may include device configuration information. Sensitive values, where included, are encrypted using a password chosen by the user during export. Users are responsible for protecting exported files and export passwords.

Local Network Access

Campus Command uses local network access to communicate with audio decoders and paging receivers configured by the user. This communication occurs between the user's device and the network addresses entered into the app. On supported platforms, local network access is also used to discover and communicate with Cast-enabled devices.

Campus Command does not use local network access to discover, collect, or transmit information to Matthew Notley.

Casting

Campus Command uses the Google Cast software development kit on supported platforms to discover and communicate with Cast-enabled devices.

On Android, the Cast SDK collects limited anonymised app-interaction and usage information, including generic device-discovery and casting-session events and general information about the device and app. Portions of this information are sent to Google. Google states that this information is encrypted in transit, does not contain identifiers traceable to a specific user, and is used in aggregate to monitor and improve the Cast SDK. Google also states that the Android Cast SDK does not transfer or share this data with third parties or other apps.

On iOS, Google states that the Cast SDK collects diagnostic data. Campus Command disables Analytics Logging, so the Analytics Logging-related Device ID is not collected. Campus Command also does not use the Cast SDK UI features associated with optional Product Interaction data. Google classifies the remaining data as coarse location and diagnostic or performance information, which is used for analytics and app functionality.

Campus Command does not separately collect or retain data collected by the Cast SDK.

For more information, see the Google Privacy Policy.

Microphone Access

Campus Command may request microphone access on a supported phone, tablet, or companion smartwatch when the announcement feature is used or when the user chooses to record a tone. Microphone audio is used only for live announcements to destinations configured by the user and, when the user chooses to record a tone, to create a sound file stored only on the user's device. When an announcement is sent from a companion smartwatch, the audio is relayed to the paired phone, which transmits it to the configured destinations.

Campus Command does not upload or analyse microphone audio. Microphone audio is recorded and stored only when the user chooses to record a tone, and only on the user's device (see Tones below).

Tones

The tones feature plays sound files chosen, added, or recorded by the user. These sound files are stored locally on the device and are transmitted to the RTP or SIP destinations configured by the user when a tone is played. Users may export their tone sound files; exported files are saved by the user and are the user's responsibility to protect. Campus Command does not upload or send tone sound files or tone playback audio to Matthew Notley or to any external server controlled by Matthew Notley.

Camera Access

Campus Command may request camera access when the user chooses to scan a QR code, such as importing a configuration or entering a field value like an API key. The camera is used only to read the QR code on the user's device.

Campus Command does not record, store, upload, or analyse camera images or video.

Companion Smartwatch

Where a companion smartwatch app is available, the list of announcement destinations and the live announcement audio are exchanged between your own paired phone and smartwatch using the platform's device-to-device connectivity. This information stays on your devices and is not sent to Matthew Notley or any external server controlled by Matthew Notley.

Notifications And Alerts

Campus Command may display in-app alerts when configured audio decoder zones appear offline. These alerts are generated locally by the app based on communication with the configured devices.

Analytics, Tracking, And Advertising

Campus Command does not include advertising SDKs or cross-app tracking technologies. Aside from the Google Cast SDK data described under Casting, it does not include third-party analytics.

App Store And Platform Services

The platform provider through which you obtain the app — Apple (App Store) or Google (Google Play) — may process information related to app downloads, purchases, crash reports, diagnostics, or store usage according to its own privacy policies and settings. This is separate from Campus Command and is not controlled by Matthew Notley.

Children

Campus Command is intended for use by authorised staff, administrators, schools, campuses, businesses, and similar organisations. It is not directed at children.

Data Deletion

Users can delete app data by using the Reset Campus Command option within the app or by deleting the app from the device. Deleting the app removes locally stored app data from the device, subject to normal operating-system behaviour.

Third-Party Devices And Services

Campus Command communicates with devices and destinations configured by the user, using third-party device APIs as provided by their respective manufacturers or owners. Users are responsible for ensuring they have permission to access and control those devices and networks.

Campus Command is an independent application and is not affiliated with or endorsed by Barix AG. Barix, Exstreamer, and Annuncicom are registered trademarks of Barix AG.

AirPlay, Apple, Apple Watch, iOS, iPad, iPhone, SF Symbols, and watchOS are trademarks of Apple Inc. Android, Google, Google Cast, and Google Play are trademarks of Google LLC.

Changes To This Privacy Policy

This Privacy Policy may be updated from time to time. If changes are made, the effective date will be updated.

Contact

For privacy questions, contact:

Matthew Notley

Online version:
https://www.campuscommand.com/privacy-policy