Editorial Policy
Last updated: October 31, 2026 · Reviewed by the Shot after Shot editorial team
Shot after Shot publishes guides about taking photos in a browser photo booth: running a group session, choosing a frame, fixing camera problems, lighting a webcam, and printing strips. This page explains who writes them, what we check before publishing, and how we handle mistakes. It applies to every article on the site, not just the newest ones.
Who writes and reviews
Guides are produced by the Shot after Shot editorial team. Each piece is written by an editor and reviewed by a second editor before publication. The review checks that the advice matches how the booth actually behaves, that instructions are in the right order, and that sources are linked. Bylines name the team while the site is transitioning to named author pages; when a named editor takes responsibility for a piece, the byline and author page will show it. Guides published before October 2026 are being reviewed against this process; until a guide is reviewed, its byline does not imply that a second editor has checked it.
How topics are chosen
We choose topics from questions people ask in support messages, from problems that appear while testing the booth, and from searches where the existing results do not answer the question for a browser-based photo booth. We do not publish a page for a keyword unless we can say something useful about it that is specific to this product and its constraints.
Sourcing and evidence
When a guide makes a factual claim about a browser, a device, or an advertising or privacy rule, we link to the primary source: browser documentation, MDN, Google's published policies, or the relevant vendor help page. Advice about the booth itself comes from using the booth. Where we describe a limitation, we say what we could not verify instead of guessing.
Testing
Flows that can be tested in a browser are run before a guide is published. That includes camera permission steps, joining a room, capture timing, editing, and downloading a strip. The methodology page explains what we test and what we cannot test from our own devices. Guides that describe a test should name the browser and device used; if a guide does not, treat the advice as general guidance rather than a tested result.
Use of AI tools
Editors may use AI-assisted drafting, outlining, or copy editing. AI output is not published without a human editor checking the claims, rewriting where the draft is generic, and taking responsibility for the final text. We do not generate pages at scale from a single template and present them as independent articles, and we do not use AI to invent tests, quotes, authors, or dates.
Photos, screenshots, and consent
Session photos are deleted after seven days. When a strip or screenshot is used in a guide, it becomes a separate editorial asset: we publish it only with the written consent of every identifiable person, keep a record of what they agreed to and for which channels, and remove it on request if consent is withdrawn. Screenshots come from our own sessions. We do not publish photos from user sessions without written consent. Frame and sticker artwork is either made for the site or used under a license that allows it.
Dates and updates
Every article shows the date it was published. When we change the substance of a guide, we update it and record the change on the corrections page. We do not change a publication date to make an old article look new. When a guide is reviewed without substantive changes, the review date is updated separately.
Corrections
If something is wrong, tell us. We correct factual errors, clarify ambiguous instructions, and update advice that no longer matches the product. The corrections page explains how to report an issue and what happens next.
Advertising independence
Advertising is sold by Google AdSense and is separate from editorial decisions. Advertisers cannot buy a recommendation, a ranking, or a place in a guide. Sponsored content, if we ever publish it, will be labeled and kept out of guides.
Contact
Editorial questions and correction requests can be sent to [email protected].
Related: How we test · Corrections · Who writes for us · Contact