Security approach
NeuraOps applies proportionate safeguards for a limited commercial-pilot service and expands controls as the product and customer risk justify them.
Last updated: 30 August 2026
Current safeguards
The service uses HTTPS, scoped access patterns, server-side validation, rate limiting, controlled AI failure handling, and human escalation for important or ambiguous workflow states.
Data minimization
The public LeadOps intake is designed to work without highly sensitive information. Users are instructed not to submit patient data, credentials, payment-card information, or regulated high-risk records.
Pilot onboarding
Before a production pilot, we review the intended data, access needs, retention, subprocessors, incident contacts, and any customer-specific security requirements. Unsupported requirements must be resolved before launch.
Responsible reporting
If you believe you found a vulnerability, do not access data, disrupt service, or publicly disclose the issue. Use the security contact route below and include only the minimum detail needed to reproduce it safely.
Limitations
No internet service can guarantee absolute security. This page describes the current approach and is not a certification or claim of compliance with a standard that has not been independently verified.