Privacy and data use.
Updated 18 October 2026. Telemetry analysis is available in the DZ replay desktop app. The website provides downloads, guides and account services.
Imported telemetry
IBT and CSV files are parsed and analyzed on your computer by the desktop app. Preparing a replay, changing laps and opening the synthetic demo do not upload telemetry for server analysis. Imported sources, lap indexes, projects and replay settings are saved locally for the current account. Signing out does not delete these local files. Keep your original files and use desktop library controls to manage local copies.
Beta waitlist
If you join the beta waitlist, we store your email address, preferred language, signup time and invitation-consent version in PostgreSQL to review applications and arrange beta invitations. Joining does not create an account or grant access. We do not add your waitlist email to analytics events. Contact support@dzreplay.com to withdraw your application or request deletion. Existing operational records and hosting backups may remain under their retention arrangements.
Accounts and operational records
Email addresses, account identifiers, login sessions and access-management records are stored in PostgreSQL. Your first successful sign-in creates an account if you have access and no account exists for that email. Sign-in codes are hashed and expire after five minutes; sessions normally expire after seven days and can be revoked. Our email provider processes the address and code needed to deliver the sign-in message. We use an HttpOnly session cookie to keep you signed in.
The server no longer accepts telemetry analysis jobs or creates analysis processing records. Account, authorization, subscription, feedback and access audit records remain part of the online services. Historical records and hosting backups may remain under their existing retention arrangements. Application logs omit request bodies, telemetry, codes and cookies; hosting logs may include ordinary connection information.
Account language preference
In versions that support account language sync, signing in saves your current English or Chinese interface language to your account if no account preference exists. Later language changes update that preference. We store the latest language and update time with your internal account ID in PostgreSQL to restore the interface language when you sign in and select the language of account and invitation emails. This does not subscribe you to marketing. If no account preference exists, emails may use the language recorded with your beta application; otherwise they default to English. The language choice remains available locally while offline, and pending changes are retried when connected. Pending changes are stored separately for each account on this computer. Language sync is part of account preferences, separate from optional analytics; it does not upload telemetry, files or language history. You can change the language in the app or signed-in account page. Deleting your account deletes its language preference; hosting backups remain subject to their retention arrangements.
Optional Google sign-in
If you choose Google sign-in, Google provides your account identifier, verified email address, name and profile-picture URL. Our authentication service stores the identity details and authorization tokens returned by Google in PostgreSQL to authenticate you and link the same verified email to your existing DZ replay account and membership. We request only basic identity information, not access to Gmail messages or Google Drive files. You can revoke Google authorization in your Google Account settings. Revoking it does not delete your DZ replay account or immediately end existing DZ replay sessions; contact support@dzreplay.com to request account-data deletion.
Desktop device identification and limits
Desktop versions with device binding identify your computer to authorize access and manage device limits. The app reads the Windows MachineGuid locally, or tries the SMBIOS UUID if it is unavailable, and derives a SHA-256 hash with a DZ replay prefix. The original system identifier is not sent to our servers or saved by DZ replay. If no system identifier or previously saved system hash is available, the app uses a randomly generated, persistent installation ID. The installation ID and any system hash are saved in the local app data folder and retained through ordinary app updates and sign-out.
For activation and authorization checks, our service receives the device hash, installation ID, identity type (system or installation) and computer name. We store this information with your account in PostgreSQL, together with device and binding IDs, first registration and latest successful verification times, revocation times, device-removal records and related access audit records. These records are linked to your account and are not anonymous. This processing supports device authorization, access security and support; it is separate from optional analytics and track sharing and is not turned off by those switches.
The device-binding rules allow up to two computers per account, across all account tiers. Website sign-in does not use a device slot, and signing out of the desktop app does not release one. To activate a third computer, remove an existing device first. You can remove devices up to twice in any rolling seven-day period; each removal stops counting toward this limit seven days after it occurs. Clearing app data, reinstalling Windows or changes to the system identifier may require activation or device replacement again. Older desktop versions may have transitional authorization behavior; these rules describe versions that support device binding.
Removing a device revokes its authorization but does not erase its binding history, device-removal records or related audits. Those server records currently have no automatic time-based deletion schedule and are retained for device management, security and handling requests. The seven-day replacement window is a limit on removals, not a data-deletion deadline. Signing out or clearing local app data does not delete server records. Contact support@dzreplay.com to request access to, correction of or deletion of device information. Requests are handled manually; we will explain any information retained for legal or security reasons, and hosting backups may remain until their normal expiry.
Preferences on your device
Display units and your analytics choice are saved in local storage when your browser permits it. These preferences are separate from your lap data. Clearing site storage removes them.
Optional desktop usage analytics
Desktop releases with Amplitude configured can send usage events only after you allow them. Events are linked to your internal account ID and include app version, opening an analysis, imports, single-lap or two-lap analysis creation, replay starts, Live connection and fixed failure codes. Telemetry samples, original files, file names, email addresses, annotation text and screen recordings are not included.
Your choice applies to the current account on this computer and is separate from website analytics. Settings & account lets you turn it off. Unsent events are kept locally for up to seven days in a limited queue; turning analytics off or signing out clears that account’s pending events. Previously sent data is not deleted by this switch. Amplitude receives connection information needed to accept uploads; usage records are associated with your account and are not anonymous.
Optional track-section contributions
At desktop startup, you can separately opt in to sharing IBT track metadata and app usage analytics. Both default to off until you save your choice. With track sharing enabled, existing and newly imported indexed IBT recordings automatically contribute exact iRacing layout IDs, track lengths in metres, official section start percentages, recording dates when available, and source and format markers to DZ replay. Your internal account ID identifies the contributor. Files, file names, paths, driver names, cars, setups, lap times, GPS and driving samples are not sent. You can disable each choice in Settings for the current account on this computer. Disabling track sharing stops future uploads and cancels pending requests; metadata already received and internal review records remain for track-library maintenance. Only reviewed layout metadata is shared through the section lookup service; contributor identities and recording dates are not returned by that service. App usage analytics requires separate consent and does not authorize sharing driving data.
Optional desktop error reporting
Desktop versions configured for error reporting ask for separate permission before recording or sending error reports to Sentry in the United States. Reports contain error types, application code locations, app version, operating system name and abnormal process exit reasons. Raw error messages, account IDs, email addresses, user file paths, telemetry files, screenshots, recordings and memory dumps are excluded. Sentry receives network information necessary to accept uploads.
Your choice is saved for the current account on this computer. You can withdraw it in Settings & account. Turning it off or signing out cancels pending uploads and clears unsent reports. Reports expire locally after 24 hours, with expiry checked when the app next runs if it was closed. Each computer accepts at most 20 reports per rolling 24 hours and one per error per hour, with at most three retries per report. Already uploaded reports remain for up to 90 days (30 days on the free Developer plan) and are not deleted by this switch.
Optional usage analytics
Analytics availability is shown here when the page finishes loading. No optional analytics script is loaded before an affirmative saved choice.
If configured and allowed, Google Analytics measures website visits and interactions. Our page events use a fixed public page URL without query parameters, fragments or a referring page URL. Website analytics is separate from the desktop app's usage analytics.
Google Analytics may use cookies and process connection and device information to produce usage reports. We disable Google signals and advertising personalization in our analytics configuration. This is optional usage measurement, not a promise that no personal information is processed by the service. We respect browser Do Not Track and Global Privacy Control signals for analytics.
You can decline or withdraw analytics here. Withdrawal stops future events from this page and attempts to remove first-party Google Analytics cookies; it does not delete reports already collected.
See Google’s Privacy Policy and how Google uses information from partner sites.
Website delivery
The hosting provider receives network information needed to serve the website and online account services, such as IP address and requested URL, and may retain operational logs. Local telemetry analysis does not make online visits invisible to the hosting provider. Avoid placing personal information in URLs.