26 October 2026 · Manual outfits and hybrid profile

Your wardrobe.
Your information.

HangerRoom is operated by Nuno Queirós Moreira Lopes, an individual operator and the controller responsible for the personal data described here. Contact [email protected] for privacy questions or requests.

When you explore the demo

Demo preferences, wardrobe edits, saved looks and purchase notes are stored on your device. They are separate from a cloud wardrobe and are not automatically imported into an account. Bundled sample photographs are not your personal wardrobe. Clearing site data removes the local demo data and may also sign you out. Copies you download remain under your control.

Website delivery and support

Cloudflare delivers and protects this website. Requests necessarily include technical information such as your IP address, requested address and browser information. This is used to deliver the service and protect it against misuse, on the basis of legitimate interests in operating a secure website.

If you contact support, your email address and message are used to respond and resolve the request. Cloudflare forwards support mail to the operator’s project Gmail inbox, provided by Google. Do not email passwords, sign-in codes or sensitive photographs. Support correspondence is retained while needed to resolve the request and deal with related disputes or legal obligations; a fixed routine deletion schedule has not yet been established.

Cloud account functions

The deployed account infrastructure uses Supabase for authentication, private database records and file storage. The selected database project is hosted in London, United Kingdom. AWS Simple Email Service in Ireland delivers authentication emails from [email protected]. This does not mean every provider log, backup or support operation is confined to those locations.

When you create an account, authentication uses your email, password and session credentials. Email confirmation is required. Passwords are handled by Supabase Auth; they are not included in account exports. Account features may store manually entered garment details, garment photos, preferences, trip dates, packed pieces, spending notes, saved outfits and feedback. A saved outfit request may include your selected city, coarse coordinates and forecast. These functions use data to provide the service you request; account and security records also support abuse prevention. Notice acknowledgments record the versions presented during registration. There is no marketing opt-in bundled with account creation.

Browser or app storage retains authentication sessions and pending outfit requests until you sign out, discard them, clear storage or the relevant account flow removes them. Sign-out does not promise removal of every device or operating-system cache. Cloud wardrobe data is kept while your account is active, unless you remove it or request account deletion. You can request a ZIP export or permanent deletion from Account. Scheduled AWS workers in Ireland use your Supabase records and stored garment files for those requests. New export and deletion requests stop accepting work if their worker heartbeat is stale. Processing may be delayed by an outage; contact support if a request remains delayed.

Manual outfits and your optional outfit profile

You can assemble and edit private manual outfits from your wardrobe without using an outfit-idea allowance. Manual records include selected pieces, their order, title, occasion, planned date, revision and optional link to an original suggestion. Saving an edited version does not rewrite the original suggestion receipt. A save, swap or wear is not automatically recorded as a positive rating.

The optional guided profile stores complete-look reference choices, styles, colours, usual occasions, preferred cuts by garment group, category exclusions, clothing presentation and retailer collection preferences. Shopping choices can include currency, a per-piece budget, favourite brands and brands you prefer not to buy. Saved progress records which steps you completed or skipped; unanswered choices remain unknown rather than dislikes. Preference provenance distinguishes explicit answers, earlier profile choices and unknown fields. We use these answers to provide the requested personalisation; they remain private, editable, exportable and removable with your account.

Styles, colours and explicit exclusions affect current suggestions. Avoided shopping brands apply to possible additions, not clothes already marked owned. Preferred cuts and clothing presentation are stored for later styling capabilities and do not currently establish physical fit, size or comfort. Retailer collection preferences are separate from gender; no retailer is contacted when you save this profile. Clothing presentation and gender are never inferred from wardrobe choices or feedback. You can clear outfit-profile answers independently of identity and exact-piece feedback.

Your style choices and feedback

Your wardrobe is a starting point for your taste, not an automatic like for every piece. Outfit likes and dislikes help choose future clothing combinations for the same occasion. For an individual piece, “Not with this outfit” remembers the occasion and the other core clothes; “Not my style anymore” avoids that exact piece across occasions. An optional reason can describe colour combinations, formality, comfort, personal taste or whether a piece feels too masculine or feminine for you. We use this feedback to provide the personalised suggestions you request as part of the service. A reason about a garment is not an inference about your identity.

