Privacy Policy

In effect from: 12 October 2026 · Version 1.7

1. Who we are

The operator of LISTAI (listai.style, the LISTAI iPhone app and the browser extension) is SERHII TYTARENKO, a sole trader (entrepreneur individuel) registered in France, SIREN 102 719 770, address: 129 Allée Mériel, 83700 Saint-Raphaël, France; trading as LIS Solutions. Data enquiries: contact@listai.style.

For your account data we are the controller. For data that a stylist enters about their clients, the stylist is the controller and we process it on the stylist’s behalf (section 4 and section 15 of the Terms of Use).

2. What data we process and why

Account: your email address — for sign-in with a one-time code (there are no passwords) and service messages; the date and version of the Terms and Policy you accepted; the version and time of your permission to transfer photographs to external AI services, and the time you withdrew it, if you did (section 6).
Profile: name, professional name, country, language, currency, units of measurement, profile photo.
Stylist workspace: saved products (data and images from shop pages, notes), looks, guides, client cards.
Wardrobe: photographs of your garments, processed images and the details you confirm (name, category, colours, brand). The original photograph is kept.
Favourites and shop photos: saved items; for items photographed in a shop — your photos of the item, its tag and from the fitting room, the shop link, details you enter or confirm (name, brand, price, size, article number, category, colour) and the barcode read from the tag.
Measurements and figure: the measurements you enter (height, girths, lengths), with their history of changes, and the figure you choose to see them on.
Try-on photos and results: your photographs saved for try-on and the resulting images.
Messages and feedback: direct messages with a stylist, comments and replies in guides, likes, ratings and reviews, read markers.
Purchases and Credits: the ledger of LISTAI Credits operations and details of App Store purchases (section 12).
Device: your device’s notification token (if you allowed notifications) and the device type (iPhone, iPad).
Usage: guide opens and clicks through to products in a guide — so that the stylist sees what interested you; technical logs and error reports (section 15).

3. Legal bases for processing

We process data on the bases provided by the GDPR (Article 6):

Performance of a contract — account, profile, workspace, wardrobe, favourites, measurements, messaging, purchases: the service cannot be provided without them.
Consent — the transfer of photographs you choose to external AI services — Pruna, OpenAI and fal, and through fal to model developers (section 6), a stylist’s access to your measurements and try-on photos (section 5), notifications on your device. Consent can be withdrawn at any time; withdrawal does not undo processing already carried out.
Legitimate interest — technical logs, error reports, security, guide-open statistics for the stylist.
Legal obligation — accounting records of purchases and responses to lawful requests.

4. Client data entered by a stylist

If a stylist adds information or photographs of their clients to LISTAI, they are used only to provide the service to that stylist: they are not included in analytics or error reports, not passed to third parties for their own purposes and not used by us to train models. The stylist is responsible for having a lawful basis to upload them and for their relationship with their clients.

6. Photographs that show a face

This section describes everything that happens to photographs that may show a face: try-on photos, fitting-room shots, photographs of a garment worn by a person. LISTAI does not look for faces in photographs, so these rules apply to every photograph you choose in LISTAI, whether or not it shows a face.

Where photographs come from: only those you take with the camera or choose on your own device — in the app or on the website. A stylist you have allowed to add garments to your wardrobe can upload garment photographs into it: they become yours, and processing them with AI needs your permission. A stylist’s library holds images the stylist uploads or saves from shop pages; they may show a person, such as a shop’s model.
What we receive and store: the whole photograph — as you took or chose it, including a face if there is one in the frame. We do not cut out or store a face separately. Before uploading, the iPhone app redraws every photograph — for try-on, the wardrobe, favourites, «Add from a shop» and the profile photo — as a new JPEG, so the location data (EXIF/GPS) of the original file is not uploaded.
What we never do: we do not detect or recognise faces, do not determine facial features or landmarks, do not create biometric templates or vector representations («embeddings») from photographs, do not identify a person from a photograph, do not build profiles, do not use photographs for advertising and do not train models on them. A photograph is processed only as an image — for the action that was started. The only computer-vision feature in the iPhone app reads the QR code on a garment tag.
What stays with us alone: saving a photograph, viewing it, entering a garment’s details by hand and opening a photograph to a stylist in LISTAI send nothing to external services. A photograph goes to an external AI service only when an AI action is performed on that photograph: try-on; recognition of a garment or a tag; background removal, smoothing or «invisible mannequin». When you add a garment to your wardrobe or use «Add from a shop», recognition and processing start right after the photo is taken or uploaded, if you have given permission. Your profile photo is never sent to an external AI service.
Permission: before a photograph you chose is transferred to any of the recipients below for the first time, we ask your permission separately — on the website and on iPhone. The request says what is sent (the photograph as a whole; it may show your face or another person), to whom and why; the buttons are «Allow and continue» and «Cancel». After Cancel nothing is transferred and no Credits are spent; a shop photo is saved without recognition. The server records the version of the permission and the time, and checks the permission before every transfer — before Credits are reserved and before any recipient is contacted, including on a retry and on a switch to a fallback model. If the recipients or the purposes of the transfer change, the version of the permission changes and we ask again.
A client’s photographs: when a stylist processes a photograph that belongs to a client — runs a try-on on a photo the client has opened to that stylist, or processes a garment from the client’s wardrobe — the client’s own permission is required, not the stylist’s. Without it nothing is transferred, and the stylist sees that the client has not allowed the processing.

