Vael is a fashion app that helps you digitize your wardrobe, get AI-styled outfit suggestions, and try garments on virtually before you buy them. This page explains, in plain language, what data we collect, why we collect it, who we share it with, and how you can delete it.
What we collect
Account data. When you sign in with Apple or email, we store your email address and an authentication identifier provided by Apple or our authentication provider (Supabase). We never see or store your Apple ID password.
Wardrobe photos. Photos of garments you add to your wardrobe are processed by our AI pipeline to extract the garment, tag its category, color, and style, and produce a clean catalog image. The catalog image is stored in our Supabase backend under a path scoped to your user ID so the app can show your wardrobe, build outfits, and render social surfaces you choose to share. Body photos, try-on results, saved-look images, chat uploads, and social render composites live in private storage; garment catalog images are kept in a public-read wardrobe image bucket under unguessable paths so the app's image feed can load quickly. Garment images are deleted when you delete the item or your account.
Body photo. If you enable virtual try-on, you upload one or more full-body reference photos. They are stored privately under your user ID in our Supabase storage, used only to render try-on results for you, and never shared or used to train any model. You can delete any body photo at any time from the try-on screen. Because a body photo can identify you, we treat it as biometric-adjacent personal data: access is restricted to your account, the small set of edge functions that perform try-on rendering, and Google Gemini for the duration of the rendering call. We retain body photos until you delete them or delete your account.
AI safety event log. Every time the AI provider (Gemini) refuses to process an image because it triggered a content-safety filter, we record an audit row containing the time, your user ID, the feature that was used, the provider's block reason, and per-category safety ratings. We do not store the original image in this log. The log lets us identify abusive accounts and respond to legal requests, and is retained for two years.
Try-on results. Rendered try-on images (your body composited with a garment by Google's Gemini image model) are saved to your private storage so you can revisit recent looks. They remain until you delete them or delete your account; we do not currently auto-expire them.
Saved looks & outfits. Outfits you save, including any associated try-on render and the list of garment IDs in the look, are stored under your account.
Friends & social features. If you connect with a friend on Vael, we store the friend relationship and the per-friend permissions you set (e.g. whether they can browse your wardrobe or see your stories). When a friend has granted you access to their wardrobe, we read their garment images on your device only for the try-on session you initiate; nothing is copied to your account. "Stories" you post (a saved look shared to friends for 24 hours) are readable only by friends you explicitly allowed.
Contact matching (optional). If you opt into the "Find friends" flow, the app asks for permission to read your iOS Contacts. Phone numbers and emails are normalized and SHA-256 hashed on your device before being sent to our backend, which compares hashes to find Vael users you may know. Raw contact details never leave your phone, and we do not store the hashes after the lookup completes.
Calendar (optional). If you grant calendar access, we read upcoming event titles and times to suggest outfits that match your day (meetings, gym, dinner, etc.). Calendar data is read only when generating a suggestion and is not stored on our servers.
Location & weather (optional). If you grant location access, your coordinates are passed to Apple WeatherKit to retrieve the current forecast. We also store the last resolved latitude, longitude, and place label in your account preferences so weather-aware outfit generation can continue to work across app sessions. Weather summaries may be cached briefly to avoid repeat lookups. Stored location preferences are deleted when you delete your account.
Notifications. If you enable push notifications, we store your APNs device token so we can send your morning outfit and social activity. We also schedule local notifications on your device (e.g. tied to calendar events) which never reach our servers.
Subscription state. If you subscribe to Vael Pro in the iOS app, Apple's StoreKit (via RevenueCat) tells us which plan you're on and when it renews or expires. We store this state in your account row so the web app and browser extension know you're Pro. We never see or store your payment details.
Public shares. If you explicitly tap "Share" on a saved look or outfit, we generate an unguessable URL (twelve random characters) that makes that single item publicly viewable. You can revoke the share at any time; revoking it makes the URL immediately return a not-found page.
Analytics events
We record product-analytics events to understand how features perform — for example, app launches, screen views, when a paywall is shown and why, when a try-on starts or completes, when onboarding steps are reached or skipped, and when buttons like "Sign out" or "Delete account" are tapped. These events are stored in our own Supabase backend and are linked to your account (not anonymous) so we can answer per-user funnel questions like "did this user reach try-on before subscribing?"
What's in an event. Each event has a name, a timestamp, your app version, a session identifier, an experiment variant, and a small set of typed parameters (e.g. paywall trigger, garment category, plan name, item count). Events never contain photos, garment names, free-text input, or any other content from your wardrobe.
Retention. Analytics events are retained for up to 12 months for product-analytics use and are deleted permanently when you delete your account.
Opt-out. Email reljapps@gmail.com and we will stop collecting analytics from your account within seven days. Note that turning analytics off does not affect functional usage tracking we need to enforce subscription limits (e.g. counting AI credits remaining).
What we don't collect
We don't sell, rent, or share your wardrobe, photos, or try-on results with advertisers. We don't track you across other apps or websites. The Vael browser extension does not collect your browsing history; it only reads the page you're actively on to detect a product image, and only when you explicitly click the Vael button does any data leave your browser.
Third-party services
We use a small set of third parties to run Vael:
- Supabase: PostgreSQL, authentication, file storage, and edge functions.
- Apple StoreKit via RevenueCat: subscription billing and entitlement management.
- Google Gemini: AI image generation for virtual try-on and AI image analysis for "Smart Import" (identifying individual garments in an outfit photo). Photos sent to Gemini are used only to fulfill your request; per Google's paid Gemini API policy, inputs are not retained after processing and are not used to train Google's models.
- OpenAI: powers our text-based AI features — auto-tagging new garments (category, color, style), generating daily outfit suggestions, "Find My Size," capsule wardrobes, packing lists, outfit critiques, and style chat. Some OpenAI requests include an image you provided, such as a garment photo, outfit screenshot, chat attachment, or shopping screenshot, when that image is necessary for the feature. Other requests send only the structured wardrobe context required for the response.
- Apple WeatherKit: weather data for outfit suggestions.
- Sentry: crash reporting. Only technical crash context (stack traces, device model, OS version); no wardrobe content or photos.
Your rights
You can delete your data at any time from the iOS app (Account → Delete my account). Deletion removes your user record, wardrobe photos, body photos, try-on renders, saved looks, friend relationships, analytics events, subscription state, chat uploads, avatars, Style Peek composites, Style Vote renders, and friend-mix social renders from our backend permanently. It propagates to the web app and any browser-extension session within seconds.
Under the GDPR (EEA, UK) and CCPA (California), you also have the right to request a copy of the data we hold about you. Email reljapps@gmail.com and we will respond within thirty days.
Children
Vael requires users to be at least 16. It is not directed at children under 16, and we do not knowingly collect data from them. If you believe we have collected data from someone under 16, email us and we will close the account and delete the data.
Changes
We may update this policy as the product evolves. Material changes will be announced in the app and on this page. The "Last updated" date above is authoritative.
Contact
Questions, concerns, data requests: reljapps@gmail.com.