What Management OS does with your Fathom data.

Management OS reads meeting data from your Fathom workspace — specifically: meeting metadata (title, attendees, host, timestamp, duration), Fathom's AI-generated meeting summaries, and full meeting transcripts. We do not access raw audio or video files, account billing data, team admin settings, or any Fathom data not explicitly listed in the scope table below.

Why: Meeting transcripts are the highest-signal source on a revenue team — what the champion actually said, what the buyer actually objected to, what the rep actually committed. Management OS reads those transcripts so Account Plans, Coaching Briefs, and the Weekly Brief reflect the real conversation rather than CRM stage labels.

We do not write to your Fathom workspace. Management OS is a read-only consumer of your Fathom data. We do not create, modify, or delete any Fathom records — no meetings, no summaries, no transcripts, no tags, no comments, no shares.

All Management OS outputs (Account Plans, Coaching Briefs, Meeting Prep dossiers, Weekly Briefs) are generated and stored in Management OS's own database and surfaced through the Management OS application — not pushed back into your Fathom workspace.

Every scope below maps to a specific feature. We requested the minimum scope set needed to deliver the Management OS feature surface; we did not request scopes that we don't currently use.

Required scopes (3)

These scopes are requested on every connection. Without them, the core Management OS feature surface does not function.

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. 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). Transcript and summary data required for a specific brief or dossier generation is passed to Anthropic; 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 Fathom-sourced data while your subscription is active. On disconnect we delete OAuth tokens immediately. 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 Fathom in the integration directory and click Connect Fathom
4. You'll be redirected to Fathom's authorization screen. Sign in with the Fathom account whose recordings you want Management OS to read
5. Review the requested scopes and click Allow
6. You'll return to Management OS with a confirmation that the integration is connected. The initial meeting sync starts immediately and typically completes within 2-5 minutes for recent meetings; full-history backfill continues in the background

If you administer Fathom on behalf of a team: Each rep's recordings are tied to their individual Fathom account. For team-wide coverage, each rep connects their own Fathom account to their Management OS user, or a workspace admin connects a shared Fathom account that has access to all team recordings.

Fathom transcripts feed three primary Management OS surfaces:

• Meeting Prep dossiers — before your next call with an account, Management OS pulls every prior Fathom transcript on that account, surfaces the open commitments, the unresolved objections, the champion language, and the next-step laddering — so you walk into the room with peer-operator context, not a CRM summary
• Coaching Briefs — managers see GROW-structured coaching prep based on what actually happened in the rep's recent calls. Discovery depth, objection handling, multi-thread coverage, next-step clarity — all scored from real transcripts against the 17 sales competencies
• Account Plan updates — every transcript on an account auto-updates the Strategic Account Plan across the 8 canonical dimensions (relationship, Porter, buying committee, value, risks, next plays). The plan reflects the latest conversation, not last quarter's snapshot

The Weekly Intelligence Brief synthesizes across all three with the three pillars — Develop Your Business (deals and accounts), Develop Your Team (coaching priorities), Develop Yourself (leader focus). Ask Anything (AMA) lets you query transcripts in plain English: "What did the Acme CFO say about budget timing on the last call?", "Which deals have no champion activity in the last 14 days of recorded meetings?"

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

On disconnect we immediately delete the stored OAuth tokens and stop reading any new meeting data. Previously synthesized briefs and dossiers 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 data after disconnect, email privacy@mgmt-os.ai with your workspace identifier. We process deletion requests within 30 days.

1. Sign in to Fathom at fathom.video
2. Open Settings → Integrations
3. Find Management OS in the list of connected apps
4. Click Disconnect or Revoke access

Revoking from Fathom's side invalidates our tokens immediately. Our next API call returns 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.