Security
How a delivered Scraper Engine instance is built to fail closed, not open.
API-key authentication
Every control endpoint (add/remove targets, trigger a run, read results) requires an X-API-Key header. No key configured means every request is rejected — the system fails closed, never open.
Encryption in transit
All traffic to and from a delivered instance runs over TLS. Scraped data and control commands are never transmitted in plaintext.
Your data stays yours
Results are delivered directly to the destination you configure — your dashboard, your CRM, your infrastructure. We don't retain a copy or route your data through a third-party store.
Bring your own credentials
Any LLM or delivery-integration keys the build uses are yours — you control the account, the spend, and can revoke access at any time. We don't hold a standing copy of your keys after delivery.
Scope discipline
We collect only publicly visible data from the target(s) explicitly agreed at scoping — no login-gated or restricted systems without that being part of the agreed scope, and never government or regulated data sources.
Credential handling during support
If a support task requires access to your environment, access is scoped to that specific task and time-boxed. We do not request or hold standing admin credentials as a condition of delivery.
Incident response
If a security issue affecting a delivered build is identified, we notify the affected party without undue delay, describe the exposure plainly, and ship a fix on a priority track.
Responsible disclosure
If you believe you've found a vulnerability in a delivered build or on this site, contact us through the channel you used to place your order. Describe the issue and, if possible, steps to reproduce it. We take reports seriously, do not pursue legal action against good-faith researchers who report responsibly, and will confirm receipt and a fix timeline directly.