Privacy

Last updated: July 2026

Your calendar belongs to you — not to me, and not to a server. cal-mirror has no account, no backend, and makes no network requests of its own. It never sends your calendar anywhere. There is nothing for me to collect, because I collect nothing.

What the app does

You tell cal-mirror which calendar to copy and where to copy it. It reads events from the source and writes copies into the destination, using Apple's Calendar framework on your device. That's the whole job. The list of pairs you set up is stored only on your device.

No collection, no tracking

No analytics. No advertising or tracking SDKs. No behavioral data. No crash or usage telemetry sent to me. cal-mirror ships with none of that and never will — surveillance isn't a feature I'm interested in building.

No credentials, ever

cal-mirror works through calendars that are already set up on your device, so it never asks for, sees, or stores any account passwords or tokens.

The one thing I can't control — and won't pretend to

If your destination calendar lives in an account like iCloud, Google, or Exchange, then once a copy lands there, that provider syncs and retains it under their policies — exactly as it would for any event you added to that calendar yourself. cal-mirror isn't part of that sync and can't reach into it. That's the honest boundary: on your device, cal-mirror keeps to itself; beyond it, your account provider's terms apply. If that matters to you, point cal-mirror at a local or self-hosted calendar as the destination.

Changes

If this policy ever changes, the update will be here and in the source, which is public. The bar it has to clear is simple: still collect nothing.

Contact

Questions or concerns: github.com/mattbaylor/cal-mirror.