Local cleaning stays in your browser.
Last updated: 11 October 2026
This site and Data Cleaning are operated by Loam, a product of Ship It! Software Limited.
Browser-local tool
In local mode, CSV parsing, profiling, cleaning, preview, and export happen in your browser. That mode does not upload file contents, filenames, columns, rows, or values to Loam or Claude.
Browser-local input handoff
Choosing a local file stores a temporary original input copy in this browser’s IndexedDB so the marketing page can open the app without another file selection. The copy may remain after this tab closes. It expires for app access after 30 minutes; physical cleanup runs on later app-entry use, rather than at a guaranteed deletion time. Clear this site’s browser data to remove retained local copies. When storage is unavailable, the handoff stays in memory for same-tab navigation. Edits, cleaning plans and temporary access stay in the open tab and are lost on reload or close. Download your result first. File contents and credentials are never placed in the URL.
Optional temporary workspace
Temporary mode uploads only after you press Upload to temporary Loam. The site Worker keeps its service-account key server-side and creates one private temporary dataset (a Namespace in the API). It returns a reveal-once token scoped to that exact dataset; the token remains only in page memory. Your browser sends file bytes directly to Loam's configured upload provider with the neutral server-side filename upload.csv, then calls the Loam regional API to import, inspect, and query the table. Loam therefore processes the uploaded bytes, generated table name, schema, and cleaning SQL. The dataset expires after 24 hours by default. Reloading or disconnecting loses access, and automatic expiry removes the dataset and its tables.
Privacy-preserving measurement
On the canonical site, we send pageviews and a small allowlist of fixed cleaning outcomes to PostHog through a same-origin Worker endpoint. Measurement uses a random session ID held only in memory for the current tab and does not create a person profile. We do not send cookies, identity, referrer, URL query, filename, columns, rows, values, plan, fuzzy candidates, SQL, or free-form errors. Analytics failures never block cleaning. Cloudflare processes ordinary network information, including IP and browser request data, to host, protect, and rate-limit the site.
Account and MCP sessions
Login with Loam creates an encrypted, HttpOnly, host-only session. Browser code receives only whether you are signed in plus an optional display name and account address. For MCP authorization, the Worker uses the delegated session server-side to show eligible workspace accounts and submit the access you approve; it does not expose Loam access or refresh tokens to browser code. Login is independent of a temporary dataset and cannot retain it.
Governed work
The dedicated Data Cleaning MCP bridge forwards only bounded protocol headers to its fixed resource server and strips product cookies. The MCP client receives only data allowed by the selected Loam account and approved object rules. Browser-local files never enter MCP, and saving a cleaned view creates a new governed object without replacing the source.