Recipients. Directly, your photograph can be transferred only to these three services, each only for its own purpose; through fal, it is also received by the developer of the model that does the processing (see below):

Pruna (Pruna AI GmbH, Munich, Germany) — virtual try-on: the photograph of the person is sent as a file and images of the selected garments as links valid for 15 minutes; no name, email address or account identifier is sent. We store the finished image with us. Retention at Pruna: Pruna’s published API specification states that an uploaded file is available for 30 minutes and then deleted automatically, but an example in the same specification shows 24 hours; Pruna does not publish how long the generated image, internal copies and logs are kept. We cannot delete a file on Pruna’s side. Basis: Pruna’s terms and its data processing agreement, which under Pruna’s published terms applies when personal data subject to the GDPR is processed: processing only on our instructions, security measures, rules for engaging sub-processors, assistance with your rights, deletion of the data when the service ends, and no transfer of data outside the EU and the EEA without our written consent.
OpenAI — recognising a garment and its tag: the chosen photograph of a garment or a tag is sent so that an OpenAI model (currently gpt-4o-mini) can suggest a category, colour, name and brand, and from a tag an article number, size, price and barcode; no name or account details are sent. Each request is sent once, without automatic retries, with an instruction not to store the response. Sharing data for training is turned off in our OpenAI account; according to OpenAI’s documentation, data sent through the API is not used for training unless the customer has explicitly opted in. OpenAI keeps abuse-monitoring logs for up to 30 days, unless longer retention is required by law or necessary to protect against harm. We do not have zero data retention or EU data residency. Basis: OpenAI’s API terms and OpenAI’s data processing addendum (for the EEA, OpenAI Ireland Ltd.), with standard contractual clauses for transfers outside the EEA.
fal (fal.ai, Features & Labels, Inc., USA) — preparing a picture: background removal, smoothing a garment and «invisible mannequin». The chosen image is sent inside the request; for smoothing and the mannequin, also the garment’s name and category. The work is done by models available through fal. Every model we currently use is developed by another company, and fal marks each one as a partner model that fal accesses through its developer’s API; under fal’s API terms (section 2.3), the data sent is then transferred to that developer. The image is therefore also received by the developer of the model that does the processing: Bria AI (the bria model) or Pixelcut (the pixelcut model) for background removal; Google (the nano-banana and nano-banana-pro models) or Black Forest Labs (the flux-pro kontext model) for smoothing and «invisible mannequin». We reach these developers only through fal and under fal’s terms; we have not verified how long they keep the image or on what terms they process it, and we state nothing about that here. The request and the response are not kept in fal’s request history: we switch that storage off with an option described in fal’s documentation (without it, they are kept for 30 days). We download the generated file into our own storage straight away and, as soon as it is saved with us, delete it at fal through the deletion interface fal provides; fal confirms in its reply the deletion of each file. If the deletion fails, we retry it once straight away; if that fails too, we record the failure (only the request identifier, the model and the kind of error — no image and no link to it) and retry the deletion during later processing, up to three more times within 30 days. If those attempts fail as well, the file remains on fal’s CDN: according to fal’s documentation, the lifetime of generated files is set by the account setting and, where none is configured, files are kept «forever and publicly readable» by link. We do not give the link to anyone. Basis: fal’s published API terms and fal’s data processing addendum — to the extent those terms apply it to the model used — with standard contractual clauses for transfers outside the EEA.

