Skip to main content

Security at Memora.

Memora connects to the tools where your team’s most sensitive work happens. This page explains how we protect that data, what we do with it, and how to reach us about security.

Request security documentation Report a vulnerability

How we protect your data.

Security is part of how Memora is built, not a separate add-on. These controls apply to every workspace.

Encryption

Data is encrypted at rest with AES-256 and in transit with TLS 1.3, with dedicated key management.

Permission-aware answers

Memora inherits document and channel permissions from Slack, GitHub, Jira and Google Workspace. People only get answers from content they can already access.

No training on your data

Your code, conversations and documents are never used to train AI models. Language model requests go to an enterprise endpoint with zero data retention.

Standard connections

Tools are connected through their own OAuth sign-in, so access is granted — and scoped — by each tool’s administrators.

How your data is used.

What happens to your content from the moment you connect a tool.

  1. You connect a tool

    An administrator signs in to the tool and grants Memora access to the workspaces you choose.

  2. Content is indexed securely

    Content and its permissions are stored encrypted, so answers can respect who is allowed to see what.

  3. Answers stay within access

    Each answer is built only from content the person asking can access, and cites its sources.

Subprocessors

Third parties that process data on our behalf. Each goes through a vendor security review.

SubprocessorPurposeLocation
Amazon Web Services (AWS)Cloud infrastructure and database hostingUSA / EU
CloudflareEdge network, DDoS protection and CDNGlobal
OpenAI EnterpriseLanguage model generation (zero-retention endpoint)USA
PostHogPrivacy-preserving product analyticsUSA / EU

Compliance documentation

We share our current security documentation, compliance status and data processing agreement (DPA) with customers and prospects on request.

Request documentation

Responsible disclosure

Found a vulnerability? Email security@memora.company with the details. Our disclosure contact is also published in our security.txt file.

Report a vulnerability

Security questions.

Is our content used to train AI models?
No. Customer content is never used to train AI models, and language model requests are sent to an enterprise endpoint with zero data retention.
Can people see answers from content they don’t have access to?
No. Memora follows the permissions in your connected tools, so each person only gets answers drawn from content they can already open in those tools.
Where is our data hosted?
Memora runs on Amazon Web Services in the USA and EU. The full list of subprocessors and their locations is on this page.
How do we get compliance documentation or a DPA?
Email security@memora.company. We share our current security documentation, compliance status and data processing agreement with customers and prospects on request.
Do you offer dedicated or self-hosted deployments?
If your organisation has specific deployment or data-residency requirements, contact us to discuss the options available for your plan.

Questions about security?

Our team can walk you through how Memora handles your data.

Email the security team Contact us