Pulse App Privacy Policy

1. Introduction

This Privacy Policy describes how Dynam Labs, Inc.("Dynam Labs," "we," "our," or "us") collects, uses, stores, and shares information when you use the Pulse mobile application ("Pulse" or the "app") on iOS or Android.

Pulse operates in two modes that share the same app binary but differ in how they connect to your vehicle:

• Companion mode— a remote keyfob paired with your in-car MCU over Bluetooth (and, in the future, UWB). Pulse does not open a direct CAN connection and does not uplink vehicle telemetry to Dynam's cloud.
• Standalone mode — a direct CAN bridge to your vehicle via a USB, Bluetooth (WiCAN), or network adapter. You may optionally enable Cloud Connectto sync vehicle telemetry with Dynam's cloud services.

By using Pulse, you agree to the practices described in this policy. For our general website privacy practices, see our site Privacy Policy.

2. Information We Collect

2.1 On your device (both modes)

When Pulse is connected to a vehicle (directly or via the MCU relay), the app processes telemetry received over the vehicle CAN bus, including:

• Speed, state of charge, range, gear, charging status, and related driving data
• Diagnostic fault codes and subsystem status
• Speed and, when available, location (latitude, longitude, heading) — by default from the vehicle CAN bus / onboard GPS; you may switch to your device's location services as the source in app settings
• Trip and drive-log history, including high-frequency telemetry snapshots
• Fault history with timestamps and telemetry context at the time of each event
• App settings, display preferences, and unit preferences
• Vehicle profile information you provide, such as a display name and Vehicle Identification Number (VIN) when entered
• Your device timezone (IANA name and UTC offset) for labeling telemetry timestamps

This data is processed on your device to power the cluster, diagnostics, drive log, and related features. It is stored locally unless you choose to enable Cloud Connect in standalone mode (see below).

2.2 Companion mode

In addition to the data above, companion mode may collect:

• A paired MCU identifier stored in your local vehicle profile after pairing
• Bluetooth scan and pairing metadata (such as device name and signal strength) while discovering and pairing with your MCU

Companion mode does not uplink vehicle telemetry, VIN, or trip logs to Dynam's cloud.

2.3 Standalone mode

In addition to the data above, standalone mode may collect:

• CAN adapter connection preferences, such as a Bluetooth peripheral identifier, TCP host and port, or USB serial device path
• A WICAN Bluetooth authentication key, stored in your device's secure storage after you provision it (including via on-device QR code scan)
• Connection health and link status for your chosen transport

2.4 Cloud Connect (standalone mode, opt-in)

If you enable Cloud Connect in standalone mode, Pulse enrolls your device with Dynam's cloud and may transmit:

• Your vehicle VIN and a per-install device identifier
• An enrollment token you provide from the Dynam partner portal
• A device certificate (via certificate signing request) for mutual TLS authentication
• Live vehicle telemetry frames, including location and speed (from whichever source you have selected), state of charge, range, gear, charging status, active faults, and link health
• Trip metadata (trip identifier, start and end times, distance, energy, state-of-charge delta, and trip-log checksum) when a drive session ends
• Full trip log files — uploaded only when explicitly requested by a remote cloud command, not automatically with every trip

Unsent telemetry may be buffered locally in an offline queue until a network connection is available. Cloud Connect is disabled by default and can be turned off at any time in app settings.

2.5 Analytics and crash reporting (both modes)

Release builds of Pulse may include optional third-party services for product analytics and crash reporting. When enabled, these services receive:

• An anonymous per-install identifier (random, not tied to your identity)
• App version, platform (iOS or Android), and Pulse operating mode
• Screen and navigation events within the app
• Feature usage events (such as mode changes, pairing completion, or connection status)
• Crash reports and scrubbed error logs

We do not send raw CAN payloads, VIN, or precise location coordinates to analytics or crash reporting services.

3. How We Use Information

We use the information described above to:

• Display real-time vehicle data in the cluster, diagnostics, and drive log
• Record and replay trips, faults, and driving history on your device
• Maintain your vehicle profile, connection settings, and app preferences
• Provide optional cloud connectivity and fleet or owner services when Cloud Connect is enabled
• Diagnose app crashes, fix errors, and improve app reliability and usability
• Understand anonymous product usage patterns to guide development

