What Management OS does with Apify.

Management OS invokes specific Apify Actors and reads their results. Each Actor produces structured data from a public source — job postings from Greenhouse / Lever / Workday / Indeed career pages, news articles from Google News and Hacker News, archived pages from the Wayback Machine, Glassdoor reviews. We do not read other users' datasets, account billing data, build logs unrelated to our invocations, or any Apify data not explicitly listed below.

Why: Structured public-source signal is leading-indicator fuel for the Weekly Brief — competitor hiring patterns, exec moves, pricing-page changes, ecosystem-conversation spikes. Apify gives us a reliable structured-scraping primitive so the Brief can act on what's actually happening on the open web, not just what shows up in CRM.

We do not write to your Apify account. Management OS only invokes Actors and reads their results. We do not modify Actor source code, change Actor settings, create or modify schedules, or change billing configuration in your Apify account.

All Management OS outputs (Weekly Briefs, competitive intel briefs, exec-move signals, account-plan updates) are generated and stored in Management OS's own database and surfaced through the Management OS application — not pushed back into your Apify account.

Apify uses a per-account API token rather than granular OAuth scopes. The token inherits the permissions of the account it belongs to. When you BYO-connect, Management OS uses the token only for the operations below; nothing else. We never modify Actors, schedules, or account settings.

Operations we call

These are the only Apify API operations Management OS calls. We do not call any account-modification or Actor-modification endpoints.

Actors we invoke

These are the canonical Apify Actors Management OS invokes. We swap Actors centrally when a better one ships, but the categories below are stable.

IP-protection discipline: outbound Actor inputs use generic parameter names that don't reveal our analytical lens. Apify Actor logs may capture inputs; we treat that as a public-disclosure surface and design accordingly.

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 token (BYO mode): When you connect your own Apify token, it's stored in the same Supabase database under workspace-scoped RLS. Encrypted at rest, never returned to client browsers. Only the Management OS server-side runtime has access via service-role credentials.

Default mode (master account): By default, Management OS runs Actors against the Mgmt OS master Apify account. No workspace-level credential is stored because none is needed. Per-workspace cost attribution lands when handlers wire in the cost telemetry tables.

Inference layer: Anthropic API (Claude models). Scraped result 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 Apify-sourced signal data while your subscription is active. On BYO disconnect we delete the API token 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.

Default — no install needed. By default, the Mgmt OS master Apify account runs every Actor on your workspace's behalf. You get the signal coverage without setting up an Apify account. Skip the rest of this section if the default works for you.

BYO — bring your own Apify token (for cost transparency, custom Actor allowlists, or enterprise security policy):

1. Sign in to Apify at console.apify.com
2. Open Settings → Integrations → API tokens
3. Click Create new token, name it "Management OS", and copy the token
4. In Management OS, open Settings → Integrations and find Apify in the integration directory
5. Click Connect Apify (BYO), paste the token, and submit. Management OS validates the token with a live /v2/users/me call before saving
6. On success, subsequent Actor invocations for your workspace use your token (and bill to your Apify account) instead of the Mgmt OS master

Apify-sourced signals feed the Weekly Intelligence Brief across all three pillars, with particular weight on the Business pillar competitive and ecosystem reads:

• Develop Your Business — competitor hiring patterns (Greenhouse / Lever / Workday), exec-move signals (Glassdoor + news), pricing-page changes (Wayback Machine diff), ecosystem-conversation spikes (Hacker News + Google News). Each signal carries recommended-action and human-owner so the Brief is directly executable
• Develop Your Team — competitive-coaching signals (e.g., competitor launches a feature your reps will face in deals next week), market-narrative shifts that change discovery questions
• Develop Yourself — leader-side awareness of market-context shifts that warrant strategic response rather than rep delegation

Ask Anything (AMA) — query Apify-sourced signals in plain English. Examples: "Which competitors hired VPs of Sales in the last 30 days?", "What changed on Acme's pricing page in the last quarter?", "Show me Hacker News threads mentioning our top three target accounts this month"

Default mode: No workspace-level credential is stored, so there is nothing to disconnect. Apify-sourced signals stop when you cancel your Management OS subscription.

BYO mode:

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

On BYO disconnect we immediately delete the stored API token and revert to the Mgmt OS master account for that workspace (or stop Apify signal flow entirely if the master is not configured). Previously synthesized briefs remain in your Management OS workspace as historical records.

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 Apify at console.apify.com
2. Open Settings → Integrations → API tokens
3. Find the token issued to Management OS in the tokens list
4. Click Revoke (or delete the token)

Revoking from Apify's side invalidates the token immediately. Our next Actor invocation returns an authentication error and we surface a re-connection prompt in Management OS Settings. The workspace falls back to the Mgmt OS master account if it's configured.

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.