Which certifications does Paqt hold?

None that we publish. This page would list badges we hold. It lists none, because we publish none.

Is a certification under review?

This page does not describe a review, an application or a timeline. Emptiness here is not a hint. The mechanisms that exist are on Security & control.

Where should a security questionnaire start?

Security & control, then Review & audit trail. Those pages name controls. This page does not stand in for them.

Why does this URL exist?

So a request for badges lands on a page that says we publish none, instead of on a wall of implied logos or a 404.

Certification badges are not published

We do not publish compliance badges on this site. This page is empty on purpose: a badge wall with nothing on it is the honest version of a page that would otherwise invent a logo. The mechanisms that exist are on Security & control.

Coming soon

There is no badge wall

We do not publish compliance badges on this site. This page is the destination for badges we actually hold. Until one is published, the Security & control page is the honest document — mechanisms, not logos.

We publish no badges

A certifications page is where vendors imply a scheme they have not completed. This one does not name a scheme, does not hint at one, and does not treat emptiness as a promise. When we hold a badge worth publishing, it will sit here.

This page is not a holding pen for a claim. It is empty because the badges are unpublished, not because a review is quietly under way.

Not on this page: A named compliance scheme we have not completed
Not on this page: A logo wall that implies a badge we do not hold
Not on this page: Language that treats this placeholder as a certification in progress
True today: No certification badges are published on this site
True today: Security & control describes scoped access, gates and the kill switch
True today: An automated test fails the build if a named scheme appears in the catalog

Read the page that names the controls

A badge is a third-party statement. A control is something you can check in the product. We publish the second.

Security & control: Per-party visibility, scoped agent credentials, clause gates
Security & control: Autonomy caps and an organization-wide kill switch
Review & audit trail: Where an agent must stop
Review & audit trail: The attributed record of what it did
This page: Exists so a Legal or Company link is not a dead URL
This page: Stays empty until a badge we hold is actually published

Questions about badges

Which certifications does Paqt hold? None that we publish. This page would list badges we hold. It lists none, because we publish none.
Is a certification under review? This page does not describe a review, an application or a timeline. Emptiness here is not a hint. The mechanisms that exist are on Security & control.
Where should a security questionnaire start? Security & control, then Review & audit trail. Those pages name controls. This page does not stand in for them.
Why does this URL exist? So a request for badges lands on a page that says we publish none, instead of on a wall of implied logos or a 404.