Skip to content
Galdocompany memory

Trust · security

Trust & Security

Galdo holds the decisions and exceptions behind how your company works, and your team and your AI agents act on what it returns. So: encryption by default, isolation by design, and straight answers about what's still on the roadmap.

Security covenants

Encryption in transit and at rest

All traffic is encrypted in transit with TLS 1.2 or 1.3 (HTTPS only), and data is encrypted at rest on the underlying cloud storage. API keys are stored SHA-256 hashed — never in plaintext.

Workspace isolation

Every query is scoped to your workspace — there are no cross-tenant reads. Each API key is bound to a single workspace and cannot reach another tenant's data.

Where data is hosted

US-hosted with encryption in transit and at rest. EU regions with per-workspace residency selection are on the roadmap.

Self-hosted deployment

On Enterprise, run Galdo on your own servers: one Docker Compose install with pre-flight checks, your own AI provider keys (Azure OpenAI, OpenAI or Anthropic) or a local model (with a local model, memory and AI calls stay on your network), and scripted backups, restores and upgrades with automatic rollback. For air-gapped environments, offline mode runs Galdo with no route outside your servers, enforced by the network rather than by settings, and nothing is downloaded at install. Each install generates its own secrets, the app reaches its database through a restricted role, and Galdo sends no telemetry or calls back to us. Talk to us to set up a pilot.

API key security

Keys are workspace-scoped, hashed at rest, revocable, and rotatable with a 24-hour grace window so you can roll without downtime. Optional per-key IP allowlisting.

Single sign-on and provisioning

On Team and Enterprise, people sign in through your identity provider (Okta, Microsoft Entra ID, or another SAML 2.0 or OpenID Connect provider) with addresses in email domains you've verified with a DNS record. A single sign-on session opens only that workspace, is time-limited, and relies on your identity provider's MFA. Enterprise adds Require SSO, where the owner keeps password access as a break-glass, and SCIM 2.0 provisioning: deactivate someone in your identity provider and they're removed from the workspace.

Auditable by design

Memory is append-only and event-sourced: every retrieved fact traces back to its source, with an append-only audit log of workspace activity that owners and admins can review on every plan. Account controls include owner, admin, developer, viewer and billing roles, MFA, enforced email verification, and revoke-all-sessions.

Reliability and transparency

Formal SLAs, a public status page and published postmortems are on the roadmap.

Compliance status

  • GDPR — Available. DPA plus data export and deletion controls.
  • CCPA — Available. Data-subject request (export/delete).
  • SOC 2 — Readiness in progress. SOC 2 readiness in progress.
  • SSO / SAML — Available. SAML 2.0 or OIDC on Team and Enterprise; SCIM on Enterprise.
  • HIPAA — Planned. Not yet available.
  • ISO 27001 — Planned. Not yet available.

Compare deployment options

  • Hosted — every plan; data in Galdo's US cloud; AI through our providers (see sub-processors); Capture extension and MCP server included; email invites plus a link; backups and upgrades run by Galdo.
  • Self-hosted — Enterprise; data on your servers; your Azure OpenAI, OpenAI or Anthropic keys, or a local model; internet access only to the AI provider you choose; Capture extension and MCP server not yet; invite links you share; scripted backups and upgrades run by you.
  • Self-hosted, offline — Enterprise; data on your servers; a local model; no route outside your servers; Capture extension and MCP server not yet; invite links you share; scripted backups and upgrades run by you.

What Capture sees, and what it never does

Capture records nothing until an admin turns it on and each person agrees in their own browser. People can see when it's recording and pause it any time. Retention, deletion and the full detail are in the Privacy Policy: https://getgaldo.com/privacy

  • Records: page addresses and titles on sites an admin has allowed; the labels of controls people click, form submissions and selected options; text typed into a field, read once when you leave the field, redacted on the device and again on our servers, and cut to 200 characters (admins can turn this off).
  • Never records: password, payment and hidden fields; incognito windows; keystrokes or the clipboard; screenshots, audio or files; any site an admin hasn't allowed, or anyone who hasn't agreed in their own browser.

