“Commercial use allowed” does not mean copyright protection is assured, a photo release is unnecessary or a generated graphic is free of trademarks. A reliable publishing workflow distinguishes the model provider’s contract, the law of the relevant jurisdiction and the origin of every source image.
Four separate permission layers
First, confirm the tool/model agreement authorizes the planned business use on the actual plan. Second, confirm you have rights to upload input photos, artwork and client files. Third, check whether the output imitates a living person, protected mark or specific source artwork. Fourth, check local legal requirements for disclosure or consumer protection. Adobe’s August 2026 guidance notably separates Firefly from partner models rather than extending one blanket assurance to every model it can access.
Contractual output rights versus copyright
OpenAI’s January 2026 terms address contractual ownership between user and provider. The US Copyright Office stated in January 2025 that copyright in AI-assisted works depends on sufficient human-authored expressive elements, not prompt writing alone. These are not contradictory: allocation under a service contract and protection against third parties under copyright law are different issues. The US report must not be treated as a worldwide law.
Product examples with real caveats
Stability’s Community License uses a business-revenue condition, and BFL’s Kontext [dev] release specifies a non-commercial license. Midjourney’s 2025 historical agreement addresses user responsibilities and ownership exceptions. Adobe emphasizes licensed Firefly training data, while partner-model rights require separate review. The correct legal conclusion depends on the exact model, date, customer, territory and intended media, not a generic “AI images are safe” statement.
Create a rights packet
For each public asset keep the approved prompt, model ID, generation date, input-source credits and licenses, consent for recognizable persons, edits, reviewer and disclosure decision. Retain provenance data where supported; do not remove disclosure signals to hide manipulation. Assign unclear legal and country-specific questions to counsel and AI 11, and subscription terms to AI 10.
Worked scenario and failure test
A marketing department wants to generate an athlete-like portrait for an advertisement. Ask first whether it uses a real person’s likeness, a copyrighted photo reference or a recognizable team mark; image output ownership under service terms does not answer any of those questions. The project may need consent, model-specific commercial permission and brand authorization even if the image is entirely synthetic. Keep signed source releases and a vendor/version rights worksheet. For a US copyright claim, consult the human expressive contribution standard; for other countries, ask legal counsel instead of copying the US conclusion wholesale.
Decision guide and practical handoff
Require tool-specific rights review and human authorship/provenance evidence for important campaigns. A responsible review packet names the exact source or model version, the permitted input assets, the requested operation and the image characteristics a reviewer must check. It should also contain an unaltered reference, the accepted derivative, and a short record of what changed. A supported feature is not necessarily a reliable one for every brief, and the team must approve both technical appearance and real-world truthfulness before distribution.
Availability, price and geographic limitations
Research cutoff: 25 October 2026. Release dates and historical tier details above are explicitly dated. Unless independently confirmed for a named country and account tier, current availability, billing currency, credit consumption, API quota and commercial entitlement are unknown—not universal. Consult official regional terms and AI 10’s dated price snapshots before procurement; do not treat a historical announcement as a live entitlement. No application, model, API response or image output was hands-on tested for this article.
Sources & Further Reading
- Adobe Stock AI Studio commercial use — published/updated 2026-08-18 (consulted at research cutoff 2026-10-25).
- OpenAI ROW consumer terms effective Jan 1 2026 — published/updated 2026-01-01 (consulted at research cutoff 2026-10-25).
- USCO 2025 AI copyrightability report announcement — published/updated 2025-01-29 (consulted at research cutoff 2026-10-25).
- FLUX.1 Kontext dev licensing announcement — published/updated 2025-06-26 (consulted at research cutoff 2026-10-25).
- Stability community license update — published/updated 2024-07-05 (consulted at research cutoff 2026-10-25).
- Midjourney April 17 2025 terms historical — published/updated 2025-04-17 (consulted at research cutoff 2026-10-25).