Accessibility, Privacy, and Security#
These pages make explicit what Cellucid does and does not do in two areas that often get skipped in visualization tooling:
Accessibility: how to produce figures and workflows that work for diverse readers (color vision deficiency, low vision, keyboard-only use), plus current limitations of a WebGL canvas-based UI.
Privacy model: what stays local, what can touch the network depending on your loading workflow, what the public deployment reports to Google Analytics, what AI agents are sent, what is stored in the browser, and what exported artifacts can contain.
If you are in a regulated environment (clinical, IRB-controlled, corporate IP), the key idea is:
Cellucid is “just a web app”, but your workflow choices — above all, which origin you run it from — determine what leaves your machine and what gets saved into shareable artifacts.
Fast path (pick your situation)#
You need to… |
Do this first (safe default) |
Then read |
|---|---|---|
Use sensitive/clinical data without uploading it |
Self-host or run locally (this alone switches off usage analytics), then open local files (H5AD, Zarr), avoid Community Annotation, and review figure metadata before sharing |
|
Answer “what does this send to third parties?” for a review board |
Read the analytics section first — it is the only third-party egress you do not start yourself, and it is hostname-gated; then the AI agents section, if agents will be used |
|
Let an AI agent work on sensitive data |
Switch on Agents see names and summaries only for the dataset, and know it is not anonymisation |
|
Share sessions safely with a team |
Treat |
|
Make figures readable for colorblind audiences |
Keep the categories you rely on within the first 24 of a field; check the export preview’s colorblind simulation |
|
Work keyboard-only |
Navigation, filtering and analysis are all keyboard-operable; only pointer-based selection is not |
Recommended reading order#
Privacy model (know what leaves your machine and what gets saved)
Accessibility (make what you publish readable to more people)
Related (often relevant):
Metadata and provenance (export metadata can include dataset paths/URLs)
Security, privacy, and trust (session bundle privacy/trust)
System requirements (managed environments, blocked storage, iframe restrictions)
Pages in this section#
Color/contrast guidance, keyboard shortcuts, motion sensitivity tips, and practical limits of a WebGL viewer.
What stays local vs hits the network, what analytics the public site reports, what is stored in the browser, and what exported artifacts can contain.