Last updated Apr 17, 2025
Keeping your data and developer environment secure is a core part of how we build Novisurf.
Novisurf is designed with data minimization in mind. We collect only the information required to provide core product functionality, keep services reliable, prevent abuse, and support account operations.
Depending on product usage, this can include account metadata, request metadata, operational logs, and service telemetry needed for debugging and performance tuning. We do not intentionally collect unnecessary sensitive data in normal product flows.
We do not keep data longer than necessary for legitimate operational needs such as uptime, fraud prevention, billing, support, and legal compliance. Retention windows vary by system and use case, and we review them as our architecture evolves.
Where possible, data is deleted or anonymized once it is no longer needed for those purposes. We continue improving internal controls to reduce retention scope and improve security posture over time.
Novisurf uses dedicated API surfaces for specific product workloads:
This separation helps isolate workloads, apply purpose-specific controls, and improve reliability and observability.
We use multiple providers so we can improve uptime, performance, and feature coverage while reducing single-provider risk. Provider usage depends on product surface, routing policy, and availability at request time.
For AI features, provider choice can vary by model, latency profile, and workload type. For infrastructure and security services, providers are selected to support isolation, resilience, and global reliability.