Privacy

This policy covers zulusec.com, operated by ZuluSec LLC, Birmingham, Alabama.

This site uses no analytics and no tracking cookies.

If you email ZuluSec or book a call, ZuluSec uses what you send solely to respond and to run the engagement, and does not share it with third parties. Scheduling is handled by Cal.com and payments by Stripe, each under their own privacy policies; ZuluSec never sees your card details.

Engagement data (credentials, findings) is handled under the confidentiality terms of the signed engagement agreement for that work. For the security audit those are the audit terms.

To have your inquiry data deleted, email ops@zulusec.com.

By default, no AI model sees your data. An engineer specifies the tooling and AI helps write it. The tooling reads your environment. Its output goes to the practitioner who judges it, and into your report. Nothing from your environment goes to a model: not what the tooling reads, not its output, not your logs or configuration, and never a credential.

That boundary is yours to set. If you want a wider AI role in exchange for speed, you can choose it, and the engagement agreement names exactly what changes. The restrictive setting is the default, and it is what regulated environments get unless you ask for something else.

Whichever setting applies to your engagement is written into the data handling terms you sign, so the commitment is contractual rather than a claim on a website.