sorted.pics
Book your event

Legal

Datenschutzerklärung

What sorted.pics does with personal data, written specifically about this site rather than in general. The part that matters most is the photographs, because the people in them never filled in a form.

KurzfassungThe short version

  • The archive publishes photographs of identifiable people. You can have one taken down, and the route is on this page.
  • No analytics are running yet, and they are planned, so the notice at the bottom of the page says so in advance. Two cookies exist, both only after you sign in to a photographer account, and both only to keep you signed in.
  • Photographers give us an email address. It is stored and never published.
  • The site runs entirely on Cloudflare, and the typefaces are currently loaded from Google, which sends your IP address to Google.

VerantwortlicherController

Name
[[LEGAL ENTITY NAME]]
Anschrift
[[STREET AND HOUSE NUMBER]]
[[POSTCODE AND CITY]]
E-Mail
hello@sorted.pics
Datenschutzbeauftragter
[[DATA PROTECTION OFFICER, OR STATE THAT NONE IS REQUIRED]]

The full provider identification is in the Impressum. A data protection officer is only required in some cases, so the honest options are to name one or to say plainly that the threshold is not met.

Fotografien von PersonenPhotographs of people

This is the most significant processing on the site, so it comes first.

The archive at sorted.pics, and the image host at img.sorted.pics that serves the files, carry photographs taken at fashion week shows: models on the runway, guests in the audience, and backstage and production staff at work. A large number of the people in them are recognisable. A photograph of a recognisable person is personal data under Art. 4 No. 1 GDPR, and publishing it is processing, whether or not anybody's name is written next to it.

Rechtsgrundlage

The operator relies on Art. 6 para. 1 lit. f GDPR, a legitimate interest in documenting a public event and in distributing press photography from it, read together with §§ 22 and 23 KUG, which allow the publication of images of contemporary history and of people who appear as part of a public gathering. Where an event's accreditation terms or a model release already cover publication, that agreement is the stronger basis and takes precedence over this one.

The basis is not the same for everyone in the archive, so it is written here as two groups rather than one sentence.

People who took part in the event. Models on the runway, designers, and accredited guests and press are published under Art. 6 para. 1 lit. f GDPR together with § 23 para. 1 no. 3 KUG, which permits images of a gathering that the person depicted took part in. Munich Fashion Week is a public, ticketed, press-covered event, photography at it is expected, and a photograph of a runway walk documents work its subject did in public and in a professional capacity. The operator weighed that against the interest of the person shown and concluded it prevails for this group, on these conditions: no frame is captioned with the name of anyone other than the photographer, single-frame pages are excluded from search engines and from the sitemap, no attempt is made to identify anyone, and the objection route below is open to everybody with no conditions attached.

People who were at work and not taking part. Catering, security, cleaning, venue and production staff did not attend the gathering in the sense § 23 KUG means, and a person doing their job is not documenting their own public appearance. The balance under Art. 6 para. 1 lit. f GDPR does not come out the same way for them, and this archive does not claim that it does. A frame whose subject is a member of staff rather than the event is removed on request without any weighing at all, and the operator removes such frames on its own initiative where it notices them.

Where accreditation terms or a model release already cover publication, that consent under § 22 KUG is the stronger basis and takes precedence over the paragraphs above. Consent given that way can be withdrawn, and withdrawing it has the same effect as an objection.

§ 23 para. 2 KUG limits all of this: an image may not be published where it harms a legitimate interest of the person shown. That limit is not a formality here. A frame that shows someone in distress, unwell, undressed beyond what the show itself put on stage, or in a way that holds them up to ridicule falls outside every basis named above, whatever the setting was.

Backstage is the hardest case in this archive and is treated as the strict one. A dressing area is a workplace and a changing room at the same time. Frames from it are published only where the people in them are working models and staff who knew photographers were present, and a backstage objection is answered by removal rather than by argument.

Widerspruch und Löschung

Anyone who appears in a photograph can have it taken down. There is no form, no account and no fee.

Write to hello@sorted.pics. Include the share link, or the frame number printed in the corner of the frame, or a description good enough to find it, and say that you are the person in the photograph.

What happens then, as a commitment and not as an aspiration:

  • Your message is acknowledged within 3 working days.
  • The frame is hidden from the archive and from every share link while the request is looked at, before any decision is taken about it.
  • You get a decision, with reasons, within 14 days.
  • If it is removed, it goes from the archive, from the manifest and from the image store, so links that were already forwarded stop resolving to it.

No proof of identity is asked for as an opening move. If a request is not obviously about the person making it, the operator may ask for enough to be sure and no more, and will say why.

Daten der Fotografinnen und FotografenPhotographer data

A photographer reaches their own profile through a signed link that is theirs alone, and edits four fields: display name, Instagram handle, website and email address. The site also holds the credit spellings their files arrived under, an internal slug, and the moment they last confirmed their details.

Published
Display name, Instagram handle, website, and the number of frames credited to them. These appear on the photographers page and beside their work.
Never published
The email address. It is stored so the operator can reach a photographer about their own frames, and it is not returned by the public listing, not rendered on any page, and not passed to anyone else.

That is not a promise made only here. The public listing selects the name, handle, website and frame count and does not read the email column at all, and the edit form tells the photographer the same thing at the moment they type it in. The form, the code and this page have to agree, and they do.

Lawful basis: Art. 6 para. 1 lit. b GDPR, because being credited correctly is the substance of the arrangement with a photographer, and Art. 6 para. 1 lit. f for the internal contact address.

