Privacy
What Edgee processes, what it stores, where, for how long, and what it never does with your data.
Edgee sits between your coding agents and LLM providers, so every request your developers send passes through it. This page explains what that means for your data. The Data Processing Addendum is the contractual reference; this page summarizes it.
Our position
- Your organization stays in control. For the traffic of your developers, your organization is the controller and Edgee is the processor. Edgee processes data only on your instructions, including the configuration you set in the console.
- Prompts are not stored. Prompts and completions are processed in memory, only for the time needed to route, compress and return each request. If you enable debug mode, Edgee stores the content of the captured requests so your team can inspect them in the console, and will delete them automatically after 30 days.
- No model training. Edgee does not use your prompts, completions or usage metadata to train, fine-tune or evaluate AI models without your prior express consent.
- No resale, no advertising. Edgee does not sell your data or use it for marketing, advertising or profiling.
What Edgee processes
| Data | Stored | Why |
|---|---|---|
| Prompts and completions | No, unless you enable debug mode | Route, compress and return each request |
| Usage metadata (token counts, model, latency, errors) | Yes | Observability, budgets, billing |
| Request and session identifiers | Yes | Link requests to sessions in the console |
| Account data (name, business email, role) | Yes | Sign-in and team management |
| Provider keys (BYOK) | Yes, encrypted | Call LLM providers on your behalf |
| Configuration (routing, compression, limits) | Yes | Apply your policies |
Usage metadata refers to developers only by Edgee-generated pseudonymous identifiers.
Prompts can contain code, and code can contain personal data or secrets. You decide what your developers send. Secret detection can flag, redact or block credentials before they reach a provider.
Debug mode
Debug mode is off by default. When an administrator enables it, Edgee stores the content of the captured requests so your team can inspect them in the console.
- Debug content is deleted automatically no more than 30 days after capture.
- Enterprise organizations can configure a shorter period.
- Backups, replication and exports do not extend this limit.
Turn debug mode on for a specific investigation, then turn it off.
LLM providers
When Edgee routes a request to an LLM provider, the provider receives the prompt and processes it under its own data processing terms.
- You choose which providers and models your organization may use, in the console and through your routing strategies.
- The model catalog lists each route with its hosting region and data-retention posture. Routes with zero-data-retention terms are filtered at edgee.ai/models?zdr=true, and you can restrict your traffic to them by switching off the other models and providers on the Models page.
- You can exclude a provider or a model at any time. The change applies from the next request.
Where data is located
- Control plane: the Edgee API runs in France and in the United States.
- Gateway: requests are handled in the nearest Gateway region by default. You can restrict your traffic to the Gateway regions of a given region or continent. Prompts are processed in memory in the region that handles the request.
- Account data: stored in France and replicated to the United States for redundancy.
- Usage metadata: stored in the United States.
- Debug content and Gateway service logs: stored in France.
Transfers outside the EU/EEA rely on the EU Standard Contractual Clauses and, where applicable, the EU-U.S. Data Privacy Framework. See the DPA for details.
For a deployment where no prompt, completion or provider key is ever sent to Edgee, see on-premise deployment.
Retention and deletion
| Data | Retention |
|---|---|
| Prompts and completions | Not stored by default |
| Debug content | Up to 30 days from capture, or a shorter Enterprise period |
| Usage metadata | Duration of the service, then a 30-day export window |
| Provider keys | No longer used once removed or when the service ends; destroyed within 30 days |
| Backups | Expire no later than 30 days after creation |
When your contract ends, you have 30 days to request an export of your usage metadata. Edgee then deletes it from active systems, unless a legal obligation requires otherwise.
Security
Edgee's security program is independently audited under SOC 2 Type II. Data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256), tenants are isolated, and access follows least-privilege principles. Reports and security documentation are available in the Trust Center.
Learn more
Data Processing Addendum
Privacy Policy
Questions about privacy: privacy@edgee.ai.