Privacy Policy

1. Scope and publisher

This policy applies to the Tridi Windows application and this documentation site, both published by Orcavia. It covers data the app reads, data it stores locally, limited store-platform usage counters, 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 processes model files and any referenced dependencies, such as external textures, locally on your device. These files are not uploaded or transmitted by Tridi.
• Formats that require conversion may produce cached viewer-ready geometry, materials, textures, topology, and conversion metadata derived from the source asset.

3. Limited store-platform usage counters

The Microsoft Store build sends fixed, content-free usage event names to Microsoft Partner Center so Orcavia can understand format reliability and which viewer features are useful. The counters cover these categories without attaching model or user data:

• Import and reload outcomes: successful or failed model imports by supported format family, plus successful or failed geometry reloads.
• Render and export outcomes: successful or failed render-image saves, plus successful or failed exports for supported model-export formats.
• Texture replacement outcomes: successful or failed texture replacements and relinks.
• Feature adoption: use of animation controls, wireframe, object selection, box selection, and the mesh validator.

Outcome counters are recorded for each successful or failed attempt. Feature-adoption counters are recorded at most once per app session. Window Screenshot intentionally records no usage counter.

Each event consists only of its fixed name and has no custom properties or payload. Tridi does not attach a filename or path, model content or metadata, render output or screenshot data, raw error text, a custom user or device identifier, an advertising identifier, or other personal or production content. Models and their dependencies remain processed locally on your device.

The Microsoft Store build sends event names through Microsoft Store Services to Partner Center. Microsoft may add store-provided market, device type, and package version context to its reports. The Steam build stores equivalent counters through Steamworks user stats in the current Steam service context. Tridi does not request or include your Microsoft or Steam account name or identifier in an event. Microsoft and Valve process their platform data under the Microsoft Privacy Statement and Valve Privacy Policy.

Developer and other distributions configured with the Null metrics backend send no usage counters. Tridi contains no advertising or profiling and does not automatically upload crash reports or diagnostic logs. Orcavia does not sell usage-counter data or use it for advertising.

Export log writes a diagnostic text file to a location you select. Tridi does not transmit that file.

4. Data stored locally

Tridi stores the following data for the current Windows user or at locations you explicitly choose:

• 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.
• Tridi project files. When you choose Save or Save As, Tridi writes a self-contained .tridi project to the location you select. A project can contain canonical scene data, supported material and texture edits, visibility, animation and camera state, presentation and workspace state, embedded environment or image resources, and a project thumbnail.

Settings are stored in settings.json, and recent model paths are stored separately in recent.json. For unpackaged builds, these files, the application log, and import-cache data are stored under %LOCALAPPDATA%\Tridi. Microsoft Store packages use the package LocalState folder under %LOCALAPPDATA%\Packages. Tridi project files are stored only at the path you choose when saving them.

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, settings.json, recent.json, 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 > Advanced options > Reset also removes the app's local package data.
• Delete exported logs and saved .tridi project files manually from the locations where you saved them.

Clear Cache, Factory Reset, app reset, and uninstall do not delete original source assets, diagnostic logs exported outside app-managed storage, or Tridi project files saved to locations you selected.

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. Tridi project files remain until you delete or replace them. Access is governed by your Windows account permissions and workstation security.

Usage counters are not stored in Tridi's app-managed files after the store backend accepts them. Counters and platform context already processed by Microsoft or Valve are retained and controlled under that provider's privacy policy; clearing Tridi's cache, resetting the app, or uninstalling it does not delete records already held by the platform provider.

8. Documentation website

Except for the PayPal checkout integration described below, 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.

Opening the optional external Lifetime purchase page loads PayPal's JavaScript SDK directly from PayPal to render the official payment button and determine whether PayPal is available. This request can disclose ordinary network and browser metadata to PayPal, including your IP address, browser user agent, and the site origin, and PayPal may use cookies or browser storage under the PayPal Privacy Statement. No PayPal order is created until you select the payment button.

When checkout starts, the page creates a random checkout token in tab-scoped session storage, sends its hash and a random idempotency identifier to Orcavia's Cloudflare Worker, and opens the PayPal checkout experience. The checkout token is not placed in a URL and is removed when the tab closes.

The commerce service stores PayPal order, capture, refund, dispute, and webhook identifiers; product, amount, currency, and status; encrypted license-key recovery data; and random viewer device identifiers used to enforce the two-device limit. It does not receive or store your PayPal password or payment-card details. PayPal processes account and payment information under the PayPal Privacy Statement. Commerce records remain until they are no longer needed for payment reconciliation, refunds, disputes, license recovery, security, or legal obligations.

9. Contact and changes

For privacy questions, email Orcavia at tridi@orcavia.dev.

This policy may change if the app or its privacy practices change. The date at the top shows the latest version.