Editorial policy

This page explains how the guides, comparisons, articles, glossary terms and tool pages on crunu.com are written and checked. Pages signed "Crunu team" link here.

Who writes these pages

Pages are written and published by the team that builds Crunu at KeepFlow L.L.C-FZ, the company described on the about page. We sign them "Crunu team" and don't put individual names on the site.

Crunu is a commercial product, and many of these pages compare it with other products. Comparison pages say so at the top, with a "Written by Crunu" note, and roundups list what Crunu lacks next to what it does well.

Where facts about Crunu come from

Every statement about what Crunu does is checked against the product itself: its protocol and threat model documents and the source code of the current release. If a feature exists only in part, the page says what part. If it doesn't exist, the page says that too, and the known limitations page lists what the design can't protect against.

Some things we leave out on purpose, because we can't back them up: test counts, performance figures, certifications Crunu doesn't hold, and customer names, reviews or ratings. The site has none of these.

Where facts about other products come from

Statements about other products come from their own published material: documentation, pricing pages, security white papers, licenses and source repositories. Each page lists those sources with the date we read them. On comparison pages, every cell of the comparison matrix has its own source and date.

When a vendor's documentation and a secondary source disagree, we go with the vendor's documentation and, where it matters, mention the disagreement. We describe other products by what they document, not by how they market it, and we don't guess at features a vendor doesn't describe publicly.

How pages are checked

Before a page is published, and whenever a claim on it changes, we go through every statement about Crunu and about other products and record the result in a fact-check log: the claim, what it was checked against, and when. The logs are kept with the site's source and aren't published. If you want to know what a particular statement rests on, ask us.

Automated checks run on every change to the site. Among other things, they reject:

• links to addresses that aren't part of the site, and anchors that point to a missing heading;
• outside links in guides, comparisons, articles and glossary terms that are missing from the page's sources list;
• sources without a date, or without an https address;
• marketing words we have decided not to use, such as "zero-knowledge" for Crunu, because its server does see metadata.

Every guide, article and comparison shows when it was last updated or checked. Dates move when the content changes, not when a page is reformatted.

How we use AI

We use AI tools, including large language models, at several stages: to research and summarize documentation, to draft and edit text, to translate pages, and to cross-check claims against their sources.

A model's output is never treated as a source. Every fact on a page has to be traced to Crunu's own documents or code, or to another product's published material, before the page goes up, and the fact-check logs and automated checks above apply to text however it was drafted. Product screens in illustrations show Kiteline, a fictional company, and are labeled as examples.

Pages in languages other than English are translated with AI from the English original, using the product's glossary for interface terms. When a translation falls behind, the English page is the reference.

Corrections

If you find a mistake, write to support@crunu.com with the page address and what you think is wrong, ideally with a link to the source that says otherwise. Security issues go to security@crunu.com instead.

We check each report against the sources. When a page is wrong, we fix it and update its date.