2.1 Engagement request and relationship data
When you submit the engagement form or otherwise contact us, we collect the information you provide, which may include:
- Name, role, and business contact details
- Organization name, type, and approximate size
- The services you are interested in and your stated timeline
- Any context you choose to include about your environment
2.2 Site usage data
We automatically collect limited technical information when you browse this site, including IP-derived general location, browser and device type, referring pages, and interaction and diagnostic logs. We use this to keep the site secure and to understand which content is useful.
2.3 Engagement data
During a penetration test we process information about the systems you place in scope and what we find in them ("Engagement Data"). Depending on the engagement, this may include:
- Asset identifiers — domains, hostnames, IP ranges, cloud accounts, API endpoints, and application URLs
- Test credentials and access material you provision for gray-box or white-box testing
- Findings, proof-of-concept evidence, screenshots, request/response captures, and log excerpts
- Remediation status, retest results, and detection artifacts produced for your team
Proof-of-concept evidence can incidentally contain personal data that exists in your systems. We minimize what we capture, redact where practical, and handle it under Section 6.
2.4 AI-assisted analysis
Our methodology uses AI to accelerate reconnaissance, triage, and drafting, with every finding validated by a human engineer. Outputs generated this way — candidate findings, summaries, prioritization — are treated as Engagement Data and carry the same access controls, retention schedule, and deletion rights described here. Engagement Data is not used to train models that serve other customers, and we do not sell or license it to model providers for training.