What Management OS does with your Google Workspace data.

Management OS reads across the Google Workspace surface the leader has authorized:

• Calendar — events, attendees, descriptions, and embedded Meet links across primary and shared calendars the account can see
• Gmail — message bodies, headers, threads, and labels for inbound and outbound mail. Used for buyer-signal extraction (champion language, intent inflections, inbound replies on open deals), board-thread surfacing, and follow-up tracking
• Drive (incl. Docs and Sheets) — files and folders the user has access to, including shared-with-me. Docs and Sheets are Drive-native, so the same scope covers both. Used as context for AI-generated outputs via the File Source Picker
• Meet — space metadata (recordings and transcripts availability per meeting). Recording or transcript content is only retrieved when the leader opts in per-meeting
• Account email — the address of the authorizing user, so Settings can display which account is connected

Google Contacts is listed in the integration catalog and the contacts scope is planned for the next Google connection refresh — it is not in the current scope set. We will not silently widen the scope set: existing users will see a re-consent prompt when that scope ships.

Management OS does not modify, delete, or send anything in your Google account. We do not send email, edit calendar events, modify Docs or Sheets you own, or change file permissions.

One narrow write surface: the drive.file scope allows Management OS to create files in your Drive — only files Management OS itself creates. This is the OAuth-enforced "app-created" restriction Google defines: with drive.file, we can write a new Google Doc when you export an Account Plan, but we cannot read, modify, or delete a Doc you already owned that we did not create.

All six scopes below are requested on a single consent screen. Removing any one disables the corresponding feature surface but does not break the rest. The scope set is defined in lib/google/oauth.ts → GOOGLE_SCOPES.

Application database: Supabase Postgres (Management OS's production database, US East). Encrypted at rest (AES-256), encrypted in transit (TLS 1.3). Workspace-scoped row-level security (RLS) means one customer's data is never visible to another.

OAuth tokens: Stored in the same Supabase database under workspace-scoped RLS. Access tokens are refreshable; refresh tokens are encrypted at rest and never returned to client browsers. Only the Management OS server-side runtime has access via service-role credentials.

Inference layer: Anthropic API (Claude models). Google data required for a specific brief or output is passed to Anthropic at inference time; outputs are returned to Management OS and stored in our database. Anthropic does not train on customer data per their API terms.

Retention: We retain Google-sourced data while your subscription is active. On disconnect we delete OAuth tokens immediately and stop reading any new Google data. On subscription cancellation, customer data is retained for 30 days for restoration, then permanently deleted. Data subject deletion requests are honored within 30 days per our Privacy Policy.

1. Sign up at mgmt-os.ai and complete onboarding to your workspace
2. Open Management OS → Settings → Integrations
3. Find Google in the integration directory and click Connect Google
4. You'll be redirected to Google's consent screen. Sign in with the Google account you want Management OS to read from
5. Review the requested scopes — the consent screen lists each one. Click Continue → Allow
6. You'll return to Management OS with a confirmation. The initial sync (calendar window + recent mail) starts immediately and typically completes within a few minutes

Workspace admin notes: if your Google Workspace administrator has restricted third-party OAuth apps, your admin may need to allow Management OS in the Google Admin Console (Security → API Controls → App access control) before consent succeeds. Until gmail.readonly clears Google's CASA review, only users on our Test Users list can authorize the Gmail portion of the connection.

The Weekly Intelligence Brief is the primary surface. Three pillars synthesize your Google data:

• Develop Your Business — buyer-intent signals from inbound mail, champion behavior shifts across deal threads, calendar coverage on priority accounts, follow-up gaps after key meetings
• Develop Your Team — rep activity patterns surfaced from Gmail + Calendar, coaching context from meeting recordings (when opted in), 1:1 prep anchored on real upcoming events
• Develop Yourself — calendar audit (how time is actually spent vs. intended), leader focus, decision deadlines surfaced from threads you're sitting on

Ask Anything (AMA) — a conversational surface where you can query your Google data in plain English. Examples: "Show me every inbound reply this week from any deal over $50K", "Which customer threads have gone quiet for 14+ days?", "Summarize what my calendar says about Q4 prep so far."

Universal File Source Picker: Drive (and Docs and Sheets, which are Drive-native) feeds the universal picker that selects context for AI-generated outputs — Account Plans, Pitch Decks, Coaching Briefs, Meeting Prep dossiers. Files you pick become context; files you don't, don't.

1. Open Management OS → Settings → Integrations
2. Find Google in the connected integrations list
3. Click Disconnect → confirm

On disconnect we revoke the access token at Google (best-effort), delete the stored OAuth tokens immediately, and stop reading any new Google data. Previously synthesized briefs and outputs remain in your Management OS workspace as historical records — they are not deleted automatically because they may contain decisions and context the leader still references.

To remove all historical briefs and Google-sourced data after disconnect, email privacy@mgmt-os.ai with your workspace identifier. We process deletion requests within 30 days.

1. Sign in to myaccount.google.com with the Google account that authorized Management OS
2. Open Security in the left navigation
3. Scroll to Your connections to third-party apps and services and click See all connections
4. Find Management OS in the list and click into it
5. Click Delete all connections you have with Management OS (Google renames this button periodically — the equivalent phrasing is "Remove access")

Revoking from Google's side invalidates our tokens immediately. Our next API call returns a 401 and we surface a re-connection prompt in Management OS Settings.

Security incident reporting: security@mgmt-os.ai
Privacy / data subject requests: privacy@mgmt-os.ai
Integration support: support@mgmt-os.ai

For general questions about Management OS, see our Support page or Manifesto.