Contact

Bug reports, feature requests, or just a note that a tool saved your marketplace upload — all of it is welcome. CSVUndo is a small project, and emails from people repairing real files decide what gets built next.

You can expect a reply within two business days. It is a one-person inbox, so the occasional message takes a little longer, but every one gets read.

Reporting a bug

If a repair produced the wrong output, two things make the fix dramatically faster:

• A small sample of the problem CSV. Five to ten rows that reproduce the issue is plenty — and please strip out anything sensitive first. Dummy values work fine: a column of 8.85E+11 or 0012345 that misbehaves the same way tells us as much as your real data would.
• Your browser and version — for example, Chrome 126 on Windows 11 or Safari on iPhone. Everything runs client-side, so the browser is the entire environment.

Reporting a security issue

Found something that undermines the privacy promise — a way to make the page send data anywhere, or a file that makes a tool run code it shouldn’t? Report it to the same address and put SECURITY in the subject line. It will be read ahead of everything else. The machine-readable copy of this is at /.well-known/security.txt. Please include the CSV (or a scrubbed version) that triggers it, since a header cell or an unusual byte sequence is usually the whole reproduction.

Feature requests

Hit a damage pattern none of the 14 tools cover — a locale quirk, an importer that rejects a file everything else accepts, something stranger? Describe it and attach a scrubbed sample. The roadmap comes straight from these emails.

Before writing, it may be worth a quick look at the guides: many common Excel-and-CSV mishaps already have a documented step-by-step fix.