HAR File Safety Guide
A practical guide to understanding, collecting, sanitizing, and sharing HAR files without creating unnecessary data risk.
Start guideField Notes
Practical guides for meeting workflows and browser troubleshooting.
Useful, technical notes for support engineers, customer success teams, sales engineers, and founders who need cleaner follow-up and safer support evidence.
Fathom Workflow Guide
A practical guide to reviewing Fathom notes, action items, transcripts, exports, and customer follow-up workflows.
Start guideWhat is a HAR file? A support engineer's guide
Understand what HAR files contain, why support teams request them, and what to check before sharing one.
Read articleWhat can a HAR file expose? Cookies, tokens, payloads, and URLs explained
Learn what sensitive data a HAR file can expose, including URLs, cookies, tokens, request bodies, response bodies, and account identifiers.
Read articleHAR file vs console log: which one should support ask for?
Understand when support teams should request a HAR file, console log, screenshot, or both for browser troubleshooting.
Read articleHow to sanitize a HAR file before sharing
Learn what to remove from HAR files before sending browser troubleshooting evidence to a vendor or support team.
Read articleHow to redact screenshots before sending them to SaaS support
A practical checklist for safely redacting screenshots before sharing UI errors, browser issues, and support evidence with SaaS vendors.
Read articleBrowser troubleshooting evidence checklist for SaaS support teams
A practical browser troubleshooting evidence checklist for SaaS support teams collecting screenshots, HAR files, console logs, timestamps, and reproduction steps.
Read articleHow to ask customers for logs without creating a data leak
A customer-safe support workflow for requesting logs, HAR files, screenshots, and troubleshooting evidence without overcollecting sensitive data.
Read articleChrome DevTools Network tab: a support engineer's practical guide
A practical support-engineer guide to using the Chrome DevTools Network tab for browser troubleshooting, HAR capture, status codes, timing, and redirects.
Read articleIs this Chrome extension safe? A practical checklist
A practical checklist for reviewing Chrome extension permissions, publisher trust, privacy policy language, updates, and data-access red flags.
Read articleHow to turn Fathom meeting notes into follow-up
Turn Fathom notes into reviewed action items, emails, and next steps without losing context after customer calls.
Read articleFathom action items checklist: what to review before sending follow-up
A practical checklist for reviewing Fathom action items before sending customer follow-up, updating tickets, or exporting meeting records.
Read articleHow to turn Fathom notes into a customer follow-up email
A practical workflow and template for turning Fathom notes into a concise, reviewed customer follow-up email.
Read articleHow to export and organize Fathom notes
A practical workflow for exporting Fathom transcripts, summaries, highlights, and action items into usable records.
Read articleFathom API key safety: what teams should know before exporting meetings
A practical guide to Fathom API key safety, access scope, storage, rotation, and meeting export workflows.
Read articleHow to safely collect a HAR file in Chrome
Step-by-step guidance for capturing a useful HAR file while reducing privacy and troubleshooting mistakes.
Read articleHow to turn Fathom transcripts into action items
Learn how technical teams can review Fathom transcripts and convert messy meeting output into owned next steps.
Read article10 common HAR file mistakes support teams see
Avoid incomplete captures, missing auth context, oversized files, and unsafe sharing when collecting HAR evidence.
Read articleHow to turn Fathom notes into tickets, docs, and checklists
A support-engineer workflow for turning Fathom meeting notes into tickets, docs, checklists, and customer follow-up.
Read articleHow to build a customer-safe HAR collection workflow
A repeatable SaaS support workflow for asking customers for HAR files without creating unnecessary data risk.
Read articleHow technical teams should use Fathom for follow-up
Practical Fathom workflows for support, sales engineering, customer success, and implementation teams.
Read articleWhat Manifest V3 means for privacy-conscious Chrome apps
A plain-English guide to how Manifest V3 affects Chrome app permissions, background behavior, data access, and privacy expectations.
Read articleLocal-first Chrome apps: what it means and why it matters
A practical explanation of local-first Chrome apps, browser-based processing, privacy tradeoffs, permissions, exports, and when server-side processing is still needed.
Read articleNo matching field notes yet.