What Intake does with the file you send it, what it keeps to itself, and what it shares — stated plainly, with each measure marked by whether it is in force today or lands with the hosted release.
Intake is currently an advanced prototype. Per-client separation and caller identification are in place in the application as it runs — with the limits stated in section 04. The remaining measures — encryption at rest, sovereign hosting, and audit logging — are being implemented for the hosted release.
A BOM is your product’s recipe and sourcing strategy — which parts, in what quantities, on which board, from which sources. Reconstructing it means reverse-engineering your design and cost structure. Protecting that is the whole point of Intake.
What we pool to get smarter carries none of your composition. Even with full access to our shared knowledge, no one can reconstruct your BOM — the data that reveals a product lives only in your private space, isolated to you.
Your uploaded files, the link between your internal part codes and real parts, with quantities and placement, plus your reports. Isolated to you, never pooled. This is the crown-jewel data, and the only place the revealing join “part X, used by you, N times, on board Z” ever exists.
How to read a file format — delimiters, where columns sit. Structure only, no part data, so sharing it reveals nothing about your parts.
Public manufacturer facts about a part — package, specs, lifecycle — keyed to the manufacturer’s own public part number. Universal reference knowledge; it never says who uses a part.
Every visitor gets their own space from the first drop: your reports, your catalogue and your decisions are visible to you alone, and no listing shows anything else. A client can additionally be issued a named token — durable, revocable, and valid both in the browser and from a program. An installation dedicated to one client can require that token for everything; this public demonstration does not, and dropping a file here asks for nothing.
Said plainly, because the distinction matters: this partition is not authentication. There is no account and no password. Whoever holds your session cookie is you, a second browser is a second client, and clearing site data starts you over. A token can be issued and withdrawn — but it can also be handed on, so it attests which token was presented, never who was sitting at the screen.
A report link carries its own authority. Its identifier is unguessable and appears on no list, but anyone holding it can open that report without presenting anything. That is deliberate: you have to be able to send a report to a buyer without opening an account for them. So treat a link as a key — it opens one report, and lets nobody discover a second.
Finally, a decision taken in the tool is recorded with whoever took it when we know, and says so honestly when we do not: a person’s name if the token named one, a system or an anonymous session otherwise. That is attribution, not proof.
Your file is read locally at the edge and turned into a clean, normalized form. Nothing is looked up in a third-party supplier database at import — your raw BOM is never shipped out to be matched. Only the normalized result travels onward.
If your security policy forbids exporting a full BOM — common in defense and aerospace — you can import a part list instead: the same parts with the structure (reference designators, placement, assembly topology) stripped out. A part list is inherently reverse-engineering-safe, so you get sourcing and qualification while never disclosing how the parts fit together.
Choose it when you upload: the intake page asks whether you are sending a BOM or a part list, and the choice travels with the analysis. In part-list mode the absent design fields are treated as expected rather than as gaps, and they are nulled in what we hand on rather than reconstructed.
At production, your data is encrypted in transit and at rest (KMS envelope encryption as the baseline). For the most sensitivity-constrained clients we offer two stronger options: PGP encryption with your own key (so even we can’t read your stored file), or fully in-browser analysis (your raw BOM never leaves your machine — we receive only the normalized result). Access is least-privilege, and Tier-1 access is audit-logged.
For clients with sovereignty requirements, Intake can be deployed on SecNumCloud-qualified sovereign infrastructure — S3NS (Thales × Google), operated in France by Thales — so your data stays under French jurisdiction. Intake’s import runs offline by design, which makes a zero-egress sovereign deployment a natural fit.
The SecNumCloud qualification is S3NS’s, not Adesio’s: Intake is not itself SecNumCloud-qualified. This deployment is available on request, and is not the current default hosting.
If you ask to be told when Intake goes live, we keep your email address and the moment you gave it. Nothing else: no IP address, no browser, no referring page, no name. None of them is needed to write to you, and each would turn a mailing list into an attendance log.
The list lives with the installation, in the same place as your reports. Nothing leaves it on its own: the form calls no outside service, and signing up triggers no send. When we do write to the people on it, the addresses — and only the addresses — are exported to our sending tool, Brevo, hosted in the European Union. That is a deliberate, dated act, never a side effect. The list is never joined to the contents of your files: an address does not say which BOM was dropped. Write to contact@adesio.io to be taken off it, and we delete the row.