Security & Privacy

How NxtOne handles your code, data, and operational telemetry.

Observing application state requires absolute data safety. NxtOne is engineered with enterprise security and data privacy as foundational architectural requirements, ensuring your code structure and production data remain strictly protected.

1. Transport Security

All communication between local runtime agents, the Lens CLI, and the NxtOne ingest gateway is secured using industry-standard TLS 1.3 encryption over HTTPS. Every payload sent requires a valid, authenticated token header (NXTONE_API_KEY) to pass our edge gateway firewalls.

2. Intelligent Data Sanitization

The agent includes an automated data-masking engine designed to safely process variables and execution contexts before they ever leave your infrastructure:

• Runtime Isolation: System-level objects (such as database connection pools, active I/O streams, or internal system threads) are automatically recognized, isolated, and bypassed by the agent to preserve application stability.
• Zero Runtime Interruption: The sanitization engine operates completely asynchronously. It is isolated from your core application logic and will never disrupt or block execution threads.

3. Code Structural Mapping & Compliance

To provide exact line-level debugging context without compromising your intellectual property, NxtOne uses a structural mapping model:

• Metadata Synchronization: During session initialization, the agent analyzes your application's structural layout (such as class names, package architecture, and method signatures) to create a telemetry map.
• Binary and Environment Exclusion: NxtOne explicitly ignores environment variables (like local .env secret keys), build binaries (.jar, .class), and heavy static assets. Your operational secrets never leave your local environment.