mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-05 02:41:56 +00:00
fix: Qualify GDPR processor role as provider-dependent
This commit is contained in:
parent
b06f8996af
commit
4159b1603f
1 changed files with 1 additions and 1 deletions
|
|
@ -55,7 +55,7 @@ graph LR
|
|||
class Azure processor
|
||||
```
|
||||
|
||||
Every provider is a **processor** under GDPR: they process data on your behalf. Each requires a Data Processing Agreement (Article 28).
|
||||
Providers are typically processors for customer-submitted data, but the exact role depends on each provider's terms of service and processing purpose. Deployers should review each provider's DPA. Each requires a Data Processing Agreement (Article 28).
|
||||
|
||||
When you self-host LiteLLM, your organization is the data controller — you determine the purpose and means of processing. LiteLLM as software has no GDPR role; the legal designation applies to the organization operating it. When using LiteLLM's hosted proxy service, the organization operating that service becomes an additional data processor.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue