When you tell Callie your daughter has soccer practice every Tuesday, or that you're flying to Phoenix next month, that information belongs to your family: not to us.
That's not a marketing line. It's a technical commitment we've baked into how Callie works at the deepest level. This post explains what we've built, and more importantly, why. In plain language, no computer science degree required.
The problem with most apps
Most family apps store your data the same way you'd jot notes on a Post-it and stick it to the fridge. Anyone who walks into that kitchen can read it. For an app, that means the company's engineers, database administrators, or anyone who accidentally gets access to the servers can see exactly what you've stored.
Grocery lists. Kids' schedules. Flight confirmation numbers. Travel plans. All sitting there, readable as a text message.
We didn't want to build that kind of product. Privacy is the whole point of Callie: it is not a feature we bolted on later.
What encryption actually means
Imagine you wrote your grocery list in a secret code that only you know. Even if someone found the paper, they'd just see gibberish. The list is useless to them. That's encryption. The information exists, but without the key to decode it, it means nothing to anyone except you.
Callie now encrypts every piece of sensitive information your family enters before it ever touches our database. Your grocery items, task lists, contact names, travel details, reminders, your kids' names: all of it is scrambled the moment you send it, using a standard called AES-256.
AES-256 is the same encryption standard used by banks, hospitals, and governments to protect their most sensitive data. It is, for all practical purposes, unbreakable. If you want to go deeper on how it works, Wikipedia has a thorough breakdown.
Where the key lives, and where it does not
Encryption is only as strong as where you keep the key. If you lock a safe and leave the key taped to the outside, you haven't really locked anything.
The key that decodes your family's data lives in Callie's application server: completely separate from the database. This means that even if someone were to access our database directly, they would see nothing but scrambled text. No names. No plans. No lists. Just noise.
What this means in practice: Even we can't read your family's data. Not our engineers, not our database, not anyone who might somehow gain unauthorized access to our servers. The only place your information is ever readable is inside the Callie app itself, in the moment it's responding to your family.
What we do and don't store
We're also deliberate about what we store at all. Callie does not keep a transcript of your conversations. When you ask something and Callie responds, that exchange isn't logged anywhere. We store the outcome (the event that got added to your calendar, the task that got saved) but not the conversation that led there.
Your family's chat history is your family's business.
Why we built it this way before launch
We could have launched without encryption and added it later. A lot of apps do exactly that. We chose not to, because the families who trust Callie with their daily lives deserve that protection from day one: not as an afterthought.
If you're paying for something that lives inside your family's private world, it should genuinely be private. That felt non-negotiable to us.
The short version
Your grocery list is your grocery list. Your kids' schedules are your kids' schedules. Your travel plans are your travel plans. Callie is here to help you manage all of it: not to collect it, read it, or profit from it.
We built the technology to back that promise up. And we'll keep building it that way.