Data Safety Summary

At a Glance

Location data collected

Yes — precise

Background location

No

Camera or microphone

No

Data sold to third parties

Never

Encrypted in transit

Yes

Data deletion on request

Yes *

Account required

Yes

Financial / payment data

No

* FMCSA-mandated records are exempt from deletion until the regulatory retention period (6 months) expires.

Google Play — Data Safety Form Reference

The table below maps to the categories in the Google Play Data Safety section.

Data type	Collected	Shared	Purpose	Required	Encrypted
Personal Information
Name (first & last)	Yes	Yes	App functionality, regulatory compliance	Required	Yes
Email address	Yes	No	Account management	Required	Yes
Phone number	Yes	No	Account management	Required	Yes
Driver's license number	Yes	Yes	FMCSA ELD compliance	Required	Yes
Profile photo	Optional	Yes	Driver identification	Optional	Yes
Location
Precise location (GPS)	Yes	Yes	HOS log entry — FMCSA required	Required	Yes
Financial Information
Payment / financial data	No	No	—	—	—
Health & Fitness
Health or fitness data	No	No	—	—	—
Messages
Messages / email / SMS	No	No	—	—	—
Contacts
Contacts	No	No	—	—	—
App Activity
App interactions (screen views, feature use)	Yes	Yes	Analytics — anonymised, sent to Firebase	Optional	Yes
Crash logs / diagnostic data	Yes	Yes	App stability (Firebase Crashlytics)	Required	Yes
Device or Other Identifiers
Device ID / anonymous crash identifier	Yes	Yes	Crash reporting (anonymised)	Required	Yes
Bluetooth device pairing identifier	Yes	No	ELD hardware pairing & reconnection	Required	Yes

App Permissions & Why They Are Used

Permission	Platform	Purpose
ACCESS_FINE_LOCATION NSLocationWhenInUseUsageDescription	Both	Record precise GPS coordinates with each HOS log entry as required by 49 CFR § 395.26
BLUETOOTH / BLUETOOTH_CONNECT / BLUETOOTH_SCAN NSBluetoothAlwaysUsageDescription	Both	Discover, pair, and communicate with compatible ELD Bluetooth hardware to read vehicle data
INTERNET	Android	Sync HOS logs, DVIR records, and driver data with the cloud backend
READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE	Android	Export ELD log files for roadside inspection transfer
VIBRATE	Android	Haptic feedback for alerts and notifications
SYSTEM_ALERT_WINDOW	Android	Display HOS limit warnings as overlay alerts while using other apps

Apple App Store — Privacy Nutrition Labels

Data Used to Track You

Baaj ELD does not use any data to track users across apps or websites owned by other companies for advertising purposes.

Data Linked to You

The following data types are collected and linked to your identity:

Contact Info: Name, email address, phone number
Identifiers: Driver's license number, user ID
Location: Precise location (at time of duty status change)
Usage Data: App interactions, HOS log actions
Diagnostics: Crash data (linked to anonymised user ID)

Data Not Linked to You

Diagnostics: Aggregate crash statistics not linked to personal identity
Device / Other IDs: Anonymised crash identifiers

Third-Party Services & Data Sub-processors

Service	Provider	Purpose	Data collected
Firebase Crashlytics	Google LLC	Crash reporting & error tracking	Device model, OS version, app version, anonymised user ID, crash diagnostics
Firebase Analytics	Google LLC	Aggregate app usage analytics	Anonymised screen views, feature interactions, session data

Analytics are configured with limited data collection. No advertising ID or personally identifiable information is sent. All events are anonymised at the point of collection.

Security Practices

All data transmitted between the App and our backend is encrypted in transit using industry-standard protocols.
Authentication credentials are stored in device secure storage and are never written to plain text.
User data stored on-device is logically isolated per account, accessible only to the App.
Passwords are never stored on device.
Our backend infrastructure applies role-based access controls and standard cloud security practices.