AirchainInformation stored on the Mac
Airchain stores station configuration, catalog metadata, category assignments, playback-stack state, as-played history, user and role records, remote-machine bookmarks, waveform caches, staged playout media, backups, and diagnostic logs in the operator’s macOS account. Remote secrets and an optional Discogs token are stored in the macOS Keychain when available. Airchain backups do not contain audio media or Keychain secrets.
Airchain also stores a durable Daily Playback Log ledger and derived per-station/day TSV plus JSON manifest files under the operator account’s Application Support folder. Rows may include station and host identity, output route, UTC/station/local clocks, actual and scheduled timing, Media ID, title, artist, category/media kind, local source path, scheduler source filename/line, and a SHA-256 of exact imported schedule-source bytes. This information remains local unless an operator copies or shares it. The Studio-local archive is not mirrored to Remote clients.
Because the ledger is stored in the station catalog database, a catalog-bearing Airchain backup can contain ledger rows even though it does not separately copy the derived TSV/manifest export pair.
Information sent to Calder Creative Media
The beta does not automatically upload station data, audio, diagnostics, playback logs, or product analytics to Calder Creative Media. Support materials are sent only when the tester chooses to share them. Those materials may contain station names, media IDs, titles, artists, local file paths, computer names, operational timing, and other information selected by the tester.
When Airchain checks for an update or downloads one at the tester’s request, it contacts the Calder Creative Media update or download server over HTTPS. As with an ordinary web request, the hosting provider may receive network and request information such as IP address, request time, requested file, and browser or app request headers. The signed update manifest does not cause an unattended install.
Calder Creative Media uses voluntarily supplied support information to diagnose the reported issue, communicate with the tester, operate the beta, and improve Airchain. It should be retained only as long as reasonably needed for those purposes, security, and applicable recordkeeping requirements. A tester may email airchain@caldercreativemedia.com to request deletion of support materials, subject to information that must be retained for security, legal, or operational records.
Diagnostics
Airchain records local performance, timing, buffering, continuity, application version, operating-system version, and operator-action context needed to diagnose playout behavior. Diagnostic collection is operator initiated through Help → Collect Diagnostics. The command creates a private archive on the Desktop and reveals it in Finder; Airchain does not automatically transmit the archive.
Review a diagnostic archive before sharing it if station details, file paths, metadata, or timing information are sensitive. The normal beta diagnostic archive does not copy Daily Playback Log TSV/manifest files as files. If support requests a pair, preserve its matching files together, verify the manifest, and review the operational metadata and paths before sharing.
Remote access
When Remote is enabled, approved Airchain clients exchange console state, library metadata, artwork, preview audio, imported audio selected by the operator, user identity, permissions, and authorized commands with the configured Studio Mac. Remote should be used only over a trusted local network or private VPN. It must not be exposed directly to the public internet.
Public-stream continuity monitoring
If the operator configures and enables public-stream continuity monitoring, Airchain connects to the station-supplied stream URL and receives stream bytes to detect interruptions. The stream operator or its hosting provider may receive ordinary connection information such as the Studio Mac’s public IP address, request time, and request headers. Airchain does not send the stream contents to Calder Creative Media.
Third-party metadata services
Operator-initiated metadata searches send title and artist search terms to MusicBrainz or Discogs. Artwork retrieval may contact Cover Art Archive. A Discogs search also sends the operator-provided Discogs token to Discogs. Those providers receive ordinary network request information and operate under their own terms and privacy policies. Airchain does not use these requests for advertising or tracking.
Tracking and analytics
The controlled beta contains no advertising SDK, cross-app tracking, or automatic product-analytics transmission. If Calder Creative Media later introduces optional telemetry, this notice and any required consent controls must be updated before collection begins.
Data control and retention
Operators can export station profiles and backups, remove catalog records without deleting source audio, move explicitly selected source files to the macOS Trash, and remove Airchain’s local application data using Finder. Local data remains until the operator removes it, the applicable feature replaces it, or macOS/storage policy removes it.
As-played history should be retained according to the station’s legal, contractual, and regulatory policy. Daily Playback Logs have no automatic retention, pruning, or historical backfill in this beta. Deleting an exported TSV/manifest pair does not erase the SQLite ledger and a later publish may recreate it; apply the station’s records policy to the ledger and exports together. Deleting a non-default station permanently deletes that station’s ledger rows and pending export outbox but leaves already-derived TSV/manifest files on disk, so preserve or securely dispose of those files separately. An absent export or partial coverage does not establish that no audio aired or that Airchain ran continuously.
Security and choices
Airchain uses macOS storage, Keychain facilities where available, HTTPS release destinations, signed updates, and authenticated Remote access, but no system can guarantee absolute security. Testers should use least-privilege accounts, protect credentials, limit Remote to trusted networks or private VPNs, keep backups, and review files before sharing them.
Metadata searches, diagnostic sharing, update checks, update downloads, Remote, and public-stream monitoring are initiated or configured by the operator. A tester who does not want the associated network request should not use that feature.
Changes and contact
The notice supplied with a beta build governs that build. Material changes to Airchain’s data practices should be reflected in an updated notice before a later build is distributed. Questions and data requests may be sent to airchain@caldercreativemedia.com.