Privacy policy
Last updated: 2026-11-05
Mycelium (the “Company,” “we,” “us”) operates mycelium-ai.co, the open-source memory layer at github.com/mycelium-hq/ai-brain-starter, Mycelium Studio and its runtime, a productized commercial runtime delivered to enterprise pilot customers under engagement letter, connected Google accounts (Gmail, Google Calendar and Google Drive), and optional connected social accounts such as Instagram via the Meta Graph API. This policy covers what each surface collects, how data is stored, how it is shared, and how you exercise your rights.
1. Marketing site (mycelium-ai.co)
The pilot inquiry form collects: company name, your name, email address, role, industry, company size band, expected pilot start window, current AI tooling toggles, biggest integration pain, and an optional free-text field. The form delivers a single email to the founder via Resend (transactional email provider, US-based, GDPR processor with a published DPA at resend.com/legal/dpa). It also saves your inquiry in Truffle, our sales workspace (see section 1c).
We use PostHog (posthog.com/privacy) for analytics on the marketing site, and only if you accept analytics in the cookie banner. Until you accept, no PostHog script loads, and no analytics cookie, storage entry or request is created. With your consent we capture pageviews, page leave events, and a small set of CTA clicks. We do not enable autocapture. You can change or withdraw your choice at any time with Cookie settings in the homepage footer, or here: .
Without consent we only use what the site needs to work: your cookie choice (stored in your browser), your language preference, and, if you sign in, the sign-in session.
We do not run third-party advertising trackers, social pixels, or session replay tools on this site.
1b. Install onboarding form (mycelium-ai.co/install)
Every AI Brain Starter install begins with an email-capture form at mycelium-ai.co/install (and mycelium-ai.co/es/instalar for Spanish). The form collects: your name, email, country, role, optional company, intent (free-text), the operating system you’ll install on, your prior Claude Code experience, and (for paying-tier or cohort branches) approximate notes count, where those notes currently live, and an optional link to a recent piece of your writing for voice-fingerprinting. Two consent checkboxes: one required (process my data to deliver the install, follow up with me about it and about Mycelium, send product updates, and add me to the right newsletter), one optional (receive occasional case studies and updates from other users).
On submit we mint a 32-character install token, store it for 30 days in Upstash Redis (US, encrypted at rest, sub-processed under our DPA), append a row to a Mycelium-owned Google Sheet via a service account so the founder has a single roster of every signup, save a record in Truffle, our sales workspace (section 1c), subscribe your email to the matching Substack publication (English: adelaidadiazroa, Spanish: perspectivasblog), and send a welcome email via Resend that contains the personalized install command. Your token is then gated against the bootstrap on your machine, so installs cannot proceed without it. You can withdraw consent and request deletion at any time at privacy@mycelium-ai.co; deletion removes you from the Sheet, Truffle, the Substack list, and the Redis token store.
When you submit the form, our servers also record install progress in PostHog (form submitted, token issued, install started, install completed, first journal saved) under your email address, so we can see where installs fail. These events are sent from our servers and use no cookies in your browser. The confirmation page may show a Loom walkthrough video; Loom may set its own cookies when that video loads.
Existing users who installed before the gate was live (clones from before the form went live) will be prompted on their next bootstrap re-run to backfill their email by completing the same form. Once we have an email-on-file marker, the prompt does not re-fire.
1c. Follow-up from our sales workspace (Truffle)
When you send one of this site’s forms (the waitlist or the Enterprise form, the install form, the pilot inquiry, or the plugin updates sign-up), or give us your email from inside Claude Code (during setup or after it), we also save what you sent in Truffle, Mycelium’s own sales workspace, so a person on our team can follow up with you. The record holds your email address, your name and company if you gave them, which form you used and when, and a short summary of your answers, which can include what you wrote in a free-text field.
When you sign in to the Mycelium app and it creates a workspace for you, or you create a new team workspace, we save a record and add you to our contact list, with a reminder for our team to write to you: the email address your sign-in verified and the workspace’s name. It doesn’t apply to a personal workspace that came with a seat your company gave you.
Truffle runs on Mycelium’s own runtime, hosted by Fly.io in the United States. Like the rest of our team workspace, its records are indexed so our team can search them, which uses providers listed in section 4 (Anthropic and Voyage AI, both in the US). We use these records only to follow up with you about Mycelium. We don’t sell them or use them for advertising. We keep a record until you ask us to delete it: write to privacy@mycelium-ai.co and we remove it with the rest of your data.
2. Open-source memory layer
The open-source memory layer at github.com/mycelium-hq/ai-brain-starter runs entirely on your own machine. We never receive your vault data, journals, decisions, or any local state created by the memory layer unless you explicitly send a portion of it to us as part of a paid pilot or a support request.
3. Productized runtime (paying pilots)
Customers on a paid pilot run the productized runtime in either a Mycelium-managed tenant (US or EU region of your choice) or in your own cloud or on-premise infrastructure (Mycelium Enterprise tier). In every deployment shape, your tenant data stays inside the tenant boundary and is never used to train shared models, shape another tenant’s outputs, or marketed to a third party.
The runtime maintains an audit log of every read, write, and synthesis event with actor, timestamp, and source. Audit logs are exportable on demand. Default retention is twelve months; longer retention is configurable per tenant under SOX or HIPAA- adjacent contracts.
3b. Connected social accounts (Instagram / Meta)
Where a customer, or Mycelium for its own brand accounts, connects an Instagram Professional account to our Instagram management tooling, we access data through Meta’s official Instagram Graph API only to operate the features you ask for: account metadata and media (the instagram_basic permission), comments on your media (instagram_manage_comments), and, where granted, direct messages on the connected account (instagram_manage_messages, plus human_agent for replies a human sends after the standard 24-hour window).
We use this data solely to display, send, and manage your Instagram content, comments, and messages inside the tool you operate. We do not sell it, do not use it for advertising, and do not share it with any third party beyond Meta’s own API. Access tokens are stored encrypted. Message and comment content is processed to display your active inbox and is not retained beyond that need unless you export it. Audit logs record the action and timestamp with message bodies redacted.
You can disconnect an account at any time in your Instagram or Facebook settings under Apps and websites, which revokes our access. To request deletion of stored data tied to a connected account, see Data deletion below. Our use of information received from the Meta APIs follows the Meta Platform Terms and Developer Policies, including the 24-hour messaging window and message-tag rules.
3c. Google user data (Gmail, Google Calendar, Google Drive)
What we ask Google for, and why. When you connect a Google account in Mycelium Studio, you choose which products to connect: Gmail, Google Calendar, Google Drive, or any combination. A product you leave unticked is not part of the request. You can connect more than one Google account, and each account’s tokens, sync state and indexed content are kept apart. Mycelium’s Google app asks for permission to read Gmail, Google Calendar and Google Drive. Creating Gmail drafts is a separate permission, asked for on its own.
How we use it today. We read your own mail, meetings and files so you can search them, ask questions whose answers cite the message, event or passage they came from, and get briefs built from your threads and meetings. If you grant the separate drafts permission, Mycelium can create follow-up drafts in your Gmail; you edit, send or discard them in Gmail. Mycelium does not send email, does not delete your email, events or files, and does not create or change calendar events or Drive files. (The optional Google Workspace tools you can install in Studio run on a Google Cloud app you create yourself, not on Mycelium’s, and that use is between you and Google.)
Sending email. When we add sending, Mycelium will send a message only after you have turned sending on yourself and approved that specific message. If we add other actions on your Google data, we will ask for your permission first and update this policy before they go live.
What we read. From Gmail: the headers, subject and text body of the messages in your mailbox, with Google’s short snippet of each; attachments are not downloaded. From Calendar: each event’s title, time, organizer, attendees, description, meeting link and your response status. From Drive: the text of Google Docs, Sheets, Slides and plain-text files in the folders you select, with each file’s name and dates.
Where it is stored. Your Google access and refresh tokens are stored on Mycelium’s runtime servers, one record per connected account, inside your own tenant, and are encrypted with AES-256-GCM before they are written to disk. Token values are never written to logs. Indexed content stays in your own tenant and is never mixed with another tenant’s. We keep Google-derived content while the account stays connected.
Who processes it.
- Answers, briefs and drafts run on the AI provider you connect, on your own key or plan. Mycelium has no shared key that can serve your content. When Mycelium Studio works on your device, the relevant parts of your Google content go from your computer to the provider you chose, under your own agreement with that provider.
- In Team and Company workspaces, Voyage AI (Voyage AI Innovations, Inc., a MongoDB company, US) computes search embeddings and reranking on Mycelium’s account. It receives the text of each indexed passage with its title and labels, and your search query. Voyage does not receive content from Personal brains.
- We do not use Google user data to develop, improve or train generalized AI or machine-learning models. We do not sell it, use it for advertising, transfer it to data brokers, or use it to assess creditworthiness.
Human access. No one at Mycelium reads your Gmail, Calendar or Drive content in the normal course of running the service. Only Mycelium’s two founders can access it, and only (a) with your explicit agreement for a specific support request, limited to the messages, events or files you name; (b) when needed for security, such as investigating a bug or abuse; or (c) when needed to comply with the law.
Disconnecting and deletion. You can disconnect a Google account at any time in Studio. Disconnecting deletes its tokens, the content indexed from it and its sync state, and asks Google to revoke Mycelium’s access. You can also remove Mycelium yourself at myaccount.google.com/connections. Drafts already created in your Gmail are yours and stay there. To delete everything tied to your account, see Data deletion below.
Limited Use. Mycelium’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. Subprocessors
Across our marketing and runtime surfaces we currently rely on the following subprocessors:
- Vercel Inc. (hosting, edge network), US
- Fly.io, Inc. (hosting for Mycelium’s runtime, including our sales workspace, Truffle), US
- Resend, Inc. (transactional email), US
- PostHog, Inc. (product analytics), US (EU instance available on request)
- Upstash, Inc. (Redis-compatible key-value store for install tokens), US
- Google LLC (Sheets API for the install signup roster; Gmail, Calendar and Drive APIs when you connect a Google account), US
- Voyage AI Innovations, Inc., a MongoDB company (search embeddings and reranking for Team and Company workspaces), US
- Substack, Inc. (newsletter delivery for installs that consent), US
- Meta Platforms, Inc. (Instagram Graph API, for connected social-account management where enabled), US
- Anthropic PBC (LLM compute, used inside the runtime where opted in by the customer), US
- OpenAI, OpenRouter, MiniMax (LLM compute, opt-in per-tenant), US
A complete subprocessor list, with regions and contractual safeguards, is available in our Data Processing Addendum at /dpa.
5. International transfers
Personal data submitted via the marketing site is processed in the United States by our subprocessors. For customers in the European Economic Area, the United Kingdom, or Switzerland, we rely on the EU Standard Contractual Clauses (2021/914) and the UK International Data Transfer Addendum (March 2022) where applicable. Customers on the Mycelium Enterprise tier can elect to keep data in an EU region under separate contractual terms.
6. Your rights (GDPR, UK GDPR, CCPA, LGPD)
You have the right to access, correct, delete, or request a copy of the personal data we hold about you. You can also object to or restrict our processing, and (where applicable) withdraw consent or lodge a complaint with a supervisory authority. To exercise any of these rights, write to privacy@mycelium-ai.co. We respond within thirty days; complex requests may extend to sixty.
6b. Data deletion
To delete data associated with your account, including data from a connected Google, Instagram or Meta account, email privacy@mycelium-ai.co with the subject “Data deletion” and the account identifier (for Instagram, the username). We remove stored tokens and any retained message, comment, insight, and roster data within thirty days and confirm by email. You can also revoke access yourself right away: in Instagram or Facebook, open Settings, then Apps and websites or Business integrations, and remove the Mycelium app.
7. Retention
The email thread and notes from an inquiry-form submission are kept while we are evaluating or running a pilot with you, and for twelve months after the pilot ends; after that we delete them unless you ask us to keep them. The inquiry’s record in Truffle (section 1c) is kept until you ask us to delete it, like every Truffle record. Audit logs in the productized runtime follow the retention schedule named in your engagement letter.
8. Security
TLS 1.3 in transit. AES-256 at rest. Per-tenant scoping on every request, every tool call, every webhook. Vulnerability reports go to security@mycelium-ai.co; we follow the coordinated disclosure timeline at /security.
9. Changes
We update this policy when our subprocessor list, retention defaults, or runtime shape change in a way that affects you. Material changes are surfaced in the footer and notified by email to active pilot customers no less than thirty days before they take effect.
10. Contact
Privacy questions: privacy@mycelium-ai.co. General contact: contact@mycelium-ai.co.
Mycelium · founded 2026