SECURITY STATEMENT

Security is an
architectural boundary.

This public website is built to minimize its attack surface and separate public presentation from private operational services.

01

Encrypted transport

Production deployment on Vercel is intended to use HTTPS. HSTS headers instruct compatible browsers to prefer secure connections after first contact.

02

Strict browser policy

A restrictive Content Security Policy limits scripts, styles, images, frames, connections, and other browser capabilities to known requirements.

03

Minimal dependencies

The public site is static and does not require third-party JavaScript packages, external fonts, advertising scripts, or analytics trackers.

04

Secret separation

Credentials, private keys, database connections, and service tokens must remain outside public source files and be managed through protected environment configuration.

05

Responsible reporting

Security researchers can review the published security.txt file for the designated reporting route and disclosure expectations.

06

No security guarantee

No public statement can guarantee absolute security. Controls require monitoring, review, patching, and appropriate protection of connected private systems.