Subprocessor List En
Third-Party Services
Document version: 2026-10-12
We use the following providers to operate OutfitMuse. Apple and Google also process sign-in and store-payment information independently under their own policies.
The notification service used depends on your device operating system and app version.
The APNs and FCM entries and notification-registration explanation below apply only to app versions that include the push notification feature. They do not describe push-specific processing in versions without this feature.
| Provider | Purpose | Information processed | Processing location |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting and storage | Account information, uploaded content, generated images and necessary service logs | Primarily the United States |
| Apple | Sign in with Apple and App Store purchases | Sign-in identifiers, email and name where provided; purchase, subscription and verification records | Locations used by the applicable Apple services |
| Google Sign-In and Google Play purchases | Sign-in identifiers, email and name where provided; purchase, subscription and verification records | Locations used by the applicable Google services | |
| Apple Push Notification service (APNs) | Deliver task-result notifications and applicable service notices or reminders subject to preferences and required consent | Push token, notification payload and technical information needed for delivery | Locations used by Apple's notification service |
| Google Firebase Cloud Messaging (FCM) | Deliver task-result notifications and applicable service notices or reminders subject to preferences and required consent | Push token, Firebase installation identifiers, notification payload and technical information needed for delivery | Locations used by Google's Firebase service |
| Google Firebase Analytics | Usage analytics | App interactions, app and device information, app-instance identifiers and account identifiers where enabled | Locations used by the configured Firebase service |
| Vercel AI Gateway | Route AI requests to OpenAI | Photos or image links, prompts, relevant preferences, outputs and necessary request metadata | Locations used by Vercel's gateway service |
| OpenAI | AI image analysis, generation, editing and outfit planning | Photos or image links, which may include faces; prompts, relevant preferences, outputs and necessary request parameters and metadata | Locations used by the applicable OpenAI API service |
| Sentry (Functional Software, Inc.) | Crash reporting and diagnostics | App and device information, error reports, diagnostic events and IP address | United States, subject to service configuration |
| WeatherAPI.com | Weather information and weather-aware recommendations | City, region and country, with necessary weather-query and server-request information | Locations used by WeatherAPI.com under its service agreement and privacy policy |
Providers may process information outside your country. The locations above describe provider services, not a promise that all records remain in one country.
AI processing and retention
Before sending personal information through Vercel to OpenAI, we explain the processing and ask for your explicit permission. If you decline, we do not send the AI request. We do not use your photos, prompts, profile or body information, or generated images to train our or third-party AI models, and do not opt in to provider training with this content.
No training does not mean no retention. OpenAI's standard API abuse-monitoring logs may include content and are generally retained for up to 30 days, with legal and safety exceptions. Vercel's retention is separate. These provider records are distinct from content saved in your OutfitMuse account and are not subject to a blanket promise of immediate deletion. See OpenAI's data-retention information and our Privacy Policy.
Further information and contact
Apple and Google handle store payment credentials; we receive the transaction information needed to verify purchases and provide benefits, not full card details, payment passwords or authentication codes.
See our Privacy Policy, Membership Terms and Account Deletion Instructions for retention, cancellation and deletion details. We update relevant disclosures before material changes to recipients or processing purposes and obtain permission where required.
Questions: support@echojoy.cn.
Notification registration and retention
Our servers process the app installation UUID, push token, notification status, language and time zone, and link these records to your account when signed in. This does not mean that we send every registration field or your sign-in credentials to Apple or Google. Our retention and account-deletion rules are described in the Privacy Policy. Provider-held records are subject to the providers' own processing and deletion rules; disabling notifications does not itself delete all existing records. Firebase installation identifiers are separate from our app's installation UUID.