WearHue Privacy Policy

Effective date: November 4, 2026

Overview

WearHue offers an on-device clothing color editor and an optional cloud wardrobe. The cloud features use Google sign-in through Firebase Authentication, private Google Cloud storage, Google Play credit purchases, and OpenAI image editing. Cloud generation starts only after you confirm it.

Accounts and purchases

The local editor does not require an account. Optional cloud features use your Google/Firebase account identifier and the profile information provided during sign-in, such as your email address and display name. Google Play handles checkout; WearHue does not receive your payment card details. The server verifies purchase tokens, grants credits, and consumes verified purchases. Minimal purchase ownership, token hashes and transaction records are retained to prevent replay and reconcile refunds. Encrypted tokens may be retained while consumption is pending.

Photos and garment descriptions

The Android photo picker provides only the photos you select. Camera capture uses an installed camera app and an app-private temporary file. Local editing photos, masks, brush corrections and color settings stay on your device. Optional wardrobe imports are uploaded to private storage. After generation confirmation, the selected person, original identity reference and prepared garment image may be sent to OpenAI for try-on. Garment creation sends the selected garment reference and your optional clothing description of up to 160 characters. The service removes EXIF/location metadata before storage. Photos, descriptions, exact colors, file paths, masks and brush coordinates are not sent to Analytics.

Storage and deletion

Person inputs and prepared garment references become eligible for scheduled deletion after 24 hours; generated job-result copies after seven days. Personal wardrobe garments remain until you delete them or your account. Cleanup retries transient failures. The raw optional description is cleared when the job completes, fails or expires; an unconfirmed request may remain on your device until recovery completes. Deleted cloud objects may remain recoverable under the storage provider’s seven-day soft-delete retention. Saved gallery images and local designs remain under your control. Account deletion removes the cloud wardrobe and results and deletes the Firebase sign-in identity; minimal account tombstones, purchase ownership and transaction records remain for replay prevention and refund reconciliation. Deleting a WearHue account does not delete your Google account.

How to delete your account

In WearHue, open Settings, choose “Delete account and photos”, and confirm. To request deletion without the app, follow the account deletion page or email seok7302@gmail.com from the address associated with your WearHue sign-in. We may ask you to verify ownership. Never send your password, purchase token or payment card details. Deleting the account removes its remaining credits. Google Play refund requests remain subject to Google Play’s process.

Usage analytics

Firebase Analytics is enabled by default and explained on the first screen. You can turn “Share usage analytics” off in Settings; the choice is stored on this device. When enabled, Firebase receives standard app-instance, session, device and lifecycle information and limited events about source selection, import/segmentation, previews, correction, verified saving, wardrobe use and generation outcomes. The SDK can derive approximate location from a masked IP address. Automatic screen reporting, advertising ID collection and ad personalization are disabled. WearHue does not attach your account identifier, purchase tokens, photos, prompts, file paths, masks, brush coordinates or exact colors to custom Analytics events. Turning collection off stops further collection on this device; events already sent may remain under Google’s retention settings.

Advertising and privacy choices

Android versions with advertising enabled use Google AdMob to show an occasional interstitial after a successful photo save, when you dismiss the save confirmation. The Google Mobile Ads SDK may collect and share IP address (which may indicate approximate location), app and ad interactions, diagnostics, and device or account identifiers for advertising, analytics, and fraud prevention. WearHue excludes Android advertising ID permissions and does not send your editing photos, masks or color choices to AdMob. The Google User Messaging Platform manages ad consent where required. If applicable, you can change your choices under Settings → Ad privacy choices. Ad privacy choices are separate from the Usage analytics setting. How Google uses information from apps that use its services.

Local working files

App-private source photos, masks, corrections and temporary exports are excluded from Android backup. Older working files are pruned after seven days and storage is bounded. Preview caches may be cleared by Android. Uninstalling or clearing app storage removes app-private files. Saving to Photos happens only after you choose Save and the app verifies the saved file can be reopened. You can remove exported images with your gallery or file manager. The local editor works offline; cloud features require a network connection.

External services

Google/Firebase, Google Cloud, Google Play and OpenAI process the information needed to provide their respective services. OpenAI has separate API data controls and retention; WearHue’s deletion periods do not describe or directly delete provider-held records. No zero-retention arrangement is claimed. See the provider information linked below.

Children and contact

WearHue is not designed for children under 13. Questions about privacy or deletion can be sent to seok7302@gmail.com. This policy will be updated when the app’s data practices change.

Request account deletion · Google Analytics data practices · OpenAI API data controls