The short version

The CSV you select is read by JavaScript running in your own browser and analysed there. It is never transmitted to LinkFinder AI or to anyone else. We do not receive it, store it, or process it, because there is no code path that sends it anywhere.

You can verify this in about five seconds. Disconnect from the internet, then run the check. It works normally. A tool that uploaded your file could not.
The analysis is one readable file: lf-crm-audit.js. It contains no upload, no fetch of file contents, and no network call carrying row data. Your browser's Network tab will show the same.
Nothing is written to a server, and the file is not stored in your browser either — close the tab and it is gone.

What we do receive

Being exact matters more here than sounding reassuring, so: the page sends aggregate counts to our analytics so we know the tool is being used. Specifically the number of contacts analysed, the completeness percentage, the number of missing fields by type, and the resulting credit total.

No name, email address, phone number, company, or row of any kind is included — those values are never part of what is sent. The numbers describe the shape of a database, not the people in it.

Where this stops being true

The check is local. Enrichment is not. If you later ask LinkFinder AI to actually fill the gaps it found, the records you submit are sent to our API and processed on our servers — that is what the service does, and it cannot work any other way.

We are drawing that line explicitly because it matters to the person reviewing this. Running the check involves no data transfer. Using the product does. They are separate decisions and you can make the first without making the second.

If you would rather share less anyway

Use the sample file instead of your own data to see what the output looks like first.
Export 500 rows rather than the whole database. The percentages come out the same.
Delete any column you would rather not include. Anything absent is simply reported as missing.

Questions

If your security or legal team needs something this page does not cover, email [email protected] and a human will answer.

This page describes how the tool is built. It is a technical description, not legal advice, and it is not a data processing agreement — your own assessment of what you are permitted to do is yours to make.

Back to the check