---

title: Privacy Policy effective: 2026-05-27

Privacy Policy

Effective: May 27, 2026

Babe Why is a desktop app that lives in your Mac's menu bar and plays voice clips when you switch to certain apps. This page explains what data the app touches, what leaves your Mac, and what we keep.

The short version: Babe Why does not collect analytics, does not track your behavior, and does not send your app-usage history anywhere. The only network calls the app makes are for license validation and (in the future) update checks. Everything else stays on your computer.

What data the app handles

App switches

Babe Why uses macOS's public app-activation notifications to know which app you've brought to the front. This is the same API used by app launchers and window managers. No special permission is required, and Babe Why does not use Accessibility, Screen Recording, or Input Monitoring. Your app-switch history is held in memory and used to decide when to play a voice clip. It is never written to disk and never transmitted.

Voice recordings (Custom Clips)

If you record your own clips through Custom Clips (a feature shipping in a future version), the recordings are saved to your Mac's Application Support folder under ~/Library/Application Support/BabeWhy/CustomClips/. They never leave your computer. You can delete them from inside the app or by removing the files directly.

The microphone is only used while you are actively recording. Babe Why does not listen passively.

Preferences

Your settings stay in your Mac's preferences (UserDefaults) under the app's identifier. That includes your chosen voice pack, ignored apps, cooldown, today's nag count, and similar. None of it is transmitted.

License key

When you activate a license, the key is stored in your Mac's Keychain (the same secure store macOS uses for Wi-Fi passwords). The key and a randomly generated machine instance ID are sent to Lemon Squeezy (the payment provider) when activating and every 24 hours to confirm the license is still valid.

Lemon Squeezy receives:

• Your license key
• The machine instance ID
• Your IP address (as a byproduct of the HTTPS request)

Their handling of that data is governed by Lemon Squeezy's Privacy Policy.

Crash reports and diagnostics

Babe Why uses Sentry to collect crash reports and uncaught errors. This helps us identify and fix bugs we wouldn't otherwise hear about. Crash reporting is on by default and can be turned off at any time in Settings → Permissions → Crash reporting.

What Sentry receives when a crash or error occurs:

• A stack trace showing what code was running
• The app version and build number
• Your macOS version and Mac model
• A randomly generated session ID

What Sentry does not receive:

• Your IP address (we set sendDefaultPii = false)
• Your username, email, or any account identifier
• Which apps you switch to or how often
• Your preferences or settings
• Any voice clip contents

Sentry's handling of the diagnostic data is governed by their privacy policy. We do not use Sentry's performance monitoring or session profiling features. Just crash and error capture.

What we do not do

• No analytics or telemetry
• No tracking of which apps you use or how often
• No third-party advertising SDKs
• No cookies (it's a desktop app, not a website)
• No sale of personal data
• No fingerprinting

Your choices

• Microphone access can be revoked at any time from System Settings → Privacy & Security → Microphone. Babe Why's Settings → Permissions tab also has a direct link.
• License key can be cleared from inside the app (Settings → About → reset, when implemented) or by quitting the app and clearing the Keychain entry for Babe Why.
• All local data is removed when you delete the app: drag Babe Why to the Trash, then remove ~/Library/Application Support/BabeWhy/ and the app's preferences via defaults delete com.babewhy.BabeWhy.

Children

Babe Why is not directed at children under 13. Some of the bundled voice clips include adult humor. We do not knowingly collect any data from minors.

Changes

If this policy changes, we'll update the effective date at the top. Material changes (like adding analytics or telemetry) will be flagged on first launch after the update.

Contact

Questions, requests to delete data, or concerns: james.paul.mckinney23@gmail.com.