Frequently asked questions

What happens to the files you drop, what your browser keeps, and what these tools can and cannot do.

Where do my files go when I drop them?
They stay with you. When you drop a folder, we make no copy of our own: we keep access to your files and read them from your disk as we go. What lives in the browser's memory (locally) is whatever we are examining plus the analysis results, and it is all erased when you close the tab. A copy is written to your computer only if you ask for it, in the Saved column of My projects: in this browser, or in the working folder you chose on your PC. If you ticked “Copy to your working folder”, each new project is copied there as soon as you drop it. One special case: when you drop a ZIP or 7z archive, its contents are unpacked into the browser's memory, since they do not exist anywhere else as files. In every case, nothing from your package is sent: not the files, not their names, not their content, not the analysis results.
Can I drop a confidential package, or one under NDA?
That is what it is built for. Nothing from your package leaves your machine: not the files, not their names, not their content, not the analysis results. So none of it can leak through us. We count the tools you open and the functions that get used, never anything of your package (see below). One thing to know: a project saved in this browser or copied to your working folder stays on this computer. Anyone who opens this browser under your Windows account can open it again, and your working folder can be read like any other folder on your PC. On a shared machine, do not save the project and untick the automatic copy, or delete the project before you leave.
What exactly does saving a project do?
Without saving, your files only live in the open tab: refresh and they are gone. With a free account, the Saved column of My projects offers two places. In this browser, the project is copied into the space your browser sets aside for this site, on this machine, and you find it again on your next visit, in this browser only. In your working folder, in Chrome, Edge and the browsers that can write to a folder you choose (Firefox and Safari cannot), it is written with its versions to the folder you chose on your PC, and your browser remembers that folder for your next visits. It is not an account, it is not an upload, and it does not follow you to another computer. No longer keeping the project erases what the browser had stored on this PC; the files in your working folder, you choose whether to delete them. If erasing fails, we tell you on screen.
Does the browser replace a copy of my folder?
No, and that is the part to remember. The space a browser grants a site is not a hard drive: it can be cleared to free room, it goes away if you clear the site data in your settings, and Safari is the strictest, it wipes storage for sites it has not seen in a while. We do ask the browser to hold on to what you save there, but the browser decides, and it often declines. Keep your original folder: saving in the browser is there to pick your work back up from one day to the next, not to archive it. Your working folder is a folder on your PC like any other: it stays until you delete it.
Besides my projects, does the tool store anything on my computer?
Yes, your settings, and one more cookie for a Premium account. Your settings: your export profiles and your preferences (the language, the side panel width, how your projects are listed, the “Copy to your working folder” box, the “Measure the clearances when a project opens” box, the comparison colors, the tool notice collapsed once read, the “The tool has been updated” notice once read). Your browser stores them the moment you change them, with no checkbox, so you find them again on your next visit. They stay on this machine and are not sent anywhere. The cookie of a Premium account checks your Premium tools: it holds only your account and your session, never anything from your files, and our server reads it to renew that check. Your sorting rules go with the version of the project you apply them to: they stay on this machine only if you keep that project. The details are in the site's cookie policy.
Can my FRANCE CAO account see my projects?
No. The account tells us whether you have access to a given tool and shows your name and your plan at the foot of the menu; nothing you drop travels along with those questions. Nothing goes back up to your account, and logging out does not touch your projects.
Can I trust the results completely?
No, and no tool deserves that. Part of what we show is inferred: manufacturing files do not say everything, so we reconstruct the rest (what a layer is for, whether copper is a pad or a plane). We can be wrong, or miss something. These tools save you time on checking, they replace neither your own review nor validation by your manufacturer. What we do commit to: never hiding what we could not read, and saying so where it changes how you read the result.
I closed the tab and lost everything.
If the project was saved neither in this browser nor in your working folder, it only lived in that tab: you need to drop the folder again, or the archive it came from. That is why a message warns you before you leave when your work is not kept.
The drilled holes are in the wrong place, or the board is the wrong size.
A drill file does not always state the unit it is written in, nor how its coordinates should be read. When that is missing, the tool works it out from the file's own content and tells you so on the file's row: “deduced unit”, “format inferred”. The unit can be corrected right there, in one click. The way coordinates are read is only reported and cannot be changed: that is what can shift holes, or make dimensions off by a factor of ten. So check the dimensions you get before sending anything to manufacturing. And if a drawing looks wrong to you, write to us from the site's Contact page: you choose what you send us, we collect nothing from your files.
Is the use of these tools measured?
We count the tools you open, not what you put in them. Some only open with a package loaded: we then know you had one. Never its name, nor the names of your files, nor their content, nor a result. We also count which functions show up and which ones you use (a comparison run, an export written), to know what is useful, again with nothing from your package. You can refuse this count from the site's privacy policy.