HeartbeatHocusFocusFilesMacHyperTile
Guide

dataaccessd, the daemon that talks to your calendar servers

dataaccessd syncs your calendar accounts to their servers, and it writes the password prompts too. Measured: a second of CPU, five plugins.

By Chethan Kumar S N · Updated

Add a work calendar to Internet Accounts and something quiet happens. Within a minute the events are there, in Calendar, in the widget, in Spotlight, and the Mac never opened an app to fetch them. The fetching is done by a daemon called dataaccessd. It holds the login, it talks to the server, and it keeps doing that whether you are looking at your calendar or not.

The name decodes like the rest of the family. It lives in a private framework called DataAccess, data access, plus the d for daemon. Its manual page hands it a job title with no adjectives: dataaccessd is the calendar sync process. It is used by the system to sync calendar data with calendar servers. That is the whole description, three sentences, dated July 17 2022, and it ends the way these pages always end: no configuration options, do not run it manually.

It is the older sibling of the calendar data daemon, and the split between them is clean once you see it. calaccessd owns the calendar database inside your Mac and decides which app may touch it. dataaccessd owns the accounts and the wires: it knows the server addresses, it performs the logins, it pulls down changes and pushes yours back. One daemon for the library, one for the delivery van.

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/DataAccess.framework/Support/dataaccessd
Size225,712 bytes, three architectures in one file: x86_64, arm64e and arm64e.x1, so it still ships for Intel Macs
SignatureApple platform binary, identifier com.apple.dataaccess.dataaccessd, on the sealed system volume
UserThe logged in user, not root
Parentlaunchd, process 1, always
Relaunches21 runs since boot, minimum runtime 10 seconds, last exit the system’s idle memory reclaim
Processor time0.95 seconds across the first hour of the current run, with no CPU added in the checks that followed
Memory5,296 KB, and falling slowly, from 5,776 KB half an hour earlier
Manual pagedataaccessd(8), dated July 17 2022, three sentences long
The cache~/Library/Caches/com.apple.dataaccess.dataaccessd, 168 KB in total
The storeReads and writes the same sealed calendar database as calaccessd, Calendar.sqlitedb in the privacy-walled group container
Log volume448 lines in a one hour window that included a refresh

Two rows deserve a second look. The binary still carries an x86_64 slice, which not every daemon does anymore; Apple keeps this one running on Intel Macs too. And the memory column falls during the run, not rises, which is the system’s pressured exit arrangement working as designed: idle memory is handed back on purpose.

The search picture says people meet this name by accident and nothing worse. The bare seed returns six suggestions and all six are this daemon: dataaccessd, dataaccessd mac, dataaccessd 1.0, dataaccessd mac process, dataaccessd activity monitor, and one German row, was ist dataaccessd. The what is family tops out at what is dataaccessd mac. There is no dataaccessd high cpu row at all, and no virus row either. One odd suggestion reads com.apple.data access.dataaccessd, which is not a typo but the real launchd label, com.apple.dataaccess.dataaccessd, wrapped in a search bar.

What it does all day

The log shows the working day in plain language, and the centrepiece is the daily refresh, caught in the act on the measured Mac at 12:49 in the afternoon. An activity the system had scheduled, com.apple.dataaccess.dataaccessd.dailyrefresh, fires. The daemon logs Daily refresh activity fired for delegate, then a UUID, then gets to work: Account was told to refresh its collections with reason 1. The account type in the same line reads MobileCalDAViCloudDADaemonAccount, which is the iCloud calendar, syncing like any other CalDAV account through the same machinery.

Before it commits, it checks the road. Probing the host, the log says, to see if we have a good enough network connection. We’ll wait up to 30.000000 seconds. Then the TLS handshake lines arrive, boringssl, the same library Safari uses, negotiating TLS 1.3 with the calendar server, and a line for Apple’s authentication framework fetching attestation data. Fetching a calendar is a login, a certificate check and an encrypted connection, and all of it is visible if you ask the log.