We rely on these agreements for your photograph to be protected at each recipient no less than this policy describes. That is a contractual commitment of the recipient, not the result of our own audits or measurements; apart from deleting the generated file at fal as described above, we cannot delete copies left with a recipient or a model developer.

Storage with us: photographs and results are stored in Cloudflare R2 (Western Europe region), and the records about them in the Supabase database (Ireland). Under the database’s access rules a photograph is visible only to its owner; a stylist sees your photographs only if you opened them to that stylist yourself (section 5): try-on photos with a separate switch, wardrobe garments with wardrobe access. A result is not published automatically.
Deletion: you can delete an individual photograph, result or garment, and your whole account (section 16). A file is queued for deletion together with its record and then removed from storage; if a file cannot be removed straight away, the attempt is repeated on your next request to the service. An account is deleted only after all its files have been removed; if a file cannot be removed, the account deletion does not complete and is repeated on the next deletion request. Try-on results a stylist made on your photographs are deleted when you stop showing your try-on photos to that stylist, close their access, delete your account, or when the stylist deletes your client card; a copy the stylist has already sent you is yours. The generated file at fal we delete ourselves as soon as it is saved with us; if the deletion still fails after the retries described above, the file remains at fal. Other copies held by recipients and model developers are deleted under their own rules (see above).
Where to see and withdraw the permission: in Profile, «AI processing of photos» — on iPhone and on the website. It shows whether the permission is in effect, and you can turn it off: future transfers stop; transfers already made are not undone. The version and time of your permission stay in your account as the record of the basis on which earlier transfers were made. You can give the permission again at your next AI action.

7. Virtual try-on

How it works: a try-on is started by you — or by a stylist to whom you have opened your try-on photos (section 5). Your photo and images of the selected garments are sent to Pruna, which creates an image. This needs your permission to transfer photographs to AI services (section 6) — also when a stylist starts the try-on. What exactly is sent, how long Pruna keeps it and on what basis — see section 6.
What stays with us: your try-on photos and your results are stored privately and are available only to you. The result of a try-on started by a stylist is kept by the stylist until you stop showing your try-on photos to that stylist, close their access or delete your account — it is then deleted. If the stylist sends the result to you, your copy becomes yours.
Nothing is published: the result is not published automatically. «Share» is your own action through the device’s system menu.

8. Recognition, texts and image processing

Garment recognition (OpenAI): when you add a garment to your wardrobe, its photo is sent to OpenAI to suggest a category, colour, name and visible brand. When you photograph an item in a shop, the item photo and the tag photo are sent to OpenAI right after they are taken — to suggest a brand, name, article number, size, price and barcode. These are only suggestions: you check them before saving. Without your permission (section 6) the photograph is saved but not transferred: a shop photo is saved without recognition, and processing a wardrobe garment waits for the permission.
Texts (OpenAI): when a product is captured with the extension — the text data of the product page (name, brand, description, composition, category, colour, the page’s structured data) for normalisation; for translation — the product and guide texts a stylist translates.
Images (fal): background removal, smoothing a garment and «invisible mannequin» — only when such processing is started for a specific image: when you add a garment to your wardrobe (if these settings are on), with the «Prepare» button in favourites, or by a stylist in the library. The selected image is sent — which may be your fitting-room photo if you chose it — together with the garment’s name and category. The result is stored with us; the original image is kept.

What exactly each provider receives, how long it keeps it and on what basis is described in section 6.

9. Browser extension

The extension does not collect data in the background or in bulk: it extracts data from a specific product page only after your explicit action and sends the data you selected to your LISTAI account. It does not track your browsing history or read cookies, passwords or the contents of other tabs. Your session token is stored locally in the browser and sent only to LISTAI servers.

10. Screenshots and uploaded material

Screenshots and other material you upload are created by your explicit action. We store them on your behalf in your workspace and show them only to people you share with. You are responsible for the rights in such material (section 6 of the Terms of Use).

11. Messages and notifications

Direct messages between you and a stylist, and comments and replies in guides, are seen only by the participants of the conversation. Their text is not passed to third parties and is not translated automatically. «Read» and «typing…» markers are seen by the other side of the conversation.

If you allowed notifications, Apple (the APNs service) receives your device token and the notification text. A new-guide notification contains the guide’s title and the stylist’s name; a reply notification contains the guide’s title; message text is not included in notifications.

