Confidentiality & Secure Communication

• Passwords, API keys, tokens, or other credentials.
• Controlled Unclassified Information (CUI) or export-controlled information.
• Regulated personal data such as protected health information, government IDs, financial account numbers, or similar sensitive personal data.
• Detailed system configurations, network diagrams, or infrastructure inventories.
• Security findings, vulnerability reports, incident details, or other information that would give an attacker leverage if intercepted.
• Contracts or client materials covered by another organization's NDA.

A short, general description of the situation is almost always enough at first contact. Detail can come once we have the right channel in place.

The kind of context that helps most in a first message is high-level and non-sensitive: what your organization does, what you're weighing, what has prompted the outreach, and the timeframe you're working within. See the contact form for the prompts we use.

Inquiries and correspondence are stored in vetted systems with access limited to Allan and any personnel directly supporting the engagement. Information you share is not used for marketing, is not sold, and is not shared with third parties outside of the vetted service providers described in our Privacy Policy.

When an engagement begins and sensitive material genuinely needs to move between us, we agree on an appropriate secure channel — for example an encrypted file exchange, a secure client workspace, or a mutually approved platform under written terms — suited to the nature of the information and any regulatory obligations that apply.

If you believe information was sent that shouldn't have been, or you notice a security concern with the site or our correspondence, please email allan@havesight.com and we'll respond personally.