Privacy notice

Who is responsible

Matthew Seymour trading as Outfit Try-On operates Outfit Try-On and is responsible for processing that Outfit Try-On decides to carry out itself, including website enquiries, carefully selected business outreach, account administration, merchant administration and service security. The full postal address appears below. For privacy questions or rights requests, email support@outfittryon.app.

The personal app and merchant service are intended for people and retailers using the Service in the United Kingdom. Users must be aged 18 or over. The Service is not intended for children, and photos of children must not be submitted.

For a retailer-embedded shopper experience, the retailer decides whether and where the experience is offered and which products it covers. The retailer is the controller for that shopper experience and Outfit Try-On processes the shopper photo and result on the retailer’s documented instructions to provide the requested preview. Outfit Try-On remains independently responsible for processing it determines for service security, legal compliance and its own merchant administration. These roles and instructions are recorded in the retailer agreement and applicable data-processing terms.

Information we handle

• Personal accounts: the email address used for one-time sign-in links; optional display name, height, UK size, fit notes and generation preference; submitted photos; product links, screenshots or uploaded product images; generated results; and the account’s try-on balance, reservations and pack history. Stripe handles the payment form for a pack purchase. Outfit Try-On retains the payment reference, pack, amount, currency and status needed to grant credits and show purchase history; it does not receive or store full card details.
• Business outreach and enquiries: a public business email address or contact form, contact name where relevant, store URL, business type, platform, approximate catalogue information, correspondence and any optional message. Initial prospect details may come from a retailer’s public website and Companies House. Enquiries and outreach replies are handled by email and are not stored in an in-app marketing CRM.
• Merchant services: store identifiers, eligible product and product-image data, integration settings, subscription and entitlement states, and usage information received through Shopify or WooCommerce.
• Retailer-embedded shopper experience: we do not receive the shopper’s name, email address, customer-account number, delivery address or payment details. A participating retailer can require the shopper to be signed in before the try-on button is shown. In that case, the retailer integration sends Outfit Try-On only a keyed, non-reversible customer reference so repeated misuse can be linked to the same retailer account without disclosing the underlying account identifier. Before the photo controls are enabled, the shopper must actively confirm in that session that they are at least 18, will upload only a photograph of themselves, and will not submit nudity or sexual or intimate content. The confirmation is not pre-selected or remembered between sessions. We process only the submitted photo, generated result, product reference and short-lived pseudonymous session details needed to create and show the visualisation.
• Conversion measurement: a server-validated add_to_cart_clicked event containing an event UUID and store, session, product and generation identifiers. It does not contain the shopper’s name or email, but we treat the identifiers as potentially pseudonymous personal data rather than calling the event anonymous.
• Operations and abuse prevention: request identifiers, limited service logs, delivery status and short-lived HMAC-hashed IP and email signals. A short-lived hashed IP signal limits rapid multi-account claims on the free signup offer; raw IP values are not stored in that throttle table. The public enquiry form uses Google reCAPTCHA v3, which processes technical and interaction signals and returns a short-lived token, action, hostname and risk score so we can reject likely automated abuse. We do not put the reCAPTCHA token or score in enquiry emails or contact records. An image rejected by an automated safety check creates a minimal event containing the rejection category, store and pseudonymous session or shopper reference, and timestamp; the rejected image and classifier response are not put in that event. Raw contact IP and email values are not stored in the enquiry throttle table.

How and why we use it

We use information to provide and secure a requested personal account or merchant service, send passwordless sign-in links, create and save requested clothing visualisations, maintain try-on balances, synchronise eligible retailer products, respond to enquiries, administer subscriptions and entitlements, measure whether a retailer-session result leads to an add-to-cart click, enforce usage limits, diagnose failures and meet legal obligations.

Shopper photos and generated results are used only to create and deliver the shopper’s requested preview, secure the service and operate the stated deletion process. Neither Matthew Seymour nor the participating retailer routinely views real shopper photos or results. Outfit Try-On does not use them for AI or model training, marketing or product research. Contracted service providers may process, temporarily retain or permit limited authorised access to content where necessary for generation, security, abuse prevention, support or legal compliance under their applicable controls. Outfit Try-On support and debugging use a separate test session and test content rather than opening the affected shopper’s files.

