Why privacy matters for a menu bar app
A menu bar manager runs continuously and receives sensitive macOS permissions. Users should know why those permissions exist and what the app sends over the network.
Tuck privacy posture
- No analytics.
- No telemetry.
- No crash-reporting SDK.
- License validation for Pro.
- Sparkle update checks for safe app updates.
How to verify it
You can monitor Tuck with Little Snitch, LuLu, Proxyman, or another network monitor. Expected calls are tied to license validation and update checks, not usage tracking.
The tradeoff
Tuck still needs Accessibility to manage menu bar behavior, and Shelf Mode may request Screen Recording so icons can be shown accurately. The permissions guide explains both prompts.
Frequently asked questions
Does Tuck collect any data or telemetry?
No. Tuck has no analytics, no telemetry, and no crash-reporting SDK. The only expected network calls are license validation for Pro and Sparkle update checks for safe app updates.
How can I verify what Tuck sends over the network?
You can monitor Tuck with Little Snitch, LuLu, Proxyman, or another network monitor. Expected calls are tied to license validation and update checks, not usage tracking.
Why does a privacy-first app still need permissions?
Tuck needs Accessibility to manage menu bar behavior, and Shelf Mode may request Screen Recording so icons can be shown accurately. These permissions are used locally to do the job, not to collect data.
Is Tuck a subscription?
No. Tuck uses one-time pricing for Pro, with no subscription.