Privacy policy

01 What this policy covers

This policy covers the nff desktop app (nff.exe), the services it calls, and this website. BlackWaves SAS, Paris, France, is the controller ("we").

The terms of use say what you may do with the Services. This page says what we collect, why, where and for how long.

02 What stays on your machine

Your folder stays on your machine. nff.exe never sends .git/ and your git history, node_modules, .env files, keys, its own index or the rest of .nff/.

The folder's other files, such as documents, PDFs and data, leave only when the agent reads them.

03 Your account

You sign in through nanocapy.com. We keep your email, your plan and your usage, to run the Services and bill you.

Stripe handles payment. We never see your card number.

04 The agent

On nff's own model, the agent's calls go to our model proxy at nanocapy.com, which forwards them to Anthropic or OpenAI. A call carries nff's prompt, your messages, the session transcript, the tool calls and their results, the files the agent reads, and the pictures you attach.

On a bring-your-own-agent plan, nff.exe runs your own Claude Code on your machine. Those messages go straight to Anthropic under your account. We receive a copy of each session.

05 The recording

We record every call nff.exe makes to our model proxy, quick answers and board router.

After each agent run we keep a copy of the folder's design files: system.json, scripts, firmware sources, meshes, STEP files, pictures and zips, up to 32 MB a file.

We also record what you do with a result: accepting or rejecting a change, an undo, a cancel, the size of your edits, the feedback you give.

06 The check server

When the checks run on our check server (geo.nanocapy.com), each check sends what it reads: the design's STEP files, its system.json, the routed board, KiCad project files and robot description files. Never a script or firmware source.

Files are kept by their hash, so a version sent once is not sent again.

A parts library call sends the part you searched for or fetched.

07 Public services the app calls

A board's 3D view fetches KiCad's public models from gitlab.com, by name. Picking a resistor or a capacitor sends its value to jlcsearch, a public parts catalogue. Neither receives your design.

08 How we use it

To run the Services: answer the agent, run the checks, route boards, count and bill your plan.

Our staff use the recording for support and to improve nff.

Recordings of sessions on nff's own model may also be used to train AI models.

A bring-your-own-agent session is never used to train AI models.

The check server's copies are used only to run the checks you ask for.

We do not sell your data, and we do not use it for advertising.

09 Who processes it

Anthropic and OpenAI run the model calls on nff's own model. Supabase stores accounts, recordings and files. Vercel runs nanocapy.com. Google Cloud runs the check server and the lab's servers. Stripe handles payment. PostHog measures this website, as the cookie policy says.

Each processes the data on our behalf, for these tasks.

10 Where and how long

Your data is stored in the United States: Supabase on AWS in us-west-2, Google Cloud in us-west1. Data sent from the EU is transferred there.

Your account, the recording and the check server's copies are kept until you delete your account. Deleting it deletes them.

Billing records are kept as long as tax law requires.

11 Your rights

Under the GDPR you can ask to access, correct, delete or export your data, or object to its use. Write to the address below. You can also complain to the CNIL.

You can delete your account yourself, from nanocapy.com/profile/privacy.

12 Changes to this policy

We update this policy when what nff.exe sends or keeps changes. The date at the top shows the latest version.

nff.exe asks you to accept this policy at each sign-in.

13 Contact

Privacy questions and GDPR requests: info@nanoforgeflow.com. See also the terms of use and the cookie policy.