For our own administration, security and carefully targeted contact with verified corporate businesses, we rely on our legitimate interest in developing and operating the business service, balanced against the recipient’s rights. We do not cold-email sole traders or ordinary partnerships without the consent required by electronic-marketing rules. Contract or steps requested before a contract may apply when someone asks us to provide an account or merchant service. Legal obligation may apply where records must be kept or disclosed by law. Each retailer is responsible for identifying the appropriate lawful basis for its retailer-embedded shopper experience; the agreed instructions and roles are recorded in the retailer agreement and applicable data-processing terms.

Business outreach

We use a small, manually researched list rather than bulk mailing. An initial message identifies Matthew Seymour and Outfit Try-On, explains why the business was selected, links to this notice and provides a simple way to object. We do not use tracking pixels in merchant outreach. If a recipient objects or asks not to be contacted, we stop direct marketing and keep only the minimum suppression record needed to respect that request.

Optional emails and referrals

Tips and offers. When you create a personal account you can tick an optional box to receive occasional tips and offers by email. The box is not ticked for you, ticking it is not a condition of using the service, and we send nothing of that kind unless you have ticked it. We record the date and time you agreed. You can withdraw at any time in Settings, which stops these emails, and you can also email support@outfittryon.app. You have an absolute right to object to direct marketing. Withdrawing does not stop account and service emails, such as sign-in codes, purchase confirmations and a single welcome message sent when a new account is first verified.

Referrals. Each personal account can show a personal referral link. When a new account is created through someone’s link, we keep a record of who referred whom so that the agreed try-on rewards can be applied after the new account’s first pack payment is confirmed, and taken back if that payment is refunded. We keep the record while either account exists. The person who shared the link sees only a count of friends who earned a reward, not who they are.

Social media

We may follow public social media accounts, and reply to public posts about second-hand fashion, from our own accounts. Replies may be drafted with the help of AI, and anything that mentions Outfit Try-On says that its owner built it. We keep a minimal record of these interactions, such as hashed (non-reversible) account identifiers and post identifiers, for 90 days so that we do not repeat ourselves. Blocking or muting our account, or emailing support@outfittryon.app, stops it. We do not message people privately through automation, and we do not use submitted photos or results in our posts.

Cookies and similar storage

The public website, personal app and retailer-embedded shopper experience do not use advertising or analytics cookies. We use only cookies or similar device storage that are technically necessary to provide a requested sign-in or session, maintain security or remember an essential service state. Google reCAPTCHA sets a necessary _GRECAPTCHA cookie when it runs on an enquiry submission to provide its risk analysis. We do not use these technologies for cross-site advertising or profiling. When you ask for a sign-in link by email, up to two short-lived first-party cookies, which expire after an hour or when the link is confirmed, remember the optional email choice you made on the sign-in form and any referral link you arrived from, so they apply to the account you confirm. The separately disclosed retailer add-to-cart event is recorded by the service after the shopper clicks the button; it is not used to place an advertising or analytics cookie and is deleted within 90 days.

We keep a small set of named daily totals to see how the service is being used: page views, sign-in steps, try-ons started and finished, and purchases. The marketing pages send a first-party counting request after a page has remained open for about one second, and the sign-in page does the same; the other totals are added by our servers when the step happens. When a link from one of our own posts carries a source label, we also add one to a daily total for the channel the visit came from, such as Instagram or Reddit. This does not run in the retailer-embedded shopper experience. It does not set or read cookies or similar device storage, and we do not keep the page address, IP address, browser details or a visitor identifier with these totals. They measure events rather than people.

AI processing and storage

The personal app uses OpenAI and, where selected and available, FASHN; merchant generations use OpenAI. These providers process submitted photos and product images to create a visual preview. Account, merchant and service data and files are stored using Supabase infrastructure, and the service is hosted using Vercel. Email is handled using Resend, public enquiry abuse checks use Google reCAPTCHA, and Stripe handles pack checkout and payment. Where a provider processes personal data outside the United Kingdom, we use an applicable transfer mechanism and safeguards required by data-protection law. We do not describe visual results as sizing or exact-fit advice.

Our providers and their approved subprocessors may process or store information in the United Kingdom, the European Economic Area, the United States and other countries in which they operate. Exact infrastructure locations may change within the provider service. Where United Kingdom transfer rules apply, we use an adequacy regulation or contractual safeguards such as the United Kingdom International Data Transfer Agreement or the United Kingdom Addendum, together with any required assessment and supplementary measures. Contact support for more information or a copy of the relevant safeguards.

Sentry provides error monitoring and receives limited error reports and technical context to diagnose failures. Reports are minimised by stripping user fields and selected request details. Remaining URL paths and diagnostic information may contain personal data. We do not intentionally send uploaded photos or generated images to Sentry.

