Security
Last updated: 2026-06-19
This page is for three readers. A workspace admin preparing an IT and legal approval memo before installing Mycelium. A Fortune 100 procurement reader following a sales-link to understand the trust posture. And a security researcher looking to report a vulnerability. All three are below.
Eight trust commitments
Eight commitments Mycelium ships on every tier, in code and in the Terms of Service. These appear inline in the onboarding wizard at the OAuth step, not buried in fine print. Some commitments are tier-conditional (Team and Enterprise add audit log and a private personal layer); we flag the tier explicitly per commitment.
These eight are the canonical list. We add new commitments only after panel review (to avoid trust-claim creep). If a future surface adds one, it lands here first, before any marketing copy refers to it.
1. Credentials encrypted at rest
What this means. OAuth tokens, refresh tokens, and API keys are encrypted at rest at the storage layer. Customer content at rest is encrypted too. We never read tokens or content in plain text from disk.
How we enforce it. Every connection uses HTTPS. Data sits on our host's encrypted disks. Your own encryption keys (BYOK) are not offered yet. More in the Data Processing Addendum.
2. Disconnecting a source deletes its data
When you disconnect a source in Studio, we delete its sign-in, its sync progress and every copy of its content in your brain’s search right away, and ask the provider to revoke our access. Two things stay for now: names and links the brain map learned from it (we are fixing this), and our encrypted daily backups, which are deleted after 5 days.
3. Never used for training
What this means. Customer content is never used to train any AI model, ours or anyone else’s. This is contractual, not aspirational.
How we enforce it. The Terms of Service prohibit training on customer content. Mycelium does not currently train any model on customer data. When you use Hosted Pass-Through inference (an opt-in feature at Team and Enterprise), the upstream model provider (Anthropic, OpenAI, Google) operates under their enterprise contracts, which prohibit training on customer prompts. The default path is BYO inference (commitment #4 below), which keeps your content off any Mycelium-controlled inference endpoint.
4. BYO inference
What this means. Mycelium does not bundle inference cost. You bring your own Claude plan or API key. Your content never reaches a Mycelium-controlled inference endpoint unless your workspace explicitly opts into Hosted Pass-Through.
How we enforce it. The runtime ships with adapter-pattern model routing. Default routing sends inference calls through the Claude plan or API key you connect at install. Hosted Pass-Through is an opt-in tier-level feature with an explicit toggle in the admin UI. The adapter does not buffer prompts on Mycelium-side servers in the BYO path. The commercial reason matters: avoiding per-token resale is structural, not seasonal. See the Pricing section for the BYO commitment in plain copy.
5. Pause sync (one-click for sensitive periods)
What this means. A one-click toggle pauses connector ingestion across all sources without disconnecting them. Useful for litigation holds, M and A windows, internal investigations, or any period where you want the ingestion path closed temporarily.
How we enforce it. The pause toggle lives on the Connectors page. While paused, no new events are ingested, no embeddings are computed, no knowledge-graph updates fire. Existing data remains queryable. Resume re-enables ingestion from the resume point forward. Backfill of the paused window is opt-in per source.
6. Audit log at Team and Enterprise
What this means. At Team and Enterprise tiers, every change to the brain is logged with time, person and what changed. The workspace admin can export the log.
How we enforce it. The append-only audit log lives at audit-log.jsonl per tenant. Workspace admins export the log via the admin endpoint. Each entry is chained to the one before it, so a deleted or edited entry shows. Personal-tier accounts do not have an audit log because they do not have admins to audit; the log is a Team-and-up surface by design.
7. Personal layer private at Team
What this means. At the Team tier and above, every workspace member has a personal layer connected to their personal sources (personal Gmail, personal Notion, iMessage, etc.). The personal layer is private to that user. Workspace admins cannot search it. Other team members cannot see it. It does not feed the company brain.
How we enforce it. The runtime enforces a per-user privacy boundary at the storage and query layer. The personal layer lives under a per-user JWT scope; the company brain is a separate JWT scope. Cross-scope reads are denied at the auth layer. An integration test asserts that an admin token cannot read another user’s personal-layer paths. The departing-employee flow (covered in the IT-approval scoping guide below) exports the user’s personal-layer content to them within 7 days, then deletes it. The full access-control architecture ships at /security/rbac.
8. Third-party security audit and SOC 2 Type II status
What this means. Mycelium has not commissioned a third-party security audit and is not SOC 2 certified. Vendor selection, engagement signature, audit kickoff, compliance-platform onboarding, and the SOC 2 Type II observation period are pending.
How we report it. Each prerequisite has its own row in Audit status below. We publish the firm name, engagement signature, kickoff date, and observation start only after each event occurs. We do not claim “SOC 2 certified” until the SOC 2 Type II report is in hand.
Deployment isolation and tenancy
For Fortune 100 procurement readers and IT teams evaluating tenant boundary enforcement. Mycelium runs one shared service, hosted in the US, with each company kept apart in software.
Shared-tenant (default for Personal, Team, and Enterprise tiers). Every request carries its company ID and is checked on the server. Each company has its own brain and its own audit log. A test checks that one company's token cannot read another company's data. Each person's private space is kept apart from the company brain.
Not built yet. Single-tenant hosting, your own cloud, EU hosting, SAML and SCIM. HIPAA is not offered yet.
Audit status
Current pre-engagement state of the third-party security audit and SOC 2 Type II work. Updated only when a milestone actually lands. Procurement should read the status directly from this table, not from a sales deck.
| Milestone | Status | Date |
|---|---|---|
| Third-party audit firm | Vendor selection pending. No engagement letter signed. | Firm name published after signature. |
| Compliance platform | Selection and onboarding pending. | Platform name published after contract. |
| Third-party audit kickoff | Pending signed engagement | Date not set |
| SOC 2 Type II observation start | Pending platform onboarding and audit kickoff | Date not set |
| SOC 2 Type II certification | Not yet certified | Targeted 2027 |
We do not claim “SOC 2 certified” until the SOC 2 Type II report is in hand. No auditor or observation start is named until it is contractually real.
Procurement officers asking for current status can contact security@mycelium-ai.co and we will confirm the same pending state in writing. There is no signed auditor name or observation start date to share yet.
IT-approval scoping guide for workspace admins
For workspace admins planning a Team or Enterprise install. Before you click “Connect” on a company Google Workspace, Slack, Notion, or similar OAuth flow, get IT and legal approval. This guide walks the standard path.
The reason this matters: admin-level OAuth to a company Google Workspace is real scope creep. You as the admin can click the consent screen, but does your IT and legal team actually have written authority for Mycelium to ingest all company email and Drive content the connector reaches? If the memo overpromises and the IT team waves it through, the IT approval becomes the privacy violation, not the enabler. This guide is built to avoid that.
Step 1. Review the scope
Read the eight trust commitments above. Decide which connectors you actually need at install. Be specific about which Slack channels, which Drive folders, and which Notion workspaces are included. The admin overrides on each connector let you tighten the default scope further.
Step 2. Draft the memo
Use the IT and legal approval memo template in Section 10 below. Fill in the company-specific blanks. Be honest about the scope you are requesting. Do not over-promise.
Step 3. Get written approval
Send the memo to your IT and legal contacts. Ask for written approval that covers (a) the connector scope, (b) the data-handling commitments, (c) any residency requirements, and (d) the audit-log retention window if you need a deviation from defaults. Do not click “Connect” in Mycelium until you have it.
Step 4. Document the approval
Save the approval thread or signed memo in your engagement-letter file with Mycelium. We can reference it in the contractual MSA or DPA as the scope authorization document.
Step 5. Install and audit
Complete the OAuth flow. The audit log starts logging immediately. Track support tickets for IT or legal objections that arise post-install. We iterate the scoping guide based on real objections, not hypothetical ones.
IT and legal approval memo template
A copy-paste template you can hand to your IT and legal teams. Fill in the [BRACKETS] with your company specifics. The template is published under the same terms as the rest of mycelium-ai.co; you are free to copy, modify, and use it for your internal approval process.
Download IT and legal memo template (Markdown)
The template covers: executive summary, connectors proposed, what gets ingested per connector, what gets skipped per connector, encryption surface, the eight trust commitments, audit status, subprocessor list, data residency, DPA reference, departing-employee flow, questions to ask Mycelium in writing, and recommended next steps for IT and legal.
Spanish-language version: Descargar plantilla de memo de IT y legal (Markdown).
Role-based access control inside your tenant
Mycelium ships folder-glob role-based access control inside every tenant. Each JWT carries a roles claim. Every vault-touching route resolves the role-set against the target path before reading or writing. Denials produce structured audit-log entries.
This is the Phase 4 deliverable on the SOC 2 CC6.1 control path. The full documentation, including the default 10-role library, the admin API surface, webhook denial behavior, backward-compatibility behavior, and the operational caveats most pages hide, lives at /security/rbac.
Vulnerability disclosure
Mycelium runs a coordinated disclosure program. Researchers who report vulnerabilities in good faith and in line with the rules below are acknowledged in our public CHANGELOG and credited in any related security advisory.
Reporting
Send vulnerability reports to security@mycelium-ai.co. Encrypted submissions are welcome; PGP key fingerprint available on request.
Please include:
- A clear, reproducible description of the issue
- The affected URL, endpoint, version, or component
- Proof-of-concept output or steps that demonstrate the impact
- Your preferred name for credit (or a request to remain anonymous)
Response timeline
- Acknowledgement within one business day
- Initial triage and severity assessment within five business days
- Remediation plan and target date within fifteen business days
- Public disclosure window: ninety days from initial report, or sooner if a fix has shipped and the customer base has been notified, whichever comes first
Scope
In scope:
- mycelium-ai.co and all subdomains operated by Mycelium
- The open-source memory layer at github.com/mycelium-hq/ai-brain-starter
- The productized runtime endpoints exposed to customers under engagement letter (subject to the safe-harbor section below)
Out of scope:
- Third-party services (Vercel infrastructure, Resend, PostHog, Anthropic, OpenAI, etc.). Please report to the vendor directly.
- Social engineering of Mycelium employees, contractors, or pilot customers
- Physical attacks on Mycelium offices or hardware
- Denial-of-service or rate-limit testing without prior written authorization
Safe harbor
Research conducted in line with this policy is considered authorized and Mycelium will not pursue civil action or report it to law enforcement. Researchers must avoid accessing or modifying customer data, must stop testing immediately on request, and must give Mycelium reasonable time to remediate before public disclosure.
Recognition
Researchers who follow this policy and submit valid vulnerability reports are acknowledged in the public CHANGELOG and (with the researcher’s consent) in any published security advisory. Cash bounties are not currently offered; we expect to launch a paid program after the SOC 2 Type II audit completes.
Privacy and data subject inquiries
For privacy questions or data-subject requests under GDPR, UK GDPR, CCPA, or LGPD, write to privacy@mycelium-ai.co.
Mycelium · founded 2026