Your choice, remembered

Updates & privacy.

Keep your apps current. Choose whether to help us understand the kinds of Macs people use.

Checking for a newer app

In app versions that include update checking, VCC Plus and DriveWire can check this website when they launch. The check sends the app name, version and build number. If a newer compatible download is available, you can open its DMG download. Installation remains your choice. A failed check does not interrupt your emulator or DriveWire session.

Optional platform statistics

The first check asks whether you will share basic platform information: your macOS major and minor version, Apple Silicon or Intel processor family, primary language, configured region and a random installation ID. Choose Share or Don't Share. Either choice is remembered across app updates, and update checks and downloads work with either choice.

The region comes from your Mac's language and region preferences; it is not a measurement of your location. The random installation ID helps estimate how many installations use each app. It is not derived from your hardware and does not identify a person or prove that two installations are different Macs.

Change your mind

Open Updates & Privacy in the app to change sharing or automatic launch checks. You can also reset its installation ID. Resetting starts a new statistical identity; it does not delete earlier history. The two apps use separate IDs. Routine app updates do not reset your choice or ask again.

What the update service records

The private update history records the time, app version and build, whether a newer download was offered, and download-button selections. A download selection does not prove a download finished or that an app was installed. Optional platform information and installation IDs are recorded only when sharing is enabled. A random request ID prevents a retried request from being counted twice.

The update history does not store IP addresses. The website, network providers and hosting security systems necessarily receive network addresses and may keep their own operational logs. Those logs are separate from optional app statistics. The update service does not request precise location, hardware serial numbers, hardware UUIDs, network-interface addresses, your account or computer name, file paths, documents, disk contents or assistant conversations.

Website visits

The production website uses Matomo, hosted at webtrack.dzhost.me, to understand page visits and link activity. This website analytics is separate from the apps' optional installation statistics and does not receive an app installation ID from the updater. The website tracker honors the browser's Do Not Track preference and does not run on local previews. Hosting and security systems may also maintain operational access logs.

Website searches

Website search sends submitted words to our VCC Plus Fess service. Website-wide search includes the manuals; manual-library search stays within the web manuals. We use our Matomo service to record successfully submitted search terms, whether the website or manual-library search was used, and the number of matches when available. This helps us understand which information visitors need. Typing alone does not send a search or search-analytics event. Browsing another results page or using Back and Forward does not create another submitted-search event.

Search analytics honors your browser’s Do Not Track preference. Search terms are recorded as explicit search events, rather than as part of ordinary page-view or referrer URLs. Fess, hosting systems and Cloudflare may also process queries and keep operational logs. Avoid entering private information into search. In-book section search runs locally in your browser and does not send its words to Fess or create search-analytics events.

Private update history

The history and dashboard are restricted to the site administrator. Records are retained for release and platform analysis until the administrator explicitly changes retention. They are not used for advertising or sold. These statements describe the app update service; ordinary website browsing and optional external services have their own network behavior.

Feedback requests

The feedback form sends your chosen product, request type, message and any contact details or screenshots you supply to our private request database. No account is required. Ordinary feedback can be anonymous; removal requests require contact information, and an email address is required when you ask for an email response. Technical details are optional and entered by you. Opening the form from an app preselects its product; it does not upload logs, documents or machine information.

Brian uses these requests to review problems, consider improvements, respond and maintain the products and Software Library. Requests and screenshots are available only to the administrator and are not published as public tickets. A notification containing a short excerpt and supplied contact email is sent to Brian. Notifications and any replies use Gmail, operated by Google. Private notes and screenshots are not automatically included in replies.

The feedback pages contain no website analytics loader. Entered messages and contact details are not sent to Matomo, Fess or update statistics, and are not linked to an app installation ID. The form uses a browser-session cookie to protect submissions and private administration, plus temporary keyed security counters to limit abuse. Ordinary hosting and security logs remain separate.

Active requests are kept while being processed. Closed requests are retained for 24 months, spam for 30 days, and screenshots for 90 days after closure unless the request is reopened for an active investigation. Screenshots are processed to remove embedded metadata. To request a correction or removal of your personal information, submit another request with your earlier reference. Email already sent cannot be recalled.

View the current Mac downloads →

A closer look

Open original