CallHistory.storedata: iOS Call Log Database
The iOS call log: phone, FaceTime and CallKit app calls in CallHistory.storedata, why it needs an encrypted backup, and how to read ZCALLRECORD.
- Location
- /private/var/mobile/Library/CallHistoryDB/CallHistory.storedata (backup: HomeDomain, Library/CallHistoryDB/CallHistory.storedata, fileID 5a4935c78a5255723f707230a451d79c540d2741)
- Evidence area
- Proves
- Incoming, outgoing and missed calls over the phone network, FaceTime and CallKit apps (such as WhatsApp), with the other party, time, duration and answer state
- Timestamps
- Cocoa time in seconds (add 978307200 for Unix time), UTC; ZDURATION in seconds
- Acquisition
- Encrypted backup (Apple lists call history among data only encrypted backups include) or full file system extraction
- Retention
- Until deleted in the Phone app or pruned by iOS; the database can hold more rows than the Recents list shows, and deleted rows may survive in freelist pages
- Collection
- idevicebackup2 (encrypted), iMazing, Full file system extraction
Tools
Compare all toolsWhat it is
CallHistory.storedata is the Core Data SQLite store behind the Recents tab of the Phone app. Every call the device places or receives through the cellular network, FaceTime Audio, FaceTime Video, and third-party apps that integrate with Apple's CallKit framework (WhatsApp, Signal, Telegram and others, when they are allowed to show calls in Recents) becomes a row in ZCALLRECORD.
Because it is a Core Data store, tables and columns carry the Z prefix and primary keys are Z_PK. Old iOS versions used call_history.db; every release this site covers uses CallHistory.storedata.
Where it lives
| Source | Path | Notes |
|---|---|---|
| Full file system | /private/var/mobile/Library/CallHistoryDB/CallHistory.storedata (+ -wal, -shm) | Core Data store, WAL mode |
| iTunes / Finder backup | HomeDomain, Library/CallHistoryDB/CallHistory.storedata | Stored as 5a/5a4935c78a5255723f707230a451d79c540d2741 |
Apple's documentation on encrypted backups lists call history among the data that only encrypted backups contain. In practice: take the backup with a password you set (and record), or expect the file to be missing. See Manifest.db and Manifest.plist for how to confirm what a backup holds.
What it proves
- The other party of a call (
ZADDRESS), the direction (ZORIGINATED) and whether it was answered (ZANSWERED). - When the call started and how long it lasted.
- Which service carried it: cellular telephony, FaceTime, or a named CallKit app.
- Sometimes a location hint (
ZLOCATION, such as a region inferred from the number) and a country code.
It does not prove what was said, nor who held the phone. With the same Apple Account on several devices, FaceTime and "Calls on Other Devices" can place a call from a Mac or iPad that later appears on the iPhone: check the service and correlate with the other devices.
Key fields
Main table ZCALLRECORD:
| Column | Meaning |
|---|---|
ZADDRESS | Other party: phone number, email or app-specific handle (stored as text or blob depending on the build) |
ZNAME | Name cached at call time, when available |
ZDATE | Call start |
ZDURATION | Duration in seconds (fractional) |
ZORIGINATED | 1 = outgoing, 0 = incoming |
ZANSWERED | 1 = answered; incoming + 0 = missed or declined |
ZCALLTYPE | Call type (telephony, FaceTime audio, FaceTime video, etc.) |
ZSERVICE_PROVIDER | com.apple.Telephony, com.apple.FaceTime, or a third-party bundle ID |
ZDISCONNECTED_CAUSE | Why the call ended, where recorded |
ZLOCATION, ZISO_COUNTRY_CODE | Location label and country derived from the number |
ZREAD | Whether a missed call was seen |
ZCALLTYPE values are not documented by Apple. Validate them on a test device running the same iOS version before putting them in a report; ZSERVICE_PROVIDER is the more reliable way to tell a WhatsApp call from a cellular one.
Timestamps
ZDATE is Cocoa time in seconds since 2001-01-01 00:00:00 UTC. The call ends at ZDATE + ZDURATION.
SELECT Z_PK,
datetime(ZDATE + 978307200, 'unixepoch') AS start_utc,
datetime(ZDATE + ZDURATION + 978307200, 'unixepoch') AS end_utc,
ROUND(ZDURATION) AS seconds,
CASE ZORIGINATED WHEN 1 THEN 'out' ELSE 'in' END AS direction,
ZANSWERED, ZSERVICE_PROVIDER, ZADDRESS, ZNAME
FROM ZCALLRECORD
ORDER BY ZDATE;
If ZADDRESS comes back as a blob, CAST(ZADDRESS AS TEXT) usually yields the number.
Retention
The Recents list in the Phone app is not a reliable measure of what the database holds: iOS can keep more rows than it shows, and pruning behaviour is not documented. Rows deleted by the user leave the table but can survive in SQLite freelist pages and the WAL. Measure the oldest ZDATE on the evidence and report it as the effective window, rather than quoting a fixed limit.
Collection
- Encrypted backup: enable backup encryption with a password you control, then back up (for example
idevicebackup2 encryption on <password>followed byidevicebackup2 backup --full). Turning encryption on is a change to the device's settings: record it in your notes. Decrypt with the password you set using iphone_backup_decrypt, MVT (mvt-ios decrypt-backup) or a commercial suite. - Full file system: collect the store with its
-waland-shmfiles. - If the backup password is already set and unknown, see the acquisition guide for the lawful options and their side effects.
Parsing
- iLEAPP has a call history module for backups and full file system extractions.
- DB Browser for SQLite or
sqlite3with the query above for a quick, verifiable table. - Commercial suites (Magnet AXIOM, Cellebrite) decode call types, but check their mapping against your own test data.
Investigator tips
- Normalise
ZADDRESSto E.164 and join it with AddressBook and thehandletable of sms.db to build a per-contact view across calls and messages. - A missed call is
ZORIGINATED = 0 AND ZANSWERED = 0; a zero-second outgoing call is an attempt, not a conversation. - CallKit rows only exist when the app integrates with CallKit and the user left "Show in Recents" enabled. Absence of WhatsApp calls here is not absence of WhatsApp calls: check the app's own database.
- Pair calls with KnowledgeC and Biome screen state and app focus to test whether the owner was actively using the phone at call time.