Your information.
A defined purpose.
This notice concerns the OmniGuard marketing website and enquiry process. A future security platform would require its own processing terms and data-flow disclosures.
Registration status
Collection settings have not been verified in this browser. The form defaults to disabled.
Browsing and the local demonstration.
The incident scenarios and permission examples are fictional and run in your browser. They do not scan a company, send their events to a model or collect your security telemetry. The site does not load advertising or visitor-analytics scripts.
This release uses system fonts and locally packaged visual assets. No third-party font service is contacted. Basic hosting and security processing may still involve request metadata handled by the hosting provider.
A motion preference may be saved in browser session storage. No form contents are stored there, in local storage or in scenario-sharing URLs.
When requests are enabled.
The form asks for a work email and company. An enquiry also includes its category and message; early-access context is optional. Acknowledging the notice does not itself select a legal basis for processing and does not subscribe you to marketing.
The server validates and stores the request with a reference, notice version and expiry. Email addresses are not treated as verified. The configured operator must publish its purpose, lawful basis, retention, recipients, transfer information and contact before enabling this workflow.
Requests may generate operational and acknowledgement deliveries through an operator-configured notification service. The configured recipients and any transfers must appear in the details above. Acknowledgement is not promotional mail.
Abuse prevention and minimisation.
The signup handler uses bounded input, origin checks and short-lived keyed fingerprints for abuse control. It does not store the raw visitor IP address in the lead tables. Application logs are designed not to include form bodies, email addresses or tokens.
Cloud hosting may maintain its own operational logs. The operator must review that handling and associated retention; the application cannot make a blanket promise of no logging anywhere.
Your requests and choices.
Use the published privacy contact, once configured, for access, correction, deletion, objection or other applicable rights. The operator must assess each request in its context. Do not send identity documents through the general website form.
The configured retention describes enquiry data, not future platform telemetry. The implementation includes expiry and a maintenance process; deployment operators remain responsible for scheduling and verifying deletion, including provider copies and backups.
Before a live launch.
The operator must review the notice against the services and providers actually used. Material changes require a new notice version and corresponding request configuration. No production service or customer-security monitoring is activated by submitting a website form.