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 subscription required), Trailmetry continuously processes 9-axis IMU data at 100–200 Hz using an on-device algorithm to detect potential impact events.

The algorithm analyses linear acceleration magnitude, angular velocity, jerk (rate of change of acceleration), and motion patterns to classify events as crashes, jumps, or uncertain. All processing is performed locally on your device — raw IMU data is never transmitted to our servers.

3.2 Post-Crash SOS Feature

If a crash is detected and the rider is unresponsive for 25 seconds, the app may attempt to send an SMS to user-configured emergency contacts containing a GPS location link. This feature requires:

• Android operating system
• SEND_SMS permission granted by the user
• Emergency contacts manually configured by the user in the app
• Active mobile network connection at time of crash

3.3 Data Collected by This Feature

• Impact event summaries — classification (crash/jump/uncertain), severity score, peak G-force, rotation, impulse, and duration are stored in your session file
• GPS at detection time — if GPS is available when an event is detected, coordinates are attached to the event record and stored locally in your session
• Emergency contact numbers — stored locally on your device in encrypted app storage only. Never transmitted to Trailmetry servers
• Raw IMU data — not stored persistently. Processed in memory only and discarded after classification

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 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