Security and data
Your work. Clear storage boundaries.
The product preview is individual and browser-local
The live example uses fictional records in a separate demo store. Replay resets only that example. LoopSolve investigations and LoopFlow maps stay in this browser on this device; they are never silently uploaded.
Browser storage is not company cloud storage or a backup. Clearing site data, changing browsers, or losing this device can remove access. If storage is blocked, temporary memory does not survive reload. Save failures are shown; export important work and keep the files somewhere you control.
Company authentication, team permissions, trusted shared storage, audit history, attachment recovery, and subscriptions are planned. They are not active in this preview. Pilot contact details are sent through Formspree; investigation content is not part of that form.
Optional consulting has a separate data process
Most of a LoopScan doesn’t need your data
A LoopScan is mostly a conversation and a walk-through, watching how work actually happens. That is where the findings come from.
Some scans need a data pull to put a number on the problem. If yours does, we ask before anything is exported, and it is read-only — we do not write back to your systems. You can decline and still get the scan.
We take the smallest pull that answers the question, and we tell you which fields that is before you send anything. Finding that 37% of your open POs are past their expected date does not require your supplier names.
If you do send data
It leaves your systems once, to the machine doing the analysis. It is not resold, not shared with anyone else, and not uploaded to a LoopSignal product.
One person does this work. No team, no subcontractor, no offshore analyst, no shared drive.
We delete our copy when the analysis that needed it is finished — and in no case later than 30 days after your readout. You get the raw pull and every query we ran against it, so you can reproduce any finding yourself.
We keep the findings document and the summary numbers we measured — things like “37% of open POs past expected date.” That is what lets us show you what changed at month six, and what we would ask your written permission before referencing anywhere else. Your supplier names, part costs, and quality records are not in that.
How we use AI
We use AI to do this work — outlining process, structuring analysis, drafting, writing code. Most of that is work about how we think, not about your rows.
Where your data is involved, the control we give you is the ask: nothing is exported without your yes, we take the smallest pull that answers the question, and if you want to know which tools touch it, ask and you will get a straight answer instead of a policy page.
If we build software for you
Built to your specification, on your systems, and yours to keep. If it needs cloud or backend infrastructure, you will know exactly what runs where, what it can reach, and who holds the keys — before it is built, not after.
What we don’t promise
We are not SOC 2 certified, and we will not be this year. If your procurement process requires it, we are not your vendor yet — tell us on the first call and we will say so plainly instead of walking you through three meetings first.
We do not have a sealed environment for AI analysis, so we are not going to claim one. If your data is part of an analysis, commercial tooling may be part of that analysis. Local hardware for exactly this is the next infrastructure we buy — but we would rather tell you what is true today than sell you a promise that is not running yet.
What we do instead is tell you where your data is at every step, and give you the ability to stop any part of it.
Questions: hello@loopsignal.co.