What Mycel is, and what it can see

Mycel is the substrate the collective builds on: agent memory, orchestration, and structured data. It lets an agent remember what happened last time, coordinate with other agents, and read the structured data a task actually needs. Built by 16x9, it connects your business tools, automates workflows, and delivers intelligent insights across your organization.

Framers get Mycel on day one. Here is exactly what it can and cannot see.

Does Mycel connect to Google on your behalf?

Yes, for a narrow purpose. When you sign in with Google, Mycel requests access to your identity and, if you are part of a Google Workspace organization, basic directory information about that organization. Specifically, Mycel requests the following scopes:

• userinfo.email and userinfo.profile, plus openid: your email address, name, and profile photo, used to identify you and sign you in.
• admin.directory.user.readonly: read-only access to basic user records in your Google Workspace directory, such as names and email addresses of people in your organization.
• admin.directory.customer.readonly: read-only access to basic information about your Google Workspace customer account.

Mycel does not access your Gmail, Google Calendar, Google Drive, or Google Chat, and never sends messages on your behalf. It does not read, send, or delete email, does not read or write calendar events, and does not read, upload, or modify files. If a future version of Mycel needs any of that, we will ask for a separate, explicit scope and update this page before it ships.

How the connection works

All connections use industry-standard OAuth 2.0 authentication. You are shown Google's own consent screen, listing the scopes above, before anything is granted. You can revoke Mycel's access to your Google account at any time at myaccount.google.com/permissions.

How data is used and stored

Identity and directory information obtained through Google sign-in is used to authenticate you, associate your activity with the correct organization inside Mycel, and let agents reference basic directory facts, such as who is on a team, when that is relevant to a task. This data is stored in Mycel's own database, separate from Google's systems, and is only visible to authorized members of your organization and to the 16x9 team operating Mycel on your behalf.

Mycel's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

For the full detail on retention, sharing, and your rights over this data, see the privacy policy.