HeartbeatHocusFocusFilesMacHyperTile
Guide

calaccessd, the daemon behind every calendar on your Mac

Every calendar read and write goes through calaccessd, and its travel engine books system wakes. Measured: 19 relaunches, under a second of CPU a day.

By Chethan Kumar S N · Updated

Open Calendar on a Monday and it is already there. The week’s events, the weather line, the birthdays pulled from contacts, the invite someone sent at 6am. None of that is Calendar.app doing the fetching. The app draws; a daemon called calaccessd does almost everything else, and it keeps doing it whether Calendar is open or not.

The name decodes the same way as its relatives. It lives inside a private framework called CalendarDaemon, cal access, calendar access, plus the d for daemon. Its manual page gives it the driest job title in the family: the calendar data process. It is used by the system to coordinate access to calendar data and to post calendar notifications. In practice that makes it the front door to every calendar on the Mac. Apps do not open the calendar database themselves. They ask calaccessd, and it decides what they may see, tells the database what changed, and shouts, politely, over the system’s notification channels when something new arrives.

Here is what it looks like on a real Mac, macOS 27.0.1 on a MacBook Pro, 29 days of uptime, the same machine this site’s other daemon pages are measured on.

The receipts

WhatMeasured
Path/System/Library/PrivateFrameworks/CalendarDaemon.framework/Support/calaccessd
Size177,040 bytes, two architectures in one file: arm64e and arm64e.x1
SignatureApple platform binary, identifier com.apple.calaccessd, on the sealed system volume
UserThe logged in user, not root
Parentlaunchd, process 1, always
Relaunches19 runs since boot, minimum runtime 4 seconds, last exit the system’s idle memory reclaim
Processor time0.43 seconds across the first 18 minutes of the current run, all of it start-up, with no further CPU in the checks that followed
Memory6,352 KB
Manual pagecalaccessd(8), dated July 17 2022, three sentences long
The storeThe group container group.com.apple.calendar, sealed behind the privacy wall
Log volume4,331 lines in the last day

Two details in that table deserve a second look. The binary is tiny, 177 KB, because the daemon is a broker, not a worker; the heavy lifting lives in the frameworks around it, CalendarFoundation, CalendarNotification, CalendarIntegrationSupport, all loaded at launch. And the store it guards is unreadable to an ordinary ls, which reports Operation not permitted. Your calendars live behind the same privacy wall as your contacts and your photos.

The search picture matches the shape of a Mac process people meet by accident. The bare seed returns four suggestions and all four are this daemon: calaccessd, calaccessd macbook, calaccessd iphone and com apple calaccessd. What is calaccessd on mac is the top row of its what-is family. There is no calaccessd virus row and no calaccessd high cpu row at all. Nobody’s Mac is being ruined by this process. They just want to know what it is.

What it does all day

The log shows a working day in plain language. It holds a persistent connection for calendar sync, and a monitor on that connection watches the Wi-Fi link, so through the night the log fills with lines like State:/Network/Interface/en0/LinkQuality linkQualityInfo, LinkQuality = 100, the daemon noticing the network is fine. When the system wakes, it logs both beats: System is waking: kIOMessageSystemWillPowerOn, then System woke: kIOMessageSystemHasPoweredOn. Calendar wants to be current before you look at it, and this is the piece that never sleeps through the alarm.

Clients come and go over XPC. A typical morning line reads activating connection: mach=true name=com.apple.tccd, the permissions daemon, because the first thing a calendar client must establish is what it is allowed to know. The full handshake is visible in the log: tcc_send_request_authorization, then the connection to tccd opening. If you have ever wondered which process is on the other end of the Allow access to your calendar prompt, on this side of the dialog it is usually this one.

What the clients get is a database service, not a file. The log prints the options each client sets when it connects, database initialization options that say things like changeTrackingID and allowDelegateSources, a checkout system for concurrent readers. When Calendar.app, a widget and Spotlight all want the week’s events at once, they each hold a handle and the daemon reconciles them. That is the coordination the manual page refuses to brag about.

The travel engine, and the wake it books

Buried in the log is the daemon’s most surprising habit. Every eight hours, on a timer the log prints verbatim, the travel engine refreshes itself: The periodic refresh timer fired for travel engine, then Uninstalling the periodic refresh timer, then Installing a periodic refresh timer, Timer interval: 29580, Estimated fire date. The point of the engine is time zones. A calendar that only knows the time zone you are in gets meetings wrong the moment you cross a border, so the daemon keeps a model of where you are likely to be and when, and refreshes it on this slow drumbeat.

Two receipts make this concrete. First, when the next fire time falls while the Mac is asleep, the daemon does not skip it; powerd’s own table shows the booking, a scheduled wake by com.apple.alarm.user-invisible-com.apple.calaccessd.travelEngine.periodicRefreshTimer, with user-invisible being Apple’s label for wakes that never show on screen. Second, the engine needs location to do its job, and on the measured Mac it does not have it: Calendar system service is not authorized to use location, the log records, a refusal, caught in the act, by the permissions daemon’s wall.

So the daemon books a wake, runs its refresh, and gets told no at the location desk. It carries on anyway with what it has. There is something reassuring about a system that keeps its appointments even when the answer is no.

The schedule, in its own words

The launch configuration is the best description anyone will write of the job. It registers wake triggers for seventeen named notifications, and the names read like a calendar’s pulse:

Trigger, verbatim from the configurationWhat it means
_CalDatabaseChangedNotificationSomething wrote to the calendar database
CalSyncClientFinishedMultiSaveA sync finished saving a batch of changes
com.apple.mobilecal.timezonechangedThe Mac changed time zone
SignificantTimeChangeNotificationMidnight, or a daylight saving jump
com.apple.reminderkit.storeChangedReminders changed, they share the store
com.apple.calendar.database.preference.notification.suggestEventLocationsA toggle flipped for suggesting event locations

