Evidence before assertion
“Uploaded” is never presented as “verified”. Every assurance state names its method and scope.
CompanyConnect Trust Centre
Trust should be inspectable.
Especially ours.
Methodology, governance, security, privacy, complaints, and accreditation status belong in public view—not behind a sales claim.
Current public claimCompanyConnect-issued, manually reviewed pilot credentials.
Not accredited · Non-cryptographic registry assertion
Trust Constitution
Four commitments that cannot be bought.
No paid outcomes
Fees may cover processing or assessment, but never guarantee a pass or a higher trust level.
Explainable decisions
Material decisions use evidence, reason codes, policy versions, correction routes, and appeal.
Minimum disclosure
Public verification exposes only the authorised claims; sensitive raw evidence stays private.
Verification lineage
From claim to current status.
A verifier should be able to follow the chain without seeing confidential evidence or relying on a generic checkmark.
- 01 · Subject and claimWho or what is making the precise statement?
- 02 · Evidence and sourceWhat supports it, and how trustworthy is the source?
- 03 · Method and decisionWhich scheme, criteria, reviewer, and result applied?
- 04 · Credential and statusIs the registry result current, expired, suspended, or revoked?
Standards register
Current references, precise claim boundaries.
Technical interoperability, organisational certification, certification-body accreditation, and legal designation are different things. CompanyConnect will keep them separate.
| Reference | Product use | Status |
|---|---|---|
| W3C VC Data Model 2.0 | Portable credential model | Roadmap / design target |
| OpenID4VCI / OpenID4VP 1.0 | Issuance and presentation roadmap | Roadmap / design target |
| Open Badges 3.0 | Portable badge interoperability roadmap | Roadmap / design target |
| WCAG 2.2 AA | Minimum accessibility target | Roadmap / design target |
Governance and recourse
High-impact trust needs human accountability.
Reasoned decisions
Every pilot approval, rejection, information request, suspension, and revocation requires a recorded reason and policy version.
Pilot methodologyComplaints and appeals
Private cases preserve the affected record, decision, applicant response, operations response, status, and audit history.
Read the processSecurity and privacy
Least privilege, minimum public disclosure, same-origin writes, row isolation, rate limits, and a strict non-sensitive evidence boundary shape the pilot.
Read the privacy noticeTransparency
Policy versions, methodology, incidents, limitations, provider gates, and accreditation status stay visible.
Inspect a live or demo result