What Management OS does with your Gong data.

Management OS reads call data from your Gong tenant: call metadata, transcripts and interaction statistics. It does not read Gong scorecards, coaching activity, trackers, library folders or Engage flows.

Why: Management OS is the leadership execution layer above the revenue stack. We synthesize call data into a Weekly Intelligence Brief that develops the leader, their team, and their business. We can't synthesize what we can't read.

We write one thing to your Gong tenant: a CALL_ENDED webhook subscription, registered on connect with api:integration-settings:write and deleted when you disconnect. It lets new calls flow into Management OS without manual configuration.

We do not create calls, modify meetings, change permission profiles, send activity or engagement events to Gong, upload CRM data through Gong, or write anything else.

These are the only scopes Management OS requests when you connect Gong. Each maps to a feature you can see. If a future feature needs another scope, this page will list it before the feature ships.

Application database: Supabase Postgres (Mgmt 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). Transcripts and metadata required for a specific brief generation are 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 Gong-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. Open Management OS → Settings → Integrations
2. Find Gong in the connected integrations list
3. Click Disconnect → confirm

On disconnect we immediately: delete the stored OAuth tokens, unregister the CALL_ENDED webhook subscription on Gong's side, and stop reading any new call data. Previously synthesized briefs remain in your Management OS workspace as historical records.

1. Sign in to Gong as an administrator
2. Open Admin Center → API → Integrations
3. Find Management OS in the connected integrations list
4. Click Revoke access

Revoking from Gong'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