Editorial Policy

We aim for plain language, accurate product descriptions, and claims that match the current state of the software.

When we describe privacy or local-first behavior, we try to keep that language specific so creators can make informed decisions.

Editorial content should be reviewed against the actual product experience, technical implementation, and current policy pages before publication or update.

If a page becomes materially outdated because the product, pricing, or infrastructure changes, we should revise it rather than leave misleading claims in place.