What Management OS does with your Calendly data.

• User and organization profile — your Calendly user URI and current organization URI, fetched via GET /users/me on connect to validate the token and scope the webhook
• Invitee detail on webhook fire — when invitee.created or invitee.canceled fires, we fetch the invitee resource: name, email, scheduling-page questions and answers, event type name, start and end times
• Scheduled event metadata — the event resource linked from the invitee record (event type, scheduling page URL) for context in the normalized signal

We do not poll your Calendly account. We only call the Calendly API when a webhook arrives. No historical backfill, no event-type discovery, no invitee history dumps.

Management OS does not write to your Calendly account. We do not create or modify event types, scheduling pages, event memberships, organization settings, or bookings. We do not create bookings on anyone's behalf.

The single Calendly write surface we touch is webhook subscription management — we create one webhook subscription on connect (scoped to your organization, for the two event types listed above) and delete it on disconnect. We do not create any other Calendly objects.

All Management OS outputs (Account Plans, Coaching Briefs, Forecast Locks, Meeting Prep dossiers, Pitch Decks) are generated and stored inside Management OS's own database and surfaced through the Management OS application — never written into your Calendly account.

Calendly uses Personal Access Token (PAT) authentication rather than OAuth scope grants. A PAT inherits the permissions of the user who created it — there is no per-permission consent screen. The list below documents the API endpoints Management OS actually calls and what they're used for, so the leader can audit token activity against this disclosure.

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.

PAT and webhook signing key: Stored in Supabase under workspace-scoped RLS, encrypted at rest, and never returned to client browsers. Only the Management OS server-side runtime can read them. PATs do not expire automatically — if you suspect compromise, the fastest path to invalidation is generating a new PAT in Calendly (which invalidates the old one) and updating the Management OS Settings field.

Inference layer: Anthropic API (Claude models). Normalized Calendly signals are passed to Anthropic at inference time when the Brief or AMA needs them; 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 normalized Calendly signals while your subscription is active. On disconnect we delete the stored PAT and the webhook signing key immediately, and we delete the webhook subscription at Calendly. 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. In Calendly, open Integrations & apps → API & webhooks → Personal access tokens and click Create new token
3. Name the token Management OS (or anything memorable), generate it, and copy the value — Calendly only shows it once
4. Open Management OS → Settings → Integrations → Calendly → Connect
5. Paste the PAT into the field and click Connect Calendly
6. Management OS validates the token, captures your organization URI, and registers the webhook subscription. From this point, every booking and cancellation in your organization fires a webhook into Management OS and surfaces as a signal in the Brief

Calendly bookings and cancellations land in the Weekly Intelligence Brief through the three-pillar structure:

• Develop Your Business — every new booking is a high-intent inbound signal, surfaced as a SEV.2 signal with the recommended action of prompt AE outreach. The Brief shows new bookings per rep, by day, with the scheduling-form responses for context
• Develop Your Team — repeated cancellations on a rep's calendar become a coaching signal (SEV.1) surfaced to the manager, with the recommended action of follow-up review
• Develop Yourself — for leaders carrying their own pipeline, the same signals surface in the leader's personal view

Ask Anything (AMA) — you can query Calendly signal history in plain English: "how many Calendly bookings did the team take this week, and how many cancelled?", "show me every booking from a @enterprise.com domain in the last 30 days."

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

On disconnect we delete the webhook subscription at Calendly (so no further webhooks fire) and delete the stored PAT plus webhook signing key immediately. Previously captured signals 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 Calendly-sourced signal data after disconnect, email privacy@mgmt-os.ai with your workspace identifier. We process deletion requests within 30 days.

1. Sign in to calendly.com → Integrations & apps → API & webhooks with the Calendly account that generated the PAT
2. Open Personal access tokens
3. Find the token you named for Management OS and click Delete → confirm

Deleting the PAT invalidates it immediately. Generating a new PAT does not automatically rotate the value Management OS holds — you would need to update the Management OS Settings field with the new PAT for the connection to keep working. The fastest path to full revocation is: delete the PAT in Calendly, then click Disconnect in Management OS Settings to clean up the stored row.

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.