Wearomancy Support

Some retailers block automated page fetches. When that happens the app keeps the link and the attribution but cannot fill in the colour and material, and it asks you to confirm them. Photographing the piece is the more reliable route for those shops. If a shop you use fails often, send us the domain and one product link and we will look at supporting it directly.

The first render after a quiet period wakes a GPU, which can take several minutes. Later renders are much faster. If a render fails, the app says so rather than showing you something stale, and trying again once the engine is warm usually works.

It is an image model working from the product photos. The better the photo of a piece, the better the render. It is a style preview rather than a fitting, so treat an odd result as the model guessing rather than as information about the garment.

Yes, in Studio. Be aware of what that changes: with a preset model your photo is never sent anywhere, and with your own photo it is sent for that render. The privacy page explains exactly who receives it and for how long.

Use export wardrobe data in the You tab before you move, which writes a JSON file you keep. There is no account and no iCloud sync, so there is no automatic transfer. This is the cost of the app not holding your data.

Delete the app. Everything the app holds is inside its own container on the device and goes with it. There is no server copy to ask us to erase. Individual pieces, renders and your birth profile can be removed from inside the app without deleting anything else.

Please write to us with the screen you were on and what you expected. Reports about a bad suggestion or a broken import are useful and get read; there is no ticket system to navigate.