UnoHive UnoHive
Back to MotorHub

MotorHub Privacy Policy

Last updated: February 25, 2026

This Privacy Policy applies specifically to the MotorHub fleet command network. For our company-wide practices, please review the UnoHive General Privacy Policy.

1. Data We Process

  • Fleet Registry Data: VIN, registration, permits, insurance and loan metadata synced by owners/associations.
  • Driver Profiles: License IDs, shift schedules, compliance status, health & safety attestations.
  • Telemetry Streams: Location traces, speed, temperature, yard dwell metrics, device diagnostics.
  • Operational Events: Queue assignments, dock timestamps, service tickets, SLA outcomes.
  • Business Records: Invoices, settlements, dues, reimbursements, digital signatures.
  • Account & Access Logs: User IDs, roles, session metadata, audit trails.

2. How We Use This Data

  • Operate shared fleet dashboards for owners, associations, and enterprise control towers.
  • Trigger automations for safety, compliance, service scheduling, and SLA governance.
  • Generate telemetry analytics, queue intelligence, and executive summaries.
  • Provide audit evidence for federation obligations, regulator requests, or insurer reviews.
  • Improve MotorHub reliability, security, and user experience.

3. Legal Basis

Processing is grounded in legitimate business interests of participating enterprises/federations, fulfillment of service agreements with UnoHive, and compliance obligations (transport regulations, tax, safety).

4. Sharing & Federation Access

  • Shared Source of Truth: Fleet owners/associations and enterprise ops teams can mutually view agreed datasets.
  • Vendors: Secure integrations with telemetry providers, OEMs, ERPs, CRMs, insurers, or regulators per contract.
  • Service Partners: Garages, yard operators, or logistics partners receive limited data required to fulfill work orders.
  • No Advertising Resale: We do not sell MotorHub data for marketing purposes.

5. Retention & Deletion

Data is retained for the duration of your MotorHub contract plus any statutory record-keeping period. Upon termination, datasets can be exported to the customer, anonymized for benchmarking, or securely purged upon written request.

6. Security Measures

  • Role-based access control with federation + enterprise scopes.
  • Encryption in transit (TLS 1.2+) and at rest (AES-256).
  • Continuous monitoring, audit logs, anomaly alerts, and SOC-grade infrastructure.
  • Incident response procedures and regulator notification commitments.

7. Data Residency & Transfers

Primary hosting is in India with optional geo-fenced clusters per enterprise agreements. Cross-border transfers occur only with contractual safeguards (SCCs, DPAs, or regulator-approved clauses).

8. User Controls & Requests

  • Data export (JSON/CSV) via admin console or API.
  • Correction or deletion requests via federated data stewards.
  • Granular access revocation for operators, partners, or subcontractors.
  • Support for subject rights (access, rectification, restriction) where applicable law requires.

9. Third-Party Telemetry Devices

When you connect OEM or aftermarket sensors, their respective privacy policies apply in addition to this document. UnoHive only ingests telemetry authorized through your contracts.

10. Updates to this Policy

We may revise this policy when new modules launch or regulations change. We will notify primary contacts and surface in-app banners. Continued use of MotorHub constitutes acceptance of updates.

11. Contact

Related Documents