Last updated: October 20, 2026
This Privacy Policy describes how Shipit Software LTD ("Company", "we", "us") collects, uses, discloses, and protects information when you visit or use CSV File Tools, its browser extension, the CSV Editor desktop and mobile apps, its CSV editor for Visual Studio Code, and its CSV editor for ChatGPT. It is incorporated into our Terms of Service.
Local browser workspace
The standalone browser CSV workspace processes selected files on your device. It may store parsed row chunks and edit history in IndexedDB and temporary download files in browser-managed private file storage. These local working copies are not sent to our server. Browser storage is subject to available space and can be removed when you clear this site's data.
Opening the app from a marketing page may keep your original file and task settings in IndexedDB for local refresh and resume. These handoffs expire after 30 minutes and are removed during subsequent handoff use; local copies can remain after the tab closes until cleanup or you clear this site's data. Back to website keeps the live editor mounted in the current tab. Refresh opens the original file, so download a copy to keep edits.
Local working storage is not a backup or a promise that edits survive a reload. Download a copy to keep your changes. The workspace removes its temporary storage when a document is closed normally; interrupted tabs or browser crashes can leave temporary data until cleanup or until you clear the site's data. Google-connected and embedded editors use their own file adapters as described below.
CSV to Parquet conversion
CSV to Parquet starts processing as soon as you choose or drop files, including files added with Add more files. The selected CSV files are sent to private processing storage to create downloadable Parquet results. Source files and results expire 24 hours after each conversion job starts, followed by physical cleanup. You can delete an individual job and its files sooner using Delete files.
The access details for these conversions stay in this tab's memory. Closing or reloading the tab loses access to the processing list and results, so keep it open until you have downloaded your files. This does not immediately delete server copies; their fixed expiry still applies. Downloaded files remain on your device until you remove them.
Google Drive and Gmail
Opening CSV Editor from Drive takes you through Google authorization automatically. Ordinary visits offer Connect Google Drive. We request access to specific files you open or create with CSV Editor and permission to add the app to Drive. Our authorization service briefly exchanges Google's authorization code for an access token and passes it to this tab's memory; it does not retain access or refresh tokens or receive CSV contents. An encrypted, temporary cookie holds launch details and authorization state for up to 10 minutes and is cleared when authorization returns. The website reads and saves files directly between your browser and Google. Access tokens and unsaved edits are not stored in browser storage or analytics. Reloading or closing the tab clears them.
Save updates the selected Drive file only when you choose it and the app can check its version. We check for changes immediately before saving. Where Google does not provide an atomic version check, another edit made during the save could still be overwritten. Save a copy creates a separate file. Your Google account controls file retention and sharing. Disconnect clears this tab's connection; you can revoke the app through your Google Account permissions. Uninstalling or revoking the app does not delete saved Drive files.
The optional Gmail add-on reads attachments from the currently open message while it runs. Choosing Save copy to Drive and open sends a selected CSV attachment through Google's Apps Script service to create a copy in your Drive. Each click creates a new copy. It does not search your mailbox, send email or modify the original attachment.
Google data is used only to provide these requested file operations. It is not used for advertising, sold, or used to train AI models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google and our hosting providers still receive ordinary request information when delivering their services. For privacy questions, use our support form without including private file contents or credentials.
Support requests
When you submit the public support form, we send your message and optional reply email to PostHog so we can review your request and contact you if you provide an email. Do not include private file contents, credentials, or access tokens. The form does not accept file attachments. Its contents are sent only when you choose Submit support request; they are not captured while you type.
Each request has a random reference separate from website sessions and desktop installation identifiers. We do not create a PostHog person profile for it. PostHog also receives ordinary request data, including IP addresses, and can derive location from them. Support messages and reply addresses are kept in our PostHog support records. You can use the same form for privacy questions or requests about your earlier submission; include its reference when available.
CSV Editor for Visual Studio Code
The VS Code extension reads the CSV or TSV document you open with its grid editor and sends your edits back to VS Code. VS Code manages the document, undo history and saving, including Auto Save and Save As. The extension does not require an account, upload file contents to Shipit Software, send app telemetry, or use a network service for editing. Its bundled editor loads locally.
Files and unsaved edits follow your VS Code workspace, backup, synchronization and remote-development settings and the policies of any storage provider you use. Installing or updating the extension and using VS Code or Microsoft services follow their respective policies. The browser extension analytics and the website and desktop analytics described elsewhere on this page do not run in this VS Code extension. If you open our website or submit a support request, the applicable website and support practices apply.
CSV Editor for ChatGPT
When you open a CSV file in the ChatGPT editor, ChatGPT supplies the selected file to the editor. The editor reads its contents in your browser and sends edits back through ChatGPT only when you choose Save. It does not require a Loam account or upload file contents to a Loam database. The editor does not collect analytics or run the website analytics or desktop diagnostics described below.
Our editor server receives the file name and a reference to the selected file in the opening request. It supplies the editor interface and instructions, but does not read or store the file contents. Loading the editor still makes network requests. Hosting providers may process ordinary request details, such as time, requested path, IP address, and browser information, to deliver and protect the service.
Unsaved edits and undo history stay in the editor's memory and are lost when it closes or reloads. Undo history is limited and is not a backup. Save updates the opened file managed by ChatGPT. Download CSV asks ChatGPT to download a separate copy, including all records even when a search hides some rows. You control the retention and deletion of downloaded copies on your device.
ChatGPT handles its own file processing and retention under OpenAI's policies and your account settings. Disabling or uninstalling the editor does not itself delete files held by ChatGPT. You choose which supported file to open and whether to save changes. For privacy questions, use the contact path on our support page. Do not include private file contents or credentials in a report.
CSV Viewer by Loam browser extension
The separately installed browser extension reads only CSV or TSV files you select or drop into its viewer. File names and contents remain in the viewer tab's memory while you view them. Closing the file or closing or reloading the tab clears that copy. Export filtered CSV downloads a separate file containing all matching rows and visible columns, including rows on other pages. Downloaded files remain in your browser's download location until you remove them. The extension does not overwrite your source file.
When you choose Copy table, the extension writes the headers and all matching rows from visible columns to your device's clipboard as tab-separated text. This includes rows on other pages. It does not read the clipboard. Copied data can be pasted into other apps, and clipboard history or synchronization follows your browser and operating system settings. Closing the viewer does not clear copied data from the clipboard or its history.
The CSV Viewer extension for Chrome, Microsoft Edge, Firefox and Safari does not upload files, keep a file history, read web pages, run remote code, or require an account. The website analytics, optional sign-in, SQL analysis, MCP, and desktop diagnostics described elsewhere on this page do not run in the extension.
The extension has its own optional usage analytics, off by default. If you enable Share usage statistics in Analytics settings and grant the requested browser permission, it sends fixed workspace-open, file-open, export-start and file-open-failure events to PostHog, hosted in the United States, together with the extension product, version, browser type and a random installation identifier. This identifier is stored locally and links reports from the same installation; these reports are not anonymous merely because they do not include your name or an account.
Reports exclude file contents, file names, paths, URLs, search terms, edits and error messages. There is no session recording or automatic click tracking. PostHog receives ordinary network information, including your IP address, when processing requests; IP-based enrichment is disabled.
All file features work with analytics off. You can change your choice in Analytics settings at any time. Disabling analytics stops future reports and deletes the locally stored installation identifier; it does not delete reports already received by PostHog. For privacy questions or requests about those reports, use our existing support form at https://csvfile.tools/support without sending private file contents or credentials.
Clicking a companion website link opens this website, where the website practices below apply. Your browser and extension store may process installation and update information under their own policies. For help, follow the contact instructions on our support page. Do not include private files in a support request.
CSV Viewer MCP
If you separately connect and authorize the CSV Viewer MCP, the client sends its prompts and tool arguments to the MCP resource. Loam processes the governed table schemas, profiles, bounded previews, cleaning plans, and results needed for the operation. Saving a reviewed cleaning plan creates a new Loam view and does not replace the source table. Your authorized Loam workspace, current permissions, OAuth authorization, and revocation state determine access on every request.
Optional account
You do not need to sign in to use this site or any of its file tools. If you choose Log in or sign up, your browser redirects to Loam Data's sign-in and consent pages, provided using Supabase Auth. After you approve access, this site's server exchanges a one-time authorization code for your account subject and, when available, your email address and display name. We use those details only to create and display the optional identity session on this site.
The server immediately discards the Loam access token, refresh token, and ID token after it retrieves your identity. It encrypts the bounded identity details and expiry in an HttpOnly, SameSite=Lax cookie that lasts for up to one hour and is scoped only to this site's origin. A separate encrypted transient cookie holds OAuth state and the PKCE verifier for up to ten minutes while login is in progress. Neither cookie uses a parent domain, and authentication details are not placed in local storage, session storage, Product analytics, or operational telemetry. CSV Viewer and Parquet Viewer cannot read each other's identity cookies.
You can continue anonymously, decline the Loam consent request, or log out at any time. Logging out clears this site's identity cookie and does not sign you out of Loam Data or another microsite.
Your CSV data
The browser reads selected files or pasted text, builds tables, applies filters and sorting, merges rows, and creates CSV, JSON, TSV, XLSX, and Parquet downloads locally. Those viewing and conversion actions do not send file names, headers, rows, cell values, or generated file contents to an analysis service.
The tool keeps the active dataset in browser memory until you reset it, open another file, close the tab, or the browser releases that memory.
Analyze with SQL works differently. For each analysis, this site's server uses a Loam service-account key to create one ordinary private leased Namespace. The service-account key stays on the server and is never sent to your browser.
Loam returns a reveal-once analysis token that is valid only for that exact Namespace. The page holds the token only in memory and sends it explicitly with analysis requests. It is not placed in a cookie, local storage, session storage, a URL, or a log, and it is lost when the page reloads or closes.
You can add multiple CSV files to the analysis. Your browser uploads each file directly to Loam Data object storage using a time-limited signed upload, and Loam creates one ordinary table per file. SQL can query or join those tables. Loam receives the uploaded file contents, table names, and SQL statements needed to perform the analysis and return its results.
The private Namespace lease expires after 24 hours by default and never more than seven days after creation. Activity does not extend this fixed expiry. Expiry revokes access and schedules physical cleanup. We do not use file contents to train an AI model.
CSV Editor desktop app for Windows and Mac
The separately installed CSV Editor desktop app opens, edits, and saves CSV files on your Windows PC or Mac. It does not require an account and does not upload file names, paths, headers, rows, cell values, or file contents to us.
Production builds send privacy-bounded application lifecycle logs and unexpected crash or error diagnostics to Sentry. They send bounded operational events to PostHog to understand app use and improve reliability. Routine measurement covers application and session lifecycle, document operations and views, setup and preferences, operating-system integrations, and reliability and outcomes. Examples include opening or saving a document, completing setup, and the outcome of automatic opening. Default-app diagnostics include the operating system’s registered name and identifier of the app assigned to open CSV files, whether CSV Editor is the default, and whether a handler is absent or detection is unavailable. Executable paths and command lines are excluded. These events include the app and release, fixed action, open source and outcome categories, a random app-scoped installation identifier kept in local app storage, and a fresh identifier for each launch. They contain no file names, paths, headers, rows, cell values, or file contents and do not create a person profile. Debug builds do not send desktop telemetry; locally signed release builds can.
After its first launch, the Windows background opener checks enabled folders for new CSV files and opens them locally. Downloads is the initial folder; you can choose folders or turn automatic opening off in Settings. Startup after Windows sign-in depends on your Startup Apps setting. The app does not upload folder listings or files. Selected folder locations and access settings stay in local app storage.
The installation identifier is not derived from your account, hardware, operating-system identity, or files. If local identifier storage fails, analytics use a session identifier instead. Desktop requests can expose ordinary network information, such as an IP address, to Sentry and PostHog. PostHog retains IP addresses and derives approximate location from them, which can include country, region, city, postal code, and estimated coordinates. These are collected with desktop product analytics. The app does not request your device's precise location. Random identifiers and the absence of person profiles do not make these records anonymous.
Desktop support requests are delivered through PostHog. The Windows in-app support dialog requires a reply email address and a nonempty message. Both are sent only when you choose Send request; opening or cancelling the dialog sends no support request, and the app does not read or attach files automatically. These deliberately submitted fields are kept in our PostHog support records without creating a person profile; they are not saved locally by the form or included in routine desktop analytics or crash diagnostics. Do not include private file contents, credentials, or access tokens. The public support form collects your message and an optional reply email, as described above.
We may offer optional accounts, cloud storage, synchronization, and other connected features. When available and you choose to use them, we may process account information, files, file metadata, and related activity to provide those services. Local editing does not itself upload files to cloud storage. The relevant feature will explain its data handling when you enable or use it.
The Mac app does not include the Windows download opener. Document processing works without a network connection, and a failure to deliver diagnostics or analytics does not prevent editing.
The Windows app keeps recent and pinned file records, including local file names, paths and opening times, in app-private local storage. A pending request to set CSV Editor as the default is kept locally for up to seven days so completion can be observed after restarting the editor. It also uses durable local recovery journals containing document content and accepted edits so you can recover unsaved work after an unexpected exit. Recovery records can remain after the app exits; they are not uploaded to us. You can remove recent entries or discard available recovery records in the app. Removing a recent entry does not delete the original file. Files you save remain on your device until you move or delete them.
The examples above describe our data practices rather than list every feature or event name. New categories of collected information, recipients, or materially different uses require this policy to be updated.
Personal data we collect
We collect the information necessary to provide our services. This can include information you give us when you create an account, purchase or subscribe, contact support, or use connected features. Loading a page, policy, favicon, or sample makes a normal request to the hosting service. Its infrastructure can process standard request details such as time, requested path, IP address, and browser information for delivery, reliability, and security.
How we use personal data
We use personal data to provide and support our services, manage accounts and subscriptions, respond to requests, secure the service, prevent misuse, diagnose failures, and improve the product. We do not sell personal data.
Product analytics measurement
We use PostHog to count page views and coarse operational events. The browser sends each bounded event to this site, which forwards it to PostHog. Each event contains a canonical path, fixed site and client labels, a validated operation and outcome, optional coarse measurement buckets, and a random in-memory session identifier that resets on reload. We do not create an analytics cookie or persistent visitor profile.
Product analytics event fields exclude query strings, referrers, IP addresses, analysis tokens, signed upload URLs, required upload headers, SQL, local file names, table names, file contents, headers, rows, cell values, pasted text, generated output, free-form errors, user identities, and other credentials. PostHog is configured to discard IP data and not create person profiles from forwarded events.
Cookies and Product analytics
The CSV File Tools website does not set a Product analytics cookie, store a Product analytics identifier in local storage, or run advertising trackers. It sends a limited operational event when a viewer, conversion, merge, export, or SQL analysis succeeds or fails. Each event contains only fixed operation, outcome, and coarse error labels, plus optional fixed-size buckets for file size, row count, column count, input-file count, and duration.
Operational telemetry never contains analysis tokens, signed upload URLs, required upload headers, SQL text, row data, local file names, or table names. It also excludes headers, cell values, pasted text, generated output, free-form errors, user IDs, and persistent browser identifiers. They also exclude login state, account subjects, email addresses, and display names. Event delivery is best-effort and does not affect the file operation. Hosting and PostHog infrastructure may also use necessary ordinary request data to deliver and protect their services.
Service providers
We use hosting and content-delivery providers to serve pages and sample files. These providers may process ordinary request data on our behalf under their own security and data-protection obligations. Local viewing does not send selected or pasted CSV contents to them. CSV to Parquet sends selected files to Loam Data processing storage and conversion servers. Analyze with SQL uses Loam Data object storage and analysis infrastructure. Optional login or signup uses Loam Data's authentication and consent service, provided using Supabase Auth, to process the login request and the bounded account details described above. Microsoft supplies the Store badge shown on this site. Loading it sends ordinary browser request data to get.microsoft.com; clicking it can request a Microsoft Store installer. The badge does not send your CSV file contents to Microsoft.
Retention and security
Browser-local CSV data is not retained by us. Each SQL analysis Namespace is private and kept only until the fixed lease expiry described above, followed by asynchronous physical cleanup. Hosting providers may retain ordinary request logs and the usage and support records for periods needed to provide the service, respond to requests, maintain security and reliability, improve the product, and meet legal obligations. Information associated with optional accounts or connected features is retained as needed for those services and their stated retention settings. The optional identity cookie lasts for up to one hour, and the in-progress login cookie lasts for up to ten minutes. We use reasonable safeguards, but no website or transmission method is completely secure.
Your choices and rights
You can use the site without selecting or pasting a file and without logging in. You can decline consent or log out to clear this site's identity session. Browser settings can restrict cookies and other storage. Depending on where you live, you may have rights to ask about, correct, or delete personal data we hold. Ordinary request logs may not always be attributable to you.
Policy changes
We may update this policy when the utility or its data practices change. The date above shows the latest revision. Material changes will be described here before they take effect where practical.
CSV Editor for iOS and Android
The separately installed mobile editor processes the files you choose on your device. File contents, file names, paths, sheet or column names, cell values and formulas are excluded from routine analytics and diagnostics. Local editing does not upload your document to Loam services or authorize a connected assistant to access it.
The operating system's document picker grants access to the document or destination you select. The editor may keep working copies and temporary save data in its private app storage. Saving or exporting writes to the destination you choose. If you select a cloud-backed file provider, that provider handles its own transfer, access and retention under its policies. Keep a saved copy of your changes; private working storage is not a backup. Clearing app data or uninstalling can remove private working copies and preferences, but does not delete files you exported to other destinations.
Production mobile builds use PostHog for bounded application activity and Sentry for lifecycle and error diagnostics. Reports include fixed app, version, platform, action and outcome categories, sanitized technical diagnostics, a random app-scoped installation identifier stored in local webview storage, and a fresh session identifier for each launch. The installation identifier is not derived from your account, hardware or documents. If local identifier storage is unavailable, analytics uses a session identifier. PostHog person-profile creation is disabled. Debug builds do not send this production telemetry.
PostHog and Sentry receive ordinary network information when reports are sent. The configured collection endpoints are in the United States. PostHog can retain IP addresses and derive approximate location from them; this is not a request for precise device location. Random identifiers and the absence of person profiles do not make these reports anonymous. Failure to deliver a report does not prevent local document editing.
The installation identifier remains in local app storage until that storage is cleared. Clearing local app data can cause a new identifier to be created on a later launch and does not erase reports already received. Operational reports are retained as reasonably needed for reliability, security and legal obligations, subject to service-provider retention controls. The current mobile editor has no in-app analytics opt-out control; operating-system network controls can restrict connections.
If you deliberately submit a support request, the message and reply address you provide are sent to PostHog support records. Opening or cancelling a support form does not send a request, and the editor does not automatically attach files. For privacy questions or requests about reports already received, use our support form and include a request reference when available; do not send private document contents or credentials.