Privacy
Data minimization starts at the public site.
This overview separates public-site and contact delivery from the private app and engine. It states current boundaries without making unverified compliance promises.
Public website
Public pages are informational and do not render private account, workspace, scan, finding or evidence data. They do not call the private engine during rendering.
Contact enquiries
The contact form collects the submitted name, work email, company, account type, plan interest, team size, target categories, usage range, use case and message. Do not submit targets, credentials, keys, raw evidence, personal data or breach data.
Contact delivery and retention
The public web does not write enquiries to a new database. When online delivery is enabled, a dedicated email adapter processes the enquiry. Deployment must declare service-level operational retention between 1 and 30 days and configure the delivery contract to enforce that maximum; mailbox retention after delivery follows the receiving organization's documented policy.
Rate-limit data
Short-lived in-memory controls retain one-way hashes of source IP and email for up to one hour to limit abuse. Duplicate message hashes are retained for up to 15 minutes. Full messages are not written to application logs.
Product account data
The separate product app may process account identity, membership, workspace, settings, billing and API-key metadata to deliver authenticated workflows.
Investigation data
The app and private engine separately store tenant-scoped targets, source artifacts, evidence, canonical objects, relationships, findings, reports, exports and operation state. The public site does not receive those stores.
Evidence and sensitive data
Collected public evidence can still be sensitive. Access, reveal, reporting and export remain tenant scoped, permission checked, redaction aware and subject to responsible use.
Cookies and preferences
The current public site does not load third-party analytics or advertising cookies. Browser-local state may be used only for a user-requested interface preference such as selected documentation or catalogue controls.
Analytics
If cookieless analytics is enabled later, it is limited to page views, CTA selection, pricing selection, API-doc opening, contact success/failure and capability-filter use. Targets, API keys, messages, workspace IDs, scan IDs and evidence values must never be recorded.
Retention and requests
Product retention depends on plan and signed contract. This public notice does not claim production deletion or backup guarantees. Use Contact to request the applicable policy and a safe privacy channel.