Security and responsible use.
A security company should be easy to question. This page covers what the developer demo does today, who gets access, and how to reach us.
Keys and data in the demo
- API keys are stored as one-way hashes and the raw key is shown once, when you create it.
- Prompt and response content is not written to the app database. Usage history stores model, token counts and latency.
- You can delete a key at any time from the console and it stops working.
Details are in the Privacy Policy.
Who gets access
Access is for companies and security professionals. Register with a company email address; we may follow up to confirm the use case. Use is governed by the Acceptable Use Policy, which limits the models to authorized, defensive and research work.
Report a vulnerability
If you find a security issue in ZeroDayAPI, email [email protected] with the details and steps to reproduce. Our contact details are also published in security.txt. Please give us reasonable time to fix an issue before sharing it publicly, and avoid accessing data that is not yours.
Compliance and regulated data
For security questionnaires, contract terms or HIPAA requirements, contact us before sending any regulated data. Teams with lock-in periods or other requirements are welcome to talk to us first.