We do not use vehicle telemetry or location data for advertising, and we do not sell your personal information.

4. Data Stored on Your Device

Pulse stores data locally in your app's private storage, including:

• A local database (SQLite) with vehicle profiles, trip metadata, fault history, settings, and an offline cloud telemetry queue when applicable
• Trip log files with high-frequency vehicle telemetry
• Cached map tiles for static trip route previews in Drive Log (not used for navigation)
• An app diagnostic log file
• Secure storage for the observability anonymous identifier and WICAN Bluetooth keys

You can manage local data in Settings → DATA, including clearing trip history, map cache, app logs, or resetting all app data (which wipes the database, trips, diagnostics, themes, and cache).

5. Data Sharing and Third Parties

We share information only as described below:

Pulse does not offer turn-by-turn navigation, route planning, or charging-station search. Those features are available on the in-car MCU app only.

Sentry, PostHog, and TomTom process data according to their own privacy policies, available at sentry.io/privacy, posthog.com/privacy, and tomtom.com/privacy.

6. Device Permissions

Pulse may request the following device permissions depending on your mode and features:

• Bluetooth — to pair with your MCU in companion mode, or to connect to a WICAN CAN adapter in standalone mode
• Camera — standalone mode only, to scan a QR code for WICAN Bluetooth key provisioning; images are processed on-device
• USB — standalone mode only, for USB SLCAN CAN adapters
• Foreground service (Android) — to maintain an active Bluetooth connection to a CAN adapter while the app is in use
• Location— when you choose device as the speed/location source, Pulse uses your phone's location services (iOS and Android); when you choose vehicle, location comes from the car's GPS signal over CAN and phone location is not used for display or logging
• Location (Android, legacy) — on Android 11 and below only, a legacy Bluetooth scan permission that may request location access; on Android 12 and above, Bluetooth scan is declared as not used for location

You control whether speed and location come from the vehicle or your device in app settings. Device location is collected only while Pulse is in use and you have selected that source.

7. Location Data

Pulse can display, record, and (when Cloud Connect is enabled) uplink location and speed from one of two sources — your choice in settings:

• Vehicle (default):coordinates and speed from the car's GPS and CAN telemetry
• Device:coordinates and speed from your phone's location services while the app is in use

Trip logs, drive-log maps, and cloud telemetry use whichever source is active at the time. Switching sources does not retroactively change past trip data.

• Companion mode:location and speed are processed and stored on your device only; they are not sent to Dynam's cloud.
• Standalone mode:location and speed are stored locally in trip logs; they are transmitted to Dynam's cloud only when Cloud Connect is enabled (live telemetry) or when a full trip log is uploaded on remote request.

8. Companion vs Standalone Summary

9. Data Retention

Data stored on your device is retained until you delete it through in-app controls, reset all app data, or uninstall the app. Cloud Connect data retained on Dynam's servers is kept for as long as needed to provide the cloud services and as required by applicable law. You may contact us to request deletion of cloud-associated data tied to your vehicle enrollment.

10. Your Choices

• Cloud Connect: disabled by default; enable or disable at any time in standalone mode settings
• Local data: clear trip history, map cache, app logs, or reset all data in Settings → DATA
• Uninstall: removing the app deletes local app data from your device
• Contact us: request access to or deletion of cloud-enrolled data by emailing us (see Contact Us below)

11. Children's Privacy

Pulse is not intended for children under 16 years of age. We do not knowingly collect personal information from children. If you believe we have collected information from a child, please contact us immediately.

12. International Users

Dynam Labs is based in the United States. If you use Pulse from outside the United States, your information may be processed and stored in the United States or other countries where our service providers operate. Depending on your location, you may have rights to access, correct, delete, or restrict processing of your personal data. To exercise these rights, contact us using the information below.

13. Changes to This Policy

We may update this privacy policy from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons. We will post the updated policy at this URL with a revised "Last Updated" date. Material changes may also be communicated through the app or other reasonable means where appropriate.

14. Contact Us

If you have questions, concerns, or requests regarding this privacy policy or our data practices for Pulse, please contact us at: