MapMyCSV

Legal

Privacy at MapMyCSV

Effective August 18, 2026. This page explains what MapMyCSV processes when you map a CSV, purchase export access, or join the launch list.

CSV contents stay in your browser

Mapping, validation, previews, and exports run in your browser. MapMyCSV does not upload your CSV, filenames, headers, mapped rows, or exported files. You can disconnect from the internet after the page loads and continue working with the mapper.

Anonymous aggregate interaction counts

MapMyCSV counts six aggregate interactions so Loopspur can determine whether the product is usable: a file or sample was loaded, a preview was seen, a buy link was clicked, paid access was confirmed, an export was completed, and a mapping pack was downloaded. Each interaction requests a fixed same-origin path with no request body or query string. Temporary in-memory deduplication prevents the page from counting the same interaction repeatedly during one page load.

These counters do not add CSV data, filenames, email addresses, account IDs, analytics identifiers, storage IDs, fingerprints, or values from your file. Cloudflare necessarily receives normal web-delivery data such as the requested path, IP address, browser information, and time when it serves the site.

Payment and access recovery

Stripe handles checkout on its own site. MapMyCSV stores only opaque Stripe purchase identifiers in Cloudflare KV so paid access and recovery can be verified. A signed private recovery link works as a bearer credential. Anyone who has that link may be able to restore your export access, so keep it private and do not send it with a CSV.

Launch-list email

If you voluntarily join the launch list, FormSubmit handles the email address you provide. It is used only for Loopspur product announcements. The launch-list form does not receive your CSV or any mapped data.

Contact

Privacy questions can be sent to hello@loopspur.com. Do not attach client CSV files, payment card details, or a private recovery link.

Return to MapMyCSV