Security at Fraser Digital Hub

This website

• Traffic is delivered over HTTPS through managed cloud infrastructure.
• The public inquiry form collects a limited business contact record and stores it in managed structured storage.
• Input length, required fields and a hidden anti-bot field are validated before storage.
• The public website does not collect passwords, payment-card information or authentication credentials.

Client engagements

Controls are selected for the actual data, systems and risk. A proposal can define identity, least privilege, secrets handling, approved environments, logging, data retention, human approval, release gates, incident contacts and deletion or handover. Fraser does not claim that a public website control automatically applies to every client environment.

AI system boundaries

Models should not grant their own permissions. Production designs keep identity, authorization, tool allowlists, deterministic validation and high-impact approvals outside model output. Reference implementations in Fraser Labs demonstrate these boundaries with synthetic data.

Responsible disclosure

If you believe you found a vulnerability, email fraserdigitalhub@gmail.com with the affected URL, a concise description and safe reproduction steps. Do not access data that is not yours, use social engineering, disrupt service or publish details before Fraser has had reasonable time to investigate.

No certification claim

Fraser Digital Hub does not currently claim ISO 27001, SOC 2, PCI DSS, HIPAA or another third-party security certification on this website. When a buyer requires a formal control framework, evidence package or certified environment, that requirement must be addressed explicitly in architecture and contracting.

Security questions

For questionnaires, architecture reviews or data-handling questions, contact Fraser before sharing sensitive material. We will identify what is known, what must be verified and which controls belong to Fraser, the client or a platform provider.