There are no accounts and no passwords. The link itself carries who you are and is signed by the server, so it is a credential and should not be forwarded. If a link is exposed, the operator can invalidate every link at once by rotating the signing secret.

Hosting und AuftragsverarbeitungHosting and processing

The whole site runs on Cloudflare. Cloudflare, Inc. is the processor, acting on the operator's instructions.

Workers
Runs the site and its API routes.
R2
Stores the photographs, in a private bucket that is reachable only through the site's own image route.
D1
Holds the label corrections and the photographer table, including the email addresses described above.
Durable Objects
Runs the live gallery room behind live.sorted.pics, one per event, holding the open connections and a recent photo log.

Because Cloudflare serves every request, it processes connection data including your IP address, the page requested, the time, and your browser's user agent, in order to deliver the site and to protect it from attack. Request observability is switched on for both Workers, so this metadata is retained by Cloudflare for its standard period.

Still open
[[CLOUDFLARE CONTRACTING ENTITY AND ITS ADDRESS]]
[[ART. 28 GDPR PROCESSING AGREEMENT, DATE SIGNED]]
[[CONFIRMED CLOUDFLARE LOG RETENTION PERIOD]]

Schriftarten von GoogleGoogle Fonts, and why it is named here

Every page on sorted.pics loads its typefaces from Google's servers at fonts.googleapis.com and fonts.gstatic.com. Your browser makes that request itself when the page opens, which means your IP address reaches Google before you have agreed to anything and whether or not you wanted it to.

This is stated because it is true of the site as built today, not because it is a good arrangement. Serving the same three typefaces from sorted.pics itself removes the transfer completely and changes nothing a visitor can see. Until that is done, it is disclosed rather than hidden.

[[SELF-HOST THE TYPEFACES, OR NAME GOOGLE AS A RECIPIENT AND OBTAIN CONSENT]]

Cookies und SpeicherungCookies and storage

A small bar at the bottom of the page says this site uses cookies and browser storage. It is a notice, not a question. Nothing on the site waits for you to answer it, and pressing Got it only makes it go away.

Was heute gespeichert wird

Checked in the source, not assumed.

  • No analytics running yet. No Google Analytics, no tag manager, no Plausible, Matomo, PostHog, Fathom, Mixpanel, Segment, Hotjar or Clarity, no tracking pixel, no session recording and no A/B tooling. The site was searched for every one of them and none is present. Measurement is planned, and the notice names it in advance.
  • Two cookies, and only if you sign in. Reading the archive sets none. Sending photographs through a shared link sets none. Signing in to a photographer account sets these two, and signing out removes them.
    • __Secure-sp.session_token is the session itself: a random value that tells the server which signed-in person is asking. It lasts 30 days.
    • __Secure-sp.session_data holds a signed copy of your own name, email address and session expiry for 5 minutes, so an ordinary page view does not have to ask the database again.
    Both are marked HttpOnly, so no script on the page can read them, Secure, so they are only ever sent over HTTPS, and SameSite=Lax, so another website cannot make your browser act as you. Neither is used to measure anything, and neither follows you to another site.
  • Why those two need no consent box. German law here is §25 TDDDG, which covers storing anything on your device, cookies and browser storage alike. Its second paragraph exempts storage that is strictly necessary to provide a service you explicitly asked for. Staying signed in after you have signed in is that. Optional measurement is not, and is dealt with below.
  • Two keys in localStorage, and that is all. sp-theme holds either light or dark, so the site opens in the theme you last picked. sp-notice records that you have seen the bar, so it does not come back. Neither is ever attached to a request, both are readable only by sorted.pics, and clearing your site data removes them. Neither key identifies anybody.

Wenn Messung dazukommt

Analytics and an advertising pixel are planned. When they arrive they will load for everyone, not behind a click, which is what the notice at the bottom of the page is telling you. If you would rather not be counted, a tracker blocker or your browser's own protection stops them, and nothing on this site breaks when they are blocked. You can also write to the address in the Impressum and ask to be left out.

SpeicherdauerRetention

Photographs
Kept for as long as the archive is published, which is intended to be open ended, and removed sooner on a successful objection.
[[FIXED RETENTION PERIOD, IF THE OPERATOR SETS ONE]]
Photographer records
Kept while their work is credited in a published archive.
[[WHAT HAPPENS TO THESE WHEN AN ARCHIVE CLOSES]]
Request logs
Held by Cloudflare for its standard period, as described above.

Ihre RechteYour rights

You have the right to access your data (Art. 15), to have it corrected (Art. 16), to have it erased (Art. 17), to have its processing restricted (Art. 18), to receive it in a portable form (Art. 20) and to object to processing based on legitimate interests (Art. 21). Where processing rests on consent you can withdraw it at any time, without affecting what was lawful before.

Write to hello@sorted.pics. If your request is about a photograph you appear in, the timings set out above apply.

You can also complain to a supervisory authority, in particular the one for the operator's place of business or for where you live.

[[COMPETENT SUPERVISORY AUTHORITY AND ITS ADDRESS]]

Was noch offen istStill to be settled

  • Controller name and address, and whether an officer is required.
  • The lawful basis for publishing photographs of identifiable people. This one is a decision, not a detail.
  • The Cloudflare contracting entity and a signed Art. 28 processing agreement, plus its confirmed log retention.
  • Google Fonts: self-host the three typefaces, or name Google as a recipient here and ask for consent.
  • Retention periods for photographs and for photographer records.
  • The competent supervisory authority.