Short answer: On 10 November 2026 VSCO updated its Creator Content Standards, effective that day, to say that if you are a paid member or a non-paying creator, your public or private creator content will not be used to develop, train or improve AI or machine-learning models for generative AI use. The same page still allows public creator content to be used for non-generative AI uses such as search, recommendations, content moderation and editing tools, and it says private content and personal information are not used for those non-generative training purposes. VSCO also says it will not train on the public content of known minors, and that third-party AI providers must contractually agree not to train generative models on public creator content submitted through its services. PetaPixel reported the same day, quoting a letter from CEO Eric Wittman. Keep dated originals of the work you post, and a copy of the standards as they stood. A TimeBind cannot change VSCO’s policy, bind a third party, or stop off-platform scraping.
Last checked 12 November 2026. General information for photographers and other creators who use VSCO, not legal or platform-policy advice. The Creator Content Standards page is quoted as it stood when we fetched it on 12 November 2026, when it was marked effective 10 November 2026. Policies can change. A platform promise is not the same as a technical bar on scraping, and a dated file does not opt you out of a model or change a term of use.
Table of Contents
What VSCO updated on 10 November 2026
VSCO’s Creator Content Standards, at the company’s support centre, were marked “Effective November 10, 2026” when we fetched the page on 12 November 2026 (the page also said it was updated that week). That date, not an older terms-of-use debate, is the official hook for this article.
Under the heading “AI License Rights,” the standards say: if you are a paid member with an active VSCO membership or a non-paying creator on VSCO, your public or private creator content will not be utilised to develop, train, or improve AI or machine-learning models for Generative AI Use. The page defines Generative AI Use as using a model or feature where the intended output is new expressive content, including images, text, audio, video or other media, in response to prompts or other inputs. That is distinguished from Non-Generative AI Uses, which process content or data without producing new expressive content as the intended output. Examples given include labels, embeddings, search results, recommendations, content moderation, editing tools, or similar functional outputs.
The standards also say that only public creator content may be used to develop, train, operate or improve models or features for those non-generative uses; that VSCO does not use private creator content or personal information from any creator for those purposes; and that it will not train on the public creator content of known minors (a creator VSCO has used reasonable methods to determine is under 18). On vendors, VSCO says it requires any third-party AI provider it works with, for a current or future feature, to agree contractually that they will not train generative AI models on public creator content submitted through its services. Public creator content shared for AI training is, the page says, anonymised where possible.
The standards separately prohibit unauthorised data scraping or bulk collection of VSCO creator content, and commercial use of public creator content without VSCO’s or the creator’s consent. A rule in a standards document is not the same as a technical barrier on the open web. See what to keep when you post work online and want to limit scraping and what a shared robots.txt AI-training opt-out can and cannot do.
PetaPixel, on 10 November 2026, reported the update and quoted a letter from VSCO CEO Eric Wittman sent to users that day. PetaPixel quoted Wittman saying VSCO does not use public or private work to train generative AI models, whether or not the creator pays, and that machine learning used for search, recommendations and editing is different from training models that generate new content. Those quotes are from PetaPixel’s report of the letter, read on 12 November 2026, alongside the standards page itself.
Why dated originals and a copy of the policy matter
Platform language about AI training has changed before, on VSCO and elsewhere, and it can change again. If you relied on the 10 November 2026 wording, keep a copy of that page or a screenshot with the date. If you post photographs or video to VSCO, the files that matter most are still the originals you hold yourself — the camera file or the master edit — not only the version sitting in an app. A policy statement does not timestamp your work, and a timestamp does not rewrite a policy.
Demand around this update was official-led and modest on social media. PetaPixel’s account, @petapixel, posted about the standards update on 10 November 2026 at 20:50 UTC; that post had 2,378 impressions in our in-window measurement, with two smaller related posts the same week. Google autocomplete in the United States on 12 November 2026 did not return policy-worded suggestions for “vsco ai training” or “vsco will not train ai”; a query for “vsco ai photos” suggested the photo-editor product, which is a different topic. We are not treating those editor suggestions as demand for this policy. The demand picture is the official effective date, same-day trade press, and a modest official-publisher post on X.
This is also a different control from Meta’s Instagram and Facebook training opt-out, or from a photograph being accused of being AI-generated. See how to keep a record of a Meta AI-training opt-out and what to keep if a night-sky photograph is accused of being AI.
Practical checklist for creators who use VSCO
- Read the current Creator Content Standards, including the definitions of generative and non-generative use, before you assume what is or is not allowed. The page we fetched was effective 10 November 2026. Save the wording you relied on, with the date.
- Keep originals off-platform. Unpublished Studio content, the standards say, is saved only on device unless you opt in to cloud sync as a paid member. Your camera file or master edit is still the record you control if an app or a setting changes.
- Notice the paid-versus-free line. The generative-training promise is stated for both paid members and non-paying creators, and for public and private creator content. Do not assume other VSCO features are the same for free and paid accounts; membership still changes tools and visibility, according to the same page.
- Notice the non-generative exception. Public creator content may still be used to develop, train, operate or improve models for search, recommendations, moderation, editing tools and similar functions. Private content and personal information are excluded from those uses, on the standards as fetched. If that distinction matters to you, keep a dated copy of it.
- Do not treat a contractual promise by a vendor as a technical bar on scraping. The standards prohibit unauthorised scraping and say providers must agree not to train generative models on content submitted through VSCO. Work that is also on a public website, a social app or a portfolio can still be collected elsewhere. See the scraping page.
- If you deactivate, delete or password-protect work, keep a dated note of what you did and a copy of the file you removed. The standards list visibility controls, including private Spaces, password-protected Galleries for some memberships, deactivation and deletion. Deletion from VSCO is not the same as deleting your original.
- Date the pack you would actually rely on: originals, a copy of the 10 November standards (or the later page you actually used), and any screenshot of a setting. A TimeBind of that zip records that exact pack. It does not change VSCO’s policy.
What a TimeBind does and does not show
A TimeBind is a dated, checkable record that an exact file existed no later than a recorded time and still matches. The SHA-256 fingerprint is made in your browser and the file is never uploaded. The record is anchored to Bitcoin (a Merkle root in an OP_RETURN). Your first Pooled TimeBind is free; after that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. See how it works.
Here it is useful for a folder of original photographs or video, a PDF or screenshot of the Creator Content Standards, and a note of a visibility or membership setting.
A TimeBind does not change a platform policy, does not bind a third-party provider, does not prevent scraping, and does not prove that a photograph was or was not used to train a model. It is one piece of a timeline of the files you kept.
Limits
This article summarises VSCO’s Creator Content Standards as marked effective 10 November 2026 and read on 12 November 2026, plus PetaPixel’s same-day report of a CEO letter. Policies and vendor contracts can change. We are not certifying VSCO’s training practices, any third party’s practices, or any photograph. This page is not legal advice. Other platforms have different rules.
Tools that can help
Use the bulk SHA-256 manifest for a folder of originals and a saved copy of the standards, and keep a dated copy of the exact set you hold yourself.
If you are worried that your images were used to train an AI model, see also the free AI image training dispute record checklist. It looks at originals, rights, terms and dated captures. It is not legal advice and cannot show whether a model used your images.
Frequently Asked Questions
-
Does VSCO now promise that it will not use my photos to train generative AI, even if I am on a free account?
The Creator Content Standards, effective 10 November 2026, say that paid members and non-paying creators are covered, and that public or private creator content will not be used to develop, train or improve models for generative AI use. Read the current page for the full wording, including definitions.
-
Can VSCO still use my public posts for AI at all?
Yes, for what the page calls non-generative AI uses, such as labels, embeddings, search, recommendations, content moderation and editing tools. It says only public creator content may be used for those purposes, not private content or personal information, and not the public content of known minors.
-
Does this stop other people or other companies from scraping my work?
No. The standards prohibit unauthorised scraping on VSCO and set contractual terms for VSCO’s own AI providers. That is not a technical bar, and it does not control copies of your work on other sites. A TimeBind does not stop scraping either.
-
Does a TimeBind change VSCO’s policy or prove a photo was not used for training?
No. A TimeBind is a dated, checkable record that an exact file existed no later than a recorded time and still matches. It does not alter a platform policy and it does not prove how a file was later used.
-
Is this the same as Meta’s Instagram or Facebook training opt-out?
No. Those are different products and different controls. VSCO’s 10 November update is a change to its own Creator Content Standards. Keep a record of each platform’s wording separately.
Sources checked
- VSCO, “Creator Content Standards,” effective 10 November 2026, https://support.vsco.co/en/articles/12698611-creator-content-standards (fetched 12 November 2026)
- PetaPixel, Jaron Schneider, “VSCO Updates Its Policy to Explicitly State It Won’t Train AI on Your Photos,” 10 November 2026, https://petapixel.com/2026/11/10/vsco-updates-its-policy-to-explicitly-state-it-wont-train-ai-on-your-photos/ (read 12 November 2026; includes quoted letter from CEO Eric Wittman)
- X, @petapixel, 10 November 2026, 20:50 UTC, 2,378 impressions as measured from in-window search, plus two smaller related posts the same week
Date the originals and policy copy you keep yourself
Your first Pooled TimeBind is free, with no credit card required. After that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Click here to start, or see plans and pricing.
