Home Blog NotchDock privacy boundaries: local data and external feeds

NotchDock privacy boundaries: local data and external feeds

A useful privacy review distinguishes local app storage, macOS services, external feeds, and website measurement. This page describes those boundaries without claiming that NotchDock makes no network requests or is suitable for every organization.

Local app data and macOS services

The reviewed source stores widget preferences in UserDefaults. Quick Access snippets and ToDo folder data use Keychain APIs. Quick Notes keeps a cache and can interact with the user’s Apple Notes app through macOS Automation. Calendar and Reminders widgets use EventKit with the corresponding macOS permission. Review the NotchDock privacy policy for the current user-facing description.

Data that needs a network

Sports and market widgets request public data from external providers. Those requests leave the Mac and are governed in part by the providers’ terms and service availability. A locally saved team or ticker choice is different from the score or price returned by the provider. Network data can be delayed, unavailable, or inconsistent with a live broadcast.

App data is separate from website measurement

The privacy policy describes website visit and download-button measurement separately from the app’s workspace. A download-button event does not prove a completed download or installation. App diagnostics are user-shared only when the user exports them for support, according to the published policy.

Review fit for your environment

  1. Check the privacy policy and release notes for the version you install.
  2. Review granted Calendar, Reminders, Automation, and other macOS permissions.
  3. For organizational use, compare those data flows with your own rules and test with non-sensitive data before enabling a widget.

This page makes no zero-telemetry, no-identifier, no-cloud, or enterprise-compliance guarantee. Use the policy and your own release review as the basis for a decision.