Privacy policy · Politica de privacidad
Effective / last updated: 2026-10-13
This page is a working draft. The operator identity details a Spanish legal notice is required to state have not been confirmed yet, so they are shown below as explicit placeholders rather than invented. Do not treat this page as launch-ready until this has been reviewed by a Spanish privacy/commercial-law professional.
Required - must be supplied
- operatorLegalName: The legal name of the person or company operating this site (an individual's full legal name for a sole trader/autónomo, or a registered company name). Required by LSSI-CE art. 10.1.a for any operator - no exception.
- operatorIdNumber: Spanish tax/registration ID (NIF for an individual, CIF for a company). Required by LSSI-CE art. 10.1.e for any operator - no exception.
- operatorAddress: A real registered/business postal address (residence/domicile, or a Spanish establishment's address). Required by LSSI-CE art. 10.1.a for any operator - no exception.
May be conditional or inapplicable - confirm, don't assume
- operatorRegistryDetails: Commercial/professional registry details (e.g. Registro Mercantil entry). LSSI-CE art. 10.1.b's duty here is scoped by art. 9.1 to providers actually registered in such a registry - an unregistered sole trader/autónomo has nothing to disclose and this can legitimately stay blank. Only becomes required if/when the operator registers (e.g. incorporates a company).
- operatorJurisdictionNote: Not an LSSI-CE art. 10 'general information' item - a governing-law/consumer-protection conclusion, not a simple fact. Confirm with a Spanish privacy/commercial-law professional which jurisdiction's courts and regime actually govern this site once its operating structure and target market are finalised; this file should never guess it.
- dataProtectionContactEmail: GDPR art. 13(1)(a) requires only the controller's OWN contact details (satisfied today by generalContactEmail, already used for data-subject-rights requests in the privacy policy); a dedicated DPO contact is required only 'where applicable' under art. 37, which this site's current operating model (no accounts, no analytics/tracking, ephemeral per-request processing) does not appear to trigger. Only fill this in if the operator specifically wants a separate data-protection address distinct from general support.
1. Who is responsible for your data (the controller)
[The controller's confirmed legal identity is not yet published here - see the legal notice's incomplete-notice section. Do not treat this policy as complete until that is filled in.], operating theCHOSENCLOSET (thechosencloset.com), is the controller of the personal data described below. Contact: hello@thechosencloset.com.
2. What this site actually does with a styling request
When you fill in a styling brief, the information you enter - occasion, location, date, budget, dress code, style and colour preferences, size, any items you say you already own (including a photo of one, if you choose to add one), and any free text you write - is sent to this site's own server to generate your three looks. This happens on request, is not tied to an account (this site has none), and is not written to a database: the server processes the request and returns the result to your browser. Your IP address is read for each request solely to apply a short-term rate limit (to stop abuse of the service) and is kept only in that limiter's in-memory counter, never written to a log or a database.
Your current styling session (the brief you submitted and the looks it produced) and anything you save to "My Edit" are stored only in your own browser's local storage, on your own device - never on this site's servers. Clearing your browser's site data removes it. Closing the tab alone does not clear it (that is what makes "come back later and see your looks" possible), but nothing here is shared with other visitors or sent anywhere else by that storage.
3. The AI provider
Two parts of a styling request may be sent to Anthropic (the maker of the Claude models), as the site's AI provider: (a) freeform text you type describing your event or inspiration, to help structure it into a brief, and (b) a compact set of facts about your brief and the looks selected for you (occasion, city, date, dress code, style words, prices, and the names of the selected items), to write the plain-language explanation shown with each look. The actual recommendation logic - which products are chosen, scored, and assembled into looks - runs entirely on this site's own server and does not call the AI provider at all.
Checked directly against Anthropic's own published terms, not assumed from how this integration is coded: Anthropic's Commercial Terms of Service state that Anthropic "may not train models on Customer Content from Services" - Customer Content covers both what is sent to it and what it returns - so, to the extent this project's Anthropic account is governed by those standard terms, API requests made through this integration are not used to train Anthropic's models. Anthropic's published data-retention policy states a default of 30 days, after which API inputs and outputs are automatically deleted from its backend, with longer retention (up to 2 years) only for content its automated systems flag as violating its Usage Policy, and up to 7 years for the resulting classification scores - this is Anthropic's stated policy, not a guarantee this application itself can enforce or verify.
Still not yet confirmed: whether the specific Anthropic account issuing this project's API key is in fact governed by the standard Commercial Terms of Service above, rather than a different arrangement (for example a custom or zero-data-retention agreement) - that account- level fact determines whether the training and retention statements above actually apply here, and can only be confirmed by checking that account's own accepted terms, not by reading this site's code.
4. Hosting, security, and retention
This site is built to run on Cloudflare's hosting platform. Cloudflare, as the hosting provider, may process standard request/connection metadata (such as IP addresses) as part of operating its network, under its own role and policies - this is outside this application's own code and is not yet confirmed against Cloudflare's current terms for this specific deployment. Request bodies are size-limited and rate-limited at the application level; error logs record error details for debugging, not the content of your styling brief.
5. International transfers
Because data may be processed by Anthropic and by Cloudflare's global network (Section 3-4), processing may take place outside your own country, potentially outside the EEA. For Anthropic specifically, this has been checked: its Data Processing Addendum incorporates the EU Standard Contractual Clauses (plus UK and Swiss addenda) as the mechanism for any such transfer, to the extent this project's account is governed by that standard addendum (see Section 3 above on that account-specific caveat). Cloudflare's own transfer mechanism for its global network has not been checked against its current terms and remains not yet confirmed.
6. Cookies and similar technologies
See the dedicated cookie policy for exactly what this site stores in your browser and why.
7. Legal basis for processing
Generating the looks you explicitly request is processed on the basis that it is necessary to provide the service you asked for at that moment. The rate-limiting use of your IP address is processed on the basis of this site's legitimate interest in keeping the service available and free of abuse. Whether any part of this processing should instead rely on consent, and whether the legitimate- interest basis above would survive a balancing-test review, has not been confirmed by a privacy professional and should be before launch - this policy does not assume consent is the basis for everything, per the audit brief's own instruction.
8. Your rights
Because this site keeps no account and no server-side record of your styling brief once the response is returned, there is typically nothing stored on this site's own servers to access, correct, or delete on your behalf after the fact - your browser's local storage, which you control directly (clearing your browser's site data removes it), is where that information actually lives. Where EU/Spanish data protection law gives you rights over data a processor (Section 3-4) may hold about you, you can contact hello@thechosencloset.com and this will be passed on as appropriate. You also have the right to lodge a complaint with the Spanish data protection authority, the Agencia Espanola de Proteccion de Datos (AEPD).
9. Affiliate links
Affiliate monetisation is planned but is not active today: every outbound retailer link currently on this site is a direct link to that retailer's own product page, with no affiliate network, tracking parameter, or redirect involved. If and when that changes, this section and the site's own disclosure near product recommendations will be updated to say so plainly.
10. Contact and updates
Questions about this policy: hello@thechosencloset.com. This policy may be updated as the site's operating structure, AI provider terms, or affiliate status are confirmed; the date at the top reflects the last update.