PulseWidth Classic privacy

Account and cloud files

UBT Performance, LLC operates PulseWidth Classic and PulseWidth Tuning. Sign-in links the app to your account, vehicle, entitlements and PWT project revisions. Vehicle identifiers, including a VIN when provided, are linked account data rather than anonymous records.

Completed project datalogs are queued for upload automatically; offline uploads retry after connectivity and account access return. PWT attachments and recovery captures may upload with account, vehicle, revision, integrity and timestamp information. These files support your chosen tuning, diagnostics and recovery workflows.

Phone permissions

USB access supports the attached vehicle adapter. A visible connected-device service supports user-started vehicle sessions. Notification permission supports service and account messages.

Performance uses foreground GPS and motion sensors for measurements. Optional sunrise/sunset lighting uses a rounded location stored on the phone, with a control to forget it. These features do not require background location. Their current measurement/theme processing is local; any file you choose to share may include its recorded content.

Fingerprint or supported face authentication unlocks a saved device session through Android. PulseWidth does not receive your biometric template. This is separate from account passwords, 2FA and server-side passkeys.

Optional dashboard music

If you enable dashboard music and grant Android Notification access, PulseWidth reads the active media player's song title, artist and playback state to show them on your dashboard. Supported playback buttons send commands to that player; the player controls audio playback and routing. PulseWidth does not read notification message bodies or store your listening history, and this music feature does not upload track metadata. You can turn it off in Settings or revoke Notification access in Android.

Information visible inside PulseWidth, including music titles, can be seen by a participant if you separately accept an in-app remote session.

Optional remote sessions and voice

Remote Tune lets an authorized participant view your PulseWidth app window and current vehicle readings after you accept a request on your device. The request identifies the participant and offers view-only access or control. Sharing is confined to PulseWidth's own window and dialogs, not other apps or the system screen. Any account, vehicle, project or log information visible in that window may be shared. You can stop control or end the session using the visible session controls.

Voice is a separate choice during a session. Microphone permission is requested when you turn voice on. Audio is transmitted live through our encrypted service connection to the connected participant; PulseWidth does not retain audio recordings or screen-frame recordings. Mute stops microphone transmission, and ending voice or the session releases the microphone. A participant may independently retain information they receive.

Our services process session requests, participant/account and device identifiers, connection details, timestamps, consent/control events, duration and usage counts to operate and secure the session. Session history does not contain screen pixels, typed text or audio. These operational records follow the security-record retention target below. Ordinary logs or project files separately saved or uploaded retain their normal account-file handling.

Access, providers and security

Account services process authentication, device activation, license history, cloud storage and operational security records. Service providers handle hosting/storage, transactional email, payments and push delivery. When you choose or authorize a tuner connection, the assigned independent tuner or shop may access your name, email and customer ID; VIN and vehicle profile; logs and tune files; notes and log conditions; read, flash and log operation history; and device or push identifiers used for tune/log workflows. Access is limited to the assigned customers and projects, not open browsing. Transfers within that authorized connection do not require a separate confirmation for each transfer.

Account IDs, device/push identifiers, request IP addresses and operational errors may be processed to run and protect these services. Do not place personal information in filenames or notes unless necessary. Encryption protects data but does not make it anonymous.

Retention and deletion

We keep account files while providing your account and recovery services. Recovery baselines are protected against accidental overwriting. That protection is not a blanket exception to an account-deletion request.

Our operating targets are removal of account-associated data within 30 days of a deletion request and expiry of residual backups within 90 days, subject to necessary verification and specifically disclosed exceptions. Routine security records use a 90-day target. Necessary accounting records follow a separately reviewed schedule; they do not justify keeping all your PWT files or logs.

Request deletion through Account & deletion, or email support@pulsewidthtuning.com if you cannot sign in. Deletion affects the shared account across Android, Windows Classic and the website. We explain any narrowly retained records and confirm verified completion. Independently exported copies remain under your control.