docs: add Provider Data Use & ZDR page

[tristantelleb]

Adds a Data Governance page documenting what each provider does with customer data when called through Eden AI's API.

For every LLM provider on Eden AI, the table shows:

• Trains? whether the provider may train on your data (No for all except DeepSeek and MiniMax)
• ZDR whether it offers Zero Data Retention, storing nothing (11 of 25 do)
• Retention how long it keeps your data otherwise

It also covers EU data residency (the providers routable through api.eu.edenai.run: Amazon Bedrock, Google Vertex, Microsoft Azure, Mistral, OVHcloud) and a short "reduce your data exposure" section. Regions are grounded in our routing config (edenai-back host_regions.py). Wired into the Data Governance nav group in docs.json.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Added a new Data Governance page covering zero data retention, provider data handling, EU data residency, and steps to reduce data exposure.
  • Expanded the Data Governance navigation to include the new page.

[coderabbitai]

Walkthrough

Adds a new Data Governance ZDR documentation page with metadata, provider data-handling details, EU residency guidance, and exposure-reduction steps, and adds it to the Data Governance navigation.

Changes

Data Governance ZDR page

Layer / File(s)	Summary
ZDR page content v3/data-governance/zdr.mdx	Adds frontmatter, schema metadata, opening copy, a provider comparison table, and EU residency and exposure sections to the new ZDR page.
Navigation entry docs.json	Adds v3/data-governance/zdr to the Data Governance pages list.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

Hop hop, I read the ZDR page by moonlit carrot glow,
I tucked the EU endpoint into my burrow of snow,
No noisy crumbs of data, just tidy docs in a row,
With a twitchy nose I bounce along—hello, hello! 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: a new documentation page about provider data use and ZDR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/zdr-provider-data-page

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@v3/data-governance/zdr.mdx`:
- Around line 54-62: The “EU data residency” and “Reduce your data exposure”
sections in zdr.mdx currently blur two different rules, so update the wording in
the EU endpoint and ZDR bullet list to clearly separate residency constraints
from zero-data-retention constraints. Use the existing “EU endpoint” and “ZDR
providers” bullets as anchors, and make it explicit that any fallbacks must
remain within the same residency set as the chosen endpoint; do not imply that
the ZDR provider list is EU-resident. If needed, split the guidance into
separate bullets or sub-bullets so readers can distinguish EU residency
requirements from ZDR-only provider eligibility.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5822c153-c9fc-46f3-a656-f31c0dca692c

📥 Commits

Reviewing files that changed from the base of the PR and between 664ceb4 and 1df6eab.

📒 Files selected for processing (2)

• docs.json
• v3/data-governance/zdr.mdx

[coderabbitai]

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Separate residency guidance from ZDR guidance.

The EU endpoint note and the ZDR list describe different constraints, but the current wording reads like one shared allowlist. Please make it explicit that fallbacks must stay within the same residency set, or split the bullets so readers don't assume any ZDR provider is EU-resident.

Proposed wording

 ## Reduce your data exposure
 
 - **EU endpoint**: restrict processing to EU-eligible providers.
-- **ZDR providers**: Amazon Bedrock, Cerebras, DeepInfra, Fireworks, Google, Groq, Microsoft Azure, Nebius, Perplexity, Qwen, Together. Pin your `model` and `fallbacks` to these.
+- **ZDR providers**: Amazon Bedrock, Cerebras, DeepInfra, Fireworks, Google, Groq, Microsoft Azure, Nebius, Perplexity, Qwen, Together.
+- **If you need EU residency**: keep `model` and `fallbacks` within the EU-eligible set above.
 - **Logs off by default**: Eden AI stores no content unless you enable log retention.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## EU data residency
	To keep data in the EU, use the [EU endpoint](/v3/data-governance/eu-endpoint) (`api.eu.edenai.run`), which routes only through EU-eligible providers. Today those are Amazon Bedrock, Google Vertex, Microsoft Azure, Mistral (Paris), and OVHcloud (Roubaix). Confirm the current list with `api.eu.edenai.run/v3/models`.
	## Reduce your data exposure
	- **EU endpoint**: restrict processing to EU-eligible providers.
	- **ZDR providers**: Amazon Bedrock, Cerebras, DeepInfra, Fireworks, Google, Groq, Microsoft Azure, Nebius, Perplexity, Qwen, Together. Pin your `model` and `fallbacks` to these.
	- **Logs off by default**: Eden AI stores no content unless you enable log retention.
	## EU data residency
	To keep data in the EU, use the [EU endpoint](/v3/data-governance/eu-endpoint) (`api.eu.edenai.run`), which routes only through EU-eligible providers. Today those are Amazon Bedrock, Google Vertex, Microsoft Azure, Mistral (Paris), and OVHcloud (Roubaix). Confirm the current list with `api.eu.edenai.run/v3/models`.
	## Reduce your data exposure
	- **EU endpoint**: restrict processing to EU-eligible providers.
	- **ZDR providers**: Amazon Bedrock, Cerebras, DeepInfra, Fireworks, Google, Groq, Microsoft Azure, Nebius, Perplexity, Qwen, Together.
	- **If you need EU residency**: keep `model` and `fallbacks` within the EU-eligible set above.
	- **Logs off by default**: Eden AI stores no content unless you enable log retention.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@v3/data-governance/zdr.mdx` around lines 54 - 62, The “EU data residency” and
“Reduce your data exposure” sections in zdr.mdx currently blur two different
rules, so update the wording in the EU endpoint and ZDR bullet list to clearly
separate residency constraints from zero-data-retention constraints. Use the
existing “EU endpoint” and “ZDR providers” bullets as anchors, and make it
explicit that any fallbacks must remain within the same residency set as the
chosen endpoint; do not imply that the ZDR provider list is EU-resident. If
needed, split the guidance into separate bullets or sub-bullets so readers can
distinguish EU residency requirements from ZDR-only provider eligibility.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
edenai	🟢 Ready	View Preview	Jun 25, 2026, 3:52 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.