Privacy Policy

Commune is an AI-native collaborative workspace operated by Commune AI. Our product lives at getcommuneai.com. This policy describes what data we collect when you use Commune, why we collect it, who we share it with, and how you can ask us to delete it.

Questions, requests, or data-deletion notices can go to privacy@getcommuneai.com.

We collect data in three buckets, each tied to a specific reason:

1. Account data

When you sign up we collect your name, email, profile photo, and (where applicable) the workspace and team membership you choose. We use this to identify you, authenticate sessions, and show your avatar to your teammates.

2. Workspace content

Messages you post, tasks you create, knowledge-base documents you upload, decisions you log, and chip outputs are stored as part of your workspace. They are visible to the people you share the workspace with, not to anyone else.

3. Connected-tool data

When you connect a third-party tool to your workspace (Meta / Facebook, Google Drive, Gmail, HubSpot, Stripe, Notion, Linear, and others as they become available), Commune reads data from that tool on your behalf so AI agents and chips can use it in your reports and answers. We only read what the OAuth scopes you grant allow, and only when a workspace member explicitly triggers an action that needs it (clicking a chip, asking the AI a question, or running a scheduled workflow).

Examples by integration:

• Meta (Facebook + Instagram): Pages you manage, post and ad insights, ad-account performance metrics, basic audience demographics, and (with explicit consent) content you publish on your behalf.
• Google (Gmail, Drive): When a member connects their Google account, Commune requests the following OAuth scopes and uses them only for the purposes listed:
  • https://www.googleapis.com/auth/gmail.readonly — read messages and threads on demand so the workspace's AI agent can summarise, search, or pull context from the member's inbox when they ask a question that needs it.
  • https://www.googleapis.com/auth/gmail.compose — create draft replies in the member's Gmail Drafts folder when the member asks the AI to draft an email. Google's consent screen describes this scope as "Manage drafts and send emails" because the scope technically grants both capabilities. Commune's product code only calls the create-draftendpoint — we do not call the send endpoint from any code path, and we do not request the separate gmail.send scope. Drafts sit in the member's Drafts folder until they open Gmail and send them manually.
  • https://www.googleapis.com/auth/drive.metadata.readonly — list the names, types, and modified times of files in the member's Drive so the AI can discover and propose candidate documents to ground its answers in. This scope does not grant access to file contents.
  • https://www.googleapis.com/auth/drive.file — read the contents of files the member has explicitly picked via the Drive Picker UI. Per Google's scope definition, this grants Commune access only to the specific files the user chose — not the rest of their Drive. Commune does not modify, delete, share, or change permissions on any file.
  Data is fetched per-request, used to produce the user-facing response, and not persisted beyond short-lived caches needed to serve the request.
• Stripe: Customer, payment, and subscription data for the connected account, used in revenue-related reports.
• Other integrations (HubSpot, Notion, Linear, Asana, Intercom, Figma, GitHub, TikTok, Zoho CRM, Xero, LinkedIn): the same principle — read what the OAuth scopes allow, only when triggered.

Connected-tool data is used to:

• Render reports and answers inside your workspace.
• Provide your workspace's AI agents with the context they need to answer questions and run chips you configured.
• Log auditable history of which workspace member triggered which action, so admins can review usage.

We do not use your data to train any AI model, sell to advertisers, share with data brokers, or surface to anyone outside your workspace.

Commune's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain English, that means:

• We only use Google user data to provide or improve user-facing features that are visible inside Commune — specifically: AI answers, drafts, and summaries the requesting user explicitly asked for.
• We do not transfer Google user data to third parties except (i) as needed to provide those user-facing features (e.g. sending the relevant snippet to our AI inference provider to produce the answer the user requested), (ii) for security purposes, (iii) to comply with applicable law, or (iv) as part of a merger, acquisition, or sale of assets — and only with the user's prior notice.
• We do not allow humans to read Google user data except (a) with the user's explicit consent for specific messages or files, (b) where necessary for security purposes (such as investigating abuse), (c) to comply with applicable law, or (d) where the data is aggregated and used for internal operations in accordance with the Limited Use policy.
• We do not use Google user data to train, develop, or improve generalised or non-personalised AI/ML models. The AI providers we call (Anthropic, OpenAI) operate under zero-retention API terms — they do not store or train on the content of our API requests.
• We do not use Google user data for advertising of any kind, and we do not use it to determine creditworthiness or for lending purposes.

