Skip to content
WolfWave

Privacy Policy

WolfWave has no tracking, no analytics, no servers. Tokens are stored in macOS Keychain. Now-playing data never leaves your Mac unless you enable a service.

Local-first

Effective Date: February 12, 2026 Last Updated: May 24, 2026

MrDemonWolf, Inc. ("we", "us", or "our") operates the WolfWave application. This Privacy Policy explains how we handle information when you use WolfWave.

Information We Collect

Information You Provide

  • Twitch Account Credentials. When you connect your Twitch account via OAuth Device Code Flow, WolfWave receives an OAuth access token from Twitch. This token is stored locally in your macOS Keychain and is never transmitted to us.
  • Channel Name. The Twitch channel name you connect to is stored locally in your macOS UserDefaults so the menu bar can display it.
  • Discord Application ID. Your Discord Application ID is stored in the app's build configuration and used to connect to Discord's local IPC socket.
  • Song Request Blocklist. Song titles and artist names you choose to block from song requests are stored locally in your macOS UserDefaults. You can remove individual entries or clear the entire list at any time from Settings → Song Requests → Blocklist → Clear All.

Information Collected Automatically

  • Now Playing Data. WolfWave reads the currently playing track, artist, and album from Apple Music on your device using ScriptingBridge. This data is only used locally and shared with the services you explicitly enable (Twitch chat, Discord Rich Presence, WebSocket).
  • Listening History (opt-in). When you enable Settings → History & Stats → Listening History, WolfWave records each scrobbled play (track, artist, album, timestamp, duration) to a local NDJSON file under Application Support. Recording only happens while the toggle is on. You set the retention window in days (0 = keep everything) and can clear all recorded history at any time from the same pane.
  • Twitch Viewer Activity (transient). When the Song Request, vote-skip, or chat-command features are enabled, WolfWave receives chat messages, channel-point redemptions, and bit cheers via the Twitch EventSub WebSocket. Viewer usernames and message bodies are held in memory for the lifetime of the queue or vote session and discarded when the queue is cleared, the session ends, or the app quits. None of this data is written to disk except for the optional blocklist entries you create yourself.

How We Use Information

WolfWave processes data entirely on your device. We do not operate servers or transmit your data to MrDemonWolf, Inc. (See Diagnostics below for the optional, on-device-only diagnostics feature.) All data flows directly between your Mac and the third-party services you connect:

DataDestinationPurpose
Now playing infoTwitch chat (via Helix API at api.twitch.tv)Respond to !song, !last, and !stats commands
Now playing infoDiscord (via local IPC socket at $TMPDIR/discord-ipc-{0..9})Display Rich Presence status
Now playing infoLocal WebSocket server (token-gated, bound to all interfaces)Stream data to OBS browser sources and overlays on the same machine or local network
Album artwork queryiTunes Search API (itunes.apple.com)Fetch album art and Apple Music / song.link URLs
EventSub subscriptionsTwitch (eventsub.wss.twitch.tv)Receive chat messages, channel-point redemptions, and bit cheers
Update checkGitHub Releases (github.com/MrDemonWolf/wolfwave)Sparkle appcast for in-app updates (skipped on Homebrew installs)

Diagnostics

WolfWave includes an optional, opt-in diagnostics feature that is turned off by default. When you enable "Collect on-device diagnostics" in Advanced settings, WolfWave uses Apple's MetricKit framework to gather crash, hang, and performance reports.

These reports are aggregated by macOS on your device and stored locally on your Mac under Application Support. They are never uploaded. WolfWave has no analytics servers and no code that transmits diagnostics anywhere. WolfWave also keeps a local, anonymous app-launch count that never leaves your device. Turning the feature off stops collection immediately.

Data Storage

  • Credentials are stored in the macOS Keychain, encrypted by the operating system.
  • User preferences are stored in the app's UserDefaults on your device.
  • No data is stored on external servers operated by MrDemonWolf, Inc.

Third-Party Services

WolfWave integrates with third-party services that have their own privacy policies:

We encourage you to review these policies. WolfWave only sends the minimum data required for each integration to function.

Data Sharing

We do not sell, rent, or share your personal information with third parties. WolfWave does not contain advertising or tracking SDKs.

Data Retention

All data is stored locally on your device. You can clear each category at any time:

CategoryLocationHow to clear
Twitch / Discord tokensmacOS KeychainSettings → Advanced → Reset Settings
App preferencesUserDefaultsSettings → Advanced → Reset Settings
Application logs~/Library/Application Support/WolfWave/Logs/Settings → Advanced → Clear Logs
Listening history (opt-in)~/Library/Application Support/WolfWave/History/plays.ndjsonSettings → History & Stats → Clear History (retention window also enforced automatically)
Song request blocklistUserDefaultsSettings → Song Requests → Blocklist → Clear All (or per-entry remove)
Song request queue / vote-skip sessionsIn-memory onlyQuitting the app discards these immediately
MetricKit diagnostics (opt-in)~/Library/Application Support/WolfWave/Diagnostics/Disable the toggle in Settings → Advanced and delete the directory

Uninstalling WolfWave removes UserDefaults, but Keychain items may persist on macOS. Use the in-app reset above or manually remove entries via Keychain Access.

Security

  • All network communication uses encrypted transport (HTTPS/WSS)
  • Credentials are stored in the macOS Keychain with hardware-backed encryption
  • The app is sandboxed with minimum required entitlements
  • The app is signed with a Developer ID certificate

Children's Privacy

WolfWave is not directed at children under 13. We do not knowingly collect information from children.

Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last Updated" date.

Contact

If you have questions about this Privacy Policy, please contact us:

On this page