Security architecture
built for trust
Memory policies. Scoped access. Encrypted credentials. Recall Racoon brings governance and operational visibility to the information your agents retain and recall.
Eight pillars of
memory security
Self-Hosted by Default
Run the memory platform on your infrastructure. Configure local processing and the integrations that connect to it.
Namespace Separation
Organize user and project memory in separate namespaces. Keep retrieval within its intended scope.
Access & Memory Policy
Apply configured access and memory policies to connected workflows. All memory API endpoints require authenticated requests — nothing reads or writes the Stash without credentials.
Secret Handling
Detect supported secret patterns on memory writes. Route detected values to the encrypted credential vault or redact them when the vault is unavailable.
Encrypted Credential Vault
Store sensitive credential values encrypted at rest. Manage credentials by project and keep references in ordinary memory.
Backups & Recovery
One command backs up the full memory store — database and vector index. A companion script copies archives off the host, so memories restore on different infrastructure if yours is lost.
Data Management
Inspect and update stored memories. Move deleted memories to Trash. Archive inactive memories to a portable, re-importable file with a tombstone — retention without loss.
Operational Oversight
A watchdog verifies the full stack every five minutes and emails you on failures and recoveries. MCP connections log a key fingerprint and the reason for any rejection — audit evidence without exposed secrets. A daily status report summarizes system health.
Keep credentials out of
ordinary memory.
Incoming memory is checked for supported secret patterns. Sensitive values follow the credential-handling path. Useful context stays available for recall.
What the scanner checks
- • API keys and access tokens
- • Passwords and credential-bearing connection strings
- • Private keys
- • Supported card-number patterns with validation
What happens next
- • With the vault available, detected values are stored encrypted and replaced with references.
- • Without the vault, detected values are redacted from memory.
- • Remaining nonsecret content is retained.
- • Project context and operation records support oversight.
Note: Detection applies to supported patterns. Redaction does not preserve a recoverable copy of the sensitive value.
Memory governed at every step.
Admission rules. Claim lifecycles. Source provenance. Recall Racoon separates reasoning from memory policy, with explicit controls over what enters the Stash and how it returns to your agents.
Control Plane
Enforce memory policies separately from model reasoning. Keep admission, conflict handling, and retrieval rules explicit.
Claim Lifecycle
Track candidate, confirmed, stale, superseded, conflicted, and archived claims. Keep changing knowledge under review.
Provenance & Audit Trails
Track sources and memory operations. Inspect the context behind a claim and the record of how memory changes.
Conflict Review
Surface conflicting information. Apply resolution policies. Bring people into the loop when review is needed.
Controls you can inspect.
Deployment Boundaries
Local processing gives you a deployment path that does not require an external AI API for embeddings or generation. Connected agents, integrations, backups, and support arrangements determine the complete data flow.
Memory Operations
Review memory activity, inspect source context, and manage changes through the available interfaces. Keep project scope and governance visible as your workflows grow.
Security Questions
Discuss credential handling, access boundaries, and operational requirements before deployment.
security@recallracoon.com