How DeskZap researches, writes and maintains its content.
This page answers the question Google calls the How test: who creates the content on this site, how is it created, and what are the standards. If you are evaluating DeskZap as a remote desktop vendor, this is what you should know about how we present ourselves.
Six things we hold ourselves to.
If any of these would be uncomfortable for us to defend in front of an experienced IT buyer, we will not publish the page.
Written by the team that builds the product
Every guide and blog post is written by the DeskZap engineering team. Our author is Jorge Monteiro, Senior App Architect at Hot Rocket Software Ltd, the company that builds DeskZap. We do not use freelance writers, agencies, or anonymous contributors for our guides.
Tested against real products, not marketing copy
Every comparison (TeamViewer, AnyDesk, Chrome Remote Desktop) is based on hands-on testing of the current public releases as of the guide's last-updated date. We cite the vendor's own current public pricing page where it matters, and we do not accept payment or sponsorship in exchange for coverage. If a vendor gives us feedback on an error, we correct it and note the change in the revision history.
Every factual claim is sourced
Security, compliance and pricing claims are backed by primary sources: the National Cyber Security Centre (NCSC), the Information Commissioner's Office (ICO), UK GDPR Article 32, the vendor's own public documentation, and the Office for National Statistics (ONS). Each guide and blog post ends with an External references section that lists every source we used, with a direct link.
Updated when the underlying facts change
Every guide and blog post shows its publication date and last-updated date at the top. We re-review the comparison guides quarterly because remote desktop vendors change pricing and features frequently. The security guides are reviewed when the ICO, NCSC or UK GDPR framework publishes material updates. If a guide is more than 12 months old, we add a 'last reviewed' notice.
Honest about what we do not know
Where information is uncertain (for example, how a vendor will price a future tier, or how regulators will interpret a new guideline), we say so. We do not present speculation as fact. Where we are wrong, we correct the page and add a dated note at the bottom explaining what changed and why.
AI-assisted, human-reviewed
We use AI tools to draft and edit content, but every published page is reviewed by a named human author before it goes live. AI assists with research, structure and proofreading; the editorial decisions and accountability remain human. This is in line with Google's helpful-content guidance, which evaluates content on its usefulness and originality, not on how it was produced.
From research question to published page.
The five steps every DeskZap guide or blog post goes through before it appears on this site.
- 01Research
We start from a real user question, not a keyword list. The question usually comes from a customer email, a sales call, or a pattern in our support inbox. We then gather the primary sources we need to answer it accurately.
- 02Draft
The draft is written in plain English with specific numbers, named vendors and concrete examples. We do not use filler phrases. Every claim that could be checked is checked against its source during the draft, not after.
- 03Review
A second person reads the draft for technical accuracy, completeness, and whether it actually answers the question. For comparison guides, we re-test the competitor product on the day of publication to make sure the screenshots and pricing are current.
- 04Publish and date
The published page shows the date and the last-updated date. If a guide covers a fast-changing topic (vendor pricing, security guidance), the last-updated date is updated and a brief note explains what changed.
- 05Maintain
Every page is on a review schedule. Guides on vendor pricing are reviewed quarterly. Security guides are reviewed when the regulator publishes material updates. If a reader flags an error, we fix it within one working week.
If a fact on this site is wrong or out of date.
Tell us. We fix factual errors within one working week. For corrections, we add a dated note at the bottom of the page explaining what changed. Corrections are not just a silent update: the page shows its history.
- URLThe exact page URL where the issue appears
- QUOTEThe specific claim that is wrong or out of date
- SOURCEA link or reference to the correct information (if you have one)
- CONTACTHow we can reach you if we have questions (optional)
We do not require attribution. Anonymous corrections are welcome.