Scope and authorship
This policy applies to the FreeGPTBanana Blog and related public learning resources. Product-owned articles use the byline FreeGPTBanana Editorial. We do not assign a personal identity, credential, or first-hand experience to that byline unless the named contributor and claim can be verified.
Preparation and review context
Each guide must state its editorial scope, review date, and relevant provider/model context when it discusses model behavior. Instructional prompt examples are identified as templates; they are not presented as quantitative benchmarks unless a reproducible benchmark method and results are published with them.
Provider capabilities change. Articles use a visible modified date and should be rechecked when the active generation model or cited official documentation materially changes.
Sources
Capability claims should link to current primary documentation from the provider. General creative advice may be based on observable workflow principles, but the article must distinguish that guidance from provider-specific facts and avoid unsupported performance or quality claims.
Generated visuals
Blog cover images may be generated through the site's current image provider integration. A generated cover is an illustration for the article, not evidence that every prompt template in the article was run as a test suite. Articles disclose the relevant provider and model in their methodology notes.
Corrections and updates
Factual corrections and material methodology changes update the page's modified date. To report an issue, email the support address and include the article URL, the statement in question, and any primary source that supports the correction.
[email protected]