Editorial Policy

Five commitments cover everything we do here.

Editorial Policy

Independence

Vendor relationships do not influence editorial coverage. Vendors do not pay for reviews, do not select what we cover, do not see drafts before fact-check, and do not have approval over scores. Cyber Security Services, which operates this site, produces a product (AILeakShield) that we review; that conflict is documented on the disclosure page and disclosed on every relevant page.

Sourcing standards

Every factual claim in a review or guide must be sourced from one of:

Every factual claim in a review or guide must be sourced from one of:

Editorial Policy

Subscribe to our newsletter

Quarterly updates when our Best Of lists are refreshed, plus a short note when a vendor ships a material change or we revise a score. No promotional email.

Corrections policy

Errors get fixed. Confirmed factual errors are corrected within five business days of confirmation, and a dated correction note is added to the review’s changelog. We never silently edit a published page to remove an error — the change is logged.

To submit a correction, email hello@aisecurityplatform.com with the URL, the disputed claim, and a source for the correct information.

AI use policy

We use AI in our editorial workflow:

Editorial Policy

Research

LLMs help us synthesize public documentation and surface questions for vendor briefings.

Editorial Policy

Drafting assistance.

LLMs help with first drafts, outline structure, and prose tightening.

Editorial Policy

Editorial review.

LLMs flag inconsistencies and missing citations during fact-check.

Every published page is reviewed and edited by a human reviewer before publication. We do not publish AI-generated content unedited. We do not allow AI to generate vendor quotes, customer quotes, or framework citations — those come from primary sources only.
Editorial Policy

Conflict of interest

The single material conflict on this site — Cyber Security Services owns AIsecurityPlatform.com and AILeakShield — is documented on the disclosure page and disclosed at the top of every page where AILeakShield appears. Other conflicts (e.g., a contributor leaving to join a vendor) will be disclosed inline if they arise.