SSWAGGES

Privacy

Your taste is personal.

Last updated: 28 July 2026

Who is responsible

SWAGGES is currently operated by its founder, Hendrix Johnson. The contact page explains the available contact route. A monitored public privacy email and formal controller address must be added before the beta is scaled.

What we collect

The public demo keeps reactions only in that page session. A beta application collects an email address, age band, clothing preference, agreement records and submission time. The app can store style choices, approximate age band, clothing preference, product reactions, saves, outfit requests, budget preferences and app settings. Security systems can process request information such as IP address, browser details and timestamps; short-lived hashed network identifiers are used to limit abusive submissions.

Purposes and lawful bases

Beta application details are used to take steps requested by applicants and administer beta access. Taste information is used to provide the personalised service a user requests. Essential security and reliability processing is based on SWAGGES’ legitimate interests in protecting and operating the service, balanced against user rights. Optional analytics and future affiliate enhancements remain off unless consent is given, and consent can be withdrawn through “Privacy choices”. If analytics is allowed, a random browser identifier is hashed server-side to measure aggregate 7- and 30-day return rates; it is never joined to an email or private taste profile. Legal obligations may require limited records to be retained.

Profiling and recommendations

SWAGGES uses age band, selected styles and product reactions to rank clothing and build outfits. This profiling changes recommendations; it does not make decisions with legal or similarly significant effects. “Why am I seeing this?” explains important recommendation signals, and taste settings can be changed or reset.

What we do not do

SWAGGES does not sell private profiles or identifiable individual taste data. Sponsored products must be labelled before a retailer click. Aggregate reporting must not be described as anonymous until minimum group sizes and re-identification safeguards are documented and tested.

Providers, recipients and transfers

Cloudflare Sites and D1 provide hosting, security and application storage. Retailer or brand content networks receive normal web request information when their product images load. A retailer receives browser request information when a user deliberately follows its link. These providers may process information outside the UK; SWAGGES must confirm the relevant contracts, locations and UK transfer safeguards before wider launch.

How long information is kept

Optional analytics events are deleted after 90 days. Analytics session identifiers last for the browser session. Hashed network rate-limit records expire after two hours. Device taste data remains until the user resets or deletes it, clears browser storage or removes the app. Signed-in profile data remains until account deletion. Beta-application retention still requires an approved maximum period; applications must not be kept indefinitely.

Your rights

Depending on the processing, UK data-protection rights can include access, correction, deletion, restriction, portability and objection. Consent can be withdrawn at any time without affecting earlier lawful processing. The app provides edit, reset, download and delete controls, but a verified contact route is still required for requests that cannot be completed in the app.

Your right to object: you can object to processing based on legitimate interests. SWAGGES must consider the request and stop unless it can demonstrate compelling lawful grounds.

If a concern is not resolved, you can complain to the UK Information Commissioner’s Office.

Children and age assurance

The beta is not available to children under 13 and does not claim to provide parental consent. Because SWAGGES is designed for people aged 13–17 as well as adults, the Children’s Code, age assurance, child-focused transparency, a data-protection impact assessment and best-interests testing require specialist review before public scale.

Changes to this notice

Material changes will receive a new date and consent version where consent is affected. Records collected under an older notice will not silently be used for a new incompatible purpose.