Privacy Policy

Privacy is our default architecture

This isn't a feature we bolted on — it's the foundation. commadelimiter.com does not store, view, collect, or stream any of the text, spreadsheets, lists, or CSV configurations you paste into our fields. There is no database, no analytics pipeline, and no server-side logging of your content. Period.

100% local browser processing

Every operation — parsing, delimiting, deduplicating, find-and-replace, quoting, batching — executes entirely within your local browser window via JavaScript. Your data never crosses a network boundary. It is never serialized into an HTTP request. No API endpoint ever receives your input. The processing lives and dies inside your tab.

Cookies & local storage

We utilize standard browser localStorage strictly to power the Auto-Save feature — caching your UI configurations, delimiter preferences, and workspace data so you can pick up exactly where you left off after a refresh or restart. That's it.

No tracking cookies. No analytics tags. No fingerprinting scripts. No third-party loggers touching your storage. The only external request is a standard font file load from cdn.jsdelivr.net, which receives zero user data beyond a routine HTTP request.

Zero network transmission = zero breach risk

Because no data is ever transmitted over a network to a remote server or database, the attack surface for enterprise data breaches on our platform is effectively zero. There is nothing to intercept, nothing to leak, and nothing to subpoena. Your data stays in your browser — and when you clear your browser data, it's gone for good.

Questions?

If you have any concerns about how this tool handles data, reach out at arcentekltd@gmail.com or visit our contact page.