Our manifesto
We build tools. You own them. Your data is yours.
Code Family exists to help real families handle the unglamorous logistics of life, health records, expiration dates, moves, homework, money, without becoming a data product themselves.
Why we exist
Families deal with a lot. Health appointments and vaccination records. Prescriptions that run out and medications that expire. Moving boxes and lease agreements and deposit disputes. Kids who need to genuinely learn their letters and numbers before they can build anything on top of them. Financial decisions, savings goals, tax documents scattered across email.
None of this is glamorous. None of it trends. But it is the actual substance of organizing a household, and it matters enormously when something slips through the cracks.
The software meant to help with these things has, over the past decade, largely become something else: engagement platforms, subscription businesses, data collection operations. The incentives of venture-backed consumer software push toward recurring revenue, user lock-in, and behavioral data as an asset. Those incentives are directly at odds with what families actually need from a tool.
We think there's a better model. We build tools. You pay once. You own the app forever. Everything stays on your device. We never see your data, and we don't have a business reason to.
What we believe
Privacy is a design choice, not a feature toggle.
Most apps that claim to respect your privacy still collect data, they just promise not to sell it, or they limit what they share, or they anonymize things before sending them. We made a different design choice: we don't collect data in the first place.
Everything Code Family apps store lives on your device. There is no server holding your health records or your family's financial picture. If someone breached our infrastructure, which would be extremely difficult since we don't run customer data infrastructure, they would find nothing, because there is nothing to find. That's not a privacy policy. That's an architecture decision.
Software should work like an appliance.
You buy a washing machine once. It works. The manufacturer doesn't charge you monthly to keep washing clothes, doesn't collect data on your laundry habits, and doesn't shut down if the company is acquired. You expect it to keep working for years without asking you for anything else.
That's how we think software for families should work. You buy it once. It works. It keeps working. We don't hold features hostage behind a subscription tier, we don't change the pricing model after you've come to rely on the app, and we don't build in engagement mechanics that turn your tool into something that demands your attention.
Families shouldn't have to read a terms of service to use a calendar.
When an app is free, your data is the product. When an app is subscription-based, you're renting access and the company has ongoing incentives to extract more value from your engagement. No-account-required, no-cloud, one-time-purchase isn't a constraint we're working around, it's the whole point.
We don't want to know your name. We don't want your email address. We don't want to track which features you use or how often you open the app. We want to build something useful and sell it to you, and then get out of the way.
Craftsmanship still matters.
We believe in native apps that feel like they belong on the platform, in thoughtful design that doesn't require explanation, and in software that does exactly what it says without unexpected behavior. Apple's platform gives us access to extraordinary tools, SwiftUI, SwiftData, native file access, the system font stack, and we use them to build things that feel at home on an iPhone, iPad, or Mac.
This isn't about being precious about aesthetics. It's about building things that are quiet and reliable and feel good to use, because those qualities matter to people who are reaching for an app in a stressful moment.
What we'll never do
- Sell your data or share it with advertisers. There's no data to sell, it lives on your device.
- Show ads. Not now, not later, not in a "free tier."
- Charge a subscription for an app that doesn't require server infrastructure to run. If we ever build something that genuinely requires ongoing server costs, we'll be honest about why.
- Require an account to use our apps.
- Add features that serve our business model at the expense of our users, dark patterns, engagement traps, notification spam.
- Pivot to SaaS because investors want recurring revenue. We're not taking venture funding.
- Shut down in a way that leaves you without access to your data. Because your data is on your device, this problem doesn't exist.
Who we build for
We build for parents managing the logistics of a household with kids. For families where one person is the de-facto health administrator, scheduling coordinator, financial planner, and homework helper, often all at once.
We build for the parent who has been through a move and knows what it costs to lose a key document. For the one who got caught without a prescription refill because the expiration crept up quietly. For the one who pulled out their phone in an emergency room and couldn't quickly find the allergy information a nurse needed.
We build for families who want their tools to respect them, who are tired of being the product, tired of monthly fees for apps they use twice a week, and tired of privacy policies that run to thirty pages and say nothing reassuring.
We don't build for enterprise. We don't build for power users who want maximum configurability. We build for ordinary families managing real life, and we try to get out of their way.
The privacy promise, specifically
Every Code Family app operates entirely on your device. No usage data is collected. No analytics SDKs are included. No crash reporters phone home. The apps don't make network requests except where the feature requires it (and for every current app in our suite, no feature requires it, there are no servers to talk to).
If you choose to use iCloud sync (where available), your data syncs through Apple's private iCloud database, meaning it's encrypted and accessible only to you. We never have access to it. Apple's privacy guarantees apply, not ours.
We will always be explicit about any change to this. If we ever build a feature that requires sending data to a server, even optionally, we'll say exactly what data, why, and what happens to it. We'll make it opt-in, not opt-out. And we'll make it easy to use the app without that feature if you'd rather not.