clipvolume has no accounts, no analytics, no crash reporting and no network access. This page exists so you can see the reasoning behind the two permissions it asks for.
Nothing. The app makes no network connections of any kind. There is no telemetry, no update check, no crash reporter. The only files it writes are macOS's standard preferences (~/Library/Preferences/com.clipvolume.app.plist), which hold whether the mixer was left expanded and whether you've seen the permission explainer.
macOS has no per-app volume API. To show a level meter for an app, or to lower or mute it, clipvolume uses Apple's Core Audio process tap API to receive that app's audio stream. When you turn an app down, the tap silences the app at the output device and clipvolume plays the same audio back at the new volume. macOS classifies this capability as “System Audio Recording”, so that is the permission you'll be asked for the first time you open the Mixer.
The play/pause button talks to Spotify, Music, TV, QuickTime Player and VLC over Apple Events (the same mechanism as AppleScript). macOS asks you once per app whether clipvolume may control it. clipvolume only ever reads the player state and the current track title (to show as a tooltip) and sends play/pause. It never launches an app that isn't already running.
clipvolume.com is a static site hosted on GitHub Pages. It sets no cookies. The download page calls the public GitHub API once to display the current version number; GitHub's privacy statement applies to that request. Fonts are loaded from Google Fonts.
The app is open source under CC BY-NC 4.0. The audio path lives in Sources/Audio/ProcessTapChannel.swift and the Apple Events path in Sources/Playback/PlaybackController.swift in the GitHub repository.