Why your personal CRM shouldn't be in the cloud

Think about what actually goes into a personal CRM. Not just names and birthdays — but the notes you'd never share publicly. Your friend's health struggles. The tension in someone's marriage. A family member's financial situation. Who's going through a hard time and why.

This is some of the most intimate data you generate. And most personal CRM apps store it on servers you don't control, often in the United States, often under terms of service that give the company significant rights to analyse and process your data.

That's worth thinking carefully about.

What cloud CRM companies have access to

When you store relationship notes in a cloud service, the company operating that service typically has technical access to your data — even if they claim not to look at it. Most privacy policies are written to permit a wide range of data processing: improving their models, debugging issues, complying with law enforcement requests, or sharing with "trusted partners."

This isn't necessarily malicious. But it means your friend's private struggles become part of a commercial data system. Even with good intentions on the company's part, you've lost the ability to guarantee confidentiality.

If you wouldn't write something in a public forum, you probably shouldn't store it on someone else's server without thinking about who else might read it.

The breach risk

Data breaches happen constantly. Major platforms with billions in security budgets get compromised regularly. A small personal CRM startup — often a team of two or three people — almost certainly has less robust security infrastructure than the attackers they'd face.

When a task manager or note-taking app gets breached, the damage is limited. When a personal CRM gets breached, what leaks is a detailed map of your social network: who you're close to, what's happening in their lives, what you think about them privately. That's a very different kind of exposure.

The sunset problem

Cloud services go away. Companies pivot, get acquired, run out of money, or simply shut down products that aren't growing fast enough. When that happens, your data may be deleted, become inaccessible, or end up in the hands of whoever acquired the company.

Relationships are long-lived. The notes you write about people today might be valuable to you in ten years. Storing them in a service that might not exist in three years is a genuine risk.

The case for local-first

The alternative is storing your relationship data on your own device, under your own control. No server, no company, no terms of service governing what can be done with your notes about your friends.

This is how Starlings works. Everything is stored locally in SwiftData on your iPhone. There is no Starlings server. There is no Starlings account. I — the developer — cannot see your data, cannot recover it, cannot be compelled to hand it over, and cannot lose it in a breach, because it doesn't exist anywhere except on your device.

If you want a backup, iCloud Sync is available. It's end-to-end encrypted by Apple, meaning even Apple can't read the contents. It's opt-in and off by default — you choose when and whether to enable it.

The trade-off is real but smaller than it seems

Local-first storage means your data doesn't sync automatically across all your devices, and there's no web interface you can access from a browser anywhere. For some use cases — business CRMs used across multiple workstations — that's a meaningful limitation.

For a personal relationship manager used primarily on your iPhone, the trade-off is minimal. Your phone is almost always with you. The relationships you're tracking are personal, not corporate. The value of the data staying private is high. The need for a web interface is low.

Choosing local-first for personal relationship data isn't paranoia. It's the same reasoning that leads most people to have private conversations in person rather than in a chat room: some things are just better kept close.