Key takeaways
- Ask about the feature you will use: where the recording, photo, or text is processed and where the result is stored.
- Local AI and synced storage can coexist. Check iCloud, exports, and connected services separately.
- Try a non-sensitive record, use the app offline after setup, and export the result before trusting it with a larger archive.
Follow one piece of data from input to result
An app can transcribe a recording or summarize an entry on the iPhone without sending that input to a remote model. It may still use iCloud, download models, verify purchases, or connect another service. To understand the claim, pick one feature you plan to use and check how it processes the input, stores the result, and handles a lost connection. This guide gives you seven practical checks.
Suppose you want to summarize a private recording. “On-device” is useful if it tells you where that recording is transcribed and where its words are summarized. It tells you less about whether the finished transcript syncs, what a support attachment includes, or where an export goes. Start with a piece of information you care about, then follow the steps you would actually use.
Which work can happen on the iPhone?
Apple’s Foundation Models framework gives developers access to an on-device language model for tasks such as summarization, entity extraction, text understanding, refinement, and structured output. Apple also provides local frameworks for speech, Vision OCR, image analysis, Natural Language processing, and other focused work. When an app uses those capabilities directly on supported hardware, the private input can remain inside the device boundary for that named task.
Local inference and local storage are different questions
An app can process a prompt locally and still store the result in a synced database. It can also store everything locally while sending one optional request to a remote service. Ask where the original input lives, where derived data lives, whether a device backup contains it, whether iCloud is optional, and whether deleting the app removes every copy. “The AI runs locally” answers only the inference question.
| Data path | What it can mean | What to verify |
|---|---|---|
| Local inference | The model processes the input on the iPhone, iPad, or Mac. | Which exact features use it, supported hardware, fallback behavior, and whether the input is ever uploaded. |
| Local storage | Records remain in the app sandbox or an App Group container. | Encryption, device backups, deletion, export, and whether extensions can read the same store. |
| Optional iCloud | Selected records may sync through the user’s Apple account. | Whether it is opt-in, which data types sync, whether media files are included, and what happens after disabling it. |
| Apple services | WeatherKit, HealthKit, StoreKit, or another system service may be used. | Permission scope, data sent to Apple, local caching, and whether the feature works when permission is denied. |
| Third-party service | A connected provider may supply bank data, collaboration, or another optional capability. | Provider name, authentication flow, fields shared, retention, disconnect behavior, and a non-connected alternative. |
| User-initiated export | You create a portable copy and choose a destination. | Format, included fields, excluded private history, and the security of the destination after export. |
Scroll horizontally to read the complete comparison on smaller screens.
Seven checks before moving your records in
- READ THE PRODUCT-SPECIFIC PRIVACY PAGE: Look for concrete nouns such as audio, transcript, entry, photo, location, and transaction, not only adjectives such as secure or private.
- CHECK THE APP STORE PRIVACY LABEL: Apple requires developers to disclose data collected by them and their partners, while noting that data processed only on the device is not considered collected.
- REVIEW PERMISSIONS IN CONTEXT: A microphone, photo, contacts, location, or Health permission should appear when its feature is used and explain why it is needed.
- TEST AIRPLANE MODE AFTER SETUP: Try the core workflow from input through result and export. Record which steps work and which clearly request a connection.
- LOOK FOR A FALLBACK: A responsible local-AI product explains what happens on unsupported hardware, when the model is unavailable, or when a permission is declined.
- EXPORT AND DELETE A TEST RECORD: Confirm that a useful format is available and that deletion behavior is understandable without contacting support.
- IDENTIFY EVERY OPTIONAL CONNECTION: Model downloads, StoreKit, WeatherKit, iCloud, Plaid, web links, and support can be legitimate while still needing disclosure.
Why we build around Apple devices
Apple provides the speech, image-recognition, and language tools that let us build focused workflows on the device. In Echo Chamber, for example, a recording can become a searchable transcript and useful notes without going to an Obsidian Ridge Labs AI server. That is a practical benefit for a conversation you need to revisit, particularly when it contains information you would not otherwise share with a software company.
The other choices still need to be made app by app. Some products use private iCloud storage; some offer optional connected services; some keep their current records local. Hardware requirements differ too. Our product pages describe those details alongside what the app helps you do, so you can judge the whole workflow.
Common questions about on-device AI
Before you choose
No. It means the named AI processing task runs locally. Downloads, purchase verification, optional iCloud, WeatherKit, connected providers, web links, and support can still use a network. Each connection should be documented separately.
Sources and further reading
Read the product documentation behind the comparison. Check the linked pages for current features and prices.