Editorial policy

How editorial content on vultax.com is produced, sourced and reviewed, so a reader can judge how much weight to put on anything published here.

Who writes and who publishes

Vultax is the publisher. Editorial work is produced by the Vultax Research desk, an internal function that publishes as an organisation.

Publisher: Vultax
Editorial desk: Vultax Research
Byline: Articles are attributed to Vultax Research. Where an article depends on a specific person's expertise, that person is named and their relevant background stated.
Contact: [email protected]

Editorial content draws on the same observed market data the product runs on, plus public documentation for anything about third parties.

Figures about Vultax coverage and detection are traced to the methodology page, which documents how each is computed and where coverage runs out.
Claims about third-party products reflect their public documentation and pricing at the time of writing, and change without notice.
Superlatives about Vultax are published only when the claim is testable and stated with its test.
Product and pricing statements in articles derive from the same entitlement table that renders the pricing page, so an article cannot promise a feature a plan does not include.

Vultax uses AI assistance in drafting and editing, and discloses it here.

AI tools assist with drafting, structuring and editing editorial content.
Data, figures and claims are sourced from Vultax systems and public documentation, not generated by a language model.
Published content is reviewed before publication, and the desk is accountable for what appears under its name.

The standards below apply to every editorial surface on this site, and they are the same ones the product surfaces hold to.

Nothing published here is financial, investment, or trading advice, and no figure is a recommendation to buy or sell.
Detection surfaces report statistical risk computed from observed market behaviour. They are not an allegation of wrongdoing against any exchange or participant.
Where a figure cannot be sourced, it is reported as unavailable rather than estimated.
Performance and latency figures are stated as targets where they are targets.
Measurement windows and sample sizes are stated with the figures they support.

Figures are rendered from single sources, so a change to a figure changes every page that shows it at the same time.

Material changes to the product, data coverage and site are recorded in the changelog at /changelog with the release date.
Articles show their published and updated dates, and are revised when the underlying data or product changes.
Questions about a published figure go to [email protected] with the page and the claim in question.