Last updated: September 4, 2026
This page sets out how GeekBlog.net decides what to publish, how we verify it, how we correct it when we get it wrong, and where the line sits between our journalism and the advertising that pays for it. It applies to every writer and editor who works on this site.
1. Independence
Editorial decisions belong to the editorial team alone. No advertiser, affiliate partner, PR agency or manufacturer has any influence over what we cover, what we conclude or when we publish. Nobody outside the editorial team sees an article before it goes live, and no payment will buy a change to a published verdict or the removal of a story that is accurate.
2. Accuracy and sourcing
- We prefer primary sources: company statements, regulatory filings, changelogs, security advisories, court records, published research and our own testing.
- Where we build on the reporting of another publication, we credit it by name and link to it. We do not present another outlet’s work as our own.
- Numbers, dates, prices and specifications are checked against the source before publication and are dated in the text where they are likely to change.
- Claims we cannot verify are labelled as unverified, and we name who is making the claim. A rumour is reported as a rumour.
- Where a story concerns a company or a person, we give them a fair opportunity to respond, and we say in the article if they declined or did not reply by the time of publication.
3. Bylines and expertise
Every article carries the name of the person responsible for it, and each byline links to a profile describing that writer’s beat and listing their recent work. Writers cover areas they know, and specialist claims outside that area are attributed to a named source rather than asserted.
4. Use of AI tools
We use software tools in our workflow, including AI assisted research, summarisation, drafting and editing. We are open about that, and we set limits on it.
- No article is published without review and approval by a human editor.
- Facts, figures, quotes and links produced with the help of an AI tool are checked against the original source before publication. A model’s output is a lead, never a citation.
- We do not publish invented quotes, invented sources or invented test results, and we do not present AI generated imagery as a photograph of a real event.
- Responsibility for everything on this site rests with the editorial team, whatever tools were used along the way.
5. Reviews and testing
When an article is based on hands on use, we say so and describe the conditions: the model, the firmware or software version, how long we used it and how it was tested. When it is based on manufacturer specifications, published benchmarks or third party testing, we say that instead. We never imply hands on experience we did not have.
Review units, when we receive them, are loans that are returned, or are disclosed in the article if they are not. Accepting a unit, a briefing or travel never obliges us to publish, and never obliges us to be positive.
6. Advertising, affiliate links and sponsored content
The site is funded by display advertising and affiliate commissions, including through the Amazon Services LLC Associates Program. Affiliate links may earn us a commission at no extra cost to you, and they never determine which products we recommend. Any content that was paid for is labelled clearly on the page as sponsored or paid, and it is written to be distinguishable at a glance from editorial coverage. We do not sell links inside editorial articles. See the Disclaimer for the full commercial disclosure.
7. Corrections and updates
We correct errors quickly and openly.
- Typographical fixes are made silently.
- Factual corrections are made in the text and recorded in a correction note on the article, saying what was wrong and when it was fixed.
- Updates to a developing story are added with the date, so the original reporting stays visible rather than being quietly rewritten.
- Evergreen guides are revisited when the underlying software or hardware changes, and the revision date is shown.
To request a correction, email contact@geekblog.net with the subject line “Correction”, the article URL, the passage in question and a source. We check every report we receive.
8. Unpublishing
Published articles are part of the record and we do not remove them on request. We will correct an inaccuracy, add context, or in rare cases remove a personal detail where leaving it up would cause disproportionate harm or where the law requires it. We do not unpublish accurate reporting because a subject dislikes it, and we do not accept payment to take a story down.
9. Sources and confidentiality
We honour agreements about attribution. Where a source asks for confidentiality and we grant it, we protect their identity. We tell readers why a source is unnamed and what position they are in to know what they told us, so far as that can be done without identifying them.
10. Conflicts of interest
Writers disclose any personal or financial interest in a company they are covering, and step aside where that interest is material. Gifts of value are declined or disclosed.
11. Images and media
We use images we have the right to use, and we credit them where the licence requires it. Photographs are not manipulated in a way that changes what they show. Illustrations, renders and AI generated visuals are used only as illustration and are never presented as documentary photographs of a real event.
12. Comments
Where comments are open, we welcome disagreement and remove abuse, spam and link placement. Comments are the views of the people who write them, not of GeekBlog.net. The rules are in section 8 of our Terms and Conditions.
Questions about this policy, or about how a specific article was reported, go to contact@geekblog.net. See also About us and our Disclaimer.