Outfits
This Privacy Policy applies to the Outfits mobile app published by Kyle Au through SwiftyIndie. For general practices across other SwiftyIndie apps, see the SwiftyIndie Privacy Policy.
We try to collect as little information as possible. Solo use of Outfits does not require an account. Optional shared trips use Sign in with Apple on iOS and Google Sign-In on Android. We do not intentionally collect information that directly identifies you—such as your mailing address or government-issued identifiers—unless you choose to contact us or sign in to collaborate.
Data on your device
Your closet items, outfits, trips, profiles, packing lists, and preferences are stored locally on your device. That information remains under your control unless you use a feature that clearly sends data off the device (described below).
On-device image processing
When you add clothing photos, Outfits may process images on your device—for example background or subject segmentation—so items look clean in your closet. That on-device processing does not upload those images by itself.
Optional AI closet tagging
If you enable AI Closet Tags (or accept the related consent when using Plan my outfits), Outfits may send clothing item photos from your closet to our cloud gateway so an AI vision model can suggest colors, categories, and tags. Photos are resized before upload and are used only to generate those suggestions and return them to the app. We do not use closet photos to advertise to you, and we do not sell them.
Optional AI trip and day planning
When you use Plan my outfits or Suggest outfits, Outfits may send closet metadata (such as item IDs, categories, colors, and tags), trip and day details (including names, notes, luggage preferences, existing outfit item IDs, and weather summaries), and your trip destination (name and coordinates, when available) to our cloud gateway so an AI model can propose outfits. Planning requests do not include clothing photos. Results are returned to the app so you can review and apply them.
Optional shared trips
Shared trips are optional. Solo trips and your closet stay on your device unless you choose to share a trip. To collaborate, you sign in with Apple on iOS or Google on Android (development builds may also offer a staging test account). We store an account profile for collaboration (a user identifier, an optional display name you choose, an optional profile photo you upload, and on Android the email Google provides for sign-in) and the shared-trip content you and other members add: trip metadata (name, dates, location, notes), day notes, outfit plans, and clothing item snapshots needed so others can see outfits—including thumbnail photos uploaded for items that appear on the shared trip.
If you upload a profile photo, it is stored in our private object storage and is visible to members of shared trips you join. You can remove the photo in the app, and deleting your Outfits account removes the stored photo with your other cloud account data. We do not use profile photos for advertising, face recognition, or training AI models.
Shared-trip data is stored in our private backend (hosted database and object storage accessed only through our cloud gateway). Other members of a trip can see the shared content for that trip. Free shared trips may expire after a retention period; Jetsetter hosts can keep trips longer. You can leave a shared trip (your local copy can remain on your device), and hosts can delete a shared trip for everyone. You can also delete your Outfits account in Settings, which removes your cloud account and shared-trip cloud data; local closet data on the device is not automatically wiped.
Authentication for shared trips uses Sign in with Apple (iOS) or Google Sign-In (Android) via our identity provider. We do not put database or storage credentials in the app; the app talks to our gateway with your user session. Google's privacy policy is available at https://policies.google.com/privacy.
AI service providers
AI features are provided through our hosted gateway (for example on Google Cloud Run). Tagging may use Moondream; planning may use OpenAI. Those providers process the request data needed to generate a response, in accordance with their terms and privacy policies. We use the responses only to power the feature you requested. We do not sell this data.
Location and places
Outfits uses the Google Places API so you can search for trip destinations. That may involve processing place search text and approximate or precise location or place data. Destination coordinates associated with a trip may also be included in AI planning requests when you use those features. Location and place data are used only to provide the features you request. Google's privacy policy is available at https://policies.google.com/privacy.
Analytics
We use TelemetryDeck to collect anonymized or aggregated diagnostic and usage information (for example app opens, feature usage such as AI planning funnels, app version, device type, operating system version, and country or region derived from your network connection). This helps us understand how Outfits is used, fix bugs, and improve the product. TelemetryDeck's privacy policy is available at https://telemetrydeck.com/privacy.
Subscriptions
Outfits uses RevenueCat to manage in-app purchases, subscriptions, and entitlements. RevenueCat may process purchase history, subscription status, entitlement information, and an anonymous app user identifier. We use this to validate purchases, unlock Jetsetter features, restore purchases, and provide related support. RevenueCat's privacy information is available at https://www.revenuecat.com/privacy.
Advertising measurement (iOS)
On iOS, Outfits may integrate the Meta (Facebook) SDK to measure app installs and the effectiveness of advertising on Meta technologies. We do not use Apple's Identifier for Advertisers (IDFA) with Meta's services. Measurement may rely on privacy-preserving techniques such as SKAdNetwork. The Android app does not include the Meta SDK. Meta's privacy policy is available at https://www.facebook.com/privacy/policy.
We do not use analytics data to personally identify you, and we do not sell your personal information.
Support and contact messages
If you email us for support or feedback, we will receive the information you choose to include in your message, such as your email address and the contents of your request. We use that information only to respond to you and manage the conversation.
Data retention
We keep information only for as long as reasonably necessary for the purposes described in this policy, including operating AI features you request, maintaining the app, improving performance, complying with legal obligations, and resolving disputes. Request payloads processed for AI features are used to generate a response for that request; we do not use them to build advertising profiles.
Your choices and data deletion
You can stop collection related to optional AI features by turning off AI Closet Tags in Settings and by not using Plan my outfits / Suggest outfits. You can leave or avoid shared trips, and you can delete your Outfits account in Settings (Delete account) to remove cloud collaboration data. You can stop all collection by uninstalling the app. If you cannot open the app or you want us to delete information you previously sent directly, email support@outfitstravel.app.
Children's privacy
Outfits is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, please contact us so we can review and delete it if appropriate.
Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will post the updated version on this page. Your continued use of Outfits after an update becomes effective means you accept the revised policy.
Effective date: August 17, 2026. Documented optional shared-trip profile photos (private storage; visible to trip members; removable / deleted with account). Earlier: Android Google Sign-In, account deletion, shared-trip outfit thumbnails; optional AI closet tagging and trip/day planning; on-device vs uploaded images.