Below the triggers sit four maintenance jobs, and the gates on them are the story: attachmentcleanup, changetablecleanup and databasecleanup, plus a daily analytics job, every one of them flagged Repeating with a delay of 28,800 or 86,400 seconds, every one of them with AllowBattery false and RequireScreenSleep true. In plain English: the daemon tidies its database, prunes orphaned attachments and compacts its change table only when the lid is shut, the screen is dark and the Mac is on power. Apple wrote the house rules into the configuration file, and they are conservative.

There is also a cast list hiding in the same file. The daemon’s launchd registration hosts service names that other guides in this series have chased separately: com.apple.CalendarAgent, the client side of calendar access; com.apple.corespotlight.daemon.calendar, the pipe that feeds calendar events into Spotlight, which is searchpartyd’s end of the pool; and com.apple.usernotifications.delegate.com.apple.iCal, the seat calendar alerts occupy in the notification system. One configuration file, four actors.

The honest cost

Two measurements keep this page square. The cheap one is processor time: 0.43 seconds in the first 18 minutes after launch, which is the daemon building its caches, and no additional CPU in the checks that followed. Even relaunched every day and a half on average, that lands at well under a second of work a day. The expensive one is sleep latency, quoted above: up to 30 seconds of holding the door during one sleep transition, with its sibling dataaccessd timing out beside it. The first number is why you should not worry about calaccessd. The second is why a Mac sometimes takes a long breath before the indicator light goes out, and the battery guide walks that log line by line.

Nothing here leaves the Mac by accident. The sync connection talks to your calendar servers, the same ones your iPhone uses, and the store is sealed. If you want fewer moving parts, the honest lever is accounts, not processes: every CalDAV or Exchange account you remove from Internet Accounts is one less thing for the daemon to watch. Quitting the daemon itself just teaches launchd to say good morning again.

Questions

What is calaccessd on my Mac?

It is the calendar data process, Apple's own words from its manual page, the daemon inside the CalendarDaemon framework that coordinates access to calendar data and posts calendar notifications. Every app that reads or writes events, Calendar itself, widgets, Spotlight, scripts using EventKit, goes through it rather than touching the calendar database directly. It runs as your own user, not root, launched by launchd out of a system framework folder, signed by Apple on the sealed system volume. Unlike most of its relatives it actually has a manual page, calaccessd in section 8, three sentences long, which says there are no configuration options and that users should not run it manually. Apple's consumer documentation never names it, which is why the bare process name looks alien in Activity Monitor.

Why is calaccessd in my battery logs or pmset output?

Because it books system wakes. The daemon's travel engine keeps a refresh timer, measured firing every 29,580 seconds, a little over eight hours, and when the timer is due while the Mac sleeps, the request lands in powerd's wake table. On the measured Mac a scheduled power event read wake by com.apple.alarm.user-invisible-com.apple.calaccessd.travelEngine.periodicRefreshTimer. The log also shows the honest cost: during one sleep transition the kernel logged calaccessd is slow at 14,615 and 15,581 milliseconds and then calaccessd timed out at 30,000 milliseconds three times, meaning it held up the walk into sleep for up to half a minute while it finished save work. That is the daemon being slow to settle, not a fault, and it is also why the name shows up in battery questions.

Why does calaccessd want my location?

For the travel engine. Its job is to predict when an event's time zone matters, a flight, a meeting abroad, a repeating call that crosses a daylight saving change, and to have the calendar ready before you notice. The log catches it asking and being refused on the measured Mac: Calendar system service is not authorized to use location. That line is worth reading twice, because it is the permission system working. The daemon also talks to tccd, the permissions daemon, through a call the log prints as tcc_send_request_authorization, and the calendar store itself sits behind the privacy wall, an ordinary ls of its group container reports Operation not permitted.

Why do I see two or three calaccessd processes?

Almost always because Xcode simulators are booted. Every iOS simulator runtime ships its own copy of the daemon inside its cryptex mount, and a booted simulator starts it the way a real iPhone would. On the measured Mac two extra copies were alive at once, one from an iOS 27.0 runtime and one from 27.1, alongside the Mac's own. The same three copies pattern shows up in this series on the notifications daemon and the Family Sharing daemon. Quit the simulator and the extras go with it.

What is the difference between calaccessd, CalendarAgent and dataaccessd?

calaccessd is the broker that owns access to the calendar database and posts change notifications. CalendarAgent is the client side, the piece apps talk to first, and on current macOS its service name, com.apple.CalendarAgent, is registered inside calaccessd's own launchd configuration, so the two are deliberately intertwined. dataaccessd is the older sibling in the DataAccess framework, the account level machinery that logs into calendar servers and fetches changes, and the two keep each other company: in the same kernel sleep log where calaccessd timed out, dataaccessd timed out right beside it. If Activity Monitor shows both, that is one daemon for the database and one for the accounts, not two programs fighting.

Can I quit or disable calaccessd?

There is nothing to configure and no point quitting it. The binary takes no options, the manual page says not to run it manually, and launchd restarts it on demand anyway, 19 times on the measured Mac since its last reboot, roughly every day and a half. Its exit reason on the clock was the system's own idle memory reclaim, JETSAM_REASON_MEMORY_IDLE_EXIT, which is macOS recycling it on purpose. Force quitting buys you minutes of quiet until the next calendar change, time zone shift or sync brings it straight back. The real lever is the accounts themselves: remove or pause a calendar account in Internet Accounts and the daemon has progressively less to do. At well under a second of processor time a day, it has earned the right to be left alone.

Ready? Buy Ribbon for $15, or read all the guides.