On-device vs cloud: where your data actually lives

Every app you use keeps your stuff somewhere. Your notes, your photos, the half-written message you never sent. Most of the time you never think about where. It just works, until the day it doesn't, and then the first question is where any of it actually lives.

That is the real question hiding under on-device vs cloud. Not which one sounds more private in a pitch, but where your data sits when you close the app: on the phone in your pocket, or on a computer in a building you will never see. I build small apps and I keep them on-device by default. So I have opinions here and I also know where that choice quietly costs you. This is the honest version, including the parts the marketing pages skip.

What on-device and cloud actually mean

On-device means the data lives on your phone or laptop. It is written to storage on the device and it stays there. Cloud means it is sent over the internet and stored on a server, a computer someone else owns and runs. Your device just holds a window onto it, and if the connection drops or the company goes under, that window can go dark.

Here is the bit that usually gets blurred. On-device describes where your data is kept, not everything an app ever does with it. An app can store your entries on your phone and still send a little text to a server for something specific, like turning speech into words or running an AI reflection. So on-device is more of a spectrum than a switch. When an app says on-device, the fair question is which part it means: the storage, the processing or both.

Why I keep things on-device

The plain reason is that data you never collect is data you can never lose, leak or be asked to hand over. If I don't run a server that holds your journal, there is no server to breach, no database to subpoena, no quiet policy change that turns your words into training data three years from now. The safest place for something personal is often the one nobody had to trust in the first place.

There is a selfish reason too. Servers are work. They cost money every month, they need looking after and the day one falls over is the day a hundred people can't open the app. Keeping data on the device means the app mostly just works, offline on a plane or on a train with no signal, because it isn't waiting on anything. For a one-person studio that isn't a philosophy so much as survival.

Where on-device genuinely wins

• Privacy by absence. Your data isn't sitting in a pile with a million other people's, waiting for the one breach that spills the lot.
• It works offline. No signal, no problem, because nothing has to travel to reach you.
• It is usually faster. Reading from the phone beats a round trip to a server and back.
• Nobody can change the deal later. There is no account to lock and no subscription that holds your history hostage the month you stop paying.

Where the cloud is honestly better

Now the part I would rather not put on a page that leans towards on-device apps. The cloud is genuinely better at some things, and pretending otherwise is how you end up with a smug app that loses people's data.

The big one is sync. If your notes live only on one phone, they live only on one phone. Open the app on a laptop and they aren't there. The cloud solves this without you thinking about it and on-device does not, at least not for free. Doing sync properly without a central server is a genuinely hard problem, and most small apps, mine included, start by simply not having it.

Then there is losing the device. If your entries sit on your phone and your phone goes in a river, they go with it, unless you backed them up. The cloud quietly handles that for you. On-device puts the backup back in your hands, which is more honest and also more effort. So a good on-device app has to make exporting and backing up easy, or it is just a nicer-looking way to lose everything.

And some jobs are simply too heavy for a phone. Big AI models, in particular, mostly run on servers because they have to. An app can keep your data on-device and still reach out to a server for the clever bit. That can be a fair trade, but it is worth knowing it is happening, rather than assuming on-device meant nothing ever left.

Strip away the branding and on-device vs cloud is one question: what leaves your device, and whether you got to choose.

How to tell where an app keeps your data

You can usually work it out in a couple of minutes, without reading a word of legalese.

• Turn on aeroplane mode and use the app. If everything you have saved still opens and works, a lot of it is on-device. If it goes blank, it lives on a server.
• Look for an export button and try it. An app that keeps your data on your device tends to make it easy to take with you. One that shrugs when you ask for your data is telling you who really holds it.
• Read the one paragraph in the privacy policy about where data is stored and skip the rest. You are looking for the words on-device, local, or the name of a cloud provider.
• Check whether there is an account you must create. If you have to sign in before you can write anything, your stuff is almost certainly on their server, tied to that login.

None of this makes on-device the right answer for everything. Sometimes you want your photos on every device you own and the cloud is the sane choice. But for the personal stuff, the journal, the notes, the things you would rather not have to explain to anyone, it is worth knowing where they sleep at night. Once you start checking, you notice how many apps would prefer you didn't ask.

Anyway, that is the trade as I see it from the building side. Flick on aeroplane mode and open your most personal app. Whatever happens next tells you most of what you need to know.

Benjamin

Founder & sole developer, Novaire Digital