All articles · 5 min read

Is it better to store home data in my own iCloud than with a provider?

The difference is who can get to your data if something goes wrong — in your own iCloud the developer cannot read it, but on the other hand nobody else has a copy either.

The two models, briefly

Model A — the provider's server. You create an account with an email address and a password. Your home data sits in the provider's database alongside every other user's. You can log in from anywhere, and the provider can help you if something goes wrong. Most apps with "log in" work this way.

Model B — your own private cloud. The app uses the iCloud account you already have on your iPhone, and writes to the area that belongs to your own Apple ID. The developer creates no user account and has no access to the content. This is the model HouseSense uses.

You cannot say that one model is safe and the other unsafe. They have different weak points, and those are worth knowing before you choose.

What the provider's server costs you: someone can read along

When home data sits in a provider's database, there is, technically, always someone who can see it. It does not require ill intent — a support agent troubleshooting an issue can typically reach your account. That is often exactly what makes support possible in the first place.

The real risks with a provider's server are the mundane ones, not the dramatic ones:

• Data breaches. A combined database is an attractive target precisely because it is combined. A breach hits every user at once.
• Change of ownership. If the provider is bought, the database goes with it, and the terms can change.
• Shutdown. If the provider closes, you need to get your data out in time — if there is even an export button.
• Opacity. You cannot verify what is being stored, or for how long.

Home data is not harmless. A floor plan with window positions, the address, and a set of photos of the contents together make up a fairly detailed picture of a specific home.

What your own cloud costs you: nobody has a copy

If the app instead puts your homes in your own private cloud, data breaches, ownership changes, shutdowns and opacity disappear — but other weaknesses take their place, and they need to be stated just as plainly:

• No support desk can save you. Nobody can retrieve a deleted home, because nobody holds a copy. Delete it, and it is gone.
• Your Apple ID becomes the single point of failure. Lose access to your Apple ID and you lose access to everything stored under it — including the homes.
• You are tied to the platform. iCloud does not carry over to Android. Switch operating systems, and you need to have already exported what you want to keep.
• Your iCloud storage is your own. If it is full, syncing stops, and there is no provider storing it for you in the meantime.

These are honest costs. You do not get privacy for free — you trade one risk for another.

Why HouseSense stores data in your own iCloud

The reasoning behind HouseSense is that a home-scanning app has no need to know its users. The app's job is to measure rooms, draw plans and calculate areas. None of those tasks require the developer to know who you are or where you live. And once you have built a user database, you have also built something that can leak.

So: no account, no password, no email address, no tracking. The homes sit on your device and in your own private iCloud. There is no place at the developer's end where anyone could look up your address — not because a lock has been put on it, but because that place does not exist.

The one place where data does leave your private iCloud is sharing with a buyer, and that is deliberately narrow: a copy with no photos and no notes, which expires after 30 days, and which you can revoke yourself at any time.

How to cover the weak point of your own cloud

The one thing your own private cloud lacks is a copy held by someone else. You can make that copy yourself, and it will be better than the provider's, because you own it:

1. Turn on two-factor authentication for your Apple ID. When everything sits in your iCloud, your Apple ID is the key. It is the single most important protection.
2. Export the finished work as PDF. A floor plan and takeoff saved as PDF in Files or on a computer outlives the app, the phone, and the provider.
3. Export the 3D model if you need to use it elsewhere. HouseSense can write the model out in common formats other programs can read — so you are not locked into one app.
4. Check that iCloud backup is turned on on the device, so the local copy is covered too.

The questions that settle it for most people

If you are choosing between two home-scanning apps, three questions separate the two models faster than any privacy policy will:

• Do I need to create an account? If yes, your data sits somewhere the provider can read.
• Can I view the home in a browser without the app? If it is there on its own, without you having shared it, it lives on a server somewhere.
• Can I export everything into common file formats? If not, you are locked in, however nice the privacy policy sounds.

Short summary

Storing home data in your own private iCloud removes the provider as a possible reader and as a possible source of a leak — but leaves you solely responsible for your Apple ID, and for exporting what you want to keep. Storing it with a provider gives you support and recovery, but costs oversight of who can see your homes. HouseSense has chosen the first, and covers the weak point with export: your floor plan as a PDF is yours, whatever happens to everything else.