Editorial Independence

Sponsorship buys recognition. Sponsors receive named acknowledgment on a dedicated Sponsors page, in the site footer, and — where applicable to their tier — on the Landing page, the About page, and inside category landing sections. Sponsor placements are clearly labeled as sponsorship.

Sponsorship buys access. Higher tiers receive access to roadmap-input calls, early access to standards summaries, content collaboration slots, and direct support channels. These benefits affect the platform, not the editorial content.

Sponsorship does not buy editorial outcomes. Specifically:

• Sponsorship does not affect whether a product, vendor, library, standard, or certification appears in /migrate, /compliance, the algorithm catalog, the standards library, or any other reference dataset.
• Sponsorship does not affect ordering, ranking, scoring, or filtering within those datasets.
• Sponsorship does not affect the substance of any assessment, including certification status, feature coverage, security level, or migration recommendations.
• Sponsorship does not buy removal of competitors, suppression of negative information, or modification of cited evidence.

Inclusion and assessment criteria are documented and applied uniformly:

• Migration data — presence of FIPS 203 / 204 / 205 certification, public product documentation, or observable shipping support.
• Compliance data — scraped directly from NIST CMVP, Common Criteria, ANSSI, ENISA, BSI, and other certification authorities.
• Standards library — published RFCs, NIST FIPS / SP, ETSI TS, ISO / IEC.

Where a sponsor's product appears in this data, it appears on the same basis as any non-sponsor product, and is marked with a “Sponsor” badge so readers can see the relationship.

When a sponsor's product appears in editorial content — a deep-dive, case study, webinar, or named example — that content carries a visible sponsorship disclosure.

When PQC Today maintainers hold any other relationship with a vendor (consulting engagement, advisory role, or employment history within the last 24 months), that relationship is disclosed on the relevant page.

We will publicly disclose any vendor request to modify, remove, or re-rank a listing in our reference data. We will not act on such requests, except to:

1. Correct a factual error supported by primary-source evidence (e.g., an updated FIPS certificate, a corrected vendor name, a fixed version number). Corrections are logged in the changelog with attribution.
2. Update data that has changed in the underlying authoritative source.

Disclosure is published in the changelog and on the relevant data page.

PQC Today is funded by:

• Vendor and enterprise sponsorship
• Consultant tier subscriptions
• Individual donations

We do not accept funding from any source that requires editorial influence as a condition. We do not run advertising. We do not use affiliate links.

If you believe this policy has been violated — that a listing, ranking, assessment, or content item has been influenced by sponsorship — please report it via a public issue on GitHub.

We will investigate, respond publicly within 30 days, and publish findings in the changelog. Reports may be made anonymously through a third-party tipline (planned).

Changes to this policy are tracked in the changelog and require a 30-day notice period before taking effect. Material weakening of the policy — reducing transparency, narrowing disclosure, or adding sponsor influence — will trigger sponsor renewal opt-outs at no cost.