Your twin looks like you. Here's what we do about that.

Handing an app a model of your own body is not a small ask. We know it is not. So before anything else about how the game works, here is the part you actually want answered.

Who can see my twin?

Nobody, unless you show them.

ftns.ai has no social feed, no friends list, no leaderboards and no follower count. There is no screen anywhere in the app where your twin appears next to someone else's, because there is no such screen to build one into. This is not a privacy setting you have to find — it is an absence in the product.

Sharing exists as exactly one thing: you export a share card or a Future Self image yourself, to wherever you choose, when you feel like it. The app never posts on your behalf. It has no ability to.

If you've ever quietly deleted a fitness app the week your progress became visible to other people, that is the specific problem this design exists to solve.

What happens to my photos?

They are optional, and they are never stored.

Your twin is built from your own metrics — nothing in the app makes you upload anything. If you do add the posed shots during setup, they are processed in memory only, are never stored on our servers, are never used to train AI models, and are discarded the moment your twin is built. Your photos are private and never posted publicly.

Which means the honest answer to "how do I delete my photos" is that there is nothing to delete. What you can delete is everything else: one tap in Settings removes your profile, your logs, your twin and your scores from the device. It is permanent, so export anything you want to keep first.

Your health data is never used for advertising, never mined, and never sold on. Where your data lives covers the rest of it, and the privacy policy is the document that counts.

Is my twin a body scan?

No. This is the distinction that matters most, and the one an accurate-looking model makes easiest to blur.

ftns.ai is a game in the Health & Fitness category. It is not a medical product. It doesn't diagnose anything, doesn't give clinical advice, and never tells you what any of your numbers mean for your health. Your twin responds to game inputs — workouts logged, sleep synced, steps counted — and turns them into a character state.

A model that looks accurate is still not measuring you. It is a game character built from the way you are playing. If you want a professional read on your body, that comes from a qualified professional, not from an app with a score in it.

Why does the twin look like you at all?

Because the closer the character is to you, the harder the consequence is to shrug off.

That is the whole bet of this category. A virtual pet drooping is a small pang — you're a slightly negligent owner. A character that is recognisably you, looking flat after three quiet weeks, is different information entirely. It is the same behaviour, reported by something you cannot hold at arm's length.

The trade-off is real and we're not going to pretend otherwise: proximity is exactly what makes the mechanic work, and exactly what makes it something to handle carefully. Which is what the rest of this page is about.

What we will not do with it

Stated plainly, because these are the obvious next moves and we are ruling them out.

• No before-and-after framing. Two frames of the same accurate body, six months apart, is a diet ad. We do not make that image, in the app or in marketing.
• No public comparison, ever. Not at launch and not later. Adding a feed or a ranked list to a private-first app is not a feature, it is a broken promise.
• No sexualised generation. Avatar generation runs under non-sexualisation constraints. The app is rated 16+ and that constraint is not negotiable at any age.
• No selling or mining your health data. Not for advertising, not to third parties.
• No health claims. We will not tell you what your body means. We are not qualified to and it is not what the product is.

The short version

If you want the mechanics rather than the policy, what a digital twin actually is explains the two speeds it changes on, including why the build only recomputes once a week.