Editorial policy

Editorial policy for NullVault guides

How NullVault guides are sourced from primary documentation, how claims are reviewed, how fictional examples are labelled, and how to request a correction.

Reviewed September 1, 2026

This page describes how the guides, comparisons, and security pages on nullvault.app are researched, written, reviewed, and corrected. It applies to every article published here, in every language.

Sourcing

Guides are sourced from primary documentation: the standards body or platform vendor that actually defines the behavior being described. In practice that means NIST publications for cryptographic primitives, and Apple and Google platform documentation for operating-system behavior.

Every guide links to the primary sources it relies on, and those links are checked for liveness as part of the build. We do not source platform claims from secondary blog coverage, aggregator sites, or other vault vendors' marketing pages.

Where documentation is ambiguous or a behavior varies by operating-system version, the guide says so instead of resolving the ambiguity in our favor.

Product claims

Feature pages describe NullVault itself, so they are held to a separate rule: each public claim is tied to a specific reviewed implementation, and carries the date it was last reviewed.

Where iOS and Android behave differently, both behaviors are stated. A feature that has shipped on one platform and not the other is labelled that way rather than described as simply available.

Language we do not use

Certain words promise more than any application can deliver, so they are excluded from product copy on this site and the build fails if they appear. Among them: claims that encryption is unbreakable, that deleted data is securely wiped, that content is forensically invisible, or that NullVault has been independently audited when no such audit exists.

Fictional examples

Several guides include a worked scenario. These are explicitly labelled as fictional and are illustrations of a decision process. They are not case studies, user reports, or accounts of product testing, and they should not be read as evidence that a particular outcome occurred.

Comparisons

Comparisons use verifiable product behavior rather than star ratings, affiliate rankings, or invented lab tests. There are no paid placements: no company can buy a position, a rating, or an inclusion in any comparison on this site.

Each comparison is required to state the circumstances in which the alternative is the better choice. A comparison that concluded in our favor on every dimension would not be a comparison.

Review and updates

Each guide carries a visible review date. Guides are revised when the platform behavior they describe changes, when a cited document is updated or withdrawn, or when a reader identifies an error.

When an article changes materially, the review date changes with it. We do not silently edit substantive claims.

Corrections

If something here is wrong, out of date, or misleading, write to support@nullvault.app. Please include the page address and what you believe is inaccurate.

Corrections to factual errors are made to the article itself, and the review date is updated. We would rather be corrected than be quoted incorrectly.

Independence

NullVault is a commercial product, and these guides are published by the company that sells it. That is a conflict of interest, and we treat it as one: nothing on this site is an independent audit, a certification, or a substitute for the platform vendor's own documentation.

Read about NullVault for who publishes this site, and the security limitations page for what the product does not protect against.