HeartbeatHocusFocusFilesMacHyperTile
Guide

familycircled, the daemon that knows who counts as your family

familycircled keeps the Family Sharing roster straight and brokers the Age Range for Apps prompt. Measured: four scheduled jobs, a sealed cache, seconds a day.

By Chethan Kumar S N · Updated

Every so often a Mac asks its owner a genuinely strange question. This one arrives inside apps rather than the firewall: an app would like to know your age range. Not your birthday, just a band. Say yes and the app learns whether you are over 18 or 13 or 21, depending on what it asked for. People who dig into where that popup comes from find a process with an even stranger name doing the brokering: familycircled.

The name decodes cleanly. It lives inside a private framework called FamilyCircle, which is what Apple calls a family group internally, the set of up to six people tied together by Family Sharing. Add the d for daemon. Its job is the roster: who is in the circle, who has been invited, which members are children, and what the rules say each of them may do. The features that sit on top, purchase sharing, Ask to Buy, Screen Time for kids, and the age range popup, all need that roster kept current on every device in the group, including Macs.

Here is the thing measured on a real Mac, macOS 27.0.1 on a MacBook Pro, 28 days of uptime, the same machine this site’s other daemon pages are measured on.

The receipts

WhatMeasured
Path/System/Library/PrivateFrameworks/FamilyCircle.framework/Resources/familycircled
Size3,735,264 bytes, three architectures in one file: x86_64, arm64e and arm64e.x1
SignatureApple platform binary, identifier com.apple.familycircled, on the sealed system volume
UserThe logged in user, not root
Parentlaunchd, process 1, always
RunningCurrent run 4 days, 9 runs on the clock
Processor time6.4 seconds across those 4 days, about a second and a half a day
Memory9,872 KB
Last exitThe system’s idle memory reclaim, which is the daemon’s normal way to leave

The framework carries two more pieces worth naming. It ships its own database schemas, one model file for the shared circle and one for private data, which tells you the daemon was built to keep a local copy of the roster rather than fetch it every time. And it ships localized strings for 44 languages, which is where the age range story comes from below.

What it does all day

The log shows the work in plain English. Every refresh is an operation the log calls FAFetchFamilyCircleOperation, fetch family circle, and after each one the daemon updates its cached counters: how many people are in the family, how many invitations are outstanding. When Settings opens the Family pane, this is the process that can answer without a round trip to Apple’s servers.

It also holds a live push connection. The log shows the Apple Push Service handing it connection status changes, and the configuration registers push subscriptions against four CloudKit containers with names like familycircle.private and familycircle.shared. That is the instant-update machinery: when a parent approves an Ask to Buy request on their iPhone, the change lands in the family’s CloudKit containers, and every Mac in the circle hears about it through this daemon’s push channel. The record syncing itself is cloudd’s job; familycircled is the client that knows what the records mean.

One more detail from the log is easy to read past and shouldn’t be. The daemon tracks the frontmost application, fetching application records and noting whether the process in front is entitled to ask family questions. Apps that want age ranges or family approvals have to identify themselves, and an Apple internal process that lacks the right entitlement gets logged with the word Grandfathering, a lenient pass for first party clients. There is a gatekeeper in here, in other words, and the log catches it carding people at the door.

The schedule, in its own words

The launch configuration names four background jobs, and the names are the best description of the daemon anyone will write:

Job, verbatim from the configurationCadenceGates
com.apple.family.cache.refresh.backgroundTaskEvery 86,400 seconds, at most once a dayMaintenance priority, external power and network required
com.apple.family.heartbeat.backgroundTaskEvery 90,000 seconds, at most once a dayUtility priority, network required, runs on battery
com.apple.family.jurisdictionChange.backgroundTaskEvery 90,000 seconds, at most once a dayNetwork required
com.apple.family.osupdate.backgroundTaskOnce, after a system update installsRuns only after setup has completed

A heartbeat a little over once a day, a cache refresh that politely waits for the charger, and a job whose name says it all: jurisdiction change. Family rules are legal rules, the age of adulthood is 13 in one country and 20 in another, and when a family member moves, the daemon re-checks which set of rules applies to them.

There is a fifth trigger, and it is the most human one in the file. The daemon asks to be woken whenever the contacts database changes, by name: CNContactStoreDidChangeNotification. Family members are contacts, so when you edit your sister’s card, the contacts daemon broadcasts the change and familycircled gets up to see whether the family roster is affected.

The age question

Back to the popup. Age Range for Apps is Apple’s answer to a law shaped problem: apps need to know roughly how old you are, and nobody wants to hand teenagers’ birthdays to every developer. The framework’s own strings file describes the whole feature in 21 lines of English, and the key ones are worth reading verbatim, straight quotes and all.

The dialog title, with the app’s name in front: “Would Like to Know Your Age Range”. The buttons: “Share Age Range” and “Don’t Share”. For adults, the option to share that you are “at least 18 years old so your experience in this app isn’t limited to child or teen settings”. For children, a line explaining that “your parent or guardian will need to help you set up Age Range for Apps”.

And then the honest one, the line that tells you Apple thought about the leak: “Sharing your age range again may allow this app to determine your age and birth year more precisely.” Ask often enough with different thresholds and an app can bisect your birthday. The dialog says so, in the small print, and it is right.

On the Mac, familycircled is the process behind all of it. It registers a service named com.apple.family.ageRange.xpc, and its log reports the current user’s age category on every roster pass, followed by a member type code. The birthday itself lives elsewhere, behind the Apple Account. What the daemon hands out, after you press the button, is the band.

