Editorial Policy.
Accuracy, context and transparency matter more than publishing first. These standards describe how we intend to report on AI research, software releases and technology products.
Show the evidence.
We aim to identify the original announcement or research behind a claim and make its limits visible. A company’s performance claim is attributed to that company, not presented as an independent finding.
Tell readers what was tested.
We distinguish release reporting, hands-on reviews, practical tutorials, opinion and comparisons. We do not imply direct product testing or independent benchmarks when no such testing occurred.
Sourcing and verification
Whenever practical, stories link to primary documentation, official product announcements, research publications or publicly available technical evidence. For material claims, we check dates, names, product availability and the distinction between a demo, preview and generally available release.
We seek corroboration for disputed or consequential claims. The absence of independent verification is itself relevant and should be explained. Readers should not treat vendor benchmark charts as independently verified results.
What each article means
News brief: a clearly attributed account of a reported announcement. Guide: educational material with steps, examples and stated prerequisites. Comparison: an explanation of capabilities, trade-offs and source limitations. Review: only used when actual hands-on evaluation has been performed and its scope can be described. Analysis: interpretive conclusions distinguished from verified reporting.
Use of AI in the editorial process
AI tools may assist with research organization, outlining, translation, drafting or visual design. Generated material is not a substitute for source verification. Before publication, a responsible editor should review factual claims, cited sources, quotes, dates, links and legal or safety implications.
We do not invent interviews, direct quotes, hands-on experiences or product screenshots. AI-generated or conceptual images should be identified as illustrations when a reader might otherwise mistake them for actual events or interfaces.
Images, screenshots and rights
Visuals may include licensed photography, official press materials, original illustrations and clearly labeled conceptual artwork. Usage rights, licenses and attribution requirements must be checked before reusing third-party content. A caption should not imply that a conceptual rendering is an authentic product screenshot or photograph.
Requests concerning an image’s provenance or rights can be raised via our Contact page.
Advertising and editorial independence
Advertisers and sponsors must not secretly determine editorial conclusions. Any sponsored article, advertorial, affiliate relationship or material commercial consideration that could affect reader understanding should be disclosed clearly near the relevant content.
We aim not to offer positive coverage in exchange for payment. Product names are used for identification, not to imply affiliation or endorsement.
Corrections, updates and removals
Readers can report an error by identifying the page, disputed statement and supporting source. We review credible reports and correct factual mistakes. Material corrections should explain what changed and, where useful, when the change was made. Minor spelling and formatting changes may be made without a formal notice.
Articles about fast-moving products may be updated when features, pricing or availability change. When content has materially changed, an updated date and editorial note should make that clear. A request for deletion or removal will be assessed case by case, including applicable legal obligations.
Conflicts, feedback and ongoing improvement
Contributors should disclose material conflicts of interest. We aim to correct misleading framing, distinguish our analysis from reported facts, and explain important sourcing limits. A published policy is a commitment to follow through, not a substitute for genuine editorial review.
Questions about this policy and correction requests may be directed to support@getrunway-app.com or through the Contact page.
Publisher: James V. Rosano & Son, Inc. · 59 HULL ST, Cohasset, MA 02025, United States · Website: getrunway-app.com. · Telephone: +1 (781) 383-6048