Privacy Policy

Nothing.

LoudCue does not run any servers, does not have a login system, does not have analytics, does not phone home. There is no LoudCue account because there is no LoudCue cloud.

• Your calendar events.LoudCue reads them from Apple's EventKit framework, the same calendar database that Apple's Calendar app uses. We never copy, transmit, or persist this data anywhere outside your Mac.
• Your settings. Lead time, sound choice, enabled calendars, and so on are stored in macOS user defaults under com.loudcue.LoudCue. They never leave your Mac.

LoudCue makes exactly two outbound network requests, both of which you can disable:

1. Update checks (Sparkle). Once per day LoudCue checks loudcue.com/appcast.xml for a newer version. The request is anonymous; we receive standard web server logs (IP, user agent, timestamp) which we don't link to any user. Disable updates in Settings if you prefer.
2. License key validation (only on the direct-download build, only when activating). When you first install LoudCue and enter your license key, we validate it once with our payments processor (Lemon Squeezy). After that the app stores a signed receipt locally and does not contact the network for licensing again. The Mac App Store build skips this step.

That's it. No analytics SDKs, no crash reporters, no telemetry, no third-party scripts.

When you grant LoudCue calendar access via macOS System Settings, you're granting EventKit permission to a local app on your Mac. Apple manages the permission. We do not see your calendar data in any aggregated, transmitted, or remote form.

You can revoke at any time in System Settings → Privacy & Security → Calendar.

If you email benjamin@reece.is, we keep that email so we can reply to you. We don't add you to a marketing list. We don't share it.

If we materially change this policy, we'll publish the new version here and bump the “Last updated” date. Substantial changes will also appear in the app's release notes.

Email benjamin@reece.is.