What happens when you choose a file
- The browser reads the selected file. DeskLens does not submit it through an upload form or send its bytes to an application API.
- A local Web Worker expands compatible ZIP entries and parses JSON or NDJSON records.
- Search, filtering, ticket rendering, CSV creation, and Markdown creation run in the current tab.
- Imported records remain in temporary browser memory. Closing or reloading the tab clears the working dataset.
What anonymous feature counts are sent
In production, DeskLens can send one of five event names to its own /api/usage
endpoint. Each event is counted at most once per browser tab:
sample_opened |
The built-in sample was opened. |
|---|---|
import_succeeded |
A user-selected file finished importing successfully. |
search_used |
The search control was used after data was available. |
csv_exported |
A CSV export was created locally. |
markdown_exported |
A Markdown export was created locally. |
Not included in the event
DeskLens does not add file names, file sizes, ticket IDs, ticket contents, search terms, exported contents, cookies, or a persistent user ID. As with any web request, the hosting network can process ordinary connection metadata, but DeskLens does not add the visitor's IP address as an analytics field.
Current file and feature limits
| Inputs | Zendesk-style ZIP, JSON, and NDJSON files. |
|---|---|
| Compressed ZIP size | 75 MB maximum. |
| Declared expanded size | 300 MB maximum across compatible ZIP entries. |
| Attachment files | Attachment files and attachment metadata are not imported or displayed. |
| Accounts and saved work | Not available. There is no cloud workspace or team sharing. |
| Browser support | A current desktop browser is recommended for larger exports. |
What local processing does not guarantee
Local processing reduces disclosure risk, but it does not prove that every historical, customized, or malformed export will parse perfectly. Before using results for an audit, migration, legal hold, or deletion decision:
- Keep the untouched source archive.
- Review every import warning and any Zendesk-generated error file.
- Compare a sample of tickets and conversations with the source account.
- Apply your organization's device, retention, and customer-data policies.
For a practical import sequence, read the Zendesk JSON export guide.
Product status
DeskLens is an independent preview tool and is not affiliated with, endorsed by, or supported by Zendesk. It currently has no account system, paid plan, service-level agreement, or cloud storage.