Privacy Policy
1. Summary
Xenthum desktop tools are designed to work locally on your Windows device.
We do not collect, store, sell, or transmit personal data or file content through XenPDF, XenShot, XenCompare, XenCADtoPDF, XenCommand, or other Xenthum desktop utilities.
Your PDFs, drawings, screenshots, images, and other files stay on your device.
2. What data we collect
Xenthum desktop tools do not collect personal data.
We do not use:
- Telemetry
- Analytics
- Advertising identifiers
- Usage tracking
- Account tracking
- Cloud sync
- Background indexing
- Automatic file uploads
The tools are designed to perform their work locally and do not send your files to Xenthum servers. XenCADtoPDF makes no network connections of its own; a web page opens only when you click a link in the app, such as this policy, and then in your own browser. XenCommand makes no network requests of its own either; the programs and web pages it opens for you, and folders on network drives you choose, are reached the way they always are, by those programs and by Windows.
3. How your files are processed
All core file operations are performed on your local machine.
For XenPDF, this includes merging, slicing, password protection, page organising, converting images to PDF, watermarking, and page preview. XenPDF stores its preferences in a settings file on your device.
For XenShot, this includes screenshot capture, snipping, annotation, copying, and saving. Captures are saved automatically to user-selected folders on your device. The buffer shows the last 5 saved captures — clearing it does not delete saved files. XenShot writes diagnostic log files locally to %APPDATA%\Xenshot\logs on your device. XenShot has no feature for uploading logs, screenshots, or local app files to Xenthum.
- Every capture is also copied to the Windows clipboard, where it stays until something else is copied.
- Text recognition (OCR) runs on your device through the OCR engine built into Windows. No image or recognised text leaves your device.
- XenShot keeps its settings in %APPDATA%\Xenshot on your device.
- If you turn on starting with Windows, Windows starts XenShot when you sign in. You can turn it off in XenShot's Settings or in Windows' startup apps.
- If you turn on the setting that lets the Print Screen key start a snip, XenShot installs a system-wide low-level keyboard hook so it can see that key. It acts only on the Print Screen key, which then starts a XenShot snip instead of Windows' own action; every other key passes straight through and is neither recorded nor stored. The hook is removed when you turn the setting off or close XenShot.
For XenCompare, this includes opening, rendering and comparing drawings, your review work and comments, and exporting reports. Rendering runs in a separate local process on your device. The company details and logo you enter for report covers, and your view settings, are stored in the app's local data folder on your device and are removed when you uninstall the app.
For XenCADtoPDF, this includes plotting your DWG and DXF drawings to PDF, naming, checking and combining the output PDFs, and writing a batch report. It does this with the CAD application installed on your device — in its own background instance, or, for ZWCAD, in the session you already have open — or with its own built-in engine when no CAD application is installed.
- Your drawings are never saved or changed. Files they refer to (external references, images, fonts) are read where they are, including on network drives you already have access to.
- PDFs and the batch report are written only to the output folder you choose. The report lists file, folder, and sheet names and any problems found, and stays on your device.
- To plot without windows appearing, XenCADtoPDF temporarily changes some settings of your CAD application and puts each one back exactly as it found it. Until they are restored, it keeps a small record of the original values on your device, so they can be put back even after a crash.
- During a batch it may place temporary files in your CAD application's folders: a copy of its PDF plot device with "open when done" switched off, and a plot-style table you picked with Browse. They are recorded and removed when the session ends. A file XenCADtoPDF did not write is never changed or deleted.
- It puts back things your CAD application records while plotting, such as its recent-files list and panel layout, when no other session of that CAD application was open.
- If a CAD session XenCADtoPDF started crashes, the CAD vendor's crash-report window is closed without sending anything.
- XenCADtoPDF keeps its preferences (such as your output folder and file-naming pattern) in a settings file on your device, and uses a local work folder for temporary plot files, which it clears.
Your CAD application is software you license separately; its own privacy terms apply to it.
For XenCommand, this includes saving the layout of your desktop as a workspace and restoring it: starting your programs, opening the folders and web pages you chose, and placing their windows on your screens.
- Workspaces and settings are stored in a folder on your device (the app's own data folder when installed from the Microsoft Store) and are removed when you uninstall the app. A workspace contains program paths, folder paths, window titles and window positions. It leaves your device only when you export it yourself.
- To recognise and place windows, XenCommand reads the titles, positions and program names of the open windows on your device. This stays on your device.
- Browser tabs: when you save a workspace, or press Read tabs, XenCommand reads the addresses and titles of a browser window's open tabs through the Windows accessibility interface and saves them in the workspace, so the window opens with them again. When you launch a workspace it reads the open browser windows' tabs the same way, to find the window that shows your saved pages. Parts of an address that look like sign-in keys or one-time codes are left out. Addresses and titles go into exported workspace files too.
- Files: a window can open a file you chose, such as a note in Notepad; its path is saved in the workspace and its exports. To find which file a Notepad window shows when you save the desktop, XenCommand looks its name up in Windows' list of recently opened files on your device. To give a Notepad file a window of its own, it closes the empty tab it opened itself and moves a saved copy of the file out of another Notepad window, through the Windows accessibility interface.
- When you launch a workspace, XenCommand starts the programs and opens the web pages you chose; those programs and pages then work as they always do, under their own terms. Folders on network drives are opened through Windows, as File Explorer opens them, with your own access rights.
- XenCommand writes diagnostic log files to its data folder on your device (at most five files of 1 MB). Window titles are written to them only if you set Log level to "debug" in Settings. XenCommand has no feature for sending logs to Xenthum.
- If you turn on “Start XenCommand when I sign in to Windows”, Windows starts XenCommand in the notification area when you sign in. You can turn it off in XenCommand's Settings or in Windows' startup apps.
Your files:
- Are not uploaded to Xenthum servers
- Are not transmitted to third-party services by the application
- Are not used for analytics, advertising, or training
- Remain in the locations you choose on your own device
4. Microsoft Store
Xenthum tools are distributed through the Microsoft Store.
Microsoft may process certain store-related information when you install, update, review, or interact with an app through the Microsoft Store. That activity is handled by Microsoft under Microsoft's own privacy terms and account settings.
Xenthum does not receive your private files, screenshots, PDFs, workspaces, or local app content from the Microsoft Store.
5. Support emails
If you contact Xenthum support, we will receive the information you choose to include in your message.
This may include your email address, your message, screenshots, error descriptions, Windows version, and any files or details you voluntarily attach.
We use support emails only to respond to your request, investigate reported issues, improve the tools, and keep a reasonable support history.
Support contact: support@xenthum.eu
6. Third-party components
Xenthum tools may use third-party or open-source components to provide local desktop functionality.
These components run as part of the local application and are not used by Xenthum to collect personal data.
XenCADtoPDF works with CAD applications from other vendors that you license separately; XenCADtoPDF is not affiliated with or endorsed by them.
See the Third-Party Licenses page for more information.
7. Children's privacy
Xenthum tools are general-purpose desktop utilities and are not directed at children.
We do not knowingly collect personal information from children. As described above, the tools are designed not to collect personal information from anyone.
8. Changes to this policy
We may update this Privacy Policy when the tools, legal requirements, or support processes change.
When we update the policy, we will update the "Last updated" date at the top of this page.
9. Who we are and contact
Xenthum is a brand of Xenmark AS (org. no. 937 996 799), Aurvågvegen 150, 6070 Tjørvåg, Norway. Xenmark AS publishes the Xenthum desktop tools and handles support email. In this policy, “Xenthum”, “we” and “us” mean Xenmark AS.
Questions about this Privacy Policy can be sent to: