Security and data
How NagaAI handles your keys, your requests and your payments. The legal terms are in the Privacy Policy.
- API keys
- NagaAI stores only a SHA-256 hash of each key, so no one can read a key back, us included. The dashboard shows a new key once. You can give a key a spending limit or an expiry date, and disable or delete it at any time.
- Your account
- You can turn on two-factor authentication for sign-in. In an organization, only workspace admins can turn request logging on or off.
- Request data
- Every request leaves a record: time, key, model, status, token counts, latency and cost. We keep it for a year, for billing and for your Logs. Request and response bodies are stored only if you turn on request logging, and then for 30 days. Details are in Privacy and logging.
- Training
- NagaAI does not use your prompts or outputs for training. The provider that runs the model may, under its own terms; see Model providers below.
- Where requests run
- Our servers, which receive your requests, keep your account and bill your usage, are in the EU. The provider that runs the model may be elsewhere.
- Model providers
- Each request is processed by a third-party inference provider under its own terms. NagaAI cannot guarantee that the provider does not retain the request or use it for training. If you need that guarantee, do not send data through NagaAI that may not be shared with third parties. If one provider fails, the request can move to another.
- Payments
- Payments go through Stripe, PayPal, Lemon Squeezy or a crypto processor, depending on the method you pick. You enter card details on the processor's page, so your card number never reaches NagaAI.
- Uptime and incidents
- Live availability and past incidents are on status.naga.ac. Each model page shows that model’s uptime.
- Report a vulnerability
- Write to [email protected]. The same contact is in security.txt.