Engine

Privacy & compliance

Retention, erasure, and AI disclosure.

The platform handles photographs of real people. Three commitments follow from that.

Retention

Shopper photos are deleted automatically after 1, 3 or 7 days — set per account, and overridable per request with output.keepForDays. Within that window a returning shopper reuses their photo instead of re-uploading.

Shorter retention is the privacy-conservative choice; longer is the smoother repeat experience.

Never used for training

Shopper photographs are never used to train models. Say so in your widget, on your site, and in your DPA — it is the single most common shopper objection.

Right to erasure

Pass an externalUserId (opaque, no PII) on upload or try-on, then:

bash
curl -X DELETE "https://api.genfashion.app/tryon/v1/customers/user_42" \
  -H "x-api-key: gk_your_api_key"

This wipes every image and anonymises every generation linked to that id, and writes an audit record you can produce for a DSAR.

Erasure only works for data that was tagged at write time. Untagged uploads expire on the retention window instead. Make tagging the path of least resistance in your integration.

EU AI Act

Every generated image carries machine-readable AI-provenance metadata. That is not configurable.

A visible AI MODIFIED badge is composited by default, and can be disabled per generation with output.aiLabel: false or per account in settings. The badge is the disclosure; the metadata is the proof.