Trust and corrections
Editorial and Corrections Policy
How PicSpeak reviews educational and product content, handles corrections, discloses AI assistance, documents sources, and manages sponsorship or conflicts.
Last reviewed: 2026-08-09
Editorial Review
PicSpeak content is written or edited by Asa Zhou for photographers and creators who use AI critique as a repeatable learning loop. Product pages, Lens Notes summaries, prompt-library descriptions, and AI-facing markdown mirrors are checked for consistency with the public product experience before publication.
Corrections
When a factual issue is found, PicSpeak updates the affected page as soon as practical and keeps the corrected claim close to the original context. Material product, pricing, or policy changes are reflected on the relevant public page and may also be summarized in Updates.
Dates and Review Cadence
Evergreen trust and AI-discovery surfaces use explicit review dates when the page format supports them. The AI markdown mirrors and llms.txt currently use a last reviewed date of 2026-08-09 so crawlers can separate current editorial guidance from older product notes.
AI-Assistance Disclosure
PicSpeak uses AI systems in the product itself for photo critique and visual-reference generation. Public editorial text may be drafted, checked, or reformatted with AI assistance, but factual claims, source links, product boundaries, and final publication decisions remain under human review.
Source and Provenance
Product claims should be traceable to the live PicSpeak interface, source code, public update notes, or cited creator/source pages. Prompt-library examples identify the original source URL and author handle when known, and PicSpeak describes its adaptation boundary without claiming extra license rights.
Sponsorship and Conflicts
PicSpeak may operate affiliate or paid product flows, but editorial guidance should not present paid placement as independent evaluation. Any sponsorship, commercial relationship, or material conflict that affects a public recommendation should be disclosed near the relevant content.
Contact
Send correction requests, source questions, or conflict disclosures to xavierzhou23@gmail.com. Include the page URL, the claim at issue, and any supporting source so the correction can be reviewed quickly.