Blog/Privacy

Why storing files in your own iCloud matters

When you save a file in an app, it goes somewhere. Where it goes is the most important privacy decision most people never think about.

There are two models for where your saved files end up, and the difference matters more than any feature list.

EZ Save home screen with private folders for ID, medical, insurance, bank letters and taxes
Everything here lives in your own iCloud, not on our servers.

Two models for storing your data

In the first model, the app sends your files to the company's own servers — their database, their cloud account. You are trusting that company's security, staff and policies with your data, indefinitely. In the second model, the app stores your files in your own cloud account — on iOS, Apple's iCloud — and the developer never holds a copy.

What “your own iCloud” actually means

On iPhone, apps can use Apple's CloudKit private database. That is a private store scoped to your Apple ID, sitting alongside your other iCloud data. The app reads and writes there on your behalf, but the developer has no server in the middle holding your content. It is your account, your storage, your control.

No server means no breach surface

You cannot leak a database you do not have. When a company stores millions of users' files on its servers, those servers become a target — one mistake exposes everyone. An app that keeps each person's data in their own iCloud has nothing central to breach. There is no pooled honeypot of user files.

Frequently asked questions

What does "stored in your own iCloud" mean?
The app saves your data in a private database inside your Apple account, using Apple's CloudKit, rather than on servers run by the app's developer.
Can the developer see my files?
In EZ Save's case, no. Content sits in your own iCloud and is encrypted on your device before it syncs, and Digital Sauce runs no servers for your content.
What happens if I run out of iCloud storage?
Syncing pauses until you free up space or upgrade your iCloud plan. Your saves on the device stay where they are.
Are there downsides to using my own iCloud?
Yes. It needs an Apple account for sync, it uses your iCloud storage, and it rules out a web app or shared team libraries.

Storage that stays in your account

EZ Save keeps your entire library in your own iCloud, Apple's private CloudKit database, with no developer server in the middle.

The honest trade-offs

This model is not magic. It relies on your Apple account, so it is the iPhone and iPad story — the Android version of EZ Save syncs through your Google account instead. And because it is tied to your account, keep your Apple ID secure and your recovery options current. For most people, those are easy trades for genuinely private storage.

How EZ Save uses it

EZ Save stores your library in your own iCloud (Apple's CloudKit private database), tied to your Apple account. There is no EZ Save server holding your files — which is exactly why we can say we never see your data. See how it works →