Update remaining root-page links to governance/ paths

This commit is contained in:
inference-bot committed 2026-11-12 02:55:40 +00:00
1 parent e84a5537d4
commit a3cb6d7ec7
3 files changed
+4 -4

No files matched your search

+2 -2
View File
@@ -34,11 +34,11 @@ Two things worth being precise about:
[model list](models.md) distinguishes policy-based zero retention from
enclave-based protection.
Full detail, including what we can and cannot see: [privacy policy](privacy-policy.md).
Full detail, including what we can and cannot see: [privacy policy](governance/privacy-policy.md).
## Get a key
Log in to the [Member Dashboard](https://dashboard.inference.coop) and create an
Log in to the [Member Dashboard](https://dashboard.inference.coop)) and create an
API key. The key is an `sk-…` string you pass as a bearer token.
## Plain `curl`
+1 -1
View File
@@ -72,7 +72,7 @@ with the account you created in step 1.
nothing lands in your history or our database. To make this your default,
open **Settings → Conversations** and turn on **Default Temporary Chat**.
For anything sensitive, we recommend a temporary chat — ideally paired with
a 🔒 enclave model. See [Privacy](privacy-policy.md#4-what-we-can-see-an-honest-caveat).
a 🔒 enclave model. See [Privacy](governance/privacy-policy.md#4-what-we-can-see-an-honest-caveat)).
Your usage draws from your monthly allowance; you can see it on the
[Member Dashboard](https://dashboard.inference.coop).
+1 -1
View File
@@ -304,4 +304,4 @@ we commit not to. Requests made through the **API** with your own key are a
different matter: those are **not stored on our side at all**, beyond the usage
record needed for metering ([API access](api-access.md)). The full distinction —
what's architecturally private versus what's a policy commitment — is in the
[Privacy Policy](privacy-policy.md).
[Privacy Policy](governance/privacy-policy.md).