VialSeq

Privacy

Short version: nothing you enter ever leaves your browser. Below is exactly what's stored, where, and how to clear it — no legal filler.

What this tool never does

• No server. This tool has no backend — there's nowhere for your data to be sent, because nothing exists to receive it.
• No cookies.
• No analytics, no trackers, no third-party scripts of any kind.
• No account, no sign-in, no way to identify you across visits or devices.

What it does store, and why

Everything below lives only in your own browser's local storage — the same mechanism a browser uses to remember, say, a half-written comment on a form. It's tied to this one browser on this one device; it's never transmitted anywhere, including to us, because there is no "us" on the receiving end.

• Your current batches, catalogue and settings — so a reload or an accidentally closed tab doesn't wipe out what you were working on.
• Named profiles or templates you explicitly choose to save, and which one (if any) you've marked as your default.
• Your chosen visual theme.
• Vial positions from a CSV you previously imported — used only to warn you if a new sequence reuses the same position.
• Saved batch-number pattern templates and tray layouts you've created.
• Whether you've already seen the first-visit welcome message, so it doesn't show again.
• The language you picked, so the tool opens in it next time.
• When you last exported a CSV, and from which sequence — so the tool can remind you, on your next visit, that what's on screen was never exported. It's a timestamp on your own machine, not a record of your activity sent anywhere.
• Which version of the tool you last saw, so the "what's new" note appears once after an update and not again.
• A copy of anything above that turned out to be damaged, kept under the same name with .corrupt added, so a saved profile isn't lost just because the tool couldn't read it. Only ever created if that actually happens, and the tool tells you when it does.

If the tool ever hits an unexpected error, it offers a "Download diagnostic file" button — a JSON file built entirely in your browser (your current configuration, the error itself, and basic browser info) that only downloads to your own computer. Nothing is ever sent anywhere automatically; it exists so you can attach it to a feedback email yourself, if you choose to.

Under EU/Spanish cookie rules (ePrivacy Directive, LSSI), storage that's strictly necessary for a feature you've actively asked for — like remembering your own work — doesn't require a consent banner. That's the case for everything on this list: it exists only to make the tool work the way you'd expect, never for tracking.

How to clear it

Two ways: use New sequence inside the tool (clears batches/catalogue/sequence, keeps saved profiles and layouts), or clear this site's data from your browser's own settings (removes everything, same as any other site).

To move it instead of clearing it — say, to a different browser or computer — use Export library in the Profiles menu. It downloads your saved profiles, tray layouts and batch-pattern templates as one file you can import back in on the other side; the same one-file-in-your-hands principle as everything else on this page.

If this ever changes

If a future version adds anything that sends data elsewhere — even a privacy-respecting, cookie-free analytics tool used only to see whether people can find this tool at all — this page and the tool's footer will say so plainly, before it ships, not after. Nothing here is meant to still be true by accident.

Questions

This is an unofficial, community-built tool — see the disclaimer in the tool's footer for what that means. If anything above is unclear, ask: feedback@vialseq.com. You can also check any of it yourself without taking our word for it — open your browser's developer tools, watch the Network tab, and use the tool normally: nothing leaves the page.

← Back to VialSeq · About · FAQ · Changelog