Wardrobe privacy

What Wardrobe processes

Wardrobe processes your account identity, uploaded photos, clothing descriptions, style notes, saved plans, outfit history, and feedback to provide the features you request. Photos and relevant style context may be sent to AI services for garment analysis and recommendations. Review suggestions before relying on them.

Optional Google Calendar connection

Google sign-in alone does not grant calendar access. If you choose to connect Calendar, Wardrobe requests read-only access to your calendar list and events so you can select calendars and request an outfit for a particular day. Wardrobe does not create, change, or delete Google Calendar events.

Opening a week reads event titles and times from your selected calendars for display. When you explicitly include Calendar in an outfit request, Wardrobe also uses event locations for the reviewed dates, up to seven days per request. It does not request attendee lists or event descriptions. Outfit-request context is sent to OpenAI to generate your personalized recommendations. Do not include a calendar whose contents you do not want processed for that purpose.

Google access tokens are handled server-side through Clerk. Selected calendar identifiers and connection settings are stored in Wardrobe. Raw event responses are not saved to the Wardrobe database or Zep style memory. Generated outfit explanations can reflect event context and are saved with your recommendations. Calendar contents and identifiers are excluded from product analytics and session replay.

Disconnecting Calendar in Wardrobe stops further reads and deletes saved calendar-derived recommendations, including planned and worn entries, after confirmation. This leaves your other wardrobe data and Google sign-in intact. You may separately revoke access for Wardrobe in your Google Account connections.

Voice input

Recording starts only when you choose Dictate and grant microphone permission. Recordings are limited to 60 seconds. Choosing Transcribe sends the recording to OpenAI; you can edit the resulting text before requesting an outfit. Wardrobe handles audio in server memory rather than storing it in its database or style memory, and deletes its temporary native recording file after use or cancellation.

Analytics and reliability

PostHog receives bounded usage events and sanitized errors to help improve the app. Where session replay is enabled, media and input masking is applied; private photos, style notes, calendar content, and credentials are excluded. Native replay is disabled until its platform masking checks are verified. You can disable optional analytics in the app privacy controls. Essential server reliability logs remain enabled in Axiom.

Service providers and retention

Wardrobe uses Clerk for authentication, Convex for application data and uploaded files, Vercel for web hosting, OpenAI for text, vision, and audio processing, Google Gemini for direct image and text embeddings, Zep for style memory, and PostHog and Axiom for observability. These providers process information needed for their respective functions under their own service terms. Wardrobe does not sell your personal data.

Saved wardrobe data supports your ongoing use of the app. Wardrobe retains your latest 100 outfit recommendations. You can delete pieces and request account-data deletion through the app or the contact below. Provider logs and backups may follow separate retention schedules; deletion is not a promise of immediate erasure from every backup.

Questions and requests

Contact davidschmittgit@gmail.com about privacy, access, correction, or deletion. This notice will be updated when data practices change.