Skip to main content

Research & editorial standards

Inkrypt Editorial

Research, fact-checking and plain-English editing

Inkrypt Editorial is responsible for everything that is not the cryptography itself: the research behind comparison articles, the accuracy of claims about other tools, readability, and the correction process when we get something wrong.

Our working rule is that a reader with no security background should finish an article able to make a decision, and a reader with a security background should not find anything in it they would have to correct. Those two goals pull against each other constantly, and most of the editing work is negotiating between them.

Every factual claim about an algorithm, a standard, or a third-party product must trace to a primary source — an RFC, a NIST publication, an OWASP cheat sheet, or the vendor's own documentation. Claims that cannot be sourced get cut, not hedged.

About this byline

Inkrypt Editorial is an organisational byline, not an individual. It covers the research, fact-checking and editing work behind everything published here, and is kept separate from the security byline so it is clear which claims carry engineering authority and which carry research authority. Corrections and sourcing questions reach it at the address below.

Areas of expertise

  • Technical writing and documentation
  • Source verification and fact-checking
  • Privacy and data-protection concepts
  • Comparative product research

Responsibilities on this site

  • Fact-checks every published article against primary sources
  • Maintains the glossary and internal linking structure
  • Handles corrections and scheduled content reviews

Contacting this team

Corrections, sourcing questions and feedback on anything published under this byline go to the address below, or through the contact form. How corrections are handled once received is set out in the editorial policy.

work.securetext@gmail.com