Screen Time (RMAdminStore) on iOS
iOS Screen Time in RMAdminStore-Local.sqlite and RMAdminStore-Cloud.sqlite: hourly app and web usage, pickups, devices and family members.
- Location
- /private/var/mobile/Library/Application Support/com.apple.remotemanagementd/RMAdminStore-Local.sqlite and RMAdminStore-Cloud.sqlite
- Evidence area
- Proves
- How long each app, web domain and category was used per hour, how often the device was picked up, and which device and user of the Screen Time account the usage belongs to
- Timestamps
- Cocoa time in seconds (ZUSAGEBLOCK.ZSTARTDATE and related), UTC; usage is bucketed per hour
- Acquisition
- Full file system extraction from an AFU device; not in iTunes / Finder backups
- Retention
- Screen Time shows the user about four weeks of history; the databases often hold a similar window. Measure the oldest usage block
- Collection
- Full file system extraction
Tools
Compare all toolsWhat it is
Screen Time is the iOS feature that reports how much the device was used and sets limits for the owner or for children in a Family Sharing group. Its data is kept by remotemanagementd in two Core Data SQLite stores named RMAdminStore:
RMAdminStore-Local.sqlite: usage recorded on this device.RMAdminStore-Cloud.sqlite: usage synced through iCloud when Share Across Devices is enabled, which can include the owner's other devices and, for a parent, the devices of children in the family group.
For an investigator it gives an hourly summary that is easy to explain in court: minutes per app and per website, and the number of pickups, per device and per user. It is coarser than Biome or knowledgeC.db, but it survives in cases where those streams have already been pruned or are sparse.
Where it lives
| Source | Path | Notes |
|---|---|---|
| Full file system | /private/var/mobile/Library/Application Support/com.apple.remotemanagementd/RMAdminStore-Local.sqlite (+ -wal, -shm) | This device's usage |
| Full file system | .../com.apple.remotemanagementd/RMAdminStore-Cloud.sqlite (+ -wal, -shm) | Usage synced across the account and family |
Neither file is in iTunes or Finder backups. The Screen Time passcode, if set, is not stored in these databases.
What it proves
- Minutes of use per app bundle ID and per web domain, per hour.
- Usage per category (Social Networking, Games, Productivity...), using Apple's category identifiers.
- Number of pickups, including pickups with no app usage.
- Which device (
ZCOREDEVICE: name, identifier, platform) and which user (ZCOREUSER: given name, family name, Apple Account, DSID, family member type) the usage belongs to. - Screen Time limits and restrictions configured, where present in the store.
It proves that the device was used for an app during an hour, not the exact minutes or who held it.
Key fields
Tables and columns below follow APOLLO's Screen Time modules; verify them on your build.
| Table / column | Meaning |
|---|---|
ZUSAGEBLOCK.ZSTARTDATE | Start of the hourly block |
ZUSAGEBLOCK.ZNUMBEROFPICKUPSWITHOUTAPPLICATIONUSAGE | Pickups with no app use |
ZUSAGECATEGORY.ZIDENTIFIER | Category code, e.g. DH1002 Social Networking, DH1001 Games |
ZUSAGETIMEDITEM.ZBUNDLEIDENTIFIER, ZDOMAIN | App bundle ID or web domain |
ZUSAGETIMEDITEM.ZTOTALTIMEINSECONDS | Seconds used in that block |
ZUSAGECOUNTEDITEM | Counted events (pickups, notifications) per bundle |
ZCOREDEVICE.ZNAME, ZIDENTIFIER, ZPLATFORM | Device the usage belongs to |
ZCOREUSER.ZGIVENNAME, ZFAMILYNAME, ZAPPLEID, ZDSID | User of the Screen Time account |
The chain is ZUSAGETIMEDITEM to ZUSAGECATEGORY to ZUSAGEBLOCK to ZUSAGE, which points to the user and the device.
Timestamps
Dates are Cocoa time in seconds, UTC, and usage is bucketed per hour.
SELECT datetime(b.ZSTARTDATE + 978307200, 'unixepoch') AS hour_utc,
t.ZBUNDLEIDENTIFIER, t.ZDOMAIN, c.ZIDENTIFIER AS category,
t.ZTOTALTIMEINSECONDS / 60.0 AS minutes,
d.ZNAME AS device, u.ZAPPLEID AS apple_account
FROM ZUSAGETIMEDITEM t
LEFT JOIN ZUSAGECATEGORY c ON c.Z_PK = t.ZCATEGORY
LEFT JOIN ZUSAGEBLOCK b ON b.Z_PK = c.ZBLOCK
LEFT JOIN ZUSAGE g ON g.Z_PK = b.ZUSAGE
LEFT JOIN ZCOREUSER u ON u.Z_PK = g.ZUSER
LEFT JOIN ZCOREDEVICE d ON d.Z_PK = g.ZDEVICE
ORDER BY b.ZSTARTDATE;
Hour boundaries follow UTC in the database. When you present a daily chart, convert to the device's local time zone and say which one you used.
Retention
The Screen Time interface shows the current and previous weeks, and the databases usually hold a comparable window of about four weeks. Turning Screen Time off, or turning off Share Across Devices, changes what is recorded and synced. Report the first and last block present, per device.
Collection
- Acquire a full file system from an AFU device and export both RMAdminStore databases with their WAL and SHM files.
- Record whether Share Across Devices and Family Sharing were in use (visible in the cloud store's device and user tables).
- If the owner's Mac is available, its own Screen Time store can hold the same synced data.
Parsing
- APOLLO provides
screentime_timed_items,screentime_counted_items,screentime_by_hourandscreentime_by_categorymodules for both stores. - Commercial suites parse Screen Time as a usage report.
sqlite3with the query above.
Investigator tips
- Always split results by
ZCOREDEVICE. Rows in the cloud store may describe an iPad, a Mac or a child's phone, not the examined iPhone. - Screen Time totals and Biome
App.InFocusintervals should broadly agree for the same hour. A large disagreement is a reason to check time zones and device attribution before anything else. - Web domains in
ZDOMAINcomplement Safari History.db. Which browsers and web views report domains varies, so test on a reference device before drawing conclusions from a missing domain. - The Apple Account in
ZCOREUSERlinks usage to an identity; compare it with Accounts3.sqlite.