Workspace members can disconnect Google at any time from Settings → AI Tools or the /connections page. Disconnecting immediately revokes Commune's OAuth token; any cached query results expire from the workspace within 7 days. Members can also revoke Commune's access directly from their Google Account permissions page.

Commune deliberately uses Google's narrow Drive scopes rather than full-Drive read access. This means the member stays in control of which specific files Commune can read.

• drive.metadata.readonly (Sensitive) lets the AI see file names and metadata across the member's Drive so it can propose "you have these candidate documents — pick which to include." It does not read content.
• drive.file (Non-sensitive) reads contents only for files the member explicitly picked through Google's Drive Picker UI. The user chooses once; their selection is persisted on the connection so the AI can re-read those files for follow-up questions.
• We do not request drive, drive.readonly, drive.metadata (read-write), or any other Drive write scope. We never create, modify, delete, rename, share, move, or change permissions on any Drive file.
• Per-request, not synced. File contents are fetched at the moment the AI needs them. We do not maintain a mirror, index, or background cache of any user's Drive. Short-lived caches needed to serve a single response are evicted within minutes.
• Content stays inside the workspace. Text from picked files is sent to the AI inference provider (Anthropic / OpenAI) under zero-retention API terms solely to produce the answer the user asked for, then returned to the requesting user inside Commune. It is not surfaced to other workspaces, not used for training, not used for advertising, not sold, and not shared with anyone outside the requesting user's workspace.
• No human reading. Commune employees do not read Drive content. Production access is logged and limited to security/abuse investigations and compliance with applicable law, in line with the Limited Use disclosure above.

Data is stored in PostgreSQL databases managed by Supabase (hosted in AWS regions in the US) and in Google Cloud Run service instances in the US. OAuth tokens for connected tools are encrypted at rest with workspace-scoped keys. All transit is over TLS.

Access inside Commune is role-gated:

• Workspace owners and admins can manage all settings + connections.
• Members can only see content from groups and projects they belong to (enforced at the database row-security level).
• Commune staff access to production is logged, limited to debug and support, and never used for marketing or training purposes.

We use the following third-party AI providers to process your requests:

• Anthropic (Claude models) — for AI agent responses and chip executions.
• OpenAI — for occasional embeddings and certain cost-optimised fallback tasks.

Both Anthropic and OpenAI process API calls under zero-retention terms for our API plan: they do not store the content of API requests beyond what is needed to return the response, and they do not use API content to train their models.

We use first-party cookies for session authentication. We use PostHog to analyse product usage at a workspace level (anonymised event counts, never the content of your messages or documents). Workspaces can opt out of analytics in workspace settings.

We do not use third-party advertising trackers. There are no Facebook Pixel, Google Ads, or similar advertising cookies in the app surface.

You can:

• Disconnect a third-party integration at any time from Settings → AI Tools or the /connectionspage. We immediately revoke the OAuth token and stop pulling data; cached query results expire from the workspace within 7 days.
• Delete your account by emailing privacy@getcommuneai.com — we remove your personal data within 30 days. If you are the sole owner of a workspace, deleting your account also deletes the workspace and its content.
• Request a copy of your data — same email; we respond within 30 days.

For European users, you have the GDPR rights of access, rectification, erasure, restriction, portability, and objection. Exercise them through the same address.

Commune is built for business teams and is not directed at children under 16. We do not knowingly collect data from anyone under 16. If you believe we have, please contact us and we will delete it.

We update this page when our data practices change. The "Last updated" date at the top reflects the most recent revision. Material changes are also announced inside the app and via email to workspace owners.

Privacy questions, deletion requests, or anything related to this policy: privacy@getcommuneai.com.