WeSearch
VSCO Terms of Use Explained: Why It Says It Isn’t Stealing Your Photos

VSCO Terms of Use Explained: Why It Says It Isn’t Stealing Your Photos

Jeremy Gray· ·8 min read · 0 reactions · 0 comments · 66 views
More from PetaPixel photography Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

VSCO is facing scrutiny over its Terms of Use, which some users find concerning. The platform's terms grant it extensive rights to use user-generated content, including the right to utilize individuals' likenesses. While VSCO asserts that such language is standard for platforms displaying user content, the lack of clear explanations raises concerns among photographers.

Key facts
About this source

PetaPixel files mainly under photography. We currently carry 92 of its stories.

Original article
PetaPixel · Jeremy Gray
Read full at PetaPixel →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherPetaPixel
Canonical URLhttps://petapixel.com/2026/05/26/vsco-terms-of-use-explained-why-it-says-it-isnt-stealing-your-photos/
Publication timeTue, 26 May 2026 21:55:22 +0000
Retrieval time2026-05-26T22:07:54.538Z
Last seen2026-05-26T22:07:54.538Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster3yaXQMG7czd_
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

VSCO Terms of Use Explained: Why It Says It Isn’t Stealing Your Photos May 26, 2026 Jeremy Gray Many photographers will remember the massive controversy Adobe found itself embroiled in nearly two years ago when photographers noticed just how invasive and overreaching the company’s updated Terms of Use were. The company quickly reacted. VSCO is now finding itself in a similar position, as users are taking notice of some concerning language in the platform’s Terms of Use. freestar.config.enabled_slots.push({ placementName: "PetaPixel_728x90_ATF_Desktop", slotId: "PetaPixel_728x90_ATF_Desktop" }); freestar.config.enabled_slots.push({ placementName: "PetaPixel_300x600_300x250_320x50_Mobile", slotId: "PetaPixel_300x600_300x250_320x50_Mobile" }); Photographer Simon Migaj was reading VSCO’s…

Excerpt limited to ~120 words for fair-use compliance. The full article is at PetaPixel.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from PetaPixel