Forgetting a person and keeping requests in the cluster: users forget, keys residency --in-cluster
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
d67bd9b2cc
commit
30f7f3474a
17 files changed
+490
-11
No files matched your search
+7
-1
@@ -500,7 +500,13 @@ portal is not done — the page shows; the console and ctl change.
|
||||
**Secrets management (S–M).** Vault/KMS for `api_key_file`, the DSN, the
|
||||
CA key, `cluster_secrets` (`store/secrets.go`, `store/seal.go`);
|
||||
envelope-encrypt them in backups (with A8 backups).
|
||||
16. **GDPR and residency (S).** "Forget user" anonymises `user_id` in usage
|
||||
16. **Done (branch `features-c2`):** `users forget` (pseudonymised usage
|
||||
and sums, kept requests, files, batches, limits and audit names), `keys
|
||||
residency --in-cluster` (asked-for, fallback and canary). Left: an
|
||||
export of everything held about a person (article 15); residency by
|
||||
region between several clusters; backups keep what was forgotten until
|
||||
they age out.
|
||||
**GDPR and residency (S).** "Forget user" anonymises `user_id` in usage
|
||||
and rollups and erases threads/memory (`store/hierarchy.go:241` leaves
|
||||
it today); per-project "never route to an External provider".
|
||||
17. **Response/semantic cache (M).** Exact-match first, per project,
|
||||
|
||||
Reference in new issue
Block a user