Legal

Legal Notice

Who operates this service, where they are registered, and how to reach them.

Last updated

This page identifies the operator of https://www.genfashion.app. It exists so that anyone — a shopper, a merchant, or a regulator — can find out who is answerable for this service without reading a contract to do it.

Operator

EntityBuildFrame Technologies Private Limited
Registered officeC-1208, ACE PLATINUM, ZETA 1, Greater Noida, Uttar Pradesh 201306, India
Governing lawIndia
Contacthello@buildframe.tech
Servicehttps://www.genfashion.app
In effect since2026-09-12

hello@buildframe.tech is a general contact address and is also where data protection requests go. That is a deliberate choice by the operator and not an oversight — but it means a request with a statutory deadline shares an inbox with ordinary correspondence. If you are sending one, write "Data protection request" in the subject line so it is not treated as support.

What this service does

GenFashion generates a synthetic image showing a garment on a person, from a photograph the shopper supplies. Every result carries machine-readable provenance metadata naming the model that produced it, which no setting removes. A visible "AI MODIFIED" badge is composited by default and a shop can switch that one off for its own storefront.

It is a visualisation aid. It is not a fitting or sizing service, and a result does not establish that a garment fits.

Responsibility for content

Product images, titles and descriptions shown through the try-on widget come from the merchant's own catalogue. BuildFrame Technologies Private Limited does not select, review or endorse them, and a complaint about a product belongs with the shop selling it.

Photographs supplied by shoppers are processed on the merchant's instructions and deleted on the schedule that merchant has set. What happens to them is described in full in the Privacy Policy.

Related documents

Corrections

If anything on this page is wrong or out of date, write to hello@buildframe.tech and say so. It is generated from the deployment's own configuration, so a correction here is a configuration change rather than an edit to prose.