StyleTrip · XYK LLC

Privacy, in
plain language.

StyleTrip is local-first. Here’s exactly what stays on your device, and when information leaves it.

Effective November 6, 2026

The short version: an account is optional, and there are no ads and no cross-app tracking. Without an account, your wardrobe and trips stay on your device. If you sign in, they’re also saved to your account so they come back on any phone.

Information stored on your device

Your wardrobe items, originals, trips, destinations, dates, outfits, packing status, generated images, and app settings are stored locally on your device. StyleTrip does not require an account. Unless you sign in, this information stays on your device and is not sent to a StyleTrip database, apart from the image processing described below. Data may be included in device backups you enable through Apple, subject to Apple’s terms and privacy policy.

Accounts and your saved wardrobe

You can use StyleTrip as a guest. If you choose to sign in, you can use Sign in with Apple or Google, and Google Firebase Authentication keeps a user ID and the email address that service provides. Sign in with Apple may give us a private relay address. Google also shares your name and profile photo with Firebase; StyleTrip does not show or use them.

When you are signed in, your wardrobe, trips, outfits, packing lists and the photos that go with them, including original photos and generated images, are saved to your account in a private Google Cloud Storage bucket. This includes any photo that shows you, and the photos behind an avatar if you made one. We save this so your wardrobe comes back when you sign in on another phone, and we use it for nothing else. It is encrypted in storage and over HTTPS, but it is not end-to-end encrypted, so it is not hidden from our service. Access goes only through short-lived links issued to your signed-in account. Your Studio photo balance also follows your account.

Signing out saves your latest changes, then removes your wardrobe from that phone. It stays in your account until you delete it.

Camera, photos, and notifications

  • Camera access is requested when you take an item photo. The system photo picker shares only the photo you select; StyleTrip does not request access to your entire library.
  • Notification access is used only if you enable packing reminders.

You can change these permissions in iOS Settings.

Image processing and optional enhancement

Your wardrobe, outfits, trips and packing work locally. Processing is off until you explicitly allow it in capture, an item, or You. Enabling it also processes items waiting in your wardrobe. You can turn it off again; this stops new uploads but cannot unsend requests already received. When processing is enabled, selected photos are sent over HTTPS through StyleTrip’s Google Firebase service for background removal and initial item details. Studio is an optional, explicitly requested enhancement. A photo of an item you are wearing may include you; choose an item-only photo if you do not want to send a photo showing a person.

Requests may include the item’s name, appearance details, your relevant notes and corrections. Trip destinations, dates and packing status are not sent. The service uses OpenAI for image generation and analysis, and image-processing providers through fal.ai, including Bria for background removal. The configured image pipeline may also use Black Forest Labs through fal.ai. Provider handling follows their applicable terms and data controls; please review those before submitting sensitive content.

StyleTrip does not store original request photos in its server database or result bucket. It temporarily stores the outputs of paid requests so a dropped connection can recover the same result without another charge. Recovery is available for seven days. A storage lifecycle rule then schedules cached outputs for deletion; deletion is asynchronous. Deleted objects may remain in protected cloud recovery storage for a further seven days and cannot be recovered through the app. Provider retention and infrastructure request logs are separate from this result cache.

Service verification and purchases

The app uses Firebase App Check with Apple App Attest to verify service requests. An installation identifier and a separate secure credential authorize its Studio photo balance. We store a hash of that credential, balances, purchase transaction identifiers, product identifiers and minimal operation records to deliver purchases, restore Studio photos and prevent duplicate charges. These service records are kept apart from any wardrobe saved to your account.

Apple processes purchases. StyleTrip verifies Apple’s signed purchase records; it does not receive your payment card details. Rate-limit counters and provider-work budgets help protect the service from abuse. Network addresses used by application rate limits are hashed rather than stored directly in those counters.

Analytics, advertising, and tracking

StyleTrip has no advertising and no cross-app tracking, and we do not sell your data.

To learn which features work and where people get stuck, when usage analytics is enabled, we use PostHog, a product analytics provider. The app sends usage events such as saving an item, creating a trip or seeing the Studio photos offer, with counts, durations and result codes, plus the app version, device model, screen size, operating system version and language. Our servers report purchases, refunds and Studio photo use the same way, including the product, price and currency of a purchase.

These events are tied to a random ID derived from your installation identifier, not to your name, email or Apple Account. They never include your photos, item names, notes, brands, destinations or trip dates. We turn off IP-based location and remove your device’s time zone before anything is sent.

You can turn this off at any time in You, under Settings, Privacy, Share usage data. The app and our servers then stop sending events tied to your ID. In the EU, EEA, UK and Switzerland it stays off unless you turn it on. Refund and subscription renewal counts sent by Apple reach us without any link to you and are not affected by this setting.

Service providers

Google Firebase and Google Cloud host service requests, verification and balance records, sign-in, and wardrobes saved to an account. Apple provides device attestation, Sign in with Apple and purchase processing. Google provides Google sign-in. PostHog processes the usage events described above. OpenAI and providers reached through fal.ai process selected content for the requested image feature. Their terms and privacy commitments apply to that processing. The public StyleTrip website and service infrastructure may process connection data such as IP addresses and request logs; the website does not use analytics or advertising cookies.

Retention and deletion

Use Recently Deleted to restore an item while it remains there. Permanently deleting an item removes its unshared local media and pending request inputs. Delete Everything removes local wardrobe and trip data, and if you’re signed in it also removes the wardrobe saved to your account. It does not remove usage events already sent; ask us using the details below if you want those deleted. Apple device backups are managed separately through your Apple settings.

You can delete your account in the app, in You, under Settings, Account. This removes your account, your saved wardrobe and photos, your remaining Studio photo balance and the data on that phone. It also revokes your Sign in with Apple token. Deleted wardrobe files may remain in protected cloud recovery storage for seven days before permanent removal; they are no longer available through the app. If another phone still has a copy of your wardrobe, you can delete that in its own app. An Apple subscription keeps renewing until you cancel it in the App Store.

Deleting local app data does not erase balance and purchase records used for restoration and duplicate-charge prevention, or cancel an Apple subscription. Manage subscriptions in the App Store. Minimal paid-operation records remain after cached results are removed so an old request cannot be charged again. For questions or requests about service records, contact us using the details below.

Security

Remote generation requests and saved wardrobes use HTTPS. No OpenAI API key is included in the app; requests pass through a server-side endpoint. No system can be guaranteed completely secure, so please avoid adding content you do not want processed as described in this policy.

Changes

We may update this policy as StyleTrip changes. The effective date at the top of this page will identify the current version.

Contact

For privacy questions or requests, contact XYK LLC at hi@xyklabs.com.