Tridi Viewer

Privacy Policy

Effective and last updated: July 14, 2026

Privacy at a glance

Tridi Viewer does not upload your models. The app does not include telemetry or analytics and does not automatically send diagnostic data. Model processing and app data stay on your Windows device.

1. Scope and publisher

This policy applies to the Tridi Viewer Windows application published by Orcavia and to this documentation site. It explains what the app reads, what it stores locally, why it stores that data, how you can remove it, and what is included when you choose to export a diagnostic log.

2. Your model files

  • Model files and their contents are not uploaded to Orcavia.
  • Models are opened and processed locally on your device.
  • The app may read local files referenced by a model, such as textures beside a glTF, OBJ, or COLLADA file.
  • Some formats are converted locally into runtime glTF or GLB data in the import cache. Cached data can contain converted geometry, materials, textures, topology, and conversion metadata derived from your source model.

3. No telemetry or analytics

Tridi Viewer does not include telemetry, analytics, advertising, profiling, or crash-report upload services. The app does not sell or share personal information. Diagnostic information is not sent automatically; exporting a log only saves a text file to the location you select.

4. Data stored locally

The app stores the following data only on your Windows device:

  • Recent files. Up to eight model file paths are kept so the Recent Models menu can reopen files quickly. Older entries are removed as new ones are added.
  • Settings. Navigation and key bindings, UI choices, rendering preferences, and CAD/STL import defaults are saved so your choices persist between sessions.
  • Application log. A local text log records startup, shutdown, renderer/import status, warnings, and errors for troubleshooting. Entries can include local file-system paths and technical details.
  • Import cache. Converted runtime models, copied local texture dependencies, topology data, source path and file metadata, content fingerprints, import reports, and converter logs may be cached. This avoids repeating expensive conversion work and enables supported non-glTF formats to be loaded through the same runtime renderer path.

Recent paths and settings are stored under HKEY_CURRENT_USER\Software\TridiViewer. Unpackaged builds store logs and cache under %LOCALAPPDATA%\TridiViewer. Microsoft Store packages store them in the package's LocalState folder under %LOCALAPPDATA%\Packages.

5. Diagnostic log export

When you explicitly choose Export log, Tridi Viewer creates a text file at a location you select. The export contains:

  • export date and time, app name, and app version;
  • Windows version and CPU architecture;
  • logical processor count and total physical memory;
  • primary display adapter name and primary display resolution;
  • the app's current working-directory path; and
  • the complete current application log.

The application log can contain local paths, including app resource, cache, working-directory, or log export paths, along with import, renderer, performance, error, and shutdown messages. A diagnostic export does not automatically include model file contents, cached model artifacts, registry settings, or the Recent Models list. Review the text file before sharing it. Tridi Viewer never transmits it for you.

6. How to delete local data

Close Tridi Viewer before deleting its data.

  1. To remove settings and recent file paths, delete the registry key HKEY_CURRENT_USER\Software\TridiViewer. From Command Prompt, you can run reg delete "HKCU\Software\TridiViewer" /f.
  2. For an unpackaged build, delete %LOCALAPPDATA%\TridiViewer to remove the application log and import cache.
  3. For the Microsoft Store package, open Windows Settings > Apps > Installed apps > Tridi Viewer > Advanced options > Reset. You can alternatively delete the package's LocalState folder after uninstalling the app.
  4. Delete any diagnostic log exports separately from the location where you chose to save them.

Removing an import cache does not delete your original model files. The app recreates required local settings or cache data the next time it runs or imports a model.

7. Retention and security

Local settings, logs, and cached files remain until they are replaced, removed by Windows, cleared by you, or removed during an app reset. Access is governed by your Windows account and device security. Keep your device and account protected, especially if model file paths or model content are sensitive.

8. This website

This static site uses no analytics, advertising, tracking scripts, cookies, remote fonts, or forms. It is hosted by GitHub Pages. GitHub may process technical request data, such as IP addresses and server logs, under the GitHub General Privacy Statement.

9. Contact and policy changes

For privacy questions or requests, contact the publisher, Orcavia, at mutar.orcavia@gmail.com.

This policy may be updated if the app's data practices or features change. The effective date at the top of this page identifies the current version.