Privacy

What happens to a file you open

When you choose or drop a file, the browser hands it to a background worker that this page starts in the same tab. The worker reads the file, works out its tables and sends the field list and the first rows back to the page to show you. When you export, the worker writes the Excel or CSV file in the tab and the browser saves it like any other download. The file and everything read from it stay in the tab's memory and are gone when you close it or press Remove.

The converter has no upload step and no server-side code for files. It is a set of plain HTML, CSS and JavaScript files.

The done-for-you service

This is the one place files leave your computer, and only when you choose it. Files you send with the form on the done-for-you page go over HTTPS to private storage on Cloudflare, with your name, email and notes. Only I open them, and only for that job. They are deleted 14 days after I deliver the finished files, when the download link also stops working; files that are never paid for are deleted after 14 days. After that the job keeps its number, size and price for my accounts, without your name, email, notes or files. The browser you uploaded from keeps a key for the job in local storage (under intake: and the job number) so the next page can show it.

What the page stores

No cookies and no account. If you buy the full export, the page keeps the licence code in the browser's local storage for this site (under the name rb.licence) so the export stays switched on next time. The code holds a random purchase number, the date, and the organisation name if you typed one at checkout; it holds no email or card details. Nothing is stored for someone who has not bought.

What the page contacts

Only this site: the pages, their scripts and stylesheet, and the sample file when you click to open it. If page counts are switched on for the site, Cloudflare Web Analytics counts page views without cookies; it is added by the host and never sees your files.

When you press Buy, or open and use the done-for-you form, the page sends this site a one-line count (/api/intake/beacon) with the name of the event and the page it happened on. It carries no cookie and nothing about you or your files; the counts are kept as daily totals.

Buying is the one exception, and it never involves your files. The Buy button takes you to Stripe's checkout, which handles the payment. When Stripe sends you back to the thanks page, the page asks this site's store address (/api/store/recordback) to check the payment with Stripe and sign a licence code. Restore on the price page sends the email and card digits or receipt number you type to the same address, which looks the purchase up at Stripe. The store keeps no record of who bought: only a hashed purchase number with a count of licences issued for it, and hashed rate-limit counters that expire within a day.

How to check

Open the browser's developer tools on the Network tab, then open a file and export it. You will see no request that carries your data. Or load the page, disconnect from the internet, and use it offline.

The browser enforces this policy, which the site sends with every page. It allows scripts and connections only to this site and the analytics counter, and no frames, plugins or form posts to other sites:

default-src 'self';
script-src 'self' https://static.cloudflareinsights.com;
style-src 'self';
img-src 'self' data:;
font-src 'self';
connect-src 'self' https://cloudflareinsights.com;
worker-src 'self';
object-src 'none';
base-uri 'self';
form-action 'self';
frame-ancestors 'none';

Questions

Write to [email protected]. I made the site and answer these myself.