Device & systemSecurity & malware
TCC.db: iOS Privacy Permissions per App
iOS TCC.db records which apps were granted or denied camera, microphone, photos, contacts and other privacy permissions, and when. Paths, values, epochs.
- Location
- /private/var/mobile/Library/TCC/TCC.db (backup: HomeDomain, Library/TCC/TCC.db, fileID 64d0019cb3d46bfc8cce545a8ba54b93e7ea9347)
- Evidence area
- Proves
- Which apps asked for, were granted, limited or denied access to protected resources (camera, microphone, photos, contacts, calendars, Bluetooth, motion...), and when that decision last changed
- Timestamps
- Unix time in seconds (access.last_modified), UTC
- Acquisition
- Reaches an iTunes / Finder backup (HomeDomain); a full file system extraction adds the -wal file. Location permissions are elsewhere (locationd clients.plist)
- Retention
- One row per app and service, kept while the app is installed; rows are updated in place, so only the latest decision is kept
- Collection
- idevicebackup2, iMazing, Full file system extraction
Tools
Compare all toolsWhat it is
TCC (Transparency, Consent and Control) is the Apple subsystem that asks "Allow this app to access your photos?" and remembers the answer. On iOS, those answers are stored in TCC.db, a SQLite database with one row per app and protected service. It is the first place to check when the question is "could this app use the microphone?" or "when did the user grant it access to contacts?".
Location Services are handled separately by locationd, not by TCC. For location permissions, see locationd caches and clients.plist.
Where it lives
| Source | Path | Notes |
|---|---|---|
| Full file system | /private/var/mobile/Library/TCC/TCC.db (+ -wal, -shm) | Main database |
| iTunes / Finder backup | HomeDomain, Library/TCC/TCC.db | Stored as 64/64d0019cb3d46bfc8cce545a8ba54b93e7ea9347 |
| sysdiagnose | logs/Accessibility/TCC.db | A copy is included in sysdiagnose archives on many builds |
What it proves
- That an app (by bundle ID) requested access to a protected service.
- The current decision: denied, allowed, or limited (Photos limited library).
- Why the decision was made (user consent, system policy, MDM policy...).
- When the row was last modified, which usually corresponds to the user's last change of that permission.
It does not prove that the app actually used the camera or microphone. For use, look at pattern-of-life sources such as PowerLog camera tables and Biome.
Key fields
Column (access table) | Meaning |
|---|---|
service | Protected resource, e.g. kTCCServiceCamera, kTCCServiceMicrophone, kTCCServicePhotos, kTCCServiceAddressBook, kTCCServiceCalendar, kTCCServiceBluetoothAlways, kTCCServiceMotion |
client | Bundle ID (or path) of the app |
client_type | 0 = bundle ID, 1 = absolute path |
auth_value | 0 = denied, 1 = unknown, 2 = allowed, 3 = limited |
auth_reason | 2 = user consent, 3 = user set, 4 = system set, 5 = service policy, 6 = MDM policy... |
last_modified | Time of the last change |
prompt_count | Number of times the prompt was shown (where present) |
Older schemas used an allowed column (0 or 1) instead of auth_value. The value mappings above are those used by MVT; confirm with .schema access.
Timestamps
last_modified is Unix time in seconds (not Cocoa time), UTC.
SELECT service, client, client_type, auth_value, auth_reason,
datetime(last_modified, 'unixepoch') AS last_modified_utc
FROM access
ORDER BY last_modified;
Retention
TCC keeps one row per app and service, updated in place. Toggling a permission overwrites the previous state, and uninstalling an app removes its rows. Earlier states may survive only in the WAL, freelist pages, or older backups. Reset Location & Privacy in Settings clears all decisions.
Collection
- A standard backup includes
TCC.db; resolve it through Manifest.db. - A full file system adds the WAL. A sysdiagnose adds a snapshot you can compare with the live database to spot changes.
- Collect installed apps data at the same time to put bundle IDs in context.
Parsing
- MVT extracts TCC entries (backup and file system modes) with readable values and flags apps listed in indicator files.
- iLEAPP reads the live database and the sysdiagnose copy; APOLLO has a
tcc_dbmodule. sqlite3with the query above.
Investigator tips
- Review camera and microphone grants for apps the owner does not recognise, and grants whose
last_modifiedfalls in a period of interest (for example, right after a device was handed to someone else). - An
auth_reasonof MDM policy means the decision was pushed by a management profile: check configuration profiles. - System daemons do not need TCC entries to access some resources, so a clean TCC.db does not exclude compromise. See the spyware triage guide.
- For stalkerware questions, combine TCC grants with the app list, profiles and Accounts3.sqlite, as described in the device and accounts guide.