TRUST // SECURITY

Security boundaries for operational conversations.

We treat building and workforce context as sensitive business information and design our intake around minimum necessary detail.

HUMAN-REVIEWED STANDARDUPDATED September 22, 2026

Use the minimum information needed to explain a planning question. Keep credentials, keys, access codes, proprietary control logic, personally identifiable employee records, and security-sensitive building details out of public forms.

Access, retention, vendors, and storage should be scoped to the engagement and the information needed for the requested work. Human review is used for consequential recommendations. Specific controls, retention periods, and processing terms should be confirmed in the written engagement for a project.

If you believe you found a security issue, do not exploit it or access another person’s information. Send a concise report through the contact page with the affected URL, impact, reproduction steps, and a safe contact method.

This site is not monitored as an emergency, dispatch, life-safety, or incident-response channel. Contact the responsible building operator, emergency service, utility, or qualified technician for urgent conditions.

NEXT // EVIDENCE

Keep the boundary clear.
Make the next move useful.

Report a security concern