Privacy Policy

Effective and last updated: July 12, 2026

Clueless Creations LLC ("Clueless Clothing," "we," "us," or "our") provides the Clueless Clothing mobile app, website, and related services. This policy explains what information those services collect, why we use it, when processors receive it, and how you can control or delete it.

1. Information We Collect

Account and authentication information

We collect a Firebase user identifier, email address, authentication provider, and any display name or profile photo you choose to provide. Firebase Authentication processes passwords, Apple credentials, and Google credentials. Clueless Clothing does not receive your raw password.

If you use Google Sign-In, our app requests the email scope. Google and Firebase may give us your Google account identifier, email address, display name, and profile photo when available. Clueless Clothing does not request or retain your phone number, contacts, or location through Google Sign-In. A data category declared by the bundled Google Sign-In SDK does not by itself mean Clueless Clothing receives or stores that category.

Wardrobe, outfit, and preference information

Information you add or create may include:

• Wardrobe photos and files you select from the camera or photo library
• Image crops, generated garment images, labels, colors, categories, notes, and tags
• Outfits, plans, calendar dates, occasions, wear history, and wardrobe statistics
• Onboarding answers, including optional pregnancy or postpartum status, style, fit, sizing, budget, and other profile preferences
• Outfit reactions, wear outcomes, dismissals, edits, ratings, and written feedback

Wardrobe photos are stored with your account and may be sent to an AI processor when a feature needs image extraction, classification, description, moderation, or generation.

If you provide an optional pregnancy or postpartum status, we save it to your profile to tailor fit-sensitive styling and recommendations. It is linked to your account, is not used for analytics, advertising, or cross-app tracking, and can be changed or removed from your profile.

AI styling conversations and other user content

Katire conversations are saved to your account so you can see conversation history, continue after an interruption, and recover from a failed response. Saved content may include your messages, Katire's responses, conversation metadata, feedback, and images or wardrobe references attached to a conversation. This is user content linked to your account, not anonymous transient text.

We use this content to answer styling questions, ground recommendations in your wardrobe, maintain conversation history, prevent unsafe or off-topic behavior, and troubleshoot failures. Actions you record, such as wearing, dismissing, editing, or rating an outfit, may improve future outfit ranking and personalization for your account.

Optional precise location

If you grant location permission, the app may read your device's current latitude and longitude. Authenticated coordinates are sent to our backend, sent to OpenWeather to obtain a forecast, and saved with your account together with a city name when available. We use that saved location for weather-aware planning and Katire's styling context.

Location is optional. You can deny or later revoke the device permission, but doing so stops new readings and does not automatically erase a location already saved to your profile. You can remove saved account data through the choices described below.

Purchases and subscriptions

Apple or Google processes in-app payments. RevenueCat receives app user and purchase identifiers, receipt or transaction information, entitlement status, renewal state, and related subscription events so we can unlock paid features. We do not receive or store your full payment card number.

Usage, device, and reliability information

We and our processors may collect:

• Product interactions, feature use, onboarding and paywall events, and timestamps
• Firebase installation and app-instance identifiers, app version, device type, and OS
• Crash reports, performance measurements, request context, and diagnostic logs
• Push notification tokens and delivery status
• Security, fraud-prevention, rate-limit, and App Check signals

We use Firebase Analytics for product analytics and Sentry for reliability monitoring. We configure these systems to limit direct personal information, but diagnostic context can still be associated with an account or device when needed to investigate a problem.

Website, support, and email information

If you sign up on the website, contact support, or receive email from us, we may collect your email address, message, attachments, preferences, campaign source, and delivery, unsubscribe, open, or click events when those features are enabled. Hosting providers may also process IP addresses, browser details, and standard request logs for security and delivery.

If you choose Allow analytics, Google Analytics 4 collects website page views, URLs and referring pages, session and engagement statistics, campaign parameters, approximate location, and browser, language, screen, and device information. Google Analytics uses first-party _ga cookies and a pseudonymous browser client ID; these cookies may remain for up to two years unless you clear them, revoke consent, or your browser shortens their lifetime. We keep Google advertising storage, advertising user data, and ad personalization denied. Cloudflare Web Analytics may separately process minimal page-load timing and performance data without tracking individual visitors across Cloudflare customers. We use this information to measure acquisition, diagnose page performance, and improve the website.

When you arrive through a campaign and allow analytics, we also store a first-party cc_attr attribution token for up to 30 days. It can contain sanitized campaign parameters, landing-page path, referring page, and timestamp so a signup or app handoff can be attributed to the visit. Rejecting or revoking analytics removes this optional token.

If you choose Allow analytics and you reached this website from a Meta advertisement, we also load the Meta pixel and measure whether that advertisement led to a web subscription. This uses a _fbp browser cookie set by Meta and a _fbc cookie holding the click identifier Meta adds to the link you followed. When a web subscription completes, our server sends Meta a purchase event containing those identifiers, the purchase amount and currency, and your email address in an irreversible hashed form so it can be matched without being read. Meta acts as an independent controller of this measurement data. This applies to the website only; it does not use your device advertising identifier, and it is not used to build advertising profiles by us.

