Privacy and technical reports

This page explains the website's measurement and the app's separate diagnostic choices. Website events, automatic app reports and local debugging exports are different data flows. Walz Media is the publisher and support route identified by the product documentation. For a data question, use Walz Media's contact route.

Reviewed October 24, 2026. The current checked package is 0.3.2 (build 6). App-control details below come from the development manual and receiver implementation; this page is not a claim that every control has been tested in that package. Runtime debugging and reports

Website measurement

The site measures aggregate use of selected pages and acquisition controls so the publisher can understand which instructions and installation routes people use. These events go to the site's own /api/site-events endpoint. They do not go to a third-party analytics provider.

An accepted event request contains only an allowlisted event name, canonical page path and fixed placement label. The server adds the deployed release label to its counters. It does not collect a referrer, query string, email address, cookie, session ID or device ID. The collector keeps a rolling window of 90 UTC dates and removes older counters during routine cleanup; cleanup resumes at startup after server downtime. It does not store raw event payloads or IP addresses. Repeated actions may count more than once. These counters do not identify unique visitors, prove an installation or establish successful app use.

The client does not send these measurement events when the browser signals Global Privacy Control or Do Not Track. The event system does not use cookies or local storage for visitor identification. Normal browsing and the copy controls remain usable without measurement.

An HTTPS request necessarily exposes its network address to the server while connected. Request logging is disabled for the event endpoint, but ordinary hosting access logs can contain request and network metadata. This page does not promise that all hosting logs are absent or that network connections are anonymous.

Automatic app reports

Automatic technical reporting is separate from website measurement. In supported builds, the welcome screen and Preferences → Performance expose the reporting choice. Confirm the displayed choice before continuing; you can turn reporting off later. The runtime guide describes the exact controls and defaults in its documentation snapshot.

When reporting is enabled and the app detects a monitored error or stall, the receiver accepts a fixed technical schema. It includes a random per-report ID, capture timestamp, error category, app version/build, macOS version, GPU model and approved numeric diagnostics such as memory, frame-production or failure counters. These measurements help investigate symptoms; they do not identify a proven cause.

The automatic report excludes names, email addresses, persistent user/device identifiers, media files, full set contents, filenames, paths, raw error messages and local journals. The server rejects fields outside its approved schema. Technical combinations such as GPU and macOS are still information about the system; we do not describe reports as anonymous.

Reports pass through the UltimateVJ HTTPS receiver to a private Walz Media developer board for investigation. Board credentials stay on the server and are not supplied by the app. No report grants remote access to your Mac.

Report retention and choices

The documented app queue holds at most five unsent reports and expires them after seven days. Temporary delivery failures retry with a delay. Turning automatic reporting off clears unsent reports and cancels an in-progress request. Turning runtime debugging off also turns automatic reporting off.

When processing reports, the receiver removes deduplication receipts older than seven days. Receipts contain report IDs and card references; cleanup depends on report processing, so inactive stored receipts can remain longer. Accepted reports remain on the private developer board until developers manage them; no automatic board-card deletion interval is established here. Turning reporting off does not retract a report already accepted.

The diagnostic route disables request logging and uses an in-memory network-address rate limit. It does not copy addresses or request headers into report cards or receipts. Ordinary hosting logs are a separate operational concern.

Local debugging and exports

Local runtime debugging is off by default according to the manual. When enabled, it writes a bounded journal under ~/Library/Logs/UltimateVJ/Diagnostics/, retaining a current and previous log of approximately 1 MiB each. Older entries rotate out.

Export Runtime Report creates a local Markdown file that combines current measurements with journal history. This is not the same payload as an automatic report. Local error messages can include media names or file paths. Review the file before sharing it. Exporting a file alone does not send it to the developer board.

The app's sets, preferences, autosave and recovery files are also local application data. Referenced media is not automatically uploaded by the diagnostic receiver. See Sets, presets and storage for locations and recovery behavior.

Optional email updates

The manual describes a separate, optional app signup for UltimateVJ updates, news and free visuals from Walz Media. Email signup is not required to use the app. Continuing through the welcome screen does not submit the email field, and diagnostic reports do not include an email address.

If you choose to sign up, the address and subscription request necessarily enter the mailing workflow. The documented flow requires a separate email verification and confirmation step, with a single-use link that expires after 24 hours. Consult the signup/confirmation notice and runtime guide for that flow. This page does not establish an email-list retention period or make a claim that mailing delivery was verified in the current package.

Links to other services

Homebrew, the release archive and linked reference/support sites handle their own requests under their policies. Following an external link can expose request information to that destination. This website's aggregate-event description does not describe those services' data handling.

For a privacy or report question, contact Walz Media and identify which flow you mean: website measurement, an automatic report, a file you shared manually or an email subscription. Do not include passwords, licence secrets or unrelated private media in a support message.