Memory Privacy & Shared Room Invariants
How Zero Data Retention protects memory extraction, and why shared rooms and group messaging strictly disable personal memory injection.
Privacy Invariants in Personalization
Personalization without rigorous privacy controls is an existential security risk. If an AI platform records your private notes, health details, financial figures, or company roadmap into an insecure or multi-tenant memory store, that data can easily leak into shared spaces or third-party training pipelines.
ARMES enforces strict, non-negotiable architectural invariants for memory.
1. Zero Retention During Fact Extraction
When our background agent extracts atomic facts or episode summaries from your conversation:
Extraction Privacy Invariant
Memory extraction requests route through the same Zero Data Retention infrastructure as standard chat completions. The AI model that reads your transcript to extract facts forgets the transcript immediately upon response completion. No transcript text is retained by the lab.
2. Shared Rooms & People Messaging Invariant
When you collaborate with other human beings in People & Messages (/people), private DMs, or group channels:
Shared Room Memory Invariant
Personal Memory Injection is Strictly Disabled in all multi-user environments. When an agent is invited into a shared conversation or direct message with another human:
- Your personal Memory Ledger is NOT injected.
- Your personal Identity Envelope is NOT injected.
- Your personal Episode Summaries are NOT accessible.
Why This Invariant is Critical
If your agent retained memory of your private financials and was invited into a project chat with an external contractor, a poorly guarded prompt could cause the agent to accidentally disclose your private numbers.
By completely stripping memory envelopes from shared rooms, ARMES guarantees that your private thoughts and personal facts never leak to collaborators.
3. Custom Webhook Agent Isolation Invariant
When interacting with external agents configured with external HTTP webhooks:
- Your personal Identity Envelope is strictly withheld.
- Your personal Memory Ledger is never sent to the external webhook endpoint.
- External webhook agents only receive the explicit prompt and immediate message parameters.
4. Immediate Vault Deletion
Unlike platforms that soft-delete memories into hidden archive tables:
- Clicking delete on any memory fact permanently removes the record from your private database vault.
- Corresponding search vectors and indexing embeddings are purged in the same transaction.
- When an account is closed, all memory ledgers, episodes, and identity profiles are permanently purged immediately from the live database and from encrypted infrastructure back ups within 7 days.