Clarify privacy limitations of Tinfoil (#12)
Co-authored-by: Darius Kazemi <darius.kazemi@gmail.com>
This commit was merged in pull request #12.
This commit is contained in:
1 parent
e50c4837c2
commit
03b1772eaf
1 file changed
+8
-8
+8
-8
@@ -14,7 +14,7 @@ provider today is best on both.
|
||||
|
||||
| Provider | Value | Privacy | Green energy | What that means |
|
||||
|---|---|---|---|---|
|
||||
| **Tinfoil** | *private* | **Strongest — architectural** | Not a green claim | Runs in hardware enclaves (TEEs) with end-to-end encryption (EHBP), verifiable via remote attestation. Neither we nor Tinfoil can read your prompts or responses at inference time. Energy mix is not disclosed. |
|
||||
| **Tinfoil** | *private* | **Strongest — architectural** | Not a green claim | Runs in hardware enclaves (TEEs) with end-to-end encryption (EHBP), verifiable via remote attestation. Neither we nor Tinfoil can read your prompts or responses at inference time. Energy mix is not disclosed. Please review the [Limitations on privacy](#limitations-on-privacy) below.|
|
||||
| **GreenPT** | *green* | **Policy-based** | **Strongest — 100% renewable** | Standard (non-enclave) hosting in the EU; privacy rests on GreenPT's commitments and EU data rules, not on cryptography. Compute runs on 100% renewable energy. |
|
||||
| **Regolo** | *green* | Policy-based — **zero data retention** | **100% renewable** | EU-hosted (Italy, Seeweb) with a stated zero-data-retention policy: prompts are not stored or reused. Compute runs on 100% renewable energy. |
|
||||
|
||||
@@ -307,10 +307,10 @@ reports back, and appears in your usage record alongside your chat calls.
|
||||
Only **Tinfoil** offers architectural privacy. The other providers are chosen
|
||||
for their value (renewable energy, public models) but do not run in enclaves —
|
||||
prompts and responses pass through them in the ordinary way. Your **chat
|
||||
history** is also stored on our server so you can revisit it, and that stored
|
||||
history is not encrypted in a way that prevents us from technically reading it —
|
||||
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](../governance/privacy-policy.md).
|
||||
history, including when using Tinfoil**, is also stored on our server so you can
|
||||
revisit it, and that stored history is not encrypted in a way that prevents us
|
||||
from technically reading it — 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](../governance/privacy-policy.md).
|
||||
Reference in new issue
Block a user