Principles

Your data should work for you

15 July 2026

Health apps have a habit of talking about privacy in the abstract, usually right before asking for another permission. So let’s be concrete about what “your data is yours” actually means here — feature by feature, not adjective by adjective.

Body scans that never leave your phone

A body scan is about the most personal thing you can put in an app. So the measurements run on your device. The imagery doesn’t get uploaded, doesn’t sit in our storage, doesn’t wait in a bucket for someone to misconfigure it.

The 3D avatar and the “Future Me” projection of your progress work from the result, not from photos on a server. The processing happens where the photo already is.

Privacy zones, because a route map is an address

Anyone who has looked at a heatmap of their runs knows the problem: every single one starts at your front door. A public activity map is a map to where you sleep.

So privacy zones cut your home and work out of the picture — you still get segments, personal records and your own heatmap of everywhere you’ve trained, without publishing your address to people who don’t need it.

Export everything, any time

The strongest promise a product can make isn’t “we’ll keep your data safe”. It’s “you can leave and take it with you”.

Full export, whenever you want, no support ticket, no dark pattern, no “are you sure?” maze. We’d rather earn your next session than trap your history.

We don’t sell it

Not to advertisers, not to data brokers, not to an insurer who’d love to know about your sleep. The business model is honest and boring: the app is free to start, and coaches sell programs in the marketplace. You’re the customer, not the inventory.

Open where others are closed

This is the part most health apps get wrong, and it’s the part we’re proudest of.

Your log has a public API and MCP access. That means your own AI agents can read your data and work with it — your tools, your workflows, your automations. Not just our AI coach inside our walls.

If you want to pull your training history into a spreadsheet, a bot, or something we haven’t thought of, the door is open. Data that only works inside one app isn’t really yours; it’s just stored under your name.

And yes — we still run our own stack

We built our own reactive backend rather than renting one. Not for the engineering flex: it means the graph of you lives on infrastructure we control, with an open interface pointing outward rather than a closed one pointing in.

That’s the whole principle. Your body, your log, your call.

Start training free

← All notes