We publish claims about services, people, roles, contacts and organization only when they can be substantiated by an approved internal source or public primary record.

We do not invent clients, results, certifications, response times, statistics or other evidence that we cannot publicly support.

For legal, regulatory and technical statements, we prefer the texts of laws, public administration bodies, European institutions, standard-setting organizations and original professional publications.

We cite the link as closely as possible to the claim it supports. We do not use the resource as general decoration or attribute to it a conclusion it does not contain.

We distinguish between a verifiable fact, an expert interpretation and a practical recommendation. If the outcome depends on a particular scenario, scope of authority, or available evidence, we will explicitly describe the limitations.

A public article is not a substitute for an individual legal, forensic or security assessment.

We will correct the documented factual error without undue delay. A complaint can be sent to the public contact email GBH Defence with a link to the page and a description of the contested claim.

We will record a significant correction as a true editorial change; a mere linguistic or technical amendment does not create a new technical update date.

Each promoted expert page has an internal owner, records of documents and a control interval corresponding to the risk and speed of changes in the given topic.

We only list the name of the author or reviewer when the public role, profile and relationship to the content is verified and publication is approved. Otherwise, we use the honest authorship of the organization GBH Defence.

We do not disclose non-public procedures, personal information, client identity or sensitive operational details. An anonymized example must be approved, marked, and must not indicate a result or accuracy that is not supported by the records.

We only change the update date after a substantial editorial change in facts, scope of service, resources or recommendations. Deploying the site, changing the appearance, or checking without change does not move the public date.

We use the same approved date in the visible page, structured data, sitemap and internal release log.