last updated: april 3, 2026
codefmt is designed to be privacy-first. this policy covers both the website at codefmt.dev and the codefmt browser extension for chrome and firefox.
what we collect
code content — when you format code using the browser extension, your code is sent to codefmt.dev/api/format for processing. code is processed in memory, never written to disk, and never stored or logged. the response is returned immediately and the code is discarded.
website formatting — when you format code on codefmt.dev, formatting runs entirely in your browser via webassembly. your code never leaves your device. javascript lint diagnostics are processed server-side using the same in-memory, no-storage approach.
settings — your formatting preferences are stored in your browser's localStorage. the browser extension can read these settings via the sync feature. no settings data is sent to any server.
what we don't collect
third-party services
vercel — hosts the website and api. vercel collects anonymous, aggregated analytics (page views, web vitals) with no personal identifiers. see vercel's privacy policy.
sentry — monitors application errors on the website. sentry receives error stack traces and browser metadata. no user code content is sent to sentry. see sentry's privacy policy.
browser extension
the codefmt browser extension (chrome and firefox) operates only on supported automation platform websites: zapier, n8n, pipedream, make, and hubspot.
the extension reads code from the platform's editor, sends it to codefmt.dev/api/format for formatting, and writes the formatted result back to the editor. the same no-storage policy applies — code is processed in memory and immediately discarded.
the extension stores your formatting preferences locally using chrome.storage.local (or the firefox equivalent). this data never leaves your browser.
contact
questions about this policy? reach out at josh@codefmt.dev.