You may choose to save a self-reported gender answer or an optional description of up to 80 characters. This is optional and is recorded with your consent: you can use wardrobe and outfit functions with “Prefer not to say”. The current rule-based engine stores your answer in your profile but does not use gender-based clothing restrictions. It does not infer or change your gender from clothes, photographs or ratings. Do not include health information, sexual history or other sensitive details in the optional description.

You can change your answer at any time. Selecting “Prefer not to say” and saving removes the previous gender answer and description from your current preference record; this withdraws your choice to store those details for the future. It does not remove copies in an export you already downloaded or immediately erase provider-managed backups. Those limits are described below.

You can clear piece preferences in your style settings. Up to 200 current piece preferences are retained; an older one may be replaced as new ones are added. Whole-outfit ratings are stored with outfit receipts, and only the most recent 200 rating records influence new suggestions. Clearing a whole-outfit rating retains a neutral revision so delayed updates cannot restore an older answer. Preferences and feedback are private to your account, included in account exports and removed with account deletion. Local-demo preferences remain on the device and are separate from account data.

Changing a piece creates a preview without rewriting a recorded outfit. An unrecorded cloud preview remains in memory; saving an edited version creates a separate manual outfit without using another outfit idea. Current styling uses the implemented ranking rules. These preferences are not used for cross-customer model training and are not sent to an AI styling provider in this release. A future AI integration will require its actual processing to be described before it is enabled.

Exports, deletion and retention

Exports include your account data and any stored garment files, including unlinked files. You may request one export per hour. A completed archive is available for 24 hours and then becomes eligible for removal by the scheduled cleanup worker. A prepared private download link lasts up to five minutes. Keep downloaded copies private; deleting an account cannot remove copies you saved or shared.

Deletion requires fresh password verification and explicit confirmation. Once accepted, private account access and new writes are frozen. The worker removes stored garment files and export archives, hard-deletes the Auth identity and cascades account records before reporting completion. A pseudonymous completion receipt, including an account identifier and hashed receipt proof, remains for 30 days to verify the request, then the worker purges it. Operational AWS worker logs retain 30 days and use service status flags and generic failures rather than photo content or account records. Processing and cleanup are retried; we do not promise immediate completion during service outages.

Removing active account data does not promise immediate erasure from infrastructure backups, provider security logs or copies already downloaded. These have separate provider-managed schedules and access controls. They are not available through your deleted account. Contact support for questions about a particular request or retained information.

Garment photos and person photos

Public garment-photo saving is switched off while its protected processing service is being tested. Do not use it to submit a person photograph. This client does not accept person photos for virtual try-on and does not send them to an AI image provider. No AI image provider has been selected for that feature.

Before person-photo try-on opens, we will identify the processor, information sent, processing locations, retention, transfer safeguards and the legal basis, and provide a separate informed choice. Ordinary wardrobe use must remain available without that choice. We do not currently use your photos for facial identification or model training.

Providers and international processing

The current setup uses Cloudflare, Supabase, AWS and Google as described above. Providers may process technical records or support data in other countries. These providers operate globally, so technical/support processing may involve countries outside the EEA. The London database is outside the EEA. The European Commission currently recognises the UK as providing an adequate level of protection through its UK adequacy decision. For other relevant transfers, provider terms describe safeguards such as standard contractual clauses: Supabase’s data processing addendum, Cloudflare’s data processing addendum and AWS’s data protection information. Google handles the support inbox under its privacy terms. Regional hosting does not guarantee that every technical record remains there. You may ask support for information about safeguards and retention for a particular request. Stripe is planned for payments but live payment collection is not enabled. There is no live retailer price monitoring or advertising/analytics integration in this release.

Your choices and rights

You can ask for access, correction, deletion, restriction or a portable copy of your personal data, and object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it for future processing. Rights depend on the applicable legal conditions. Email [email protected]; we may need proportionate evidence that a request relates to your account. You may complain to your data protection authority, including Portugal’s CNPD.

HangerRoom is intended for adults. Do not upload another person’s photo without the necessary permission. Outfit suggestions do not make decisions with legal or similarly significant effects about you.

Changes and a future company

This dated notice is retained as a record of this version. If a company later becomes the operator and data controller, we will publish its identity and contact details, explain when the change takes effect and notify affected account holders. Any transfer of existing data must have an appropriate legal basis and safeguards; changing this page alone does not transfer responsibility.