Skip to content

Security Policy

If you find a security vulnerability in MemStrata software or infrastructure, email security@memstrata.dev.

  • We aim to acknowledge all reports within 24 hours.
  • We target a patch or mitigation within 7 days for critical issues.
  • We will not take legal action against researchers who follow this policy.

Request the current PGP public key from security@memstrata.dev.


By default, imported sources, indexes, and local answering-model inference stay on the device. Provider keys are stored in the operating-system credential vault.

Loopback product services bind to localhost. Do not assume a single suite-wide port.


MemStrata is local-first, not air-gapped. Outbound calls depend on what you enable:

FlowTypical destinationData
Account, OAuth, entitlements, device registrationMemStrata hosted servicesIdentity and device-bound entitlement fields
LicensingMemStrata hosted licensingEntitlement check
User-selected cloud answering modelThe provider you configureQuestion and selected evidence for that request
Optional connectors or managed emailThe destination you configureMinimized message and recipient
WebsitePlausible, Vercel, CloudflarePage and request metadata as disclosed

No source tree is uploaded for training. Customer content is not used for training unless the customer separately opts in.


  • Optional browser capture, if installed for a product that supports it, needs host permissions for the consented sites.
  • Local services may use localhost TLS exceptions expected for loopback development.

SOC 2 Type II is not claimed. For a procurement questionnaire, email security@memstrata.dev.


We do not currently run a formal bug bounty. Researchers who disclose valid issues may be credited in release notes if they wish.