Reports. If you report a message, comment or review, LISTAI receives that text and a limited part of the conversation around it — up to ten items before and after it, from the same conversation only — together with who wrote what. We use this only to review the report, protect users and enforce the Terms of Use (our legitimate interest). Reports are reviewed by LISTAI; the stylist does not see them. The copy is kept for as long as needed to handle the report and any related claim, even if the original is deleted later. Before a report is sent, the app tells you plainly what will be included.

Blocking and filtering. You can block a person: after that neither of you can write to the other, and you receive no notifications from them. Messages, comments and reviews are checked on our server against a local list of words that are not allowed before they are saved; the text is not passed to anyone for this check. A refused text is not stored — we record only that a refusal happened.

12. Purchases and Credits

In-app purchases are processed by Apple; we do not receive your card details. To grant Credits exactly once, we verify the transaction signed by Apple and store: the transaction identifiers, the product, the number of Credits granted, the price and currency, the date, the environment (production or test) and the link to your account. The ledger of Credits spent and granted is kept for as long as the account exists.

13. Where data is stored

Database and authentication — Supabase (Ireland region, EU). Files (photographs and images) — Cloudflare R2, Western Europe region (WEUR). The application is hosted by Vercel. Some recipients (sections 6 and 14) process data outside the EEA; in such cases the transfer relies on mechanisms provided by the GDPR (standard contractual clauses and/or the EU–U.S. Data Privacy Framework).

14. Sub-processors and other recipients

Supabase — database, authentication, real-time updates (EU, Ireland).
Cloudflare (R2) — file storage (Western Europe region).
Vercel — hosting of the web application and server.
ZeptoMail (Zoho) — delivery of sign-in code emails.
Sentry — error reports; image bytes, signed links and storage keys are removed from events before they are sent.
OpenAI — garment and tag recognition (section 6), normalisation and translation of texts (section 8).
fal.ai (Features & Labels, Inc.) — preparing images (section 6). The company is based in the USA. fal reaches the models we use through it via their developers’ APIs — Bria AI, Pixelcut, Google and Black Forest Labs — so the developer of the model also receives the image (section 6).
Pruna — virtual try-on (sections 6 and 7).
Apple — in-app purchases and delivery of notifications to your device (sections 11 and 12).

We transfer your photographs to external AI services only through the three recipients named in section 6, and through fal they are received by the model developers named there; they are not transferred to any other AI service. Videos in guides are embedded from YouTube or Vimeo, and the app loads YouTube video thumbnails: these services see your IP address when you open such a guide.

15. Technical logs and cookies

We keep technical logs of the service (including request identifiers and error codes) to diagnose failures. Image bytes, signed links and storage keys are removed from error reports before they are sent. There is no analytics SDK in the product. The website uses only strictly necessary cookies, to keep you signed in. There is no advertising, tracking or third-party analytics cookies; the iPhone app does not use the advertising identifier and does not track you across other apps.

16. Retention and deletion

Data is kept for as long as your account exists. Individual photos, try-on results, garments and messages can be deleted at any time.

You can delete your account yourself: in the app — Profile → Delete account; on the website — in your profile. Deletion erases your profile, wardrobe, favourites, measurements, try-on photos and results, messages, the Credits ledger and the related files in our storage, as well as try-on results stylists made on your photographs; stylists’ client cards are unlinked from the deleted account. Files are queued for deletion, and the account is deleted only after all its files have been removed; if a file cannot be removed, the account deletion does not complete and is repeated on the next deletion request. App Store purchase records are kept for accounting without a link to the account. The files fal generates we delete at fal ourselves — as soon as the result is saved with us, with the deletion of each file confirmed; if the deletion still fails after the retries described in section 6, the file remains at fal. Other copies already sent to recipients — at Pruna, at OpenAI, at the developers of the models fal uses, and anything fal keeps other than the generated files (section 6) — are deleted under their own rules; we cannot delete them ourselves.

Technical logs and error reports are kept for the period set by our hosting and error-reporting providers. Sign-in code emails are not stored after delivery.

17. Your rights

Under the GDPR you may request access to your data, its rectification, erasure, restriction of processing and portability, object to processing and withdraw consent. Contact contact@listai.style. You also have the right to lodge a complaint with a supervisory authority — in France, the CNIL.

18. Age

The service is not intended for people under 16.

19. Changes

We may update this policy. We will announce material changes on the website and in the app and ask you to confirm the new version the next time you open LISTAI. The date and version of the current text are shown at the top.