Does “works offline” mean the same thing as “runs on your device”?

Two different designs share one label

The first design keeps a copy. The app downloads what you might need, or holds on to the changes you make, so the screen still fills when there is no signal. In a sync-dependent design, the account or authoritative copy may remain on a server; the exact split depends on the app. Offline is a fallback, and the connection is expected back.

In the on-device design, computation runs on the processor in your hand. In a strictly local, offline-only design, the feature does not depend on a server to do its core work. An app can still have separate network features, and long-term behavior depends on the software, operating system, and files it needs.

Offline availability does not settle whether data is sent

A sync-enabled offline app may upload or exchange queued changes when connectivity returns. What is sent, when, and to whom depends on the app and sync design.

This is why availability and privacy come apart. An app that keeps working in a basement or on a flight is well built, and that design may be the reason you can use it at all. It still tells you nothing about who eventually sees the contents. A delay is not a boundary.

The wording tells you which one you have

Product pages tend to be careful rather than dishonest, and the care is the tell. Read for the noun a claim attaches to, and for whether the sentence describes where the work happens or when the data travels. These phrases are reliable signals.

A single product page rarely picks one of these categories and stays there. It moves between them one clause at a time — a sentence about your account, a sentence about your download, a sentence about the model — and each clause can be accurate on its own while the overall shape stays unclear until you read for which noun each verb attaches to.

• “Saved to your account” usually indicates service storage. Cross-device continuity indicates data exchange, which may happen through a service or directly between devices. Check the actual path.
• “Download for offline use,” “available offline”: content caching. It describes what you can read without a signal, not what stays private.
• “No account needed,” “works without signing in”: a strong signal, because an app that never asks who you are has little to attach your data to. It is not proof on its own that nothing is sent.
• “Processed on your device,” “your request never leaves your phone”: a claim about computation and transmission. Check what it covers, since it can be true of one step, such as noticing the wake word, while the rest of the request still travels.
• “End-to-end encrypted”: the data does travel, and the operator says it cannot read it in transit. That is a real guarantee, and a different one from not sending it.

Running locally does not by itself mean nothing is sent

The two properties are independent, and an app can have one without the other. Local computation with the network still open is ordinary: the model runs on the phone while crash reports, analytics, a backup of your notes or a license check go out anyway. Where the computation happens and what the app transmits are separate questions, and both have to be answered.

So the useful question is narrower than the label. Ask what work is done on the device, then ask what leaves it, including what leaves it later. Turning the network off for a few minutes is a fast way to see which one an app actually is, though a quiet ten minutes doesn't prove a quiet year. An app that computes locally and opens no connection at all is the one case where offline and on-device describe the same thing: offline is about availability, on-device is about where the work happens, and neither one by itself says what left the device.