Privacy Policy
Last Updated: August 7, 2026 • MemHouse Core Security Specification v0.4
VPC & Air-Gapped Isolation
Memory facts are filtered by authenticated Tenant Account and Scope. Operators should validate authorization controls and deployment configuration for their threat model.
No Model Training
Your facts and vector embeddings are never utilized to train public underlying models or third-party LLMs.
Zero Phone-Home Dependencies
Self-hosted and Enterprise deployments execute completely within your sovereign infrastructure.
1. Scope & Data Processing Architecture
MemHouse provides a stateful governed memory engine for AI agents, personal assistants (OpenClaw, Hermes Agent), orchestrators (LangGraph, CrewAI, AutoGen), and ephemeral swarms. When integrated into your applications, MemHouse processes raw observations and extracts structured factual statements (`subject`, `predicate`, `object`) on behalf of your tenant accounts.
2. Data We Process & Isolation Guarantees
- Tenant Facts & Vector Embeddings: Fact extractions are bound to strict composite index keys (`account_id`, `scope_id`). Facts are filtered using Gate A (quality/de-duplication) and Gate B (scope explosion protection) before entering active state.
- Provenance & Audit Trail Metadata: Every fact stores immutably its source observation ID, extraction model timestamp, and confidence score.
- No Public Telemetry: Enterprise self-hosted nodes execute zero phone-home diagnostic or usage reporting calls unless explicitly enabled by your systems administrator.
3. Data Retention, Curation & Deletion Rights
MemHouse supports granular lifecycle state management (`proposed` → `held` → `active` → `retracted`). You maintain 100% full authority to purge or retract facts via the REST API or MCP tool server (`mcp_memhouse_retract_fact`). Cascading soft and hard deletes immediately remove facts from PostgreSQL `pgvector` indexes.
4. Security Controls & Privacy-Law Support
MemHouse is designed to support encrypted transport and storage when operators configure those controls in their infrastructure. TLS versions and at-rest encryption depend on the deployment. Data deletion workflows are intended to help operators respond to GDPR and CCPA requests, but the software alone does not make a deployment compliant or constitute certification.
5. Contact Security & DPO
For privacy requests, DPA discussions, or security reports, use the enterprise inquiry form.