How DataLensia Handles Your Data

A verifiable explanation of local file processing, no account requirement, and the basic usage analytics that run in production.

What local processing means

Local processing means core operations on your file — parsing, validating, comparing, converting, and rendering — run in the browser tab on your device. You do not need to sign in, and DataLensia has no file-processing backend that stores these datasets. You can use the core tools without identifying yourself. In production, Vercel Analytics measures page usage and Microsoft Clarity records general interactions. Data areas are marked for Clarity masking, while usage telemetry still runs. Shared links and remote features can send data elsewhere, as described below.

Check the network activity yourself

You can inspect network traffic yourself. Expect analytics requests in production; check that core tools do not upload your file to a DataLensia file-processing backend.

Open DevTools. Press F12 (Windows/Linux) or Cmd+Option+I (macOS) in Chrome, Firefox, or Edge.
Switch to the Network tab and clear its log (the 🚫 icon).
Open any DataLensia tool — for example the JSON Validator — and paste or upload a JSON file.
Inspect the requests in the list. Vercel Analytics and Microsoft Clarity may send usage events while you use the site. Check their destinations and payloads separately from file processing; analytics requests do not mean your file is sent to a DataLensia processing backend.
Keep the tool open, then go offline. Repeat the local operation in that tool. Analytics and remote features pause until you reconnect.

Client-side vs. server-side JSON tools

Online JSON tools vary: some process files on a server, while others work locally. Here is how DataLensia's core tools compare with a tool that uploads files for processing:

Property	Client-side (DataLensia)	Typical server-side tool
Where parsing happens	Your browser's JS engine	A remote server
What leaves your device?	Usage telemetry; core file contents stay local unless you share or use a remote feature	Uploaded file contents
Works offline?	Local operations in a loaded tool	Usually not, if processing needs a server
Suitable for regulated data (PII, health, financial)?	Follow your organization's policy; analytics still run	Depends on the provider's data handling policy
Verifiable by the user	Yes, via browser DevTools (see above)	Not directly — requires trusting the provider

Remember: You can use core tools without an account, and your files are processed locally. Production analytics still collect usage events. API and GitHub features contact other services; shared links can expose data through URLs.

Frequently asked questions

Does DataLensia upload my JSON or CSV file to a server?

Core tools parse, validate, transform, and render file contents in your browser. There is no DataLensia backend that processes or stores files you upload or paste into those tools, and you do not need an account. Production analytics still receive page and interaction information. Optional API requests and GitHub Sync send selected data to other services; shared links contain data in the URL and may send it to the hosting server when opened.

How can I check what is sent over the network?

Open your browser's DevTools and select the Network tab. Inspect the requests before and after uploading or pasting a file. Expect page assets and, in production, analytics requests; the core tool should not upload your file to a DataLensia processing backend. Shared links and remote features are separate cases.

Can DataLensia work completely offline?

After a core tool has loaded, its local file operations can continue offline. Analytics and features that contact an API, GitHub, or another remote service need an internet connection.

Where is my data stored while I use DataLensia?

Core tool data is held in your browser's memory and, if you save a workspace, in browser storage. DataLensia does not have an account or file-processing backend that stores your dataset. Production analytics providers separately receive page and interaction telemetry; see the Privacy Policy for details.

What happens to my data when I close the tab?

Unsaved file contents in memory are cleared when you close the tab. Saved workspaces remain in your browser until you delete them. Analytics providers may retain usage events under their own policies.

Is the 'Share' link feature an exception to the no-upload rule?

Yes. Shared links contain a compressed, unencrypted copy of the data you choose to share. Smaller links use a URL query, which reaches the hosting server and may appear in logs or analytics; larger links use a URL fragment that is not sent with the page request. Anyone with the link can access the data. Clarity is configured to skip direct visits to shared links, but this does not prevent a URL query from reaching the host.

Can I backup or collaborate on my workspaces remotely?

Yes. GitHub Sync connects to your repository and sends the workspace data you choose to sync to GitHub. Review GitHub's data handling and your organization's rules before syncing sensitive content.