Privacy Policy
This Privacy Policy explains how Systemics Inc., d/b/a Echelon Fleet Systems (“Echelon,” “Echelon Fleet Systems,” “we,” “us,” or “our”), operating exclusively at https://echelonfleet.com and its subdomains (app.echelonfleet.com, api.echelonfleet.com), collects, uses, processes, isolates, and safeguards personal and operational data across our multi-tenant motorcoach fleet operating system, driver portal, and third-party OAuth integrations.
Echelon supports enterprise Single Sign-On (SSO) via Google OAuth 2.0 and Microsoft Identity Platform (Microsoft Entra ID / Azure AD). Echelon's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We never sell user data, never use OAuth profile or workspace data for advertising, and never use customer or OAuth data to train generalized artificial intelligence or foundational machine learning models.
1. Overview & Scope
Echelon provides an enterprise cloud software platform for passenger motorcoach, charter, shuttle, and transit operators. Our platform powers automated charter quoting, vehicle and driver dispatch optimization, FMCSA 49 CFR Part 395 Hours-of-Service (HOS) and Electronic Logging Device (ELD) compliance tracking, IFTA fuel tax reporting, and commercial billing workflows on echelonfleet.com.
When an enterprise motor carrier or fleet operator (a “Customer” or “Tenant”) provisions a workspace on Echelon, the Customer acts as the Data Controller (or “Business” under CCPA/CPRA) for the fleet, passenger, and driver records stored within its isolated tenant, and Echelon acts as the Data Processor (or “Service Provider”) governed by our Data Processing Addendum (DPA). For direct website visitors, account registrants, and demo workspace requestors on echelonfleet.com, Echelon acts as an independent Data Controller.
2. Categories of Data Collected
We collect and process only the minimum data necessary to operate the Echelon console, authenticate users, maintain regulatory records, and execute customer-authorized integrations:
- Account, Identity & Authentication Data: Full name, work email address, organization name, role-based access control (RBAC) permissions, bcrypt password hashes (for password-authenticated accounts), and OAuth 2.0 / OpenID Connect subject identifiers (sub, oid, tid) and verified email claims provided by Google or Microsoft Entra ID.
- Driver Qualification & Credential Metadata: Commercial Driver's License (CDL) class, state, endorsements (e.g., Passenger “P” endorsement), expiration dates, DOT medical examiner certificate status, and clearance badges (such as TWIC, DoD installation access, or airport tarmac security credentials) entered by the fleet operator for dispatch eligibility verification.
- FMCSA 49 CFR Part 395 ELD & Hours-of-Service (HOS) Logs: Duty status transitions (Off-Duty, Sleeper Berth, Driving, On-Duty Not Driving), 10-hour driving and 15-hour on-duty passenger-carrying rule counters (49 CFR § 395.5), 60/70-hour rolling cycle records, driver log certifications, co-driver assignments, and annotated audit trails of any supervisor edits.
- Fleet, Vehicle Telematics & Geospatial Route Data: Vehicle Identification Numbers (VINs), license plates, odometer and engine hour readings, real-time GPS coordinates, deadhead and charter route geometries, and geofenced airport / stadium / convention center ground transportation zones processed via Google Maps Platform APIs (Places, Routes, Distance Matrix, and Geocoding).
- Financial, Charter Billing & IFTA Tax Records: Charter quotes, trip orders, facility fee line items, customer invoices, payment status metadata synchronized with Stripe or Intuit QuickBooks Online, and state-by-state IFTA mileage and fuel purchase ledgers.
- Security, Audit & Technical Telemetry: IP addresses, TLS session metadata, browser user-agent strings, request timestamps, and immutable security audit logs recording authentication events and administrative actions.
3. Google OAuth 2.0 & Google API Services User Data Policy (Limited Use Disclosure)
“Echelon's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.”
When you choose to sign in or connect your workspace using “Sign in with Google” on https://echelonfleet.com, Echelon requests only the minimum OAuth 2.0 scopes required to authenticate your identity and operate user-requested features:
- openid, email, and profile: Used strictly to verify your work email address, match your identity to your authorized Echelon tenant, populate your display name and avatar in the console, and enforce multi-tenant Row-Level Security (RLS).
- Google Maps Platform APIs (Places, Routes, Geocoding): Used to geocode charter pickup/dropoff stops, calculate commercial motorcoach mileage and drive times, and identify airport or venue ground-transportation geofences. Location queries sent to Google Maps APIs are bound to trip locations rather than personal consumer profiling.
Strict Limited Use Commitments:
- We never sell, rent, or trade Google user data to any third party.
- We never use Google user data for targeted advertising, retargeting, creditworthiness scoring, or data broker enrichment.
- We never use Google user data to train, fine-tune, or improve generalized artificial intelligence or foundational machine learning models.
- Human employees at Echelon do not read or access Google user data unless explicitly authorized by the account holder for a specific support request, required for security abuse investigation, or mandated by applicable law.
- Users may revoke Echelon's Google OAuth access at any time from /console/settings or directly via their Google Account Third-Party Access settings.
4. Microsoft Identity Platform (Microsoft Entra ID / Azure AD) OAuth & SSO Disclosure
Enterprise tenants may authenticate users through the Microsoft Identity Platform (Microsoft Entra ID / Azure Active Directory) using OAuth 2.0 and OpenID Connect (OIDC) with Proof Key for Code Exchange (PKCE).
- Scopes & Claims Processed: Echelon requests only standard delegated identity scopes (openid, profile, email, User.Read) and reads the directory Tenant ID (tid), Object ID (oid), User Principal Name (upn / preferred_username), and assigned security group claims.
- Purpose of Processing: Microsoft Entra ID claims are used exclusively for enterprise Single Sign-On (SSO), automated tenant domain binding, Role-Based Access Control (RBAC) mapping (e.g., Org Admin, Dispatcher, Finance, Safety Officer, Driver), and immutable security audit logging.
- No Unauthorized Graph Access: Echelon does not read employee mailboxes, Microsoft Teams messages, OneDrive files, or broader directory graphs beyond the authenticated user's basic sign-in profile. Enterprise administrators may revoke consent at any time via the Microsoft Entra admin center or /console/settings.
5. Twilio 10DLC SMS / A2P Messaging & Driver Dispatch Notification Privacy
Echelon delivers transactional operational SMS notifications to commercial drivers, dispatch personnel, and charter group primary contacts (such as dispatch assignments, schedule changes, HOS approaching-limit alerts, and vehicle gate arrival notifications) via registered A2P 10DLC channels.
“No mobile information or SMS opt-in consent data will be shared with third parties or affiliates for marketing or promotional purposes. Drivers and contacts may opt out of SMS notifications at any time by replying STOP, or reply HELP for assistance.”
Message frequency varies based on active trip dispatches and safety alerts. Standard message and data rates may apply. All text messaging originator opt-in data and consent records are strictly excluded from any third-party sharing, except with our direct telecommunications carrier subprocessor (Twilio Inc.) solely for message transmission.
6. FMCSA ELD (49 CFR § 395.22 / § 395.30) & GPS Telematics Retention
Because commercial motorcoach carriers are subject to federal Department of Transportation (USDOT) and Federal Motor Carrier Safety Administration (FMCSA) recordkeeping mandates, Echelon enforces specialized retention and immutability controls on regulated operational records:
- ELD & HOS Record Integrity (49 CFR § 395.30): Original driver duty status records cannot be overwritten or erased. Any supervisory proposed edit requires driver certification and retains the original record alongside an immutable audit trail showing the timestamp, actor, and reason annotation.
- Statutory Retention Periods: ELD records of duty status (RODS) and supporting documents are retained for a minimum of six (6) months in accordance with 49 CFR § 395.8(k), Driver Vehicle Inspection Reports (DVIRs) for a minimum of three (3) months (49 CFR § 396.11), and IFTA fuel tax and distance records for four (4) years per International Fuel Tax Agreement audit requirements, unless the Customer configures a longer retention policy or exports and terminates its workspace.
- Demo Workspaces: Ephemeral demo workspaces created via /demo are isolated sandbox environments preloaded with public FMCSA census metadata and synthetic sample trips. You may purge your demo workspace at any time from the console.
7. CCPA/CPRA, GDPR, Data Subject Rights & Contact
Depending on your jurisdiction (including the California Consumer Privacy Act / California Privacy Rights Act (CCPA/CPRA), state privacy statutes in Virginia, Colorado, Connecticut, and Texas, and the EU/UK General Data Protection Regulation (GDPR)), you have the right to:
- Request access to and a portable copy of the personal data we hold about you;
- Request correction of inaccurate or incomplete personal information;
- Request deletion of your personal data (subject to mandatory FMCSA/DOT and tax statutory retention exceptions where applicable to commercial drivers);
- Object to or restrict certain processing, and withdraw OAuth or cookie consent at any time without affecting the lawfulness of prior processing;
- Be free from unlawful discrimination for exercising any privacy rights. Echelon does not “sell” or “share” personal information for cross-context behavioral advertising as defined under the CCPA/CPRA.
If your data is stored inside an enterprise Customer's fleet tenant (for example, as a driver or dispatcher employed by a motorcoach operator), please direct your request first to your employer (the Data Controller), or email us and we will coordinate with your organization's administrator in accordance with our Data Processing Addendum.
Systemics Inc., d/b/a Echelon Fleet Systems — Privacy & Compliance Office
Domain: https://echelonfleet.com
Privacy Inquiries & DSR Requests: privacy@echelonfleet.com
Security & Vulnerability Reports: security@echelonfleet.com
Legal & OAuth Verification: legal@echelonfleet.com
Questions regarding OAuth verification, privacy, or enterprise compliance? Contact legal@echelonfleet.com or privacy@echelonfleet.com.