Summary
Koda Sidecar Chrome apps are designed to keep sensitive workflow data local whenever
possible. Fathom Action Items & Exporter processes meeting exports in Chrome.
Redaction Retriever processes HAR files, console logs, text logs, screenshots, and
support bundle exports locally in the user's browser.
Extension access
Data requested from Fathom
With a user-provided Fathom API key, the extension may request meeting titles, dates,
recorder identity, invitee names and emails, structured action items, completion
status, assigned owners, Fathom meeting links, summaries, transcripts, and highlights.
Transcripts, summaries, and highlights are requested only when the user selects export
or filtering options that need them.
Redaction Retriever
Support evidence processed locally
Redaction Retriever may process user-selected HAR files, console logs, text logs,
screenshots, reproduction notes, and custom redaction terms. These files are scanned
and bundled locally in Chrome and are not uploaded to Koda Sidecar servers.
Local storage
Data stored in Chrome
The extension stores the user's Fathom API key, team preferences, email defaults,
saved owners, reviewed action items, processed meeting references, hidden meeting IDs,
trial count, license status, and Redaction Retriever export count in Chrome extension
storage.
Use
What Koda Sidecar does not do
Koda Sidecar does not sell user data, use meeting data for advertising, train AI
models on meeting data or support evidence, receive meeting content or support
evidence on Koda Sidecar servers, or send email automatically.
Deletion
Retention and control
Local settings remain until the user removes the extension, clears extension storage,
or uses the extension's delete-data controls. Stripe and Fathom retain data according
to their own policies.
Contact
Privacy questions can be sent to
jeff@kodasidecar.com. Users should not send
API keys, license keys, confidential meeting content, raw HAR files, logs, or
screenshots in support requests.