Every tool should have a clear job
The title, description and first screen should say what the tool does in ordinary language. A page should not promise a result that the browser cannot actually produce.
Calculations are checked with known examples
Calculator logic is tested with simple values whose answers can be worked out independently. Money, tax, health and other important topics include a reminder that a general estimate is not a professional decision or an official local rule.
Conversions explain fidelity
A file conversion page must say whether it preserves text, values, pages, layout, formulas, images, tables, macros or embedded files. If a format cannot be handled safely in the browser, the site should say so instead of suggesting that every file type is supported.
Privacy claims must match the implementation
The site checks whether a tool actually sends data before describing it as local. Files and values handled in the current browser-only tools are not stored by KitLumo. Future server-side processing would require a separately isolated service and a new privacy explanation.
Corrections are welcome
A report that identifies a reproducible error is treated as a maintenance task. Users can report the tool, the input pattern and the observed result without including confidential source data.