The refresh is not the only drumbeat. Per account, the daemon keeps a retry timer, com.apple.dataaccess.dataaccessd.retry followed by the account’s UUID, registered when an account fails and unregistered when it succeeds. On the measured Mac those retry beats landed at 10:17 and 10:52 in the morning, between attempts. And it listens for pushes: the daemon registers three push service hooks with the system, so when a calendar server has news, the message arrives down the line the push daemon keeps warm, and dataaccessd wakes to fetch it. The log catches it asking that daemon for a public token, the handshake push clients make.

Five plugins, one daemon

The strongest evidence for what this process does is sitting in a folder most people have never opened: /System/Library/Address Book Plug-Ins. That is where dataaccessd loads its account engines from, one bundle per protocol, and the live file table on the measured Mac showed the daemon holding them open:

Plugin bundleThe protocol it serves
CardDAVPlugin.sourcebundleContacts over CardDAV, the address book standard
Exchange.sourcebundleMicrosoft Exchange, mail and calendar together
LDAP.sourcebundleDirectory lookups, company address books
DirectoryServices.sourcebundleThe Mac’s own directory layer
LocalSource.sourcebundleOn-device sources, the calendars that never leave your Mac

That is why the framework is called DataAccess and not CalendarAccess. This one daemon is the account machinery for calendars, contacts and directory services at once, which is also why a broken work account can misbehave in two apps at the same time. The Address Book path is a fossil with a function: the bundle format predates the App Store, the job never moved out.

The words on disk

Beside the plugins sits a string table, 61 English strings, and reading it is like finding the daemon’s script for every account dialog you have ever seen. Enter the password for the account, with a separate version for CalDAV, CardDAV, Exchange, Hotmail, LDAP and subscribed calendars. Cannot authenticate to the server because the certificate is not valid. The certificate from this server for that account could not be verified. An identical CardDAV account already exists. Strings for meeting replies, accepted, tentative, declined, and a button that says View Events. Strings for device management, a compliance warning and a policy failure title, for Macs owned by a company. Even Holiday Calendar, the description of the subscribed holidays calendar, is in this file.

This is the bridge between a lowercase process name and something you have personally clicked. When macOS asks for your Exchange password, the text on screen came from this string table, served by this daemon, because this daemon is the one that tried the login. It also mints the default folder names for accounts, one string each for the main Calendar, Contacts, Notes and Tasks lists, which tells you the daemon was built to carry all four kinds of account data even though the manual page only mentions calendars.

The schedule, in its own words

The launch configuration is the best description anyone will write of the job. It wakes on three named notifications: _CalDatabaseChangedNotification, something wrote to the calendar database; a preference notification for how many days of calendars to sync; and com.apple.dataaccess.checkHolidayCalendarAccount, the check that runs when you toggle the holidays calendar. Then there is one scheduled activity, com.apple.dataaccess.connected, and its gates are worth reading out loud: AllowBattery true, RequireBatteryLevel 15, RequireNetworkConnectivity true, RequiresBuddyComplete true, RequireScreenSleep false, priority Maintenance. In plain English: sync on battery is fine, but never below fifteen percent, never without a network, never before the Mac has finished its first-day setup, and no waiting for a dark screen.

Compare that with its sibling’s house rules, where the maintenance jobs wait for a sleeping screen and the charger, and the difference in temperament is the point. calaccessd tidies when nobody is looking. dataaccessd syncs when your calendar needs to be right, which is usually exactly when you are looking at it.

The honest cost

Two measurements keep this page square. The cheap one is processor time: 0.95 seconds in the first hour of the current run, all of it around launch and the midday refresh, with zero added in the checks that followed. Even relaunched roughly every day and a half, that lands at about a second of work a day. The expensive one is patience, not CPU: in the kernel’s sleep log, the same one the calaccessd page walks through, this daemon once timed out at 30,000 milliseconds right beside its sibling, holding the walk into sleep while it settled a sync. That is a Mac taking a long breath before the indicator light goes out, not a fault.

