Vellum Wardrobe Data Details
This page carries the specifics behind our Privacy Policy: which providers we use, what each receives, where they process, and how long each kind of data is kept. It changes as the app changes; the date above is the date of the last change.
Providers
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Google (Gemini API) | Identifies garments, cuts them out, and makes the images of clothing on a model | The photographs a generation needs — the only provider that ever receives a photograph of a person — and pictures of clothing | United States |
| Kling AI Pte. Ltd. | Animates a finished look into a short video | Images the app has already generated, never a photograph you supplied | Singapore |
| Runware OÜ | Arranges pictures of clothing into outfit displays | Images of clothing only, never a photograph of a person. No feature in the current version of the app sends it anything. | European Union |
| Google Cloud / Firebase | Hosts your account, your library and our servers; delivers notifications | Your account and library | United States |
| Google Analytics for Firebase | Usage analytics | Device and usage information and purchase amounts — never your photographs or your name | United States |
| Apple | Sign in with Apple, purchases, notifications, TestFlight | What Apple's own terms describe | Apple's regions |
| Microsoft (Bing), Google Search, and the retailers whose pages you open | Finding clothing images on the web when you search for clothes to add | Your search words and your device's network address, as they would be in a browser; an image you choose to add is downloaded from the retailer. Nothing about you or your account. | Their own regions |
Google and Kling both state, in the terms that govern our use of their services, that content we submit is not used to train their own models. Runware makes no equivalent commitment, which is why nothing but pictures of clothing would ever be sent there.
Retention schedule
| Data | Kept for |
|---|---|
| Your account, library, photographs and generated content | While your account is open |
| Photographs and images supplied to a generation — your own photographs, images you add from the web, and a generated picture used as the starting point for another (working copies) | Up to 12 months, then deleted automatically |
| Working files for a generation — the photograph sent, any reference images, the result, and the record that indexes them | Up to 30 days, then deleted automatically |
| Finished videos awaiting collection by your device | Up to 30 days, then deleted automatically |
| Credit movements and purchase records | While your account exists — they are how a failed generation is refunded |
| Purchase and credit records required for accounting and tax | Up to 7 years, with no photographs attached |
| Records that free credits were claimed: one keyed on your sign-in identity, holding your account and device identifiers and the date; one keyed on a random identifier for your device, holding only the date (and, in a test version, how many test credits the device received). They exist so free allowances cannot be claimed again by creating another account or signing in on the same phone; they hold no photographs, no name and no email. | Kept after account deletion, for that one purpose. The device identifier is removed from your phone when you erase the device. |
| Everything else above | Deleted when you delete your account; cleared from operational backups within 30 days (files) and 7 days (records) |
Changes to this page
- 14 September 2026 — page created, carrying the provider list and retention schedule that used to sit inside the Privacy Policy. Later the same day: the web-search recipients added; the free-credit records described in full (the identity-keyed one holds the account and device identifiers); the 12-month row covers web images and generated starting pictures.
Contact
Diorama Labs LLC · support@dioramafoundry.com