Privacy Policy
This document tells you exactly what data Callllendar handles, where it goes, and what I (the developer) can and cannot see. If anything is unclear, get in touch via Support.
The short, honest version: what's on your calendar is none of my business, and I genuinely don't want it. Callllendar runs on your Mac and talks directly to your own calendar provider. I'm not in the middle, there's no Callllendar server, and the app sends no telemetry, analytics, or crash reports anywhere.
Short version
- Your events never touch a server I run. Local calendars are stored in a database on your Mac; connected calendars sync directly between your Mac and your own provider (iCloud or any CalDAV host) over TLS.
- No telemetry. The app does not phone home with usage analytics, crash reports, or "anonymized improvement data." It never has, and it never will.
- The only network calls Callllendar makes are to your calendar provider, and — if you leave it enabled — periodic fetches of public link-safety lists. No personal data is sent in those fetches.
- Your purchase is handled entirely by Apple through the Mac App Store. Apple is the seller. I never see your name, email, or payment details — only Apple's aggregate sales reports.
- No cookies or trackers on this website. It's static HTML with no analytics and no third-party scripts.
What data the app stores on your Mac
- Your events and calendars — titles, times, locations, notes, attendees, reminders — the same details any calendar client handles.
- Account configuration: server URLs, your username, your account's calendar list. Stored locally inside the app's sandbox container.
- Your CalDAV password, stored in the macOS Keychain. The Keychain is system-encrypted at rest; the app reads it on demand.
- Application preferences (theme, week start, layout), stored locally.
None of this leaves your Mac unless you explicitly sync to a connected account, send an invitation, or export an event.
Network calls the app makes
To your calendar provider (Apple / CalDAV)
Standard calendar sync over TLS — through Apple's EventKit for local Apple calendars, or directly to your CalDAV server. Your provider sees what it would from any calendar client: your IP, a user-agent string, and the times you connected. I don't see any of this.
To public link-safety lists (optional)
To warn on risky meeting links and strip trackers from them, the app ships with bundled snapshots of public safety lists (such as the Disconnect tracker list, PhishTank, and URLhaus) and — if you leave automatic updates on — periodically fetches refreshed copies from their public sources. These are plain downloads of public lists: the app sends no information about you, your calendar, or your browsing in the request. You can turn the updates off in Settings. When you open a link from an event, the destination is checked against the locally-stored lists on your device — the link is not sent to me.
What the app does NOT call
The Mac App Store build of Callllendar contains no licensing or "phone-home" code. There are no license-validation pings and no in-app update checks — Apple handles purchase and updates. There's no analytics or crash-reporting SDK of any kind.
Calendar access (EventKit)
If you connect Apple Calendar, macOS asks your permission for Calendar access, which Callllendar uses only to read and write your events through Apple's EventKit — on your device. You can revoke this anytime in System Settings → Privacy & Security → Calendars.
What I (the developer) can see
- Apple's App Store sales reports. Apple gives me aggregate figures — units sold and proceeds, by territory and date. Apple does not share your name, email address, or payment details with me.
- That's it. I don't see what's on your calendar, who you meet with, what you've searched for, or anything else inside the running app. None of it leaves your Mac. Even if I wanted to read your schedule — I don't — I have no plumbing to do it.
What I do NOT collect
- No event content, ever. Not yours, not anyone's.
- No usage analytics, no event logs, no "created X events this week" stats.
- No crash reports — the app has no crash-reporting integration. If something breaks, please tell me; nothing reaches me automatically.
- No advertising identifiers, no fingerprinting, no cookies on any web property associated with the app.
- No newsletter you didn't ask for. If you ever get email from me, it's because you emailed me first.
Third parties
- Apple is the seller (merchant of record) and provides the operating system, the App Store, EventKit, and the Keychain. Apple's privacy policy applies to your purchase: apple.com/legal/privacy.
- The safety-list sources (Disconnect, PhishTank, URLhaus) serve the public link-safety lists described above.
That's the entire third-party list. No analytics, no error trackers, no email-marketing tools, no chat widgets, no CRMs — and the Support page contacts me by a plain email link, with no form-processing middleman.
Your rights
Depending on where you live, you may have the right to access, correct, port, or delete personal data a company holds about you (PIPEDA in Canada, GDPR in the EU/UK, CPRA in California, etc.). Because I hold no personal data about you — your purchase details live with Apple, not me — there's nothing for me to export or delete on the app side. For purchase data, contact Apple. For anything else, reach out and I'll help.
Children
Callllendar is not directed at children under 13 (or 16 where that's the threshold). I don't knowingly collect data from children — or anyone. If you have a concern, contact me.
Data location
Your events and app data live on your Mac, inside the app's sandbox container. I don't operate any server that holds your data. Purchase records are held by Apple.
Changes to this policy
I'll update this page when material things change. The "Effective" date above reflects the most recent change.
Contact
Privacy questions, data-access requests, or general "wait, you do what now?" questions: see the email link on the Support page.
— The Callllendar developer