Significant Locations: iOS routined Databases
iOS Significant Locations in routined Local.sqlite, Cloud-V2.sqlite and Cache.sqlite: what visits and raw fixes prove, and why a full file system is needed.
- Location
- /private/var/mobile/Library/Caches/com.apple.routined/ (Local.sqlite, Cloud-V2.sqlite, Cache.sqlite)
- Evidence area
- Proves
- Places the device learned and visited, with entry and exit times and a confidence and uncertainty per visit, plus short-lived raw location fixes
- Timestamps
- Cocoa time in seconds (add 978307200 for Unix time), UTC
- Acquisition
- Full file system extraction from an AFU device; not included in iTunes / Finder backups
- Retention
- Raw fixes in Cache.sqlite: days. Learned visits in Local.sqlite: weeks to months, until iOS ages them out or the user clears Significant Locations
- Collection
- Full file system extraction
Tools
Compare all toolsWhat it is
Significant Locations is the iOS feature that learns places its owner visits often (home, work, a gym) so that Maps, Calendar and suggestions can predict travel. The data is maintained by the routined daemon in a set of Core Data SQLite databases. In the settings it sits under Privacy & Security, Location Services, System Services, Significant Locations, where the user can view it (after authentication) and clear it.
For an investigator, routined is often the best on-device record of movement: it keeps visits (arrival, departure, place, confidence) for weeks, and raw location fixes for a few days. It is also one of the most misread artifacts, because every value carries an uncertainty.
Where it lives
All paths below are under /private/var/mobile/Library/Caches/com.apple.routined/:
| Database | Content | Notes |
|---|---|---|
Local.sqlite | Learned locations of interest and visits on this device | Core evidence for visits |
Cloud-V2.sqlite | Learned places and visits mirrored with the owner's other devices through iCloud | Can contain other devices' data |
Cache.sqlite | Recent raw location fixes (ZRTCLLOCATIONMO) | Very short retention |
Each database comes with -wal and -shm files. The folder is a cache directory, excluded from iTunes and Finder backups, and the files are protected by data protection keys that are only available after the first unlock. Plan for a full file system extraction of a device in AFU state. Older location stores such as cache_encryptedB.db under /private/var/root/Library/Caches/locationd/ may also exist; their content and presence vary by version.
What it proves
- That the device's location services associated it with a place during a time window, with a stated confidence.
- The sequence of places across days, and how often a place was visited.
- For recent days, individual fixes with accuracy, speed and course.
It does not prove that the owner was there (the phone can travel without its owner), and it does not give precise addresses. Coordinates are estimates with a radius. Never present a visit as a pinpoint.
Key fields
Table and column names below are those most often documented for recent releases; confirm them with .tables and .schema on your copy.
| Table | Useful columns |
|---|---|
ZRTLEARNEDLOCATIONOFINTERESTMO (Local) | ZLOCATIONLATITUDE, ZLOCATIONLONGITUDE, ZLOCATIONUNCERTAINTY, place type and naming fields |
ZRTLEARNEDLOCATIONOFINTERESTVISITMO (Local) | ZENTRYDATE, ZEXITDATE, ZCONFIDENCE, ZLOCATIONLATITUDE, ZLOCATIONLONGITUDE, ZLOCATIONUNCERTAINTY, ZLOCATIONOFINTEREST |
ZRTLEARNEDLOCATIONOFINTERESTTRANSITIONMO (Local) | Transitions between places, with start and stop dates |
ZRTCLLOCATIONMO (Cache) | ZTIMESTAMP, ZLATITUDE, ZLONGITUDE, ZHORIZONTALACCURACY, ZALTITUDE, ZSPEED, ZCOURSE |
In Cloud-V2.sqlite, look for a device table and device identifiers on visit rows, so you can separate the examined iPhone from the owner's other devices.
Timestamps
Dates are Cocoa time in seconds, UTC.
-- Local.sqlite: visits with duration and uncertainty
SELECT v.Z_PK,
datetime(v.ZENTRYDATE + 978307200, 'unixepoch') AS entry_utc,
datetime(v.ZEXITDATE + 978307200, 'unixepoch') AS exit_utc,
ROUND((v.ZEXITDATE - v.ZENTRYDATE) / 60.0) AS minutes,
v.ZLOCATIONLATITUDE AS lat, v.ZLOCATIONLONGITUDE AS lon,
v.ZLOCATIONUNCERTAINTY AS radius_m, v.ZCONFIDENCE
FROM ZRTLEARNEDLOCATIONOFINTERESTVISITMO v
ORDER BY v.ZENTRYDATE;
-- Cache.sqlite: raw fixes
SELECT datetime(ZTIMESTAMP + 978307200, 'unixepoch') AS fix_utc,
ZLATITUDE, ZLONGITUDE, ZHORIZONTALACCURACY, ZSPEED
FROM ZRTCLLOCATIONMO ORDER BY ZTIMESTAMP;
Retention
Raw fixes in Cache.sqlite are kept for days. Learned visits in Local.sqlite last longer, typically weeks to a few months, before routined ages them out. The user can clear the whole history in Settings, and turning Significant Locations off stops collection. Report the oldest and newest entries you found in each database, and whether the feature was enabled.
Collection
- Acquire a full file system from an AFU device, as soon as possible: raw fixes disappear within days.
- Export the whole
com.apple.routinedfolder with its WAL and SHM files and keep the folder structure. - Isolate the device from networks during handling. New visits and iCloud syncing continue as long as the phone runs and has a signal.
Parsing
- iLEAPP has routined modules for visits, learned places and cached locations, with map output.
- APOLLO includes routined modules for its pattern-of-life timeline.
sqlite3or DB Browser for SQLite with the queries above.
Investigator tips
- Report visits with their uncertainty radius and confidence. A 200 m radius in a dense city covers dozens of addresses.
- Correlate with GPS in Photos.sqlite, Wi-Fi joins and cell data. Independent sources that agree are what make location evidence persuasive.
- Check
Cloud-V2.sqlitedevice identifiers before attributing a visit to the examined iPhone. - Put visits next to device use from KnowledgeC and Biome: an unlocked phone in active use at a location is stronger than a phone that stayed locked all evening.
- An empty
Local.sqlitemay mean the feature was off or recently cleared. Look for the setting and for WAL remnants before drawing conclusions.