Fathom

fathom.videounclaimedrecord 562 · read 2026-10-13 · rules/v1evidence pack ↗
Does your organization use Fathom? One sensor, and Openwake watches it on its own: the documents re-read daily, every moved clause told.Start free
Trains on customer data
Training posture: does not train
for the product and account type the quoted document covers
“We do not authorize third parties (e.g., OpenAI, Anthropic, Google, etc) to use your personal information or Meeting Content Information to train their artificial intelligence models;”
privacy policysource ↗confidence 0.60
Opt-out mechanism
none described
Not stated in the documents we could read. An absence here is an unknown, not a no.
AI features
present
“* Based on how you configure your account settings, we may use and create de-identified data generated from Meeting Content Information to improve our Service by training, improving, and customizing our in-house artificial intelligence models.”
privacy policysource ↗confidence 0.55
Model providers named
none named
Not stated in the documents we could read. An absence here is an unknown, not a no.
Retention
30 days
“If we receive an account deletion request, we will use commercially reasonable efforts to delete your recordings and personal information within 30 days of your account deletion request, although we cannot guarantee that deletion will always occur within this timeframe.”
privacy policysource ↗confidence 0.50
Hosting regions
United States
“Our Service are hosted in the United States and intended for visitors located within the United States.”
privacy policysource ↗confidence 0.50
Subprocessor notice
30 days
“Customer has 30 days after notice of a change to the Approved Subprocessors to object, otherwise Customer will be deemed to accept the changes.”
dpasource ↗confidence 0.55

Downstream

Who's behind Fathom, as listed in its own subprocessor documents. 1 subprocessor.

Model providers

  • none listed

Hyperscalers

  • none listed

Other subprocessors

  • Zoomunstated

Reviewer notes

Extracted by deterministic rules (rules/v1), no language model. Coverage is limited to recognisable clauses and a gazetteer of common subprocessors; absent values mean 'not matched', not 'not present'.

Documents read

Document changes

Fact changes

No changes recorded yet. Changes appear here when a later reading differs from an earlier one.

Corrections

No correction requests. Anyone may dispute a fact with a source; requests and resolutions are public and ledger-entered.

Facts are as stated in Fathom's public documents on the date read. This is a record, not legal advice. Work for Fathom? Claim this profile · Something wrong? Request a correction.