Privacy Policy
What we collect, why, who sees it and how to make it go away.
Effective date: November 6, 2026
This update explains background try-on processing, retained previews, DAILY preferences and current account controls. Earlier-version storage disclosures still apply.
- 1. Who we are
- 2. The short version
- 3. What we collect
- 4. Why we use it
- 5. Photos, likeness and try-on
- 6. Who we share it with
- 7. How long we keep it
- 8. Deleting your account and your choices
- 9. Children
- 10. Security
- 11. Where your data lives
- 12. Your rights
- 13. Changes to this policy
- 14. Contact
1. Who we are
KNOWE is made by KNOWE Studios, Inc., a Delaware corporation ("KNOWE", "we", "us"). This policy covers the KNOWE iPhone app, the two extensions bundled with it (the KNOWE Safari extension and the KNOWE share-sheet extension) and the website at knowe.app (including knowe.design, which points to the same site). Together we call these the "Service".
KNOWE is a styling companion. FOR YOU recommends outfits, CLOSET keeps your clothes and wishlist pieces, OUTFITS holds the looks you choose to save and CALENDAR helps you plan outfits with friends. Doing that well means handling personal information, including photos of you. This policy also covers information kept from earlier versions and optional features described below, even when those features are not available in your current app.
2. The short version
- We collect what you give us to style you: your email, name, birthdate, sizes, notes, selected photos and preferences, along with the looks you like, save and try on. Earlier versions also recorded love and pass choices.
- Your full-body try-on photo is kept on your phone. When you approve a try-on, the photo and selected outfit information pass through Supabase to OpenAI. Background requests use temporary private input storage so the work can finish after you leave the app. The photo is used to generate a preview, not to recognise or identify you.
- We don't sell your information and we don't share it for cross-context advertising. There are no ad networks in the app and no tracking across other companies' apps or websites.
- A small number of service providers process data for us (hosting, image generation, product search, push notifications, product analytics and crash reporting). Every one of them is named in section 6.
- You can delete your account from Account → Privacy & account at any time. That removes your data and your photos from our systems.
- KNOWE is for adults. You must be 18 or older to have an account.
3. What we collect
Almost everything below is optional. The app works with an email and a password; the rest makes styling better and you choose how much to add.
Account and profile
- Sign-in details: your email address and password. We store only a salted hash of the password, never the password itself.
- Profile: the name, username, gender or clothing-style selection, birthdate, city, clothing sizes, body notes, budget, favourite brands and profile photo you choose to provide. Earlier versions may also have collected favourite artists and shows.
- Recommendation and notification preferences: your DAILY refresh schedule, style preferences, budget and time zone; the alert categories you choose; and notification read, dismissal and clear-history state. Earlier versions may also have offered editorial-drop subscriptions.
Photos and images
- Full-body try-on photo: the photo you add so virtual try-on can show looks on you. It is stored on your phone, with a copy in the shared app container for the extensions. When you approve a background try-on, its input, including your photo and selected outfit information, is uploaded to private Supabase storage for the job. That input is processed through OpenAI and scheduled for cleanup as described in section 7. Not every repeat request needs a new model call: KNOWE can reuse a compatible preview already made for your photo and outfit.
- Try-on results: generated images include your likeness. Completed previews are retained privately under your account so you can return after leaving the app and reuse a result without another generation. A preview does not automatically appear in OUTFITS: you choose Save to add it there. We also keep job status, result references, hashes used to match repeat requests and references to the selected clothing. These support recovery, cache reuse and identifying unowned pieces in a saved outfit. Saving is separate from sharing. Some older results, including BUILD A LOOK images saved by earlier app versions, remain at long, random public addresses. The update does not move those older public copies into private storage. In versions that offer a background choice, changing it processes the result again to cut out the figure and place it on the chosen background.
- CLOSET photos: photos of pieces you add and standalone clothing images we generate, including images associated with wishlist items. Saved clothing images are stored in a folder tied to your account. The optional library scan and selected source photos follow the review rules below. Product photos you confirm for Gmail-imported items use separate private storage. Earlier versions called this collection CAPSULE.
- Photos you submit to identify a piece or find similar pieces, including photos you share to KNOWE from another app. These are stored in a folder tied to your account in our storage, at a link the search provider can read so it can run the image search.
- Pictures from Instagram, Facebook and Threads: when you save a post from one of these sites (by sharing it to KNOWE, saving it from Safari or using a link-save feature, including SHORTLIST or LOOK BOOK in earlier versions), our server tries to store a copy of the post's picture in a folder tied to your account in our storage. It does the same for any other link whose picture comes from their servers. We keep a copy because their picture links stop working after a few days, which would leave your saved piece blank. If our server can't read the post or can't copy its picture, the saved item keeps their own link to the picture, if the app finds one, and that link stops working after a few days. A copy can also be made for a save that doesn't finish, or each time you save the same post; those extra copies aren't shown anywhere and are kept like the others (section 7). For other link previews, we ordinarily keep the website's image address. Separate clothing-image extraction and the optional receipt-photo import described below can create stored images when you choose those features.
- Who can open a stored picture: current try-on previews and new Closet-generated outfits use private storage. You and friends allowed to see a shared look receive links that stop working within an hour. Event outfit uploads also use private storage and event-based access. A new Closet outfit requires you to share that specific outfit before friends can view it, even if you previously chose to share all built looks. Other stored pictures, including capsule photos and closet images, older public BUILD A LOOK or try-on copies, photos submitted to identify a piece, profile photos and the social-post copies above, remain at long, random addresses. Anyone who has one of those public addresses can open the picture, even after you stop sharing the item or delete it, until the picture itself is deleted (section 7). This public-address rule does not apply to newly generated Closet outfits or product photos saved for Gmail-imported items. Receipt product photos are accessible only through their owner's Closet; temporary image links can work until they expire, within an hour.
Event outfit photos: when you add an outfit to a CALENDAR event, KNOWE stores a private event-specific image and its association with you and the event. This can be an uploaded photo or a copy of a saved outfit. People with permission to view that event can see the shared outfit through temporary links. Adding it to an event is a sharing action; simply saving a try-on to OUTFITS is not.
Photo library scan and clothing review
You can choose outfit photos yourself or ask KNOWE to scan the photo library that iOS allows it to access. With limited access, only the photos you allow are available. Scanning looks for people and clothing on your iPhone; it does not identify people or compare faces. The scan works in batches that you can continue. Downloading photos that are only in iCloud requires a separate choice in the import screen. You can also include other photos in the local review.
Found photos start unselected. Local scanning does not send their images to KNOWE's server or an AI provider. You review the photos and choose which ones to use. Each import then asks you to approve sending that selection through Supabase to OpenAI to find the clothing. This is separate from iOS photo access and the app's general photo notice. Choose photos of yourself or someone who has agreed and exclude other people's clothing. KNOWE does not determine who owns an item from a photo.
Before adding anything, you can edit each proposed item's name, brand, category, colour, material, size, notes and style or occasion tags. Confirm that you own the item and choose whether to include it. Suggested details can be wrong or incomplete. When you choose to add reviewed items, their selected source photos and reviewed details are sent to OpenAI to generate standalone clothing images. The extraction service processes source photos for those requests without saving them to our storage. This does not remove the provider retention described in sections 6 and 7.
Only the items you confirm are added to your CLOSET. Generated clothing images use the public-address rules above, including an image generated during an add attempt whose item does not finish saving. Closing the import or signing out clears its temporary photo copies from the app; it does not delete photos from your Photos library. Saved clothing details and generated images follow the existing Closet access and retention rules.
Taste and saves
- Your explicit DAILY feedback, including thumbs-up choices and any ratings or reasons submitted in earlier versions, associated with the recommended outfit and the time you gave the feedback. The recommendation process uses a limited set of recent feedback examples and the outfit details to learn combinations you prefer. It does not publish your feedback to other members. Earlier love and pass records can include the image, occasion, decision time and position in the deck.
- Clothing and wishlist items in CLOSET, saved OUTFITS and their notes, categories, prices and product links. This also covers records from the earlier CAPSULE, SHORTLIST and LOOK BOOK collections.
- When you save a link, by pasting it or sending it from Safari or the share sheet, our server opens that page the way a browser would, without signing in to the site, to read its picture, title and price. It sends the site the address and nothing about your account. If our server can't read the page or finds no picture on it, the app reads the page from your phone instead, sometimes by opening it out of sight. The site, and any analytics or advertising tools it uses, see that like a visit from your phone, under the site's own privacy policy, and cookies the site sets are kept in the app on your phone.
- Recommendation history and taste summaries derived from your preferences and permitted activity, including the taste profile called MY SIGNATURE in earlier versions. DAILY uses clothing details, your shopping preferences and recent outfit feedback to recommend varied combinations. Your full-body photo is not needed to create these recommendations. Gmail-derived details remain subject to the narrower rules below.
Optional Gmail receipts
Gmail receipt import is a limited private pilot. If it is enabled for your account and you connect Gmail from CLOSET, KNOWE can help you find clothing purchases and turn the items you choose into editable closet entries. This connection is separate from your KNOWE sign-in.
- Permission and searches: Google grants read-only access to your email messages and settings. This permission is broader than receipts or a date range. KNOWE limits its searches to likely receipts within the dates you choose, and searches only when you ask. It first reads sender, subject and date information so you can select the emails to review. It does not send, change or delete mail, monitor your inbox in the background or download attachments or images during the header search. Choosing Review clothing after the processing notice starts selected-receipt processing and automatic product-photo lookup, as described below. Header searches alone do not start that lookup.
- The connection: Google's sign-in software stores access credentials in your iPhone's Keychain. KNOWE associates the connection with your current KNOWE account on that device. Gmail access tokens are not sent to KNOWE's servers. Google receives the connection request and the searches and message requests made from your device.
- Selected receipts: only after you select receipts and agree to processing does the app read their contents and send their text, sender, subject and date to KNOWE's server functions, hosted by Supabase. We first try to identify purchases from structured receipt details. When needed, limited purchase excerpts go to OpenAI to identify clothing. We remove common contact, address and payment details before that step where we can, but automated removal can miss personal information. You can decline processing or choose different receipts. Receipt-import processing does not send product photos or their addresses to OpenAI.
- Automatic product-photo lookup: after the app explains the processing and you choose Review clothing, it extracts clothing details from the selected receipts and automatically looks for product photos on supported official retailer websites. It can use a public product-page link associated with an item in the selected receipt. Otherwise, it sends the extracted item name, brand and colour, with known retailer context when available, through KNOWE's Supabase server to Searlo to find public product pages. This happens before you edit or approve the proposed clothing details. Editing the item name, brand or colour during review can repeat the lookup using the changed details. The search does not send the original receipt, its subject or sender, Gmail credentials, photos or receipt/product-page URLs to Searlo. It does not use images embedded in the receipt, email thumbnails or tracking links. Photo saving remains optional.
- Website requests and your review: the app automatically checks supported official product pages and requests a matching product image identified by the page's product metadata. Your device contacts the retailer and its image-delivery provider without cookies, page scripts, Gmail credentials, receipt text or KNOWE account details. The hosts receive your IP address and the requested public page or image address under their own privacy policies. The app does not open email attachments or fall back to receipt images or search-result thumbnails. Review the retailer, product title, colour and photo, then confirm This is my item and color before saving it. Automated lookup can find a different product or colour, or no usable photo; KNOWE does not treat its result as a guaranteed match. You can remove a preview and save clothing details without a photo.
- Saving a product photo: the preview stays on your device until you choose to add it. Use Remove photo to discard it and import details only. Adding a selected item saves its confirmed product photo too. Saved copies use KNOWE's private storage, after embedded image metadata is removed. To add a missing photo to an already-imported item, review and confirm it, then choose Add photo to CLOSET; this does not create another item, replace an existing photo or change its reviewed details. Receipt photo lookup and import do not send product photos, product-page links or image addresses to OpenAI.
- What you save: you review and can edit each proposed item's name, brand, category, colour, size and material before adding it. Product photos are optional; the import works without one. We keep the clothing fields you approve, plus private hashed identifiers and import status that prevent the same purchase from being added twice. These identifiers are not copies of the email or its subject, sender or order number.
- Styling your imported clothes: the resulting entries are kept in your own Closet. When you request closet recommendations or choose clothing for a try-on, the relevant saved garment details can be processed by OpenAI for that request. This does not send the original receipt again. A product photo you saved can also be sent to OpenAI when you later explicitly select that item for an image try-on; importing the receipt or loading its photo does not start a try-on. Apart from the product-photo lookup for the receipt review you request, imported receipt details are excluded from automatic taste profiles, product sourcing for recommendations and stylist booking drafts, and are not automatically shared with other members or stylists. Saving a newly generated Closet outfit keeps it private. You can separately choose to share that specific outfit; saving it again does not undo sharing you already chose.
See section 7 for retention, and section 8 for disconnecting Gmail and deleting imported items.
Styling bookings and messages from earlier versions or where offered
- When you book a stylist: the occasion and its type, the date, the service tier and delivery speed, your budget, the location you enter (name, map coordinates and place reference), what you're picturing, moment notes, pieces you'd like styled around and friends you tag.
- The looks drafted for your booking, and messages between you and your stylist in the session thread.
Friends, invites and sharing
- Friend requests and friendships, and the usernames you search for.
- CALENDAR events you create, their details, the people you invite and the outfits each participant chooses to share. If a version offers invitations by phone number, we store the number with the invite so its link can be redeemed.
- In versions that offer device-calendar sync, the title, date, time and place of upcoming events from the calendars you choose, along with the calendar name, for the next three months. This requires you to turn sync on and grant iOS access. We never read the guest list, notes or attachments and never write to your calendar. Turning sync off requests deletion of the imported occasions; earlier versions expose this control in MOMENTS or Profile.
- Your outfit-sharing choices and event access permissions. Older versions can also have item-sharing choices in LOOK BOOK or SHORTLIST and public shortlist links you created by tapping Share. Anyone with such a public link can see your name and the listed items.
Voice
- If you describe a piece by voice, the app records your microphone only while you hold to speak and transcribes it. The transcript is used to fill in the piece's details.
The Safari extension
- When you choose Save to wishlist on a product page, the Safari extension reads the page's title, image and address and passes them to KNOWE. The current app imports the product as a wishlist item in CLOSET. The extension can also run a try-on using your chosen photo. Earlier versions saved links to SHORTLIST.
- When you send something to KNOWE from another app's share sheet (a link from Chrome or a retailer app, a pin from Pinterest, a post or a photo from Instagram or Photos), the share extension receives only what you shared: the address and title, or the photo and its caption. It can also run a try-on on it using your saved photo. It reads nothing else from that app, and it only runs when you pick KNOWE in the share sheet.
- The extension shows a small tab on pages so you can save from anywhere, but it sends nothing until you act. We don't collect your browsing history.
Device and usage
- A push notification token for your device, and whether it's a production or test build.
- In-app events such as screens viewed, taps on products and outbound links, app opens and which features were switched on for you, tied to your account so we can see what's working. These go to our own database and to PostHog, our analytics provider (section 6).
- With each of those events, the details of your phone and the app: app version and build, iPhone model, iOS version, screen size, language, time zone, whether you're on Wi-Fi or cellular and whether the build came from TestFlight. Your IP address reaches PostHog with each request, as it does with any server. PostHog discards it instead of storing it with the event, and doesn't turn it into a location. We never send your email or name to PostHog.
- A record of each request to our image and language models (which feature, when, an estimated cost) tied to your account, so we can control spend and stop abuse.
- A few steps that happen on our servers rather than in the app, which our servers send to PostHog (section 6), tied to your account so we can see what's working: whether each try-on finished or why it didn't, with the model and its estimated cost from the record above, and the steps of a styling session you book (booked, looks drafted, a look approved, a change of status) with its tier. These carry no phone or app details, and never your photos, the occasion, notes, budget or location, or anything you typed.
- Issue reports you file from the app, with the screen you were on.
- If the app crashes or hits an error, a crash or error report: what failed and where in the app's code, a short list of what the app did just before (for example, which request failed and its status code) and the phone and app details above, tied to your account. A crash report is sent the next time you open the app. These go to PostHog (section 6). They don't include photos or what's on screen, and never your email or name.
The website and the waiting list
- If you join the list at knowe.app: your email, your three quiz answers (moment, style lean, spend) and any referral code or campaign tags on the link you used.
- If you reserve a founding membership: Stripe handles the payment. We receive and store a Stripe customer reference, the checkout session reference and the amount. We never see your card number.
Support
- Anything you send to support@knowe.app, and reports you file about content or members in the app.
4. Why we use it
- To run the Service: sign you in, generate DAILY recommendations and try-ons, retain previews for recovery and reuse, save the outfits you choose, keep your CLOSET and wishlist, support events with friends and send relevant updates. This also covers existing bookings and messages from earlier versions or where those features are offered.
- To style you well: your permitted clothing details, style preferences, sizes, body notes, budget and outfit feedback help shape recommendations. Current preferences and budget guide the selection while recent likes help rank combinations you may enjoy. Where styling services are offered, the information you provide also helps your stylist. Gmail-derived details remain restricted as described in section 3.
- To keep KNOWE safe and honest: enforce our Terms, review reports, detect abuse and control the cost of the AI features.
- To understand and improve the product: aggregate usage of features and flows and crash and error reports so we can fix what breaks. We don't build advertising profiles.
- To talk to you: account emails such as password resets, replies to support and, if you joined the list, your invitation.
- To meet legal obligations and protect our rights.
If you're in the EEA, the UK or Switzerland, our legal bases are: performance of our contract with you (running the Service); your consent (photos of you, voice, notifications, your calendar, optional Gmail receipt processing and optional profile fields), which you can withdraw at any time; our legitimate interests (keeping the Service secure, improving it and controlling its cost), balanced against your rights; and our legal obligations.
5. Photos, likeness and try-on
This section exists because photos of your body deserve plain language.
- What try-on does. When you approve a try-on, KNOWE processes your full-body photo, selected garment images and relevant outfit details through Supabase and OpenAI. Some requests include an occasion or background choice. The model returns an approximation of you wearing the selected pieces. Background jobs can finish after you leave the app. When a compatible result for the same photo and outfit is already available, KNOWE can return it without another model call.
- Generation, not identification. The photo is used to generate an image. We don't use facial recognition, we don't create or store a face template, faceprint or any measurement that could identify you and we don't compare your photo against anyone else's. To our knowledge the model providers don't either; their terms are linked in section 6.
- Where the photo lives. The original selected photo stays in the app's private storage on your phone, with a copy in the shared container for the extensions. Replacing or removing it in Account → Photos & receipts removes those local copies. Approved background requests also place their input in private server storage so processing can continue independently of the app. Job inputs are scheduled for cleanup after completion or failure; interrupted or unattached uploads become eligible after one day. Cleanup failures can delay removal. See section 7 for retention and provider processing. Removing the local photo does not cancel work already submitted or delete completed previews.
- Results are kept for you. Completed previews are retained privately under your account for recovery and reuse, including when you have not saved them to OUTFITS. Open a ready preview from Notifications and choose Save if you want it in OUTFITS. Saving does not automatically share it. A new Closet-generated outfit also requires a separate sharing action. Earlier public BUILD A LOOK and try-on copies keep their existing public addresses (section 3). Removing a saved outfit or its notification does not delete the retained preview. Its stored image remains until account deletion or earlier removal as described in section 7. Already-issued private links can work until they expire, within an hour; an old public address can work until its picture is deleted.
- Backgrounds. In app versions that offer a background choice, if you change the background of a result, the generated image is sent to remove.bg to cut out the figure, then composited on the background you chose.
- Only you. Add photos of yourself, or of someone who has clearly agreed. Our Terms don't allow try-ons of other people without their consent.
- Your consent and biometric privacy laws. Before your first try-on photo the app shows a consent screen that says what is captured, who processes it, where it lives and how to delete it, and records when you agreed. Current TRY ON results and new Closet-generated outfits follow its private-storage and short-lived-link protections. Older public BUILD A LOOK and try-on copies remain at their existing addresses, as section 3 explains; installing the update does not make them private. You can withdraw your consent at any time. Removing your photo in Account → Photos & receipts prevents using that local photo for new try-ons; it does not cancel a request already submitted. To also delete the try-on images already stored, delete your account, or email support@knowe.app from the address on your account and we'll delete all of them within 30 days. We don't sell, lease, trade or otherwise profit from photos of you and we don't create a face template, faceprint or any other biometric identifier from them. Where a law (for example in Illinois, Texas or Washington) treats photos processed by an image model as biometric data, this section, the retention rules in section 7 and the consent screen, with the older-copy distinction above, are our written policy for it: photos and generated images in our storage are kept only until you delete your account, or until we delete one sooner because you asked, and in any case no longer than 3 years after the last time you used KNOWE. The local try-on photo stays on your phone until you replace or remove it. Private background-job inputs follow the shorter cleanup process in section 7.
6. Who we share it with
We share personal information only in the ways below. We don't sell it, and we don't share it for cross-context behavioural advertising.
Service providers
These companies process data on our instructions to run the Service. Each receives only what the feature needs.
| Provider | What it receives | Why | Where |
|---|---|---|---|
| Supabase, Inc. | Your account, profile, taste data, DAILY preferences and feedback, closet and wishlist records, saved outfits, events, shared event photos, bookings, messages, device token, notification state, uploaded images, temporary background try-on inputs, job and cache records, social-post copies and generated previews, including previews not saved to OUTFITS. If you use Gmail import, selected receipt content during processing, the clothing details and optional product photos you choose to save, the extracted item name, brand, colour and known retailer context used for automatic product-photo lookup during the receipt review you request, private duplicate-prevention identifiers and import usage records. Also generates account emails such as password resets and invitations. | Database, sign-in, file storage and the server functions behind every feature, including receipt processing and saving reviewed clothing. | United States (AWS us-east-1, Virginia). |
| Resend, Inc. | The address and content of each account email (password resets, invitations), sent from hello@knowe.app. | Delivering account emails. | United States. |
| Google LLC (Google Workspace) | Anything you send to our support or contact mailboxes, and our replies. If you connect Gmail, Google also receives sign-in and authorization requests, and the receipt searches and message requests your device makes. | Our support mailboxes; authenticating your optional Gmail connection and returning the mail you ask KNOWE to review. | United States, with Google's data centres worldwide. |
| OpenAI | Your full-body photo, selected garment images and relevant outfit or occasion details when generating a new try-on. Compatible cached previews can be reused without a new generation request. Selected photos used to identify clothes and generate standalone clothing images. Garment, product and editorial images and their text, for extracting pieces, finding similar items and describing looks. Clothing details, product information, shopping preferences and bounded recent outfit-feedback examples for DAILY and closet recommendations. Feedback can include garment names, brands, colours, item types, whether a piece is owned or new, the outfit occasion, purchase total, rating and any earlier feedback reasons. Requests use limited text and request-local item references rather than your account identifier. Your voice transcripts, text describing your swipe and save history and booking details. If you agree to Gmail receipt processing, limited purchase excerpts when needed to identify clothing, without product photos or their addresses during receipt import; saved receipt-derived garment details when you request closet recommendations or select them for try-on, and a saved product photo if you later explicitly use it for image try-on. | Generating try-on and clothing images; identifying garments; composing and ranking DAILY and closet recommendations, including through the OpenAI Decisions API; finding similar products; and, in earlier versions or where offered, editorial selection, taste summaries and stylist booking drafts. Gmail-derived details are limited to the receipt and requested closet features described in section 3. | United States. OpenAI doesn't use data sent through its API to improve its models and keeps requests for up to 30 days only to detect abuse. |
| remove.bg (Kaleido AI GmbH) | A generated try-on image, only when you choose a new background in an app version that offers it. | Cutting the figure out of the image. | Austria (EU). |
| SerpApi, LLC (Google Lens results) | A link to the photo you submit to identify a piece or find similar pieces; editorial images. | Garment identification and visual search. | United States. |
| Searlo | Text search queries (for example, a piece you described by voice or a product name). When you choose Review clothing, automatic product-photo searches can send extracted item names, brands, colours and known retailer context through KNOWE's server. They do not include the original receipt, its subject or sender, Gmail credentials, photos or receipt/product-page URLs. | Web and product search, including finding official retailer product pages during the receipt review you request. | European Union (servers in France). Queries are kept for up to 90 days. |
| Google Maps Platform (Places) | The text you type in the booking Location field and the place you pick. | Location suggestions for bookings. | United States. |
| Open-Meteo | The approximate coordinates of your booking location. No account identifier. | A weather forecast for your moment, used when drafting looks. | Switzerland (OpenMeteo GmbH), with servers in the US and the EU. Request logs are deleted after 90 days. |
| Apple, speech recognition | Audio of your voice notes while you hold to speak. | Transcription. Apple's servers may be used for accuracy; on-device recognition is used when available. | Per Apple's privacy policy. |
| Apple Push Notification service | Your device's push token and the notification text. | Delivering notifications. | Per Apple's privacy policy. |
| Getty Images (Embedded Viewer) | When an app version or surface displays an editorial image through the Getty viewer, your device requests it from embed.gettyimages.com. Getty may receive your IP address and device information and may set cookies under its own privacy policy. | Displaying licensed editorial photography. | United States. |
| PostHog, Inc. | The in-app events described in section 3, with your account id as the identifier, and with each event the app version, iPhone model, iOS version, language and time zone. Your IP address reaches PostHog with each request; PostHog discards it rather than storing it, and doesn't turn it into a location. Crash and error reports from the app, with the same identifier and details. Steps our servers send, with the same identifier but no phone or app details: try-on outcomes with the model and estimated cost, and the steps of your styling sessions with their tier and status. No photos, no session recording, no capture of what's on screen and never your email or name. PostHog also tells the app which features are switched on for you. | Product analytics, crash reporting and feature switches: seeing what's working, finding and fixing what breaks and turning features on gradually. | United States (PostHog Cloud US, AWS us-east-1, Virginia). PostHog acts as our processor and keeps events for 1 year. |
| Stripe, Inc. | Website only. Your email and payment details for founding reservations you made, or make while reservations are offered, at knowe.app. | Payment processing. | United States. |
Retailer websites and image hosts: after you choose Review clothing, the app can automatically request supported official product pages from your device and load matching product images identified in those pages' product metadata. These hosts receive your IP address and the requested public page or image address. They act under their own privacy policies, not as KNOWE's receipt processor. The requests use no cookies and send no Gmail credentials, receipt text or KNOWE account details. They do not start during Gmail header searches. Receipt images and search-result thumbnails are not photo sources. You must confirm a photo before it is saved to your CLOSET.
When you tap Buy or open a product or article, you leave for the retailer's or publisher's site. Their privacy policy applies there. We record that you tapped the link.
Your stylist, for earlier bookings or where offered
When you book, the stylist working on your session sees your booking details, your messages and the profile fields that help them style you (name, sizes, body notes, budget, taste profile and your profile photo if you added one). Stylists agree to use that information only for your session.
Connecting Gmail does not give a stylist access to your mail or receipt-derived closet entries. These entries are excluded from the closet information used to draft stylist bookings.
Friends and the public
Your username and name are visible to members who search for you. Friends' access to saved items follows your sharing settings. New Closet-generated outfits require a separate Share choice for the specific outfit; simply saving one keeps it private. Current TRY ON results and new Closet outfits use private image links that stop working within an hour. Other pictures, including older public BUILD A LOOK and try-on copies, follow the public-address rules in section 3: anyone who already has that public address can still open the picture until it is deleted. A public shortlist link created in a version offering that feature is visible to anyone who has it. People allowed to view a shared CALENDAR event can see the outfits added to that event. If you export or send an outfit picture yourself, the recipient may keep a separate copy; removing it from KNOWE cannot remove their copy.
Legal and business
We may disclose information to comply with law, a court order or a lawful request; to enforce our Terms; to protect the safety of members or the public; or to a successor in a merger, acquisition or sale of assets, in which case this policy continues to apply to the transferred data. Information obtained through Gmail, including clothing details and outfit results derived from it, remains subject to the stricter Limited Use rules below. A business transfer of that information requires your explicit prior consent.
Google data and Limited Use
KNOWE's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. These protections also cover clothing details and outfit results derived from Gmail. We do not sell this information, use it for advertising or credit decisions or use it to train general AI models. Transfers are limited to the features you consent to, security needs, legal requirements or a business transfer you explicitly approve in advance. Human access to identifiable Gmail data requires your specific permission, a security need or a legal obligation. Aggregated, anonymized information may be used for internal operations.
7. How long we keep it
- Photos and generated images in our storage: until you delete your account, and in any case no longer than 3 years after the last time you used KNOWE. This covers completed try-on previews whether or not you save them to OUTFITS, new Closet-generated outfits, event outfit photos, older BUILD A LOOK and try-on copies, clothing images, photos submitted to identify a piece, profile photos and the social-post copies described in section 3. Temporary background inputs follow the shorter cleanup process below. Deleting a saved item removes its listing and the access that listing gave friends, but the stored picture remains until your account is deleted or you ask us to delete it sooner. For private current TRY ON and new Closet images, previously issued links can continue to work until they expire, within an hour. For older public copies and the other pictures stored at public addresses, anyone who already has that address can open the image until it is deleted. Receipt product photos follow the separate item-deletion rule below. To have other stored pictures deleted sooner, email support@knowe.app from the address on your account. Tell us which picture, or ask us to delete every stored picture no longer in your saved items, and we'll do it within 30 days.
- Photo library import: temporary scan copies and editable review state stay on your device until you close the import or sign out. Selected source photos sent for extraction or clothing-image generation are not saved by that service to our storage; provider retention still applies. Generated clothing images, including ones from incomplete saves, follow the stored-image rules above.
- Your full-body photo and background inputs: the local photo stays on your phone until you replace it, remove it or delete the app. A background request's private server input becomes eligible for cleanup once the job is ready or has failed. Inputs left by interrupted requests or uploads become eligible after one day. The worker attempts deletion in cleanup batches; an error or service interruption can leave an input until a later cleanup succeeds or your account is deleted. One day is the cleanup eligibility threshold, not a guaranteed deletion deadline. Provider retention still applies to data already sent for processing.
- Account and feature records: your profile, taste data, recommendations, clothing and wishlist records, saved outfits, job and cache references, events, bookings and messages remain associated with your account while it exists unless you delete an available record or ask us to remove it. Removing a DAILY thumbs-up deletes that current feedback record; previously generated recommendations are not rewritten. The recommendation process currently considers a bounded recent feedback window, not every past rating. That selection window is not an automatic deletion deadline for other account records.
- Gmail receipt import: receipt headers and review state are temporary on your device. KNOWE processes selected email text for the request without storing the raw email in your account or including it in analytics or error logs. This is not a promise that processors retain nothing: the provider retention rules below still apply. Approved clothing fields and optional private product photos remain with the item until you delete it or your account, subject to the 3-year inactivity limit above. Deleting the item removes its Closet access and requests deletion of its stored product photo. Already-issued temporary links can work until they expire, within an hour; file deletion can fail and require cleanup later, including account deletion or the inactivity sweep. A photo loaded only for review is not saved to your account unless you choose to add it. Private duplicate-prevention identifiers remain even after an item is deleted, so importing the same receipt does not restore it; these identifiers and import usage records are deleted with your account. Disconnecting Gmail leaves clothing and product photos you already imported in place.
- Usage events and AI request records: up to 24 months in identifiable form in our database, then de-identified (the link to your account is removed) or deleted. The copy of the usage events, crash reports and error reports that PostHog holds is kept for 1 year. When you delete your account, our records are de-identified straight away; the copy at PostHog keeps your account id, which no longer points to anyone once the account is gone, together with the device details described in section 3, and expires on that 1-year schedule.
- Waiting-list entries: until we've sent invitations for the launch, or earlier if you ask us to remove yours. Founding reservation records are kept as long as needed for your membership and for tax and accounting law.
- Support email and reports: up to 2 years after the matter is closed, so we can follow up and show how a report was handled. Issue reports you file from the app are deleted with your account.
- Backups: our database provider keeps rolling backups for a short period (7 days). Deleted data drops out of backups on that schedule.
- Service providers: the AI providers above may retain requests briefly for abuse monitoring under their own terms (from about an hour at remove.bg to 30 days at OpenAI) and, on the tiers we use, don't use your content to train their models.
8. Deleting your account and your choices
Delete your account
In the current app, open Account → Privacy & account → Delete account and confirm. Earlier versions place this under Profile. This permanently deletes your account, profile, taste data, recommendations and feedback, saves, clothing and wishlist records, job and cache records, bookings and messages, friendships and invites, event participation and the images stored under your account. Stored images include private job inputs, completed try-on previews, older BUILD A LOOK copies, clothing images, event outfit photos, receipt product photos, identification photos, profile photos and stored social-post copies. It cannot be undone. Copies that another person has already exported are outside KNOWE's control. If you cannot get into the app, email support@knowe.app from the address on the account and we will delete it for you within 30 days.
Other choices
- Gmail: open Closet → Add to your closet → Connect email and tap Disconnect. This clears local access and requests revocation of the Google connection. You can also remove KNOWE's access in your Google Account connections. Signing out of KNOWE clears local access but does not by itself revoke Google's permission. Delete imported clothing from CLOSET to remove its access and request cleanup of its optional product photo; delete your KNOWE account to also remove its receipt duplicate-prevention records. You can continue using Photos and other closet features without Gmail.
- Photos: replace or remove your try-on photo in Account → Photos & receipts. This removes the local photo, not work already submitted or stored results. Receipt product photos follow the item-deletion and temporary-link rules above. Removing other outfits or clothing records can leave the stored image until account deletion or earlier removal on request (section 7).
- Permissions: camera, photo library, microphone, speech recognition, calendar and notifications are each optional and can be changed any time in iPhone Settings.
- Sharing: saving a preview to OUTFITS does not share it. Choose Share or add your outfit to a CALENDAR event when you want others to see it. Earlier versions also offer item-by-item friend sharing and public shortlist links. To disable an older public link, email support@knowe.app.
- Notifications: open the bell for in-app updates. Remove or Clear all hides updates from that inbox; it does not delete the outfit, event or pending friend request. Account → Notification settings shows phone permission status and lets you manage alert categories. You can change iOS permission in iPhone Settings. Account → DAILY controls the daily, weekly or monthly recommendation schedule and ready alerts, which use your time zone for delivery around 8 a.m. or when a delayed edit is ready. Turning off phone alerts does not remove in-app updates.
- DAILY and feedback: change style preferences and budget in Account → Style & shopping, or turn DAILY off in Account → DAILY. Tap an active thumbs-up again to remove that feedback from future recommendation inputs. This does not remove recommendations already generated.
- Email: account emails (like password resets) are required to run the Service. Anything else has an unsubscribe link.
- Tracking: the app doesn't track you across other companies' apps and websites, so it never asks for App Tracking Transparency permission. knowe.app doesn't track you across other sites either, and it carries no advertising or analytics tools from other companies. So we treat every visit as if your browser had sent a Do Not Track or Global Privacy Control signal, whether or not it does.
9. Children
KNOWE is for adults. You must be 18 or older to create an account. We ask for your birthdate when you set up your profile and don't allow accounts below that age. We don't knowingly collect personal information from anyone under 18, and never from a child under 13. If you believe someone under 18 has an account, email support@knowe.app and we'll delete it.
10. Security
Data travels over encrypted connections (TLS). Your data in our database is protected by per-row access rules so your account can only read its own rows. Passwords are hashed. Access to production systems is limited to the people who need it. No system is perfectly secure; if we learn of a breach affecting your information we'll notify you as the law requires.
11. Where your data lives
We're based in the United States and our systems and most providers are there (see the table in section 6; remove.bg is in Austria, Searlo's servers are in France and Open-Meteo is in Switzerland). If you use KNOWE from outside the US, your information is transferred to and processed in the US, where privacy law may differ from your country's. If you use KNOWE from the EEA, the UK or Switzerland, we rely on the European Commission's Standard Contractual Clauses (and the EU-US Data Privacy Framework where a provider is certified under it) for these transfers. Email us for a copy of the clauses.
12. Your rights
Depending on where you live you may have the right to access, correct, delete or receive a copy of your personal information, to object to or restrict certain processing and to withdraw consent. You can do most of this yourself in the app (edit your profile, delete items, delete your account). Deleting a receipt-imported item requests deletion of its optional product photo, with the temporary-link and cleanup limits above. Deleting other items doesn't delete their stored pictures; to have those deleted too, email us (section 7). For anything else, email support@knowe.app. We'll verify the request using the email on your account and respond within the time the law allows (45 days under US state privacy laws, extendable once by a further 45 days; one month under the GDPR and UK GDPR, extendable by two months for complex requests). We won't treat you differently for exercising your rights.
California residents. The categories we collect are listed in section 3 (identifiers, characteristics such as birthdate and gender, commercial information such as saves and reservations, visual information, audio when you use voice, internet activity in the app, geolocation you enter for bookings and inferences such as your taste profile). We disclose them to the service providers in section 6 for business purposes. We don't sell personal information and don't share it for cross-context behavioural advertising and we haven't in the past 12 months. You may designate an authorised agent; we'll ask them for proof. We use sensitive personal information, such as photos of you, only to provide the features you ask for, so the right to limit its use doesn't apply. Because we don't sell or share personal information, we don't offer a "Do Not Sell or Share My Personal Information" link.
EEA, UK and Switzerland. KNOWE is offered in the United States. If you use it from the EEA, the UK or Switzerland, the controller of your personal information is KNOWE Studios, Inc., 2021 Fillmore St, PMB 2419, San Francisco, CA 94115; we haven't appointed a local representative. Email support@knowe.app to exercise your rights, and you can also lodge a complaint with your data protection authority (in the UK, the Information Commissioner's Office).
13. Changes to this policy
When we change this policy we'll update the effective date at the top. If a change materially affects how we handle photos or other personal information, we'll tell you in the app or by email before it takes effect.
14. Contact
Questions, requests or concerns: support@knowe.app.
KNOWE Studios, Inc.
2021 Fillmore St, PMB 2419
San Francisco, CA 94115