Data handling
By default, Nexoviaai keeps the metadata needed to bill, secure and audit each request, and does not store what you send or receive.
Pre-launch. This page describes the controls the platform is being built with. Each is verified before general availability, and we update this page as they go live.
What happens to a request
- Your application calls the Nexoviaai API with a key.
- The gateway checks the key, your budgets, rate limits, model allow-list and regional rules.
- Your routing policy selects a provider and model. If that model is unavailable, the request falls back only to models your policy allows.
- The request goes to the provider over an encrypted connection, and the provider returns the output.
- We record the usage metadata and return the output to you. Content is not written to storage unless you have turned on content logging.
What we keep
| Data | Stored by default | Kept for | Who can see it |
|---|---|---|---|
| Usage metadata: key ID, model, tokens, cost, latency, status, time | Yes | 24 months | Your admins; our billing and support staff |
| Audit log: admin actions, key changes, policy edits | Yes | 24 months | Your admins; our security staff |
| Prompt and response content | No | Only if you turn logging on: 1 to 90 days, as you set | Your authorised users; our staff only for support you request |
| Account and billing records | Yes | Life of account plus 7 years | Our finance staff |
Model providers
Each provider handles requests under its own API terms. We route only to providers whose API terms do not allow training on customer data by default. Some providers keep request data for a short period to monitor abuse. Our subprocessor list, published at launch, will show each provider's region and retention terms.
No training
We do not use your prompts, outputs or files to train any model, and we do not sell or share them for anyone else's training.
Regional routing
You can restrict traffic to selected providers and regions in your routing policy, where providers offer regional processing. We also block models in countries their providers do not serve.
Deletion and export
- You can delete content logs at any time from the dashboard.
- When an account closes, content logs are deleted within 30 days. Metadata is kept only for the periods above, and backups roll off within 35 days.
- Admins can export usage and audit logs as CSV or through the API.