Trust Centre

Clear claims.
Controlled evidence.

Security, privacy, resilience and assurance information for Horizon Lab. We publish only claims we can support and show work that is still underway.

Version 1.0 · Assurance source reviewed 30 September 2026 · Next review by 31 December 2026

Pre-launch position. This page describes the current assurance roadmap, not completed independent verification.

Our approach

Trust by design.

Security

Secure development, controlled access, vulnerability management and incident readiness.

Privacy

Purpose-limited data use, client confidentiality and accountable handling of personal information.

Resilience

Monitoring, recovery planning and clear communication when service is affected.

Assurance

Claims tied to evidence, named owners and review dates—not unsupported badges.

Current position

A roadmap is not a certification.

These labels distinguish work that is underway from independently completed assurance.

OWASP ASVS 5.0 Level 2

Adopted as the portal engineering baseline. Verification and independent testing remain release gates.

In progress

Secure software lifecycle

NIST Secure Software Development Framework guidance supports design, build, review and release practices.

In progress

Independent penetration test

Required before public release, with critical and high findings remediated and retested.

Planned

ISO/IEC 27001

Horizon Lab does not currently claim ISO/IEC 27001 certification.

Not certified

SOC 2

Horizon Lab has not completed a SOC 2 Type I or Type II examination.

Not examined
Trust resources

What is available.
What is still being prepared.

Privacy statement

Public draft

How Horizon Lab proposes to handle personal information. Published for specialist review before launch.

Read the draft

Portal terms of use

Public draft

Rules for authorised access, permitted use, confidentiality and security. Published for specialist review before launch.

Read the draft

Subprocessor register

Planned

The providers supporting the service, their processing locations and relevant transfer safeguards. The register remains pre-launch work.

Security and resilience pack

Controlled

A security questionnaire, high-level architecture and continuity overview, and available assurance evidence. Availability and scope are confirmed individually; the controlled-access workflow is still being prepared.

Penetration-test executive summary

Planned

A summary that does not disclose exploitable detail, following independent testing, remediation and approval.

Service status

Planned

An independently hosted source of availability updates and incident communications. No live status service is connected yet.

Controlled evidence

Useful assurance.
Appropriate access.

Existing and prospective clients can discuss the evidence needed for their due diligence. Sensitive technical detail, vulnerabilities, client identities and client-specific evidence do not belong on a public website.

The planned process verifies the requester and purpose, limits the material shared and provides approved, logged, time-bound access. This workflow is not yet live.

Planned access process
  1. Identify the requesting organisation, purpose and evidence needed.
  2. Verify the business relationship and need to know.
  3. Agree confidentiality terms where required.
  4. Have a Trust Administrator approve only the necessary resources.
  5. Provide time-limited access and record views or downloads.
  6. Allow immediate revocation and retain records under the agreed schedule.
Discuss assurance requirements The website enquiry form is a preview and does not send requests yet.
Security concerns

Report privately.

Suspected vulnerabilities should be reported confidentially. Do not access client data or publish sensitive findings before they can be investigated.

The dedicated security reporting mailbox will be published once it is activated, monitored and tested. Do not submit exploitable detail through this prototype.

Privacy enquiries

Questions about your information.

The Horizon Lab Privacy Officer will handle access, correction and other personal-information questions.

The dedicated privacy contact channel is being prepared and must be confirmed before launch. The draft privacy statement explains the proposed approach.

Read the privacy statement