data usage
A quick look at how Nap uses operational data to improve quality, security, and reliability.
Overview
This Data Usage page describes how Nap uses operational and product data to deliver core functionality, improve system quality, and keep the platform secure. We aim to keep this section practical and transparent so teams understand what signals are used and why they matter. Data usage decisions are based on product necessity, security obligations, support needs, and responsible service improvement. We avoid collecting information that does not support these goals.
Product analytics
Aggregated usage patterns help us understand adoption, usability friction, and feature value over time. For example, we may analyze completion rates for common flows, where users drop during setup, or which commands frequently fail because of environment mismatch. This allows us to prioritize fixes and improve onboarding. We prefer aggregate reporting over user-level profiling whenever possible.
Performance and reliability
To keep Nap stable, we use telemetry related to error frequency, request latency, service availability, queue processing, and operational health. These signals help us identify degraded behavior quickly, reduce incident duration, and validate reliability improvements after deployments. Diagnostic data is also used to reproduce and resolve bugs reported by users and internal monitoring systems.
Security monitoring
Security-relevant events and service activity are reviewed to detect abuse patterns, unauthorized access attempts, and indicators of compromise. This includes access anomalies, suspicious traffic signatures, and behavior inconsistent with normal account usage. We use these signals to enforce platform protections, respond to incidents, and improve preventive controls.
Support and troubleshooting
Support workflows may use account context and relevant operational logs to investigate user-reported issues. Our support goal is to access the minimum data required to resolve the ticket and restore normal operation. Access to support tooling is controlled, and data handling is limited to operational needs.
Retention and minimization
Data is retained only as long as needed for service operation, compliance, security, support, and reasonable product improvement workflows. Retention duration may differ across telemetry classes. We regularly review data classes and remove or reduce collection where it is no longer justified.
How this connects to your privacy
Data usage is one part of our broader privacy approach. For details about lawful processing, subprocessors, user rights, and contact options, refer to the Privacy Policy page. Together, these documents explain both what we collect and how we use it in practice.