Privacy

1Overview

Calendar Time Logger is a work-tracking app for iPhone, iPad, Mac, and Apple Watch, developed by Abir Barman ("I", "me"). It records the work sessions you start and finish, and can add each finished session to Apple Calendar.

The app is designed so that your information stays under your control. It has no accounts, no servers operated by the developer, no analytics or advertising, and no third-party code. Your data is stored on your devices and, where you use iCloud, in your private iCloud database, which is stored by Apple under your Apple Account. I don't receive a copy of it and can't access it.

This policy applies to the Calendar Time Logger apps and to this website, ctl.abirbarman.com.

2Information Calendar Time Logger handles

The app works with the information you enter and the work you record:

• Templates: name, icon, color, category, chosen calendar, tags, notes, Urgent and Important defaults, menu bar and notification settings.
• Work sessions: the template's name, icon, and color at the time, category, Urgent and Important, start and finish times, pauses, notes, tags, the calendar and Calendar event it was written to, and its Calendar status.
• Categories: their names.
• Preferences: such as your daily goal, Calendar options, notification choices, menu bar and appearance settings, and export columns.
• Device list: for Live Sync, each of your devices keeps one small record: a random device identifier, the device's name (or a name you set), its kind, system and app versions, hardware model identifier, and when it last reported and synced, plus a short connection history.

The app doesn't ask for your name, email address, contacts, location, photos, camera, microphone, or health data.

If you email me for support, I receive your email address and whatever you include in your message. I use it only to reply and to fix the problem you report.

3Information stored on your devices

On Mac, iPhone, and iPad, your templates, categories, and work sessions are stored in the app's own container on that device. Preferences are stored in the app's settings on that device.

