1. Developer and Contact
Wheron is provided by Soosu Studio. For privacy questions, data requests, or support, please contact us at wheron@soosu.studio.
2. Information Wheron Handles
Wheron helps you manage a digital wardrobe, analyze clothing photos, create outfit suggestions, record worn outfits, use weather-aware styling features, and optionally subscribe to Premium. The app does not ask for your contacts, microphone, calendar, or phone call access.
- Account information: when you create an account or sign in, Wheron uses Firebase Authentication and may handle your Firebase user ID, display name, email address, profile photo URL, Google sign-in token, email sign-in information, and authentication state. Password handling is provided by Firebase Authentication; Soosu Studio does not store your password in the app.
- Profile information: nickname, profile image, profile image download URL, profile image storage path, and related update timestamps.
- Wardrobe records: clothing category, name, brand, seasons, colors, color keys, palette colors, material, notes, pattern, fit, style tags, details, purchase price, purchase date, wear count, last worn date, image URL, storage path, source URI, group membership, and created or updated times.
- Images and AI input: clothing photos selected from your device, camera-captured clothing photos, replacement images, selfie images, optional height and weight values for try-on features, generated clothing images, generated outfit images, and image metadata needed for analysis or generation.
- Outfit and history data: daily worn outfit records, outfit suggestions, weekly outfit plans, scenario recommendations, favorite status, ratings, wear counts, color harmony information, titles, reasons, and related timestamps.
- Location and weather data: when you use weather-aware outfit features, Wheron may request coarse or precise location from Android, use latitude and longitude to request weather and air-quality data, and store weather snapshots with generated outfits or history records.
- Premium and billing data: Wheron uses Google Play Billing to query Premium offers, start purchases, restore purchases, acknowledge purchases, and determine whether Premium is active. An obfuscated hash of your Firebase user ID may be sent to Google Play Billing as an account identifier.
- Ads and consent data: Wheron may show Google AdMob native ads to non-Premium users and may run a consent flow where required. Ad requests and consent services may process advertising identifiers, device information, app information, approximate location inferred from network data, and interaction data according to Google's policies.
- Notifications, settings, and local state: morning outfit notification settings, theme mode, try-on promotion state, in-app review prompt counters, app cache, camera cache, share cache, image cache, and local database information.
- Usage, diagnostic, and integrity information: Wheron uses Firebase Analytics, Firebase Crashlytics, Firebase App Check with Play Integrity, Google Play services, and Android system services. These services may process app interaction, screen view, crash, diagnostic, device, app version, operating system, and app integrity information according to their own policies.
3. How We Collect Information
- Account information is collected when you create an account, sign in with email, sign in with Google, update your profile, sign out, or delete your account.
- Wardrobe records are created when you add, edit, group, move, delete, or review clothing items.
- Images are collected only when you choose photos, capture photos, upload a profile image, upload a selfie, replace a clothing image, generate a catalog image, generate a try-on image, or share an outfit image.
- AI-related data is processed when you ask Wheron to analyze clothing, generate item images, generate outfit suggestions, generate try-on images, generate scenario recommendations, or generate weekly plans.
- Location and weather data is collected only when you use features that need local weather or forecast information and grant the required Android permission.
- Premium and purchase information is handled when the app checks Premium status, displays offers, launches a purchase, restores a purchase, or acknowledges a purchase.
- Ads and consent information is handled when the app starts, checks consent status, initializes AdMob, or requests ads for non-Premium users.
- Settings, notification preferences, review prompt state, cache files, and local app data are stored when you use the related features.
- Firebase Analytics, Firebase Crashlytics, Firebase App Check, Google Play services, AdMob, and Android system services collect data through their SDKs or platform features when the app is used.
4. How We Use Information
- To authenticate your account and keep wardrobe data scoped to your signed-in user.
- To save, display, update, group, search, delete, and synchronize wardrobe items.
- To analyze clothing photos, create item metadata, generate clean catalog images, and generate outfit or try-on images.
- To save worn outfit history, build style statistics, create scenario suggestions, create weekly plans, and remember outfit feedback.
- To use local weather, forecast, air-quality, and location labels for weather-aware outfit recommendations.
- To send local morning outfit notifications when you enable them.
- To manage Premium access, remove ads for Premium users, and enforce free or Premium feature limits.
- To show ads to eligible non-Premium users and manage consent where required.
- To support sharing, caching, local preferences, profile settings, and in-app review prompts.
- To maintain, debug, secure, measure, and improve Wheron.
- To protect backend services from abuse through app integrity checks.
- To respond to support or privacy inquiries that you send to us.
5. Local Storage, Cloud Storage, and Sharing
Wheron stores local preferences such as app_theme_preferences, morning_outfit_notification_preferences, style_try_on_prefs, and in_app_review_tracker. The app may also use a local Room database, image cache, camera cache under wardrobe-camera, and share cache under outfit-shares.
When you are signed in, Wheron stores user-scoped data in Firebase Firestore under your user document, including collections such as wardrobeItems, wardrobeGroups, wardrobeHistory, outfitSuggestions, outfitPlans, and scenarioRecommendations. Profile and selfie metadata may be stored on the user document.
Images may be stored in Firebase Storage, including profile images under paths such as users/{uid}/profile/avatar.jpg, selfie images under users/{uid}/selfie, generated wardrobe images under users/{uid}/wardrobe/generated, and generated outfit images under users/{uid}/wardrobe/outfits.
AI features may send selected images, generated image inputs, wardrobe metadata, selfie body profile information, item summaries, weather summaries, and prompts to Firebase AI Logic or Google AI services to produce analysis and generated content.
Weather features may send latitude and longitude to Open-Meteo weather and air-quality services. Android location, Geocoder, camera, photo picker, sharing, backup, and device-transfer features may be handled by Android or services configured on your device.
We do not sell your personal information. Data may be processed by third-party services used by Wheron, including Firebase Authentication, Firebase Firestore, Firebase Storage, Firebase AI Logic or Google AI, Firebase Analytics, Firebase Crashlytics, Firebase App Check, Google Sign-In, Android Credential Manager, Google Play Billing, Google Play Review, Google Play services, Google AdMob, Google consent services, Open-Meteo, Android system services, and device backup services. Those services are governed by their own privacy terms.
If you send a support email, share an outfit image, share a screenshot, use device backup, or transfer data through another service, that action is controlled by you and may be handled by the service you choose.
6. Permissions
- Internet: used for Firebase services, authentication, AI features, image upload/download, weather data, air-quality data, billing, ads, consent, analytics, crash reporting, app integrity, and related service communication.
- Location: used to load weather and forecast information for your current area when you choose weather-aware outfit features.
- Post notifications: used for morning outfit notifications when enabled.
- Receive boot completed: used to reschedule local morning outfit notifications after device restart, time changes, or time zone changes.
- Advertising ID: used by Google AdMob and related Google advertising services where available and allowed by your settings.
- Google Play Billing: used to offer, purchase, restore, and verify Premium subscriptions through Google Play.
- Photo picker, camera capture, and sharing: handled by Android when you choose wardrobe photos, profile photos, selfie photos, camera capture, image replacement, or outfit sharing workflows.
7. Account Deletion, Retention, and Deletion
- Local settings, local database rows, image caches, camera caches, share caches, and notification schedules remain on your device until you sign out, delete your account, clear app data, or uninstall the app.
- The in-app sign-out action clears local user preferences, local database tables, image caches, app cache directories, and morning outfit notification schedules on the current device.
- The in-app delete account action deletes the Firebase Authentication account and clears local user data on the current device. Cloud Firestore documents, Firebase Storage images, analytics records, crash records, billing records, and third-party service records may require backend cleanup, automatic retention processes, or a support request to remove where applicable.
- You can request help with cloud data deletion by contacting wheron@soosu.studio.
- Google Play purchase records, AdMob records, Firebase Analytics, Firebase Crashlytics, Firebase App Check, Google Play services, Open-Meteo, and other third-party providers retain data according to their own settings and policies.
- Support emails are retained only as long as reasonably necessary to respond to your request, maintain records, or meet legal obligations.
8. Security
We use reasonable technical and organizational measures to protect information handled by Wheron, including Firebase security features and Android platform storage. Wardrobe photos, selfie photos, body information, location-based weather, and outfit history can be sensitive, so you should protect your device, account credentials, backups, screenshots, and any information you share. No method of transmission or storage is completely secure.
9. Children's Privacy
Wheron is not directed to children under the age required by applicable law to use online services without parental consent. We do not knowingly collect personal information from children. If you believe a child has provided personal information through Wheron, please contact us.
10. International Processing
Information processed by Firebase, Google, Open-Meteo, Android services, or other service providers may be stored or processed in countries outside your country of residence. We take steps intended to use service providers with appropriate privacy and security commitments.
11. Changes to This Policy
We may update this Privacy Policy from time to time. When we make changes, we will update the date below and publish the revised policy on this page.