Privacy architecture

Keep visualization compute close to the reader.

VSLZ is designed so the server can stay thin and stateless. A render tool validates a declarative specification and returns it with a versioned UI resource. The host device performs layout, rendering, interaction, and theme adaptation.

What the application does not keep

• No account system or visualization history.
• No database, queue, or background render job.
• No third-party data fetch from render tools.
• No server-side chart, diagram, screenshot, or graph layout computation.

Operational logs

Deployments may expose standard platform-level operational logs such as request status, duration, and route errors. VSLZ should not log raw prompts, chart data, Mermaid source, or node metadata. Verify the active deployment’s platform configuration before making a stronger privacy claim.

Client-side rendering

Interactive widgets load visualization libraries in the host’s browser or WebView. Unsupported hosts receive a textual fallback rather than a hard failure.