Retention and deletion

• Personal-account profile details, saved item data, photos and generated results remain available in the account until the user deletes the saved try-on data or asks us to erase it, unless a specific security or legal reason requires limited retention. The in-app deletion control removes those saved records but leaves the sign-in account and credit history intact.
• The personal account email and credit history are retained while the account is active. Account closure or erasure requests can be sent to support. Transaction records required for tax, accounting, fraud, chargeback or legal obligations may be retained after other account data is deleted.
• Retailer try-on processing is enabled only when scheduled deletion is operational. Once enabled, commerce shopper photos and generated results remain in Outfit Try-On’s active application storage for no more than 24 hours. We schedule deletion earlier than that limit, and the session-delete control starts removal sooner. The shopper can download a generated preview to their own device before it is removed. This active-storage limit does not mean every provider or infrastructure copy is gone within 24 hours: limited content may remain temporarily in in-flight processing or provider safety, abuse-prevention, legal-compliance or protected-backup systems under the applicable provider controls and periods.
• Pseudonymous add-to-cart and minimal image-safety rejection events are kept for up to 90 days.
• Short-lived contact and free-signup throttle records expire after 48 hours. Safe error details and all other identifiable operational logs under our control are deleted within 30 days, unless a particular record must be retained longer for an active security incident or legal obligation.
• Sentry service-error events are currently retained for 30 days. Separate Sentry provider-account administration audit logs are retained indefinitely. Any service-plan change requires this retention position to be reassessed and this notice to be updated where needed.
• Store configuration, synced product data and identifiable operational records are deleted within 90 days after a merchant disconnects or its service ends, except where transaction, tax, dispute or security records must be retained longer.
• Signed agreements, key acceptance or compliance evidence, and correspondence needed for a legal claim or dispute may be kept for up to six years. A minimal suppression record may be kept for longer so that an opt-out is not forgotten.
• Ordinary prospecting and enquiry correspondence is deleted 12 months after the last contact. Where someone opts out of merchant outreach, we retain only the email address and opt-out date for as long as we continue that outreach so that the request is not forgotten.
• Disposable retailer shopper images are excluded from application-managed backup archives. Core database recovery continues for billing, credits, store configuration and necessary acceptance evidence. Infrastructure providers may still hold limited protected copies under their applicable backup periods; those copies are not used in ordinary operations. If a restore brings expired retailer media back into active storage, it must be deleted before the service makes it available.

Who receives information

Information is shared only where needed with the relevant retailer and commerce platform, the selected image-generation provider (OpenAI or FASHN), Supabase, Vercel, Resend, Google reCAPTCHA and Stripe, and with professional advisers or authorities where required. Stripe receives checkout and payment data when a pack is purchased. We do not sell account, enquiry or outreach information. We do not use submitted photos or results for advertising, marketing, AI training or product research.

Sentry receives the minimised error diagnostics and technical context described above to monitor failures and support incident diagnosis.

Your choices and rights

Depending on the circumstances, you may have rights to access, correct, delete or restrict personal data, object to processing, receive portable data, withdraw consent where consent is used, or complain to the UK Information Commissioner’s Office. You have an absolute right to object to direct marketing. Personal-account users can delete saved try-on data in Settings and can email support@outfittryon.app for account closure or another privacy request. Outfit Try-On also accepts retailer-session shopper privacy and deletion requests directly, acknowledges them promptly and coordinates with the relevant retailer; a shopper will not be required to restart the request through the retailer. We aim to complete a valid request within one calendar month. We cannot promise immediate deletion where safe processing, protected backups or legal duties require more time.

Security and changes

We use access controls and operational safeguards appropriate to the Service. Personal-account content is restricted to its signed-in user. The retailer-embedded experience does not receive a shopper name, email address, direct customer-account identifier, delivery address or payment details; it processes the submitted photo, generated result and short-lived pseudonymous session or usage identifiers. Submitted person and product images are screened, and generated previews are screened before they are saved or displayed. The Service is designed to block nude and sexual images using safety screening, but automated checks can make mistakes. No online service is completely secure, and this notice does not make an unverified promise about encryption or storage geography. If a personal-data incident affects a merchant’s shoppers, Outfit Try-On will notify that retailer without undue delay and cooperate with its investigation. We will notify affected people or the Information Commissioner’s Office wherever the law requires Outfit Try-On to do so. We will publish a revised date when this notice changes and provide additional notice where required.

Business and contact details

Email support@outfittryon.app for support, privacy requests, complaints or legal notices.