Costume Network privacy policy

Costume Network helps you explore costume ideas, create illustrative previews and save clothing pieces. Contact Costume Network support at support@costumenetwork.com for privacy, deletion or support requests.

Information you choose to provide

We process costume descriptions, search terms, selected photos and extracted clothing descriptions to create costumes and closet pieces. Creating an optional account adds your name, email, profile handle and account identifier. iOS uses email sign-in; web and Android also offer Google sign-in. Google Cloud Identity Platform manages new accounts. Existing legacy Supabase sessions remain compatible.

Drafts, saved costumes, history, wishlist, selected closet pieces and photo preparation files are stored on your device. Account closet pieces and originals are stored privately in Google Cloud Storage. When you explicitly keep a named costume, its brief, selected product facts, owned-piece decisions and a copy of its existing illustrative preview are stored privately with your account. After initial Keep, edits are saved after five seconds idle and before starting New or opening another plan. Autosave continues as version history grows; earlier versions are not removed automatically. History is loaded in pages of fifty versions. Keeping, autosaving or opening starts no AI generation. Unkept prior drafts are retained only on this device, up to twenty active drafts, until you remove or clear them. Original input photos remain in their existing device or guest workflow storage. Guest workflows and imported photos also use private server storage to support asynchronous completion and recovery. Camera, photo-library and microphone access are optional and requested when you use the corresponding feature. Native speech recognition uses the device operating system’s recognition service.

AI and service providers

Before a new AI request, the app asks for explicit permission. The text and photos you choose go through our Google Cloud service to OpenAI to analyze garments, create descriptions and cutouts, and generate illustrative previews. Search terms derived from your idea are sent to ScrapingBee for retailer retrieval. AI can infer details incorrectly; results are not exact try-on. Choose only photos you have permission to use and avoid sensitive information.

Idea first also sends generated component crops (not your personal photos) to SerpAPI’s Google Lens search to retrieve visual product matches. See SerpAPI’s privacy policy. These providers process data to operate the requested services. See OpenAI’s privacy policy, Google Cloud’s privacy notice and ScrapingBee’s privacy policy. Retailer links open external sites governed by those retailers’ policies. We do not sell personal data or use it for cross-app advertising tracking.

Optional completion notifications

When enabled, iOS and Android ask for notification permission after you start a costume or clothing-photo import. We privately store a device push token with your guest workflow for up to one day and send the token, a generic completion message and the original costume or import request identifier to Expo, Apple or Google for push delivery. No costume description, photo or image URL is included. Tokens are removed from active delivery records after an attempted send, cancellation or expiration; private storage backups follow the retention policy below. Disable notifications in your device settings at any time. Starting New or clearing device data cancels the pending subscription when connected; a message already sent may still arrive. Browser push is not supported.

Operational information

The service records request identifiers, account or guest identifiers, network IP information, errors, stage durations, provider usage and daily budget information for authentication, abuse prevention, reliability and cost limits. These records may be associated with your requests. We do not request precise location, contacts, payment information or advertising identifiers.

Your choices and deletion

You can decline AI processing and browse saved content. In Settings, turn off AI permission to block new requests; a request already transmitted can finish. You can use styling as a guest. An account is optional and enables a shared closet.

For GCP accounts, choose Settings → Delete account and confirm. This removes the authenticated GCP identity, profile, saved account closet, associated closet originals and cutouts, and pending sign-in records. It also clears this device’s credentials, drafts, history, wishlist and prepared or cached photos. Another device may retain its local history until you clear its app data or uninstall; the deleted account cannot sign in again.

Legacy Supabase accounts are outside this deletion endpoint. Contact us to request deletion of a legacy account, guest server workflows, operational records or data that is not linked to your GCP account. Include enough information to identify your request without sending passwords or access tokens. Deleting a GCP account does not automatically remove independent guest styling workflows from the server.

Retention and protection

Account closet data remains until deletion. Guest server workflow data currently has no automatic expiry; you can request its deletion by email. Sign-in flow records expire for access after ten minutes and are eligible for storage deletion after two days. Active objects removed from Google Cloud Storage may remain in protected, non-public soft-deleted backups for up to seven days. Minimal deletion receipts contain hashed identifiers and a completion status to reconcile interrupted requests, and follow the sign-in storage lifecycle. Operational records are kept for service administration and can be included in a deletion request; we do not claim an automatic expiry for them.

Private cloud storage, authenticated access, expiring image links and device secure storage protect data. Provider retention follows their service policies. No method of storage or transmission is completely secure. Changes affecting AI sharing require renewed app permission. This policy is accessible from Settings and the consent prompt.