Nothing here leaves the Mac by accident. The daemon talks to your calendar servers, the same ones your iPhone uses, over the same encrypted connections, and the calendar store it reads is sealed behind the privacy wall. Apple’s consumer documentation never names it; the closest it comes is a page titled Use your Internet accounts on Mac, which explains that you can use Exchange, Google, Yahoo and other internet accounts in Mac apps by adding the accounts to your Mac, and leaves the machinery out entirely. If you want fewer moving parts, the honest lever is accounts, not processes: quit a calendar you no longer use in Internet Accounts settings and this daemon has one less login to keep warm. The work people blame on it is almost always the account’s work, and the account was your idea.

Questions

What is dataaccessd on my Mac?

It is the calendar sync process, Apple's own words from its manual page, the daemon inside the DataAccess framework that syncs calendar data with calendar servers. When you add a Google, Exchange, Yahoo or work CalDAV account in Internet Accounts, this is the process that logs in, fetches events and pushes changes back, whether Calendar is open or not. It runs as your own user, not root, is launched by launchd from a system framework folder, and is signed by Apple on the sealed system volume. Like its sibling calaccessd it has a manual page, dataaccessd(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 name looks alien in Activity Monitor.

Why does my Mac keep asking for a calendar account password?

Often because dataaccessd is doing its job and the server said no. The daemon ships its own alert vocabulary, 61 English strings on disk, and it is the process behind prompts like Enter the password for the account, Cannot authenticate to the server because the certificate is not valid, and The certificate from this server could not be verified. There is a version of the password prompt for every protocol it speaks: CalDAV, CardDAV, Exchange, Hotmail, LDAP and subscribed calendars. An expired password, a changed server certificate or a company proxy will surface as one of these dialogs. Fixing the account in Internet Accounts settings fixes the dialog, because the dialog was never the problem, the login was.

What is the difference between dataaccessd and calaccessd?

One daemon for the accounts, one for the database. dataaccessd is the older sibling: it holds the logins and talks to the calendar servers over HTTPS. calaccessd is the broker inside the Mac: every app that reads or writes events goes through it, and it owns the calendar database in the group container. The two keep each other company in the kernel's sleep log, where a slow settle before sleep once showed calaccessd timing out at 30,000 milliseconds with dataaccessd timing out right beside it. If Activity Monitor shows both, that is a Mac with its calendar machinery intact, not two programs fighting.

Why do I see two or three dataaccessd 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 one extra copy was alive, from the iOS 27.1 runtime, alongside the Mac's own, and the same three copies pattern shows up in this series on the calendar data daemon and the Family Sharing daemon. Quit the simulator and the extras go with it.

Can I quit or disable dataaccessd?

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, 21 times on the measured Mac since the last reboot, roughly every day and a half. Its last exit reason on the clock was JETSAM_REASON_MEMORY_IDLE_EXIT, the system's own idle memory reclaim, which is macOS recycling it on purpose. Force quitting buys minutes of quiet until the next push notification or refresh timer brings it straight back. The real lever is the accounts themselves: every calendar account you remove from Internet Accounts is one less login this daemon has to keep alive.

Does dataaccessd sync on battery? Why is it awake at night?

Yes, within limits the daemon's own configuration file states out loud. Its sync activity is flagged AllowBattery true with RequireBatteryLevel 15 and RequireNetworkConnectivity true, so it will sync on battery, but never below fifteen percent and never without a network. It does not wait for the screen to sleep. The wake-ups people notice at night are usually pushes: the daemon registers three push service hooks with the system, so when a calendar server has news, the push daemon delivers it and dataaccessd wakes to fetch. The measurement here is calm, 0.95 seconds of processor time in the first hour of a run and none added in later checks, so a busy night means a busy account, not a daemon gone wrong.

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