CESMII Smart Manufacturing Roadmap Agent
In force from 27 August 2026. Version 1.
This policy explains what happens to personal data when you use the CESMII Smart Manufacturing Roadmap Agent. It is written to be read, not to be survived.
We handle two kinds of personal data, and our responsibilities differ between them.
If you need a data processing agreement covering the second role, which most institutional buyers do, ask us and we will provide one.
| Data | Why | Legal basis |
|---|---|---|
| E-mail address | Your account, signing in by e-mail link, and telling you about something that affects your engagements. | Performance of our contract with you. |
| Purchases and credit balance | Knowing what you bought and what you have left to spend. | Performance of the contract, and our accounting obligations. |
| Engagement content | Producing your deliverables. It can contain names, job titles and opinions of people at your client. | Processed on your instructions. You are the controller of this content. |
| Technical logs | Keeping the service up, finding faults and blocking abuse. Method, path, status, timing. | Our legitimate interest in a service that works and is not attacked. |
| Payment records | Confirming payment and granting access. | Performance of the contract. Card details are handled by Stripe and never reach us. |
We do not profile you, we do not advertise, and we do not sell anything to anyone about you.
The service runs on other people's infrastructure. These are all of them, what each one sees, and why.
| Provider | What it is for | What it can see |
|---|---|---|
| Render | Runs the application and stores your engagements and files. | Everything you upload and everything produced. |
| Vercel | Serves the web interface. | Technical request data only. |
| Supabase | Stores accounts, plans and credit balances. | Your e-mail address and your entitlements. |
| Stripe | Takes payment. | Your payment details and billing e-mail. |
| Resend | Sends sign-in links. | Your e-mail address. |
| OpenRouter | Routes each request to a language model and to the provider serving it, and generates the drafted text. Its own providers are governed by its terms. | The content of the prompt for that step, which includes the parts of your engagement it needs. |
| Tavily | Web search for the benchmarks and industry examples. | The search terms, which describe an industry rather than a person. |
The application, and with it your engagements and the files you upload, runs on Render in its Oregon region, in the United States. Accounts, plans and credit balances are held on Supabase in the European Union. The web interface is served by Vercel's global network.
Several of the providers above are established in the United States and process data there. Those transfers rest on the standard contractual clauses adopted by the European Commission, which form part of the data processing terms of each provider concerned. Ask us and we will point you to the terms that apply to any provider in the table.
Producing a deliverable means sending part of your engagement content to a language model, which OpenRouter routes to whichever provider is serving that model.
Your content is not used to train anybody's model. Every request the Agent sends sets OpenRouter's data collection preference to deny, which restricts routing to providers that do not collect submitted content, and the equivalent restriction is set on the account. A request that no such provider can serve fails and can be run again; it is never quietly handed to a provider that would keep the content.
You can ask us for a copy of your data, to correct it, to delete it, to receive it in a portable form, to restrict what we do with it, or to object to processing based on our legitimate interest. Write to the contact address above and you will get an answer within one month.
If you are unhappy with how we handle it you can complain to the French supervisory authority, the CNIL, at cnil.fr.
Where the data concerns your client rather than you, the request should come through you, because you are its controller and we act on your instructions.
The Agent sets no cookies and runs no analytics. It keeps three values in your browser's local storage, all of them necessary for the thing to work at all:
cesmii_session, your signed-in session, removed when you sign out.cesmii_api_token, used only in single-organisation deployments.cesmii_ui_lang, so the interface opens in the language you last chose.None of them tracks you, none is shared, and clearing your browser storage removes all three. That is why you are not being asked to accept anything.
Access is per account, and an engagement is visible only to the account that created it. Sign-in uses signed session tokens rather than stored passwords, so there is no password database to lose. Traffic is encrypted in transit. Keys and secrets are held as server-side environment values and never reach the browser.
No system is perfect. If you find a weakness, tell us at the contact address and we will treat it seriously.
If this policy changes in a way that affects you, we will say so by e-mail rather than quietly editing the page. The version and date at the top always tell you which text is in force.