Privacy Policy
Privacy at a glance: Tridi Viewer processes source assets and their local dependencies on your workstation. It does not upload models, collect usage analytics, or send diagnostic data automatically.
1. Scope and publisher
This policy applies to the Tridi Viewer Windows application and this documentation site, both published by Orcavia. It covers data the app reads, data it stores locally, diagnostic exports, and data removal.
2. Source assets and dependencies
- Model files and their contents are not uploaded to Orcavia.
- Models are opened, parsed, and rendered on your Windows device.
- Tridi may read local dependencies referenced by a model, including external textures used by glTF, OBJ, or COLLADA assets.
- Formats that require conversion may produce cached viewer-ready geometry, materials, textures, topology, and conversion metadata derived from the source asset.
3. No telemetry or automatic reports
Tridi Viewer includes no advertising, profiling, usage analytics, or automatic crash-report upload. Orcavia does not sell or share personal information from the app.
Export log writes a diagnostic text file to a location you select. Tridi does not transmit that file.
4. Data stored locally
Tridi Viewer stores the following data for the current Windows user:
- Recent files. Up to 16 model paths are retained for the Recent Models list. Older entries are removed as new ones are added.
- Settings. Navigation, shortcuts, interface state, rendering preferences, and CAD or STL import defaults persist between sessions.
- Application log. A local text log records startup, renderer and importer status, warnings, errors, performance information, and shutdown events. Entries may contain local paths.
- Import cache. Converted viewer-ready assets, copied texture dependencies, topology data, source metadata, content fingerprints, import reports, and converter logs may be cached to avoid repeating conversion work.
Recent paths and settings are stored under HKEY_CURRENT_USER\Software\TridiViewer. Unpackaged builds store logs and cache data under %LOCALAPPDATA%\TridiViewer. Microsoft Store packages use the package LocalState folder under %LOCALAPPDATA%\Packages.
5. Diagnostic log exports
When you choose Export log, the exported text file contains:
- the export date and time, app name, and app version;
- the Windows version and CPU architecture;
- logical processor count and total physical memory;
- the primary display adapter and display resolution;
- the current working-directory path; and
- the complete current application log.
The application log can include resource, cache, source, working-directory, or export paths, plus import and rendering messages. It does not automatically include model contents, cached asset files, registry settings, or the Recent Models list.
Review the text file before sharing it: project names, asset names, and folder structure may reveal personal or confidential production information.
6. Removing local data
- Preferences > System > Clear Cache closes loaded models and removes generated import-cache data. It preserves settings, recent paths, and the application log.
- Factory Reset requires confirmation, closes the app, and removes Tridi-managed settings, recent paths, key bindings, logs, and import-cache data for the current Windows user.
- For a Microsoft Store installation, Windows Settings > Apps > Installed apps > Tridi Viewer > Advanced options > Reset also removes the app's local package data.
- Delete exported logs manually from the location where you saved them.
Clear Cache, Factory Reset, app reset, and uninstall do not delete original source assets or diagnostic logs exported outside app-managed storage.
7. Retention and access
Settings, logs, recent paths, and cached data remain until you clear or reset them, uninstall or reset the app, or Windows removes them. Access is governed by your Windows account permissions and workstation security.
8. Documentation website
This site uses no analytics, advertising, tracking scripts, cookies, forms, or remote fonts. The hosting provider may retain standard connection logs, such as IP address, request path, and request time, to deliver and protect the site.
9. Contact and changes
For privacy questions, email Orcavia at mutar.orcavia@gmail.com.
This policy may change if the app or its privacy practices change. The date at the top shows the latest version.