Sub-processors

Who else handles data for hosted Galdo. We notify customers at least 30 days before adding one (see the DPA: https://getgaldo.com/dpa). A self-hosted install uses none of these.

  • US-hosted infrastructure — hosting: application servers, database and backups (United States)
  • Microsoft Azure OpenAI — embeddings for search (United States)
  • Anthropic — AI models: extracting memories, answering questions in Ask and the Slack app, and Capture session summaries and procedures. Keeps inputs/outputs up to 30 days; not used for training (United States)
  • Resend — transactional email: verification, invitations and digests (United States)
  • Google — sign in with Google (Global, only if used)
  • GitHub — sign in with GitHub (Global, only if used)
  • Slack — the Company Brain Slack app, for workspaces that install it (Global, only if used)
  • Connected apps — Notion, Jira, Outlook, OneDrive and the other tools on /connectors that a workspace chooses to connect (Global, only if used)
  • Google Gemini — understanding YouTube videos you add to Galdo, only if used (Global)
  • Google Analytics — visit analytics for the getgaldo.com marketing site only (Global)

Questions reviewers ask

  • Do you train AI models on our data? No. We don't train models on your content, and our AI providers don't keep it for training.
  • Where is our data stored? On hosted Galdo, in the US. EU regions are on the roadmap. On a self-hosted install, only on your own servers.
  • Can one customer ever see another's data? No. Every query is scoped to a single workspace, and each API key belongs to exactly one workspace.
  • What happens when someone leaves the company? Remove them in the dashboard, or deactivate them in your identity provider with SCIM on Enterprise. They lose access to the workspace.
  • Can we run Galdo without internet access? Yes, on Enterprise. Offline mode runs on your servers with no route outside them and a local model, so nothing leaves your network.
  • Will you fill in our security questionnaire or sign a DPA? Yes. Send the questionnaire to security@mnemohq.com and we answer within one business day. Our DPA is published at getgaldo.com/dpa.

Recent security changes

  • October 27, 2026 — Offline mode for self-hosted installs: run Galdo with no route outside your servers, enforced by the network, with models loaded from a file.
  • October 26, 2026 — Self-hosted deployment on Enterprise: one Docker Compose install on your servers, with your own AI keys or a local model, and scripted backups, restores and upgrades.
  • October 24, 2026 — Single sign-on and SCIM: SAML 2.0 or OpenID Connect sign-in on Team and Enterprise; Require SSO and SCIM provisioning on Enterprise.
  • October 22, 2026 — Consent before Capture records anything: Galdo Capture stays off until an admin turns it on and each person agrees in their own browser.

Report a vulnerability

Found a security problem in Galdo? Email security@mnemohq.com. We acknowledge every report within one business day, and keep you updated until it's fixed.

In scope: getgaldo.com, mnemohq.com and its subdomains (the app, the API and the MCP server), the Galdo Capture browser extension, and the self-hosted install.

Safe harbor: if you act in good faith and follow these guidelines, we consider your research authorized, and we won't take or support legal action against you for it.

No bug bounty: we don't run a paid bug bounty. This is responsible disclosure: we fix what you report and tell you when it's done. Machine-readable contact: https://getgaldo.com/.well-known/security.txt

  • Tell us what you found and where (the URL, endpoint or extension version), the steps to reproduce it, and the impact you expect.
  • Give us a reasonable time to fix it before you share it publicly. We'll tell you when the fix is out.
  • Test only with your own account and data. Don't access, change or delete anyone else's data, and if you come across some, stop and tell us.
  • Don't run denial-of-service, spam or social-engineering tests against Galdo, our customers or our people.

Questions about security?

Founder-led — I respond to security questions within one business day. Happy to complete your security questionnaire, sign a DPA, or walk your team through the architecture. Coordinated disclosure welcome — email security@mnemohq.com. DPA: https://getgaldo.com/dpa

Explore Galdo