Privacy Policy

1. Introduction

Trailmetry ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application and website.

Trailmetry is a mountain bike telemetry platform that interfaces with third-party BLE (Bluetooth Low Energy) sensors — including WitMotion IMU sensors (CE/FCC certified) and standard Bluetooth heart rate monitors — to provide suspension analysis, riding metrics, and experimental safety features.

2. Information We Collect

3. Experimental Crash Detection Feature Android Only

3.1 How It Works

When a WitMotion WT9011DCL sensor is mounted on a helmet and paired with the app (Android only, Pro Connect subscription required), Trailmetry continuously processes its motion data (acceleration and rotation, about 100 Hz) with an on-device algorithm to detect potential impact events.

The algorithm analyses impact acceleration, rotation speed, changes in head orientation and the rider's movement before and after the event to classify it as a crash, a jump/landing or an uncertain event. All detection is performed locally on your device. Sensor data is never transmitted to our servers.

Detection keeps working with the phone locked or the app in the background, provided location access is set to "Allow all the time" and the helmet sensor stays connected via Bluetooth.

3.2 Post-Crash SOS Feature

When a crash is detected, the app starts a countdown and alerts you with a sound, vibration and a lock-screen notification. You can cancel at any time with the "I'M OK" button, in the app or directly on the notification. If you do not respond, an SMS containing a link to your GPS position is sent to the emergency contacts you configured.

The SMS is sent automatically by the Trailmetry server through our SMS provider, without any action on your part. This feature requires:

• Android operating system
• A Trailmetry account, signed in, with an active Pro Connect subscription
• Emergency contacts (up to 2) configured by you in the app
• A mobile data connection at the time of the crash (if there is none, the app keeps retrying automatically and sends the alert as soon as the connection returns)
• Location access granted, for the GPS position to be included

Automatic SMS is available for contacts in the countries offered in the app (European countries, French overseas territories, Japan, Australia, New Zealand and Mexico). For other countries, or if the server cannot send the message, the app opens your phone's SMS app with the message ready, and you must then press Send yourself.

If you tap "False alarm" after an alert was sent, your contacts receive a second SMS telling them you are OK.

To protect the service against misuse, the number of automatic alerts is limited (per user, per contact and per day). When a limit is reached, the app uses your phone's SMS app instead.

After an alert is sent, the app disconnects the bike sensors to save battery and saves the ride in progress. Tapping "False alarm" reconnects them.

3.3 Data Collected by This Feature

Stored on your device only:

• Impact event summaries: classification (crash/jump/uncertain), severity score, peak impact, rotation, and the timeline of the alert (countdown, "I'M OK", SOS sent) are stored in your session file
• Helmet trace: the peak impact and rotation recorded during the ride, and a short window of sensor data (about one second) around each detected event, stored in your session file so you can review it in the session analysis
• GPS at detection time: if available, coordinates are attached to the event record in your session
• Emergency contact numbers: stored in the app's storage on your device

Sent to our server only when an SOS or false-alarm message is sent:

• Your emergency contact numbers, your GPS position (if available), your rider name and the app language, used only to write and deliver the SMS
• Your account identifier, to check your subscription and apply the alert limits

This data is processed on Amazon Web Services servers in the European Union (Ireland). SMS are delivered through Amazon's messaging service and mobile network operators. To prevent duplicate alerts and misuse, technical records are kept for a limited time: contact numbers in anti-abuse counters for up to 2 days, alert identifiers (without phone numbers or position) for 7 days, and monthly usage counters for 40 days. Server logs, with phone numbers partially masked, are kept for up to 30 days. This data is never used for marketing and never sold.

Before adding someone as an emergency contact, make sure they agree to receive SOS messages from you.

3.4 Limitation of Liability

By enabling this feature, you acknowledge and agree that:

• Trailmetry provides this feature on an "as-is" basis with no warranty of any kind
• Trailmetry accepts no liability for failure to detect a crash, failure to send or deliver an SOS, or any injury, loss, or damage arising from use or non-use of this feature
• You assume full responsibility for your safety while riding
• This feature does not replace a riding buddy, trail awareness, or appropriate protective equipment

4. Heart Rate Sensor Integration

4.1 Compatible Devices

Trailmetry connects to any standard Bluetooth Low Energy (BLE) heart rate monitor using the standard Heart Rate Service (UUID 0x180D / Characteristic 0x2A37), including devices from:

• Garmin (HRM-Pro, HRM-Dual, etc.)
• Polar (H10, H9, Verity Sense, etc.)
• Wahoo TICKR series
• CooSpo, CycPlus, and other ANT+/BLE dual-mode monitors
• Any device advertising the standard Bluetooth Heart Rate Service

Trailmetry does not endorse any specific heart rate monitor brand. The devices listed above are examples of compatible hardware only.

4.2 What We Do with Heart Rate Data

Heart rate data is used exclusively to:

• Display live BPM during a ride session
• Record BPM alongside suspension and GPS data points in your session file for post-ride review
• Enable correlation analysis between rider exertion and suspension activity — for example, identifying sections where high heart rate coincides with rough terrain or heavy braking
• Optionally display HRV (heart rate variability) from RR interval data if provided by the sensor

4.3 What This Feature Is Not

4.4 Heart Rate Data Storage

• BPM values are stored as part of your local session file alongside other telemetry data
• If cloud sync is enabled, heart rate data is included in the encrypted session upload to AWS
• Heart rate data is never shared with third parties or used for advertising purposes
• You can delete any session (including its heart rate data) at any time from within the app

5. Data Storage and Synchronization

5.1 Local Storage (No Account)

5.2 Cloud Storage (With Account)

• Session data (suspension, GPS, heart rate, impact summaries) is synchronised to AWS cloud infrastructure
• Amazon S3: Session files, exported data
• Amazon DynamoDB: User profiles, session metadata, trail records
• All data is encrypted in transit (TLS 1.3) and at rest (AWS encryption)
• Raw IMU data from crash detection is never uploaded — only the processed impact summary is stored

6. How We Use Your Information

6.1 Core Functionality

• Analyse suspension performance and provide tuning recommendations
• Generate riding insights and progress tracking
• Enable session comparisons and historical analysis
• Correlate heart rate with suspension activity for ride analysis
• Provide experimental crash event logging and SOS features (Android, opt-in)

6.2 Service Improvement

• Improve algorithm accuracy and recommendations
• Develop new features and functionality
• Optimise app performance and user experience
• Conduct anonymised research on riding patterns and suspension behaviour (opt-in only)

7. Information Sharing and Disclosure

7.1 Service Providers

We may share information with trusted service providers who assist in:

• Cloud infrastructure and data storage (AWS)
• Analytics and app performance monitoring
• Customer support and communication services
• Payment processing (if applicable)

7.2 Emergency SOS

When the SOS feature triggers, the app sends an SMS directly from your device to your pre-configured emergency contacts using your device's messaging system. This SMS is sent by your device — not by Trailmetry's servers. Trailmetry does not receive, store, or process the content of SOS messages.

8. Your Privacy Rights

8.1 Access and Control

• View and download your riding data at any time
• Modify account information and preferences
• Control data synchronisation settings
• Export data in standard formats
• Disable crash detection or heart rate features at any time
• Delete emergency contacts from app storage at any time

8.2 Deletion Rights

• Delete individual riding sessions including all associated sensor data
• Remove account and associated cloud data
• Request complete data deletion by contacting us
• Uninstall the app to remove all locally stored data

9. Data Security

9.2 Access Controls

• Limited employee access to personal data
• Role-based permissions and monitoring
• Multi-factor authentication for admin access
• Regular access reviews and updates