Wardrobe Support

Yes, and we state it plainly because the on-device processing could easily be read to imply otherwise. Both photographs are stored in your own private space in your FCT account: the cutout Wardrobe made and the original photo you took. That is what lets your closet appear on every device you sign in on. Where the original and the cutout are byte-identical, they share one stored object rather than being uploaded twice.

The reading. Vision lifts the cutout from the background on your device, and on-device Foundation Models propose a garment's category, color, season and formality and compose outfit suggestions. None of that goes to us or to a third-party AI service: Wardrobe uses no cloud model at all. What the reading produces is then stored in your account like any other record.

No. Outfit generation is constrained to the items in your catalog, so a suggestion is always a combination of clothes you have actually scanned. It will tell you it cannot build an outfit before it will invent a garment to complete one.

There is no third-party analytics SDK, no advertising identifier and no cross-app tracking. Wardrobe does report anonymous diagnostics to FCT, crash and performance data, a trail of screen and action names (never content), and feature-use counts, keyed to a random install identifier that is joined to no account and carries nothing you typed, viewed or stored.

Your closet stays whole and fully browsable, including items added while subscribed. The free caps apply only to confirming another item or generating another outfit, never to what is already there.