Terms of Service
These terms define acceptable use for VeriFalcon's public crawler, authenticated scan workflow, exports, and pilot-stage operation.
Users must only scan properties, staging environments, and accounts they are allowed to test.
Key Takeaways
Start here, then expand detailed sections as needed.
Use Boundaries
Users must only scan properties, staging environments, and accounts they are allowed to test.
The product may reject private-network targets, rate-limit scan creation, and stop crawling when targets block or distress signals appear.
VeriFalcon is still in a pilot-stage operating model, so direct support and audit offers are scope-led rather than fully automated.
Acceptable use
- scan websites, docs, applications, or staging surfaces you own or are authorized to test
- use authenticated scanning only with accounts you are allowed to provide
- avoid using production administrator credentials when a scoped test account will work
- respect crawl blocks, rate limits, and target-owner requests
Prohibited use
- scanning targets you do not have permission to test
- using the crawler for vulnerability discovery, credential attacks, or abusive automation
- attempting to reach private infrastructure, metadata services, localhost, or internal network addresses
- using the product to overload, disrupt, or scrape third-party services
Exports and reports
Inline results and CSV exports are available without an email gate. PDF export requires email capture so VeriFalcon can measure demand and support follow-up around higher-intent reports.
Availability and changes
VeriFalcon is operated as an early-stage product and pilot workflow. Features, limits, pricing, and availability may change as the product is validated and hardened.
Related Pages
Continue with pages that map to adjacent use cases and comparisons.