What Management OS does with your Apollo data.

Management OS reads account, contact, and engagement data from your Apollo workspace via the Apollo REST API — specifically: account records, contact and people records, sequence enrollment and email activity (opens, clicks, replies — not body content), opportunity records, and user/team membership. We do not access raw email bodies, billing data, credit usage, ad-spend data, or any Apollo data not explicitly listed below.

Why: Apollo is one of the highest-coverage sources for buyer firmographics, contact accuracy, and outbound engagement telemetry. Management OS reads that data so Account Plans reflect real buying-committee shape, and so the Brief surfaces actual outbound coverage rather than what the CRM stage label implies.

We do not write to your Apollo workspace. Management OS is a read-only consumer of your Apollo data. We do not create, modify, or delete any Apollo records — no accounts, no contacts, no sequences, no opportunities, no notes, no enrollments, no email sends.

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 Apollo workspace.

Apollo uses a single per-user API key rather than granular OAuth scopes. The key inherits the permissions of the user who generated it. When you connect, Management OS uses the key only for the read operations below; nothing else. We never call create, update, or delete endpoints.

Read-only operations we call

These are the only Apollo API endpoints Management OS calls. We do not call any write or admin endpoints.

When you generate the Apollo API key, select read-only permissions on the scopes Apollo lets you toggle — Management OS only needs read access. If your Apollo plan does not surface per-scope toggles, the key inherits your user's read permissions, which is sufficient.

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.

API key: Stored in the same Supabase database under workspace-scoped RLS. The key is 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). Account, contact, and engagement data required for a specific brief 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 Apollo-sourced data while your subscription is active. On disconnect we delete the API key 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 in to Apollo at app.apollo.io
2. Open Settings → Integrations → API (path may vary by plan)
3. Click Create New Key, name it "Management OS", select read-only scopes, and copy the key — Apollo shows it once
4. In Management OS, open Settings → Integrations and find Apollo in the integration directory
5. Click Connect Apollo, paste the API key, and submit. Management OS validates the key with a live call before saving
6. On success, the initial account and contact sync starts immediately and typically completes within 5-15 minutes depending on workspace size; full-history backfill continues in the background

If you administer Apollo on behalf of a team: The API key inherits the permissions of the user who generated it. For workspace-wide coverage, generate the key under a user with workspace admin permissions in Apollo.

The Weekly Intelligence Brief is the primary surface. Three pillars synthesize your Apollo data alongside your CRM and meeting data:

• Develop Your Business — deal scoring with buying-committee coverage from Apollo, Account Plan enrichment with firmographics, champion-behavior alerts on contacts whose engagement drops, outbound-cadence reads at the account level
• Develop Your Team — coaching priorities tied to specific reps and deals, outbound activity vs. quota coverage from Apollo sequence data, rep-effectiveness rankings on actual engagement, not CRM activity hygiene
• Develop Yourself — leader focus, calendar audit, ninety-day competency focus, decision deadlines you're sitting on

Ask Anything (AMA) — a conversational surface where you can query your Apollo data in plain English. Examples: "Which accounts have zero outbound activity in the last 14 days?", "Show me deals where the champion stopped opening emails", "Who on the buying committee at Acme have we never reached?"

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

On disconnect we immediately delete the stored API key and stop reading any new Apollo data. Previously synthesized briefs and plans 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 Apollo at app.apollo.io
2. Open Settings → Integrations → API
3. Find the API key issued to Management OS in the keys list
4. Click Revoke (or Regenerate, which invalidates the prior key)

Revoking from Apollo's side invalidates the key 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.