Privacy and Security

Privacy and Security

Cadence is local-first. It has no account system, analytics, advertising, telemetry, crash-reporting service, embedded web view, or network client.

Local data

Cadence can read audio, artwork, metadata, and LRC files selected or dropped by the user. Confirmed imports are copied into ~/Music/Cadence.library together with SwiftData records and recovery manifests. Interface and playback preferences use macOS preferences.

The app does not transmit library contents, listening activity, tags, playlists, artwork, lyrics, search terms, or preferences. Settings opens an external URL only after the user selects a project link.

File access

Cadence runs in App Sandbox. macOS grants access to selected files and to the Music folder used by the managed library. The original source files are left unchanged. Trash operations affect only managed copies.

Security boundaries

• managed paths must stay inside Cadence.library;
• import uses staging, hashing, manifests, and rollback/recovery;
• Restore fails closed if a managed destination conflicts;
• schema migrations are versioned and tested on temporary libraries;
• the repository must not contain credentials, signing identities, personal media, or real-library screenshots.

Removing data

Use Restore or Empty Trash for managed items. To remove the whole managed library, quit Cadence and delete ~/Music/Cadence.library. Back up source music before deleting any library package.

Reporting a vulnerability

Use private vulnerability reporting. Do not publish exploit details, private media, usernames, home-directory paths, tokens, certificates, or unrelated logs.