The cache you cannot open

People find this one themselves, which is why familycircle cache shows up in search suggestions. The folder is ~/Library/Caches/familycircled, and if you point a disk usage command at it you get the privacy wall:

$ du -sh ~/Library/Caches 2>&1 | head -2
du: /Users/you/Library/Caches/familycircled: Operation not permitted
du: /Users/you/Library/Caches/CloudKit: Operation not permitted

Operation not permitted, rather than permission denied, is the tell for macOS privacy protection rather than Unix file modes, the same wall that hides the CloudKit caches from the System Data ledger. The contents are still measurable through the daemon’s own open file table: a 49,152 byte Cache.db with a 32,768 byte shared memory sidecar, plus a second small store under ~/Library/HTTPStorages for anything fetched over the network. Nothing in there is worth the fight to read. It is a roster cache, and the roster it caches is your own family.

The family it travels with

familycircled is one of four family agents launchd keeps on tap, and the other three round out the picture:

On the measured Mac only familycircled was running at rest, which fits: the others are launch on demand, woken when an app or a notification needs them, while the roster daemon idles along at the login window and in every user session.

Its open file table also names three account service bundles it consults: the Apple Account owner, the media store owner, and the IDS messaging owner. That is the daemon checking which services the family’s shared entitlements, purchases and subscriptions, actually ride on.

What it costs

About a second and a half of processor time a day and 10 MB of memory, which puts it near the bottom of the whole ledger of daemons this site has measured, just above the cable daemon and just below the phone call daemon. It has no high CPU search rows at all, and the measurements explain why: it cannot burn power thinking about your family, only talking to them, and the talks are short.

If you are not in a family group, the daemon still runs, because the Mac ships ready for one and the login window session needs a broker on tap. It will simply have almost nothing to say. The way to shrink it is not Activity Monitor, it is the Family pane in System Settings: leave the group, or turn off the features, and familycircled’s day gets even quieter than it already is.

Questions

What is familycircled on my Mac?

It is the daemon inside Apple's FamilyCircle framework, the private framework Family Sharing is built on. Its job is the roster: who is in your family group, who has been invited, and what each member is allowed to do, which is the machinery under Family Sharing features like purchase sharing, Ask to Buy and Screen Time for children. It runs as your own user, out of a system framework folder, launched by launchd, and it also runs at the login window before anyone has signed in. It has no icon, no settings pane and no manual page, and Apple's own Family Sharing pages never name it, which is why the bare process name reads like malware to anyone who finds it in Activity Monitor.

Why did an app ask for my age range, and what does familycircled have to do with it?

That popup is the Age Range for Apps feature, and on the Mac this daemon is the broker. An app can ask whether you are over a threshold, say 18, without learning your birthday, and the dialog offers Share Age Range and Don't Share buttons. The strings for that dialog live inside the FamilyCircle framework itself, in 44 languages, including a line for child accounts that says a parent or guardian will need to help set the feature up. The daemon registers a service whose name is literally com.apple.family.ageRange.xpc, and its log reports your current age category on every roster refresh. Your exact birthday never reaches the app, and the framework's own wording warns that sharing your range again with the same app may let it narrow your age down.

What is the familycircled folder in my Library caches?

It is a small SQLite cache, two files, Cache.db and its shared memory sidecar, 49,152 bytes and 32,768 bytes on the measured Mac, holding the last known state of your family group so Settings does not have to fetch the roster from scratch. You cannot read it. The folder sits behind the privacy wall, and an ordinary du reports Operation not permitted, the same wall the CloudKit caches sit behind. Its size is still knowable the honest way, through the daemon's own open file table, which is how every number on this page was measured. Deleting the folder buys nothing: the daemon rebuilds it, and macOS will not let most tools touch it anyway.

Why is familycircled running, and should I worry about CPU?

It runs because you are in a family group, or because the Mac ships ready for one, and it costs almost nothing to keep alive. On the measured Mac it had used 6.4 seconds of processor time across four days of running, about a second and a half a day, on under 10 MB of memory, with 9 launches on the clock. Its configuration wakes it for four named background jobs, a daily cache refresh that only runs on external power, a heartbeat roughly once every 25 hours, a job that reacts when the legal jurisdiction over a family member changes, and one that runs once after a system update. It also wakes whenever your contacts change, because family members are contacts. A familycircled column that climbs means network trouble or a failing sync, not surveillance.

Why do I see more than one familycircled in Activity Monitor?

Almost always because Xcode simulators are booted. Every iOS simulator runtime ships its own copy of the daemon, and a booted simulator starts it the way a real iPhone would. On the measured Mac two extra copies were alive, one from an iOS 27.0 runtime and one from 27.1, alongside the Mac's own, a pattern this series has also caught on the Siri and dictation daemon and the remote widget daemon. It is also why the search suggestions for the bare name lean iPhone: developers meet this process on the phone side of the fence first. Quit the simulator and the extras go with it.

Can I quit or disable familycircled?

There is nothing to configure and nothing to quit with a purpose. The binary takes no options, it has no manual page, and it is woken by events rather than kept alive, so force quitting it buys seconds of quiet before the next contact change or scheduled job brings it right back. Its exit reason on the measured Mac was the system's own idle reclaim, which is the normal way it goes away. The real levers are the features: leave the family group in System Settings under Family, or turn off the specific features like Ask to Buy and Screen Time, and the daemon has progressively less to do. At a second and a half of CPU a day, most people should let it be.

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