Meeting notes and privacy
Olympus can connect Fathom, Granola, Fireflies.ai, and Otter.ai to add call knowledge to the matching CRM opportunity. Availability depends on your provider plan and an Olympus activation review. A visible provider card does not mean imports are enabled.Before an import starts
A workspace administrator must connect the provider and approve the meeting intelligence policy. The policy records the approved processing regions, model subprocessors, training restriction, and retention limit. Olympus checks bounded meeting metadata first. It can use booking, calendar, conference, participant, and meeting-time evidence to find the right CRM record. Transcript and note content is not fetched for internal-only or unrelated meetings. When the match is uncertain, the meeting stays out of an opportunity until an authorized user reviews it.What Olympus stores
For an admitted meeting, Olympus can store:- the provider, title, meeting time, and approved source link;
- participant names and email addresses used for CRM matching;
- a summary, decisions, and action items; and
- timestamped transcript segments when the provider returns them.
Where meeting notes appear
Imported call knowledge appears in the Meetings tab for the opportunity it is attached to. Olympus does not create a separate organization-wide transcript archive. The opportunity list shows bounded summaries, decisions, and action items. A transcript is loaded in small pages only after the user opens an attached meeting. Moving or unlinking a meeting removes that content from the old opportunity. Transcript access is recorded without copying transcript text into the access log. The Olympus Agent can read the same bounded opportunity meeting summary when it reads that opportunity. It does not receive an organization-wide transcript collection, provider credentials, or webhook data.Retention and deletion
The default meeting-content retention period is 365 days. Your organization’s policy can set a period from 30 days to seven years. Delivery hints follow the organization’s raw provider-data period, which defaults to 30 days. Metadata for a meeting that never becomes eligible is removed after no more than 30 days. At expiry, Olympus removes readable summaries, decisions, actions, participant details, source links, and transcript text while keeping content-free identifiers needed for audit and replay protection. Disconnecting a provider stops new imports but keeps meeting knowledge already attached to opportunities. Disconnect is not a deletion request. An authorized contact-erasure request also scrubs matching meeting content and opportunity intelligence. Olympus records a one-way tombstone so a later provider replay does not restore the erased meeting. Some cleanup runs asynchronously. The request is complete only after those cleanup jobs have succeeded. There is no self-service meeting-erasure control today. Contact your workspace privacy administrator for an authorized request.Access and account coverage
Meeting connections belong to an Olympus organization. Provider coverage depends on the connected account and plan:
Only users with CRM access can read attached meeting notes. Workspace administrators manage provider credentials, imports, and the capture policy.