• iPhone widgets, Live Activities, and Apple Watch use a small summary (the session in progress, your templates, today's total, and recent sessions) kept in a container shared only between the app and its own widgets.
• The device identifier used for the device list is random, kept in that device's Keychain, never synced, and never derived from the hardware.
• Lock Screen: the Live Activity and Lock Screen widget mark the template name as private, so it's hidden when your iPhone hides Lock Screen content while locked.
• Sample data you choose to explore on the welcome screen stays on that device. It is never synced to iCloud or written to Calendar, and you can remove it in Settings.

4iCloud and CloudKit

When your devices are signed in to the same Apple Account, Calendar Time Logger uses Apple's CloudKit to sync your templates, categories, and work sessions (including their notes, tags, priority, and Calendar status) through your private iCloud database. Shared preferences (daily goal, Calendar behavior, notification choices, and export columns) and the device list use iCloud key-value storage.

This data is stored by Apple in your iCloud account and is governed by Apple's iCloud terms and privacy policy. Only your Apple Account can read your private database. Abir Barman doesn't operate a server for the app, doesn't receive a copy of your data, and has no access to your private iCloud database.

Some settings stay on each device and are not synced: the default calendar, menu bar, window, and appearance settings, and the record of which device wrote each Calendar event. If you're signed out of iCloud, everything stays on the device.

5Calendar data

Calendar access is optional. If you grant it, Calendar Time Logger uses it to list your calendars so you can choose one, to add an event when you finish a work session, and to update or remove the events it created. Without access, your work is still recorded; sessions are simply marked as not in Calendar.

Full access is requested because "Add Events Only" access can't list calendars or update existing events. The app reads events only to find its own, which it recognizes by a link stored in each event, near each session's time. It never changes or deletes events it didn't create, and nothing it reads from Calendar is sent anywhere.

For each finished session, the event contains:

• the template name as the title, and the session's start and finish times;
• notes with active work, paused time, category, and Urgent and Important, plus your tags and session notes if you turn those options on;
• a link back to the session in Calendar Time Logger.

Once written, the event is part of your calendar. If that calendar belongs to an account such as iCloud, Google, or Exchange, it syncs the way any event in that calendar does, which is outside Calendar Time Logger's control.

6Cross-device synchronization

Mac, iPhone, and iPad sync through your private iCloud database as described above. The iPhone and Apple Watch communicate directly, as described in the next section. There is no other sync path: no servers of our own, and no Bluetooth or local-network sync built by the app.

For Live Sync › Devices, each device writes its own record and its connection history (when the app opened or closed and when it lost or regained iCloud, with a reason such as "No network") to your iCloud key-value storage, where only your Apple Account can read it.

Only the device that finishes a session writes its Calendar event, so a synced session is never added twice.

7Apple Watch

The iPhone and Apple Watch exchange the session in progress, template names, symbols, colors, categories, and priorities, today's total, and the last five finished sessions directly, using WatchConnectivity, Apple's encrypted link between a paired iPhone and Apple Watch. Nothing goes through a server.

The Watch keeps no database of its own: only a cached summary, and any taps it hasn't yet delivered to the iPhone. Work started or finished on the Watch is saved on the iPhone, which also writes the Calendar event.

8Website information

ctl.abirbarman.com is a static website. It doesn't use cookies, analytics, advertising, tracking pixels, embedded third-party content, or forms, and it doesn't store anything in your browser.

Like any website, it is delivered by a hosting provider (currently Vercel), whose servers necessarily receive standard technical information with each request, such as your IP address, browser type, and the page requested, and may keep it briefly in server logs for security and reliability. I don't use that information to identify or profile visitors.

The Support page's email link opens your own email app; nothing is sent until you send the message yourself.

9Third-party services

Calendar Time Logger contains no third-party code, SDKs, or libraries. It relies only on Apple services that are part of your devices:

• iCloud and CloudKit for sync, under your Apple Account;
• Apple Calendar (EventKit), if you allow Calendar access;
• WatchConnectivity between your iPhone and Apple Watch;
• notifications, which the app schedules on your device;
• the App Store, through which the app will be distributed.

Apple's handling of data in these services is described in Apple's own privacy policy. When you export work logs to Excel, the file is saved or shared wherever you choose, and what happens to it afterwards is up to you.

10Analytics and diagnostics

The app contains no analytics, crash-reporting, advertising, or tracking code, and it has no networking code of its own.

Separately, Apple lets you choose in your device's settings whether to share analytics with app developers. If you opt in, Apple may provide me with crash reports and aggregated usage information for the app through App Store Connect, under Apple's privacy policy. I use these only to find and fix problems.

11Data retention

• Templates, categories, and work logs are kept on your devices, and in your iCloud if you sync, until you delete them.
• Cancelled sessions are kept in the app's store but never shown, counted, or written to Calendar.
• Connection history in Live Sync is deleted automatically after 7 days.
• Devices not seen for 60 days are removed from the device list automatically.
• Calendar events the app wrote stay in your calendar until you, or the app at your request, remove them.
• Support emails are kept in my email account only as long as needed to help you.

12Data deletion

Because I don't hold your data, you delete it yourself, using the app and your Apple settings:

• A work log: delete it in Work Logs and choose whether to remove its Calendar event too. With sync on, the deletion reaches your other devices.
• A template: delete it in Templates. Work logs recorded with it are kept.
• A device: choose Remove Device in Live Sync to delete its record and history from your device list. Nothing on that device is deleted.
• Sample data: remove it in Settings › Sample Data.
• Calendar access: turn off Calendar sync in the app's settings, or revoke access in your device's Privacy & Security settings. Events already written stay in Calendar.
• Everything on one device: delete the app (on Mac, quit it and delete its container). This removes the data stored on that device, but not the copy in your iCloud or events already in Calendar.
• Your iCloud copy: delete work logs and templates in the app while sync is on. You can also manage or delete app data stored in iCloud from your Apple Account's iCloud storage settings on your device, where Apple lists it.

To delete a support email conversation, email me and ask.

13Children's privacy

Calendar Time Logger is a general productivity app and isn't directed at children. I don't knowingly collect personal information from anyone, including children: the app sends me nothing, and the only information I receive is what someone chooses to send by email. If you believe a child has emailed me personal information, contact me and I'll delete it.

14Security

Calendar Time Logger relies on Apple's platform protections: the app runs in its own sandboxed container, sync uses your private iCloud database, the iPhone and Apple Watch use Apple's encrypted connection, and the device identifier lives in the Keychain. Protecting your devices and Apple Account with a passcode and two-factor authentication protects your work data too. No method of storage or transmission is perfectly secure, but because I operate no servers, there is no central copy of your data to breach.

15Changes to this policy

If the app or this website changes how information is handled, I'll update this page and the "Last updated" date above before the change takes effect. Significant changes will also be noted in the app's release notes.

16Contact

Questions about privacy are welcome.

Developer

Abir Barman

Email

abir@abirbarman.com

Website

abirbarman.com