Google Analytics and the Meta pixel are denied by default and do not load until you allow them. Declining also stops the server-side purchase measurement described above. You can reject them without affecting the website or app and can change or revoke your choice on our Privacy Choices page.

2. How We Use Information

We use information to:

• Authenticate your account and keep it secure
• Store and display your wardrobe, outfits, plans, and conversation history
• Extract clothing details and generate outfit or styling recommendations
• Personalize and rank future recommendations using your choices and recorded outcomes
• Provide weather-aware planning and Katire context when you enable location
• Verify purchases, manage entitlements, and restore subscriptions
• Send service messages, optional marketing, and push notifications
• Measure feature performance, diagnose failures, prevent abuse, and improve the Service
• Comply with law, enforce our terms, and protect users and the Service

3. AI Processing

Depending on the feature and current provider route, user content may be processed by OpenAI, Google Gemini, Anthropic, or Black Forest Labs. We send the content and context needed for the requested feature, which can include messages, wardrobe attributes, or an image. Provider availability and the model used can change without changing the purpose described here.

We do not sell your prompts, chats, or wardrobe photos, and we do not use them to train a public, general-purpose Clueless model. AI providers process content under their business or API terms and configured controls, which may include limited retention for security, abuse prevention, or service operation. Authorized personnel may inspect limited content when reasonably necessary to resolve a support, safety, security, or reliability issue.

4. Processors and Other Recipients

We disclose information only as needed for the following roles:

• Google Firebase and Google Cloud: authentication, Firestore database, Cloud Storage, backend hosting, messaging, analytics, App Check, remote configuration, and related infrastructure
• OpenAI, Google Gemini, Anthropic, and Black Forest Labs: AI styling, text or image understanding, embeddings, moderation, and image generation, depending on the feature route
• OpenWeather: forecast lookup using the coordinates submitted by the app
• RevenueCat, Apple, and Google Play: purchases, subscription status, entitlement management, refunds, and app distribution
• Sentry: crash, error, and performance monitoring
• Resend and other email infrastructure: account, lifecycle, support, and marketing email delivery and events
• Cloudflare: website hosting, delivery, and security logs
• Authorities or transaction participants: when required by law, needed to protect rights or safety, or involved in a merger, financing, acquisition, or sale

We do not share wardrobe photos, styling conversations, or precise location with data brokers or advertising networks, and we do not use Apple's advertising identifier. Where you have allowed analytics on this website, we share the limited advertising-measurement data described in Section 1 with Meta so that a web subscription can be attributed to the advertisement that produced it. Some laws treat that as sharing for cross-context behavioural advertising; it happens only with your consent and you can withdraw it at any time on our Privacy Choices page.

5. Retention and Deletion

Account content is generally kept while your account is active so the app can provide sync, history, recovery, and personalization. You can delete individual wardrobe items, outfits, or conversations where the app provides that control.

When you delete your account, our backend deletes the account's Firebase Storage files, user-linked Firestore records and subcollections, and Firebase Authentication record. It also requests deletion of the RevenueCat subscriber record. Account deletion does not cancel a subscription managed by Apple or Google, and those stores may retain transaction records under their own legal and accounting obligations.

Some limited records may remain for fraud prevention, security, tax, dispute, or other legal obligations. Processor logs, aggregated or deidentified analytics, and disaster recovery backups may remain until their normal retention cycles complete. We do not use retained records to continue providing a deleted account with personalized service.

6. Your Choices and Rights

Visit Privacy Choices and Account Deletion for the current in-app deletion path, the off-app request path, subscription-cancellation instructions, permission controls, and ways to request access, correction, a copy, or deletion of your information.

You can also:

• Revoke camera, photo, notification, or location permission in device settings
• Use the unsubscribe link in marketing email or visit Email Preferences
• Contact us to object to or restrict processing where applicable

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal information, withdraw consent, or appeal a decision. California residents may also request information about collection and disclosure. We do not sell or share personal information for cross-context behavioral advertising, and we will not discriminate against you for exercising a privacy right.

7. Security

We use access controls, authenticated APIs, encrypted network transport, private storage, secret management, monitoring, and other administrative and technical safeguards designed for the sensitivity of the information we process. No system is completely secure, so we cannot guarantee absolute security.

8. International Processing

Clueless Creations LLC is based in the United States. We and our processors may process information in the United States and other countries. Where required, we rely on contractual or other lawful transfer mechanisms.

9. Children

Clueless Clothing is not directed to children under 13, and we do not knowingly collect personal information from a child under 13. If you believe a child provided information to us, contact us so we can investigate and delete it.

10. Changes to This Policy

We may update this policy when the Service or our practices change. We will update the date at the top and provide additional notice when required by law.

11. Contact Us

Clueless Creations LLC is responsible for the information described in this policy. For privacy questions or requests, email eduardo@clueless.clothing or visit Support.