Last updated: October 2026
Core tools process your JSON, CSV, and NDJSON files in your browser. There is no DataLensia backend that processes or stores files you upload or paste into those tools. No account, name, or sign-in is required. Optional features can send data elsewhere: API requests go to the service you configure, and GitHub Sync sends selected workspace data to GitHub. Shared links contain a copy of the data you choose to share. Smaller links put it in the URL query, which reaches the hosting server when someone opens the link and may be recorded in logs or analytics; larger links use a URL fragment that is not sent with the page request. The data in a shared link is compressed, not encrypted.
In production, Vercel Analytics measures page usage, while Microsoft Clarity records page views and general interactions such as clicks and scrolling. We do not ask who you are or connect this activity to a DataLensia account. Analytics providers may still use technical identifiers. You can use the core tools without identifying yourself, but this does not mean analytics are switched off. Editors, JSON viewers, tables, diagrams, and data previews are marked for Clarity masking, which is intended to hide their contents in session recordings. Clarity is configured to skip direct visits to links containing shared workspace data.
We tell Clarity not to use analytics or advertising storage. Clarity can still measure page visits and basic interactions. When its Consent Mode applies, cookies and linking between page visits are limited. DataLensia also uses browser storage for saved workspaces and preferences.
Core file operations happen on your device. Shared links contain a copy of the data you choose to share, so send them only to people you trust. Review the destination before using a feature that contacts an API or GitHub.
If you have any questions about this Privacy Policy, join our Discord community: Discord