diff --git a/privacy-policy.md b/privacy-policy.md
index 80ae8c6..2e6cf92 100644
--- a/privacy-policy.md
+++ b/privacy-policy.md
@@ -1,11 +1,11 @@
 # Privacy Policy
 
-**Last updated:** September 10, 2026
+**Last updated:** October 6, 2026
 
 ## In plain language
 
 - We collect only what we need: your email, name, and basic usage data.
-- **Your AI conversations are encrypted** — even we can't read them at the inference step.
+- **Some models are private by design** — inference runs in encrypted enclaves we cannot read. **Others are chosen for renewable energy or open development, not architectural privacy.** Pick the model that matches your needs.
 - We **do** store your chat history on our server (so you can revisit it). We promise not to read it, but this is a promise, not a technical guarantee.
 - We never train on your data, and we never sell it.
 - You can export or delete your data at any time.
@@ -26,13 +26,19 @@ The Inference Cooperative is a member-governed project. We are **not** an ad-sup
 - **Content:** your prompts and the AI's responses (stored in your chat history).
 - **Billing data:** handled by Open Collective — we do not see full payment details.
 
-## 3. What we *can't* see (architectural privacy)
+## 3. Privacy depends on the model you choose
 
-Inference runs inside **encrypted enclaves** (TEEs). Your model inputs and outputs are encrypted end-to-end, so **even our own infrastructure cannot read them at the inference step.** This is verifiable through remote attestation — it's a property of the system, not a promise.
+We serve models from multiple providers, and they do **not** all offer the same privacy. You choose per task:
+
+- **Privacy-protected models (Tinfoil)** run inference inside **encrypted enclaves** (TEEs). Your model inputs and outputs are encrypted end-to-end, so **even our own infrastructure cannot read them at the inference step.** This is verifiable through remote attestation — a property of the system, not a promise.
+- **Renewable-energy models (GreenPT)** run on 100% renewable infrastructure. Their protection is about energy, not architectural privacy — inputs and outputs are processed under GreenPT's own terms and data-processing agreement, not in an enclave.
+- **Publicly developed models (PublicAI / Apertus)** are fully open. They likewise are chosen for open development, not architectural privacy.
+
+**The distinction matters.** If you need the strongest privacy, use a Tinfoil model. If you choose a GreenPT or PublicAI model, be aware that your inputs and outputs are not encrypted in a way that prevents them from being processed in the clear. We never read or sell your data regardless of model — but the *architectural* guarantee exists only on the Tinfoil path.
 
 ## 4. What we *can* see (an honest caveat)
 
-Your **chat history is stored on our server** so you can revisit past conversations. Unlike the inference step, stored chat history is **not** encrypted in a way that prevents us from technically reading it.
+Your **chat history is stored on our server** so you can revisit past conversations. Stored chat history is **not** encrypted in a way that prevents us from technically reading it, regardless of which model generated it.
 
 We commit not to read it. But this is a **policy commitment**, not an architectural guarantee. We're transparent about this distinction because it matters.
 
@@ -52,7 +58,9 @@ Web search runs through our self-hosted search instance. Search queries are forw
 
 ## 7. Third parties
 
-- **Tinfoil** — provides encrypted inference (cannot read your content).
+- **Tinfoil** — provides encrypted (TEE) inference; its privacy and data-processing terms apply.
+- **GreenPT** — provides renewable-energy inference; its terms and data-processing agreement apply (EU-hosted, GDPR-compliant).
+- **PublicAI** — provides openly developed models (Apertus); its terms apply.
 - **Open Collective** — handles billing and membership (their own privacy policy applies).
 - **Cloudron** — our self-hosted platform; no third-party cloud provider.
 - **Search engines** — receive your search queries (see §5).