interactionC.db: iOS Contact Interactions
iOS interactionC.db records who the owner messaged, called or shared with, across Apple and third-party apps. Paths, tables, epochs and pitfalls.
- Location
- /private/var/mobile/Library/CoreDuet/People/interactionC.db (backup: HomeDomain, Library/CoreDuet/People/interactionC.db, fileID 1f5a521220a3ad80ebfdc196978df8e7a2e49dee)
- Proves
- That the owner interacted with a contact (message, call, share, mail) through a given app and direction at a given time, including apps whose own databases are encrypted or deleted
- Timestamps
- Cocoa time in seconds (ZSTARTDATE, ZENDDATE, ZCREATIONDATE and contact first/last dates), UTC
- Acquisition
- Reaches an iTunes / Finder backup (HomeDomain); a full file system extraction adds the -wal file and freelist pages
- Retention
- Weeks to a few months of interactions are commonly observed; pruning is internal to CoreDuet. Measure on the evidence
- Collection
- idevicebackup2, iMazing, Full file system extraction
Tools
Compare all toolsWhat it is
interactionC.db is a CoreDuet database that records interactions between the device owner and other people: a message sent, a call placed, a photo shared through the share sheet, an email. iOS uses it to rank share sheet suggestions and Siri contact predictions. Apps donate these interactions to the system through Apple's intents frameworks, which is why the database contains events from Messages, Phone and Mail as well as from third-party apps such as WhatsApp.
Its forensic value is that it sits outside each app's own storage. When a messenger's database is encrypted, wiped or deleted with the app, interactionC.db can still show that a conversation with a given person happened, in which direction and when, and sometimes with a snippet of content.
Where it lives
| Source | Path | Notes |
|---|---|---|
| Full file system | /private/var/mobile/Library/CoreDuet/People/interactionC.db (+ -wal, -shm) | Next to knowledgeC's Knowledge folder |
| iTunes / Finder backup | HomeDomain, Library/CoreDuet/People/interactionC.db | Stored as 1f/1f5a521220a3ad80ebfdc196978df8e7a2e49dee |
The database is documented for iOS 14 to 18. Its presence and schema on iOS 26 have not been confirmed publicly at the time of writing: check your extraction before relying on it.
What it proves
- An interaction between the owner and one or more contacts, with the donating app (
ZBUNDLEID), direction (incoming or outgoing) and mechanism. - Contact handles (phone numbers, email addresses, app-specific identifiers) and display names as known to the donating app.
- For some interactions, attachment metadata or text content (
ZATTACHMENT.ZCONTENTTEXT,ZUTI,ZCONTENTURL). - Per-contact first and last incoming and outgoing dates and counts, useful for summarising a relationship.
It does not contain full conversations. What is donated depends on the app and its version: absence of an interaction does not prove absence of contact.
Key fields
| Table / column | Meaning |
|---|---|
ZINTERACTIONS.ZSTARTDATE, ZENDDATE, ZCREATIONDATE | Interaction time window and record creation |
ZINTERACTIONS.ZBUNDLEID, ZTARGETBUNDLEID | Donating app and target (e.g. share extension) |
ZINTERACTIONS.ZDIRECTION | 0 = incoming, 1 = outgoing (as used by APOLLO and MVT) |
ZINTERACTIONS.ZSENDER | Foreign key to ZCONTACTS |
ZINTERACTIONS.ZDOMAINIDENTIFIER, ZGROUPNAME | Conversation identifier and group name |
Z_1INTERACTIONS | Join table linking interactions to recipient contacts (the number can vary) |
ZCONTACTS.ZDISPLAYNAME, ZIDENTIFIER, ZPERSONID | Name, handle and Contacts identifier |
ZCONTACTS.ZFIRST*DATE, ZLAST*DATE, *COUNT | Relationship summary per contact |
ZATTACHMENT.ZCONTENTTEXT, ZUTI, ZCONTENTURL | Attachment or content details |
Core Data join tables are numbered (Z_1INTERACTIONS, Z_2...) and the numbers can change between versions. Confirm with .tables.
Timestamps
All dates are Cocoa time in seconds, UTC.
SELECT datetime(i.ZSTARTDATE + 978307200, 'unixepoch') AS start_utc,
i.ZBUNDLEID,
CASE i.ZDIRECTION WHEN 0 THEN 'incoming' WHEN 1 THEN 'outgoing' END AS direction,
s.ZDISPLAYNAME AS sender_name, s.ZIDENTIFIER AS sender_handle,
i.ZDOMAINIDENTIFIER, i.ZGROUPNAME, i.ZRECIPIENTCOUNT
FROM ZINTERACTIONS i
LEFT JOIN ZCONTACTS s ON i.ZSENDER = s.Z_PK
ORDER BY i.ZSTARTDATE;
ZCREATIONDATE normally trails ZSTARTDATE by milliseconds, so it adds little as a separate event.
Retention
Interactions are pruned by CoreDuet, not by the user. Weeks to a few months of history are typical, but it varies by release and activity. Deleting an app does not immediately delete its donated interactions, which is one reason this database is worth checking after an app was removed. Report the date range actually present.
Collection
- A standard backup is enough for the main database; resolve it through Manifest.db.
- A full file system extraction adds the WAL, where the most recent interactions often sit.
- Collect AddressBook at the same time to resolve
ZPERSONIDand handles to names.
Parsing
- APOLLO (
interaction_contact_interactions) is the reference query; MVT reuses it in itsInteractionCmodule and resolves WhatsApp identifiers against the WhatsApp contact data. - iLEAPP reports interaction contacts.
sqlite3with the query above, extended withZ_1INTERACTIONSfor recipients.
Investigator tips
- Messaging apps increasingly identify contacts by opaque IDs. WhatsApp, for example, can use LID identifiers that only map to a phone number through its own tables: resolve them with the WhatsApp data rather than guessing.
- Compare interactions for a messenger against that app's own database. An outgoing interaction with no matching message suggests deletion.
- For Signal and Telegram, whose databases are hard to reach, interactions may be the only readable trace, depending on what the app donates.
- Put interactions next to sms.db and KnowledgeC and Biome app focus to check the app was actually in use.