Privacy and GDPR
What Strix stores, how keys are hashed and encrypted, and how to export or delete an account.
Strix stores the minimum needed to route, bill, and (if you leave memory on) remember derived facts. Prompt bodies are not written to AI Gateway logs (AIG_COLLECT_LOG_PAYLOAD is false). Guardrails never inspect prompt text.
Data map
| Store | Contents | Delete |
|---|---|---|
D1 users | Name, hashed primary key, enabled, deleted_at after erasure | Soft-delete |
D1 api_keys | SHA-256 of strix_… keys, prefix/last4 | revoked_at + hash overwritten |
D1 provider_credentials | AES-GCM ciphertext (OpenRouter, Venice) | Overwrite then DELETE |
D1 memory_events / memory_facts | Turns and derived facts | Hard-delete on account delete; Forget tombstones facts and deletes events |
Vectorize VECTORIZE_MEMORY | Embeddings of facts | deleteByIds |
D1 memory_settings / memory_jobs | Opt-in + job rows | Hard-delete |
D1 usage_logs / billing events | Tokens, model, cost, request id | Retained for accounting; error cleared; no prompts |
D1 sessions | Optional chat transcripts | Hard-delete |
Export and delete
Authenticated with your Strix key (CORS limited to the dashboard origin):
POST /v1/account/export— JSON: profile metadata, key prefixes only, billing status, memory export.POST /v1/account/delete— body{ "confirm": "DELETE" }. Afterwards that key returns 401.- Dashboard: Settings and Billing → Export / Delete account (two confirms + type DELETE).
- Memory-only:
POST /v1/memory/forgetand durable memory.
Human-readable policy: /privacy. Contact privacy@strixgate.dev.