Skip to content
Security

How MemScope keeps your team’s memories private

MemScope exists because sharing memory across a team is only useful if the boundaries hold. Access is computed, not negotiated.

Access decided by policy

One fixed set of rules is the only thing that decides whether a memory may be read. It uses no AI. The same memory and the same person always get the same answer.

AI never grants access

AI only suggests labels. Your organization’s rules can only make a memory more private — they can never widen access or override policy.

Admins manage, they don’t read

Organization Owners and Admins manage people, teams and policy. Being an owner or admin never lets you read a memory on its own — there is no admin bypass, ever.

Platform staff see XXX

MemScope platform administrators cannot read customer memory content by default. Debug views return redacted content.

Time-limited support access

Customer-issued support grants last 1 hour, 24 hours or 7 days, are revocable, and every reveal is written to an append-only audit log.

Each organization kept separate

Every lookup is limited to your organization. Forbidden and missing records return the identical 404, so nothing leaks by inference.

Log redaction

Memory content never reaches logs. A central redaction layer turns raw content into XXX before it crosses a logging boundary, and exceptions never echo request bodies.

Immutable history

Raw memory content is immutable per version. Corrections create new versions; a forgotten memory can be restored by authorized users for 30 days, then its content is erased for good.

Separation of duties, by design

The person who runs the organization is not automatically the person who can read every memory. Platform operators are not exempt either. Support access is granted by the customer, limited in time, and fully audited.

Review the API and MCP behavior

Access decision

An org admin asks to read a memoryDecided by your organization's policyOwner or admin  still needs to be in its audience (no bypass)MemScope staff  sees XXX unless you grant time-limited support access

Where MemScope runs

The hosting, encryption and AI-processing facts behind the controls above.

Hosted on DigitalOcean

MemScope runs on a DigitalOcean Kubernetes cluster in the NYC3 (New York) region and stores its data in DigitalOcean Managed PostgreSQL.

Encrypted in transit

memscope.ai, app.memscope.ai, api.memscope.ai and mcp.memscope.ai are served over HTTPS (TLS), with certificates from Let’s Encrypt. Inside the cluster, a network policy lets only the ingress controller reach the application.

Encrypted at rest by the database provider

Stored data is protected by the managed database’s disk encryption. MemScope does not use per-organization encryption keys.

AI requests without retention

Requests to AI models go through OpenRouter and ask for zero data retention and no training. An organization setting turns external AI off for saving: new and corrected memories are then labeled, embedded and checked for duplicates by local models. It does not cover search: recall always sends the query to the external embedding model, and the query with the text of up to 40 candidate memories the searcher may read to the external decision model for ranking. Operator-set sensitivity limits can keep memories above a chosen level away from a provider; by default they allow every level.

Data retention and deletion

Forget, then erase
A forgotten memory leaves recall and listings at once. People allowed to can restore it for 30 days; after that its content is erased for good, unless it is on legal hold. The audit log keeps the record.
Corrections keep history
A correction creates a new version. Earlier versions are kept and shown only to people allowed to read them.
Permanent purge
An organization owner can permanently purge a memory, or every memory a member wrote. The content of every version and its search embeddings are destroyed; only a record without content (ids, timestamps, audit history) remains.
Export
Any member can download a JSON export of the memories they are allowed to read.
Operational logs
Request and tool-call logs hold ids, never memory content, and are deleted after 30 days.

Subprocessors

The third-party services MemScope uses to run the product, and what each one handles.

  • DigitalOcean

    Purpose: Hosting: the Kubernetes cluster, the managed PostgreSQL database and DNS.

    Data: All MemScope data, including memory content.

  • OpenRouter

    Purpose: Routes AI requests (labels, duplicate checks, search embeddings and ranking) to model providers, asking for zero data retention and no training.

    Data: Memory text when a memory is saved, unless the organization turns external AI off. On every search, whatever that setting says: the query, and the query with the text of up to 40 candidate memories the searcher may read.

  • Stripe

    Purpose: Subscription billing, checkout and the billing portal.

    Data: Billing contact and payment details. Never memory content.

  • Resend

    Purpose: Transactional email: email verification, password resets and invitations.

    Data: The recipient’s email address and the message. Never memory content.

  • Google Analytics

    Purpose: Website analytics, loaded only after a visitor allows it.

    Data: Page paths with ids and query strings removed, and a few named events. Never memory content, search queries, emails or names.

Report a security issue

If you think you've found a vulnerability in MemScope, email contact@memscope.ai with “Security report” in the subject. Include the steps to reproduce it and what you could see or change.

  • Test only with your own account and organization. Don’t view, change or keep anyone else’s data.
  • No denial-of-service, spam or social-engineering tests.
  • Give us reasonable time to fix the issue before you share details publicly.

We'll confirm we received your report and keep you updated while we fix it. The machine-readable contact is at /.well-known/security.txt.

Bring your most sensitive knowledge