Last updated Milebit, Inc.
This Privacy Policy describes how Milebit, Inc. ("we", "us", or "our") collects, uses, and protects information when you use the Milebit, Inc. mobile application, website (milebit.io), and related services (collectively, the "Services").
By using Milebit, Inc. you agree to the practices described in this Privacy Policy.
We may collect information you voluntarily provide, including:
Name, email address, phone number
Account credentials
Fleet or company information (if applicable)
Subscription or billing status (if enabled)
Communications with support, service providers, or partners
Driver documents you add, such as your commercial driver's license (CDL) and DOT medical examiner's certificate: the photo or file and the fields you enter or confirm (for example name, licence number, class, endorsements, state and expiry date).
Work records, if you drive for a carrier that uses these features: loads assigned to you (stops, times, reference numbers, freight documents such as bills of lading and proof of delivery, and charges), pay summaries and settlements your carrier records for you, repair orders for your truck, fuel purchases, and pre-trip inspections. For fuel cards we keep only a label and the last four digits of the card number.
Referral and promotional codes you enter.
Milebit, Inc. provides routing, navigation, and live-location features.
We may collect:
Real-time GPS location
Background location data only with your explicit permission
Live-location data used for navigation and sharing
Key clarifications:
If the app is closed and background permissions are disabled, location tracking does not occur.
Background location data is collected only with your explicit permission.
Live-location data is shown in real time. A location history is also kept: for a driver, positions recorded during a trip; for a fleet, positions of its vehicles. How long that history is kept depends on the fleet's plan — see Data Retention below.
Milebit, Inc. does not maintain a user-facing "places visited" history.
Friends. When you and another driver become friends, each of you can see the other's live location on the map. This is on by default for every friend. You can turn it off for one friend or for all friends in the app at any time.
Public map. You can choose to appear on the public map, so that drivers who are not your friends can see your position, direction, speed and whether you are driving or parked. This is off unless you turn it on.
Your carrier. If you drive for a Fleet Customer, its authorized users can see your location as described in Section 5.
Live location may be used temporarily to provide nearby analytics and location-based features and is not retained after real-time processing is completed, except for limited operational caching described in Section 8.
Disabling location access may limit certain core features of the Services.
Routes you create are kept for as long as your account exists, and you can delete any route at any time. During a trip we record your positions as a location history. How long routes, trip records and location history are kept is described in Section 8.
We do not operate as a bank.
We do not store full payment card details.
Subscription payments are processed by Apple (App Store), Google (Google Play) or, for fleet accounts billed directly, Stripe.
Subscription-related records may be retained for accounting and compliance purposes and deleted in accordance with applicable laws.
Device and operating system information
App usage logs and diagnostics
IP address and security-related data
Analytics events (screens viewed, features used, time spent)
via Firebase Analytics and AppMetrica
Crash and error reports via Sentry, and app usage events via Firebase Analytics
You may opt out of analytics collection through the app settings.
With your permission, we may send push notifications related to:
Route updates and navigation alerts
Weather and road hazard warnings on your active route
Community activity
Account, billing, and security notices
You may disable push notifications at any time through your device settings or in-app preferences. We use platform notification services (Firebase Cloud Messaging for Android, Apple Push Notification Service for iOS) to deliver these notifications.
If your account is part of a fleet, the app may offer a Pre-Trip Inspection checklist. For each step of the checklist you photograph or record a short video of your truck or trailer.
Each photo or video is uploaded and automatically analyzed by an AI service (Google Gemini) to check that the shot matches the requested view and to flag possible vehicle defects visible in that frame.
This is a driver aid, not a mechanical certification: the AI does not clear a vehicle to drive, and a missed or misjudged defect does not mean the vehicle is safe.
Before a video is stored or sent for analysis, we remove the location and timestamp metadata your phone embeds in the file. This is separate from any location or time you choose to attach to the inspection itself.
If you are part of a fleet, your fleet's authorized administrators can see the photos, videos, and AI findings for inspections you submit (see Section 5).
An inspection you start but do not submit (a draft) is deleted, together with its photos and videos, after 48 hours. A submitted inspection is kept as part of your fleet's vehicle record — see Section 8.
Services Directory providers. If you post a listing through our Telegram bot, we collect your Telegram user ID, username and display name, the United States phone number you share through Telegram, the fact that you confirmed it with a one-time SMS code, the listing content (text, category, state, cities, optional address or map pin, price, hours, languages, delivery and halal details), up to five photos, and the contact details you choose to publish. We remove location metadata (EXIF) from photos. We also keep reports and recommendations drivers submit about listings, and moderation decisions.
We use information to:
Provide routing, navigation, and live-location features
Enable social and fleet-related functionality
Generate expense and route analytics
Improve and optimize the Services
Develop AI-based features using aggregated and anonymized data
Maintain security and prevent misuse
To run the Services Directory: to verify that a provider controls the phone number, to publish listings and the provider's chosen contact details to drivers signed in to Milebit, to review listings with automated tools and staff, to handle reports, and to remind providers before a listing expires.
Milebit, Inc. uses AI to analyze routes, predict optimal paths, and provide personalized route recommendations. AI features include:
Route ranking by time, cost, and safety with explanations for each recommendation
Predictive parking availability
Fuel cost optimization along planned routes
AI is also used to moderate what users post, to summarise and translate industry news, to answer questions in the in-product assistant for fleet accounts, to estimate vehicle damage from photographs, and to check pre-trip inspection photos and videos against the requested shot and flag possible vehicle defects.
Which providers process what. AI features are performed by third-party providers. Depending on the feature and our configuration:
Public text — community posts and comments for moderation, Services Directory listings, and news items for summaries and translation — is processed by Anthropic (United States), Google Gemini or DeepSeek. DeepSeek operates from China, so text sent to it is processed outside the United States.
Text that belongs to a carrier or to a private conversation — questions to the assistant for fleet accounts together with the company data needed to answer them, repair-order summaries, freight letters and dispatch messages you ask us to read, questions about your fuel plan, and messages to our support chat — is processed by Anthropic or Google Gemini (both United States). It is not sent to DeepSeek. We use both under their paid commercial API terms, which state that they do not train their models on content sent through the API.
If you ask the app to transcribe a voice message or translate a chat message, that message is processed by Google Gemini.
Freight documents you or your carrier upload for a load (such as bills of lading and proof of delivery) are read by Anthropic or Google Gemini to compare them with the load.
If you choose to scan a driver document, such as your CDL or medical certificate, to fill in its fields, the photo is sent to Anthropic or Google Gemini to read those fields. We do not store the scanned photo, and you confirm or correct every field before it is saved.
Photographs for damage estimates, and photos and videos for pre-trip inspections, are processed by Google Gemini or Anthropic.
Messages about road events in drivers' Telegram groups are processed by Google Gemini to extract the type and place of the event; names are removed.
Only the content needed for the feature is sent. We do not send your location history to these providers, and apart from what appears on a document you choose to scan, we do not send your contact details. Their own terms govern how they handle the content they receive; where a provider offers a setting that excludes customer content from model training, we use it.
We do not use automated decision-making that produces legal or similarly significant effects on users.
Chats with service providers are kept while your account exists; you may delete your messages at any time.
Messages may be deleted earlier upon user request.
Voice rooms are not part of the Services today, and no audio is transmitted, processed or stored. If the feature is introduced, this Policy will be updated before it is enabled, and microphone access will be requested only when you choose to join a room.
Road reports. You can mark road events on the map: accident, police, traffic, hazard, road closed and inspection activity. A report is placed at or near your current position, within two miles, and is visible to all Milebit users together with your display name. You can attach up to three photos. Before any photo is shown, faces and licence plates are automatically detected and blurred on our servers, location and other metadata are removed, and the original is deleted; if blurring fails, the photo is not published. Faces are located only to blur them: we do not recognise or identify people and keep no facial data. Other drivers can confirm a report or mark it as no longer there. A report stays on the map for two to three hours, longer if other drivers confirm it. Photos are deleted within 24 hours after the report ends. We keep the report itself (type, place and time) to improve road information; if you delete your account, it stays without your name. Some reports come from messages in drivers' Telegram groups, which we summarise with AI and publish without names. Do not use the app while driving. Milebit is not an emergency service: in an emergency, call 911.
Community feed. Posts, comments and photos you publish in the community feed are visible to all Milebit users with your display name. Text is checked by AI before it appears, and other users can report posts to us.
Finding friends from your contacts. If you choose to find friends from your phone contacts and confirm that you want to upload them, the phone numbers and names from your address book are sent to our servers to check which of them belong to Milebit users. We use them only to suggest friends to you, we do not contact the people in your address book, and you can delete the uploaded contacts at any time in the app settings. If you decline, nothing is read or uploaded.
Services Directory. Listing content and the contact details a provider chooses are shown to drivers signed in to Milebit. We do not sell this information.
If you use Milebit, Inc. through an employer, carrier, fleet, or other organization (a "Fleet Customer"), certain information may be visible to authorized representatives of that Fleet Customer (such as dispatchers, safety managers, or administrators) ("Fleet Admins"), depending on the account configuration and the features enabled.
Fleet Admins are employees or authorized representatives of the Fleet Customer, not Milebit, Inc. personnel.
Depending on configuration, Fleet Admins may access certain operational data necessary for fleet operations, such as:
Location sharing status, live location, and location history with timestamps
Routes created for work use (planned routes and stops)
Activity and usage related to fleet operations (e.g., trip status, feature usage in fleet workspace)
Pre-trip inspection records, including the photos and videos you submit and the AI-flagged findings for each one
Driver documents you add (such as your CDL and medical certificate) and their expiry dates
Loads assigned to you, freight documents, pay summaries and settlements
Repair orders for vehicles you drive, and fuel purchases
Pre-trip inspection reviews by the carrier's safety team, including requests to retake photos and their decisions
Your carrier may also use an AI assistant in its workspace to ask questions about its own fleet; to answer, the assistant uses the carrier's data, which can include the records above.
Your employer sees your location, and the sharing switch does not hide it from them. The switch in the app controls whether other drivers — the people on your friends list — can see where you are. It does not apply to the carrier you work for: while you are an active driver of a Fleet Customer, that carrier's authorized users can see your live position and your location history for as long as their plan retains it. If you do not want your employer to see your position, the only way is to stop sharing location with the app entirely, by revoking location access on your device — which also disables navigation and trip features.
Access levels depend on the Fleet Customer's configuration and permissions. Milebit, Inc. personnel are not Fleet Admins. Milebit employees may access limited account and usage information only for support, security, fraud prevention, or legal compliance purposes, subject to internal access controls.
Who is responsible for fleet data. For personal information that a Fleet Customer enters or collects through its workspace, the Fleet Customer decides how it is used and we process it on the Fleet Customer's behalf as its service provider (a "processor"). Requests about that information are best sent to the carrier; if you send one to us, we will pass it on. A data processing agreement is available to Fleet Customers on request at legal@milebit.io. For your own driver account and the features you use for yourself, Milebit, Inc. is responsible directly.
Data is stored on servers operated by Railway, with databases and file storage located in the United States. Encrypted backups are held with a second provider, also in the United States.
We apply industry-standard security measures, including encryption in transit and at rest.
Encrypted backups may be retained for up to 90 days.
How you sign in. A driver account is created and accessed with a Google account, an Apple account, or a mobile phone number confirmed by a one-time code sent over SMS. A fleet account is accessed with an email address and password, or with a Google account.
Two-factor authentication. A fleet account may be protected by a one-time code from an authenticator app, together with a set of single-use recovery codes. We store only the secret needed to verify those codes, encrypted, and never the codes themselves. Two-factor authentication is mandatory for Milebit, Inc. personnel who can access customer accounts, and optional for our customers.
Access from outside the United States. Our data is stored in the United States, but Milebit, Inc. personnel and contractors who support and develop the Services may access it from other countries. They do so under confidentiality obligations, through accounts protected by two-factor authentication, and only as needed for support, security and development.
Security incidents. If we learn of a security incident that affects your personal information, we will investigate it, take steps to contain it, and notify affected users, Fleet Customers and regulators without undue delay and as the law requires.
More detail and reporting. Our safeguards are described on the Security page. To report a vulnerability or ask a security question, write to legal@milebit.io.
No system is fully secure, and we cannot guarantee absolute security.
The Milebit website (milebit.io) sets essential cookies automatically for basic functionality and security, including remembering the cookie choice described below. Analytics and advertising cookies are set only after you consent through the cookie banner shown on your first visit — nothing beyond essential cookies runs before you choose.
With your consent, we use Google Analytics (GA4) to understand how visitors use milebit.io — pages viewed, buttons clicked, and similar aggregate behavior.
With your consent, we use the Meta Pixel (Facebook/Instagram) on milebit.io to measure our advertising and build audiences for future campaigns. The Pixel sets cookies in your browser and, together with our server, sends Meta a hashed, irreversible version of the email address you type into the waitlist form, along with your IP address and browser information, and events such as page views, waitlist form submissions, app store badge clicks, pricing toggle switches, blog opens, and sections viewed. We do not send your name or phone number to Meta from the website. This is what U.S. state privacy laws call "sharing" for cross-context behavioral advertising — see Section 10 for your rights and how to opt out.
You can accept or decline analytics and advertising cookies together in the banner, and withdraw that choice at any time using the "Do Not Sell or Share My Personal Information" link in the site footer, which withdraws consent immediately. If your browser sends the Global Privacy Control signal, we honor it as an opt-out of sharing without you needing to visit that link. Declining does not limit your ability to join the waitlist or use the site.
The website sends this data to Meta only after you accept the cookie banner. App versions that include the Personalized ads setting send this data only while that setting is on. It is on by default and you can turn it off at any time in Settings. On iOS, the app also sends it only if you allowed tracking when asked.
Location history: positions collected from a driver's device during a trip and from a fleet's connected telematics are stored as a location trail. The default retention is 7 days; a Fleet Customer may purchase a longer retention for its own fleet — 30 days, 180 days, or 1 year. The retention period is fixed at the moment each position is recorded, so buying a longer plan does not restore positions already deleted.
Routes and trip records: kept for as long as your account exists. A route is the record of a trip — dates, stops, mileage — and carriers must keep trip records for tax and regulatory reporting. You may delete any route yourself at any time, and all of your routes are deleted when your account is deleted. The detailed GPS trace of a finished trip is reduced when the trip ends and removed one year later.
Chats with service providers: kept for as long as your account exists, so that both sides keep the record of an agreed repair. You may delete your messages at any time, and your chat participation is deleted when your account is deleted.
Road reports: shown on the map for two to three hours, longer if confirmed. Photos are deleted within 24 hours after the report ends. The report record (type, place and time) is kept to improve road information; after you delete your account it stays without your name. Weigh station status reports are kept the same way as station history.
Driver documents: kept until you delete them or your account. Photos used only to scan a document are not stored.
Work records (loads, freight documents, pay summaries and settlements, repair orders, inspections): part of your carrier's business records and kept under its retention. When you delete your account, they stay with the carrier as described on our Data Deletion page.
Pre-trip inspection photos and videos: an inspection you start but do not submit (a draft) is deleted, together with its photos and videos, after 48 hours. A submitted inspection — including its photos, videos, and AI findings — is kept as part of your fleet's vehicle record, the same way other maintenance and inspection records are, for as long as the record is needed. It is not deleted when your account is deleted; instead, it stays with your fleet, no longer linked to your name or other personal identifiers.
Services Directory: a listing stays published for up to 90 days unless renewed. When a listing is removed or expires, its photos are deleted; we keep a record of the listing and of any reports and moderation decisions to handle complaints and prevent abuse.
Subscription records (if applicable): retained for accounting and compliance purposes for up to 12 months.
Backups: encrypted copies are kept for 90 days and then destroyed automatically.
We retain operational and analytics data for up to ninety (90) days, unless a longer retention period is required for legal, accounting, security, or compliance purposes.
Certain data, including billing records, transaction history, compliance logs, and audit records, may be retained for longer periods as required by applicable laws and regulations.
You may:
Request deletion of your personal data
Delete your account directly within the app (Settings → Delete Account)
Control permissions through device settings
Disable sharing and social features at any time
Request access to your personal data by contacting us via email
For privacy and data-related requests, contact legal@milebit.io.
For technical issues with your account, contact support@milebit.io.
If you are a resident of California, Virginia, Colorado, Connecticut, Texas, or another U.S. state with applicable privacy legislation, you may have additional rights, including the right to know what personal information we collect, request its deletion or correction, and opt out of the sale or sharing of your data.
Milebit, Inc. does not sell your personal information for money. We do share the personal information listed below with Meta (Facebook/Instagram) for cross-context behavioral advertising — on the website only after you accept the cookie banner, and in the app as described in Section 7.4 — which U.S. state privacy laws such as the CCPA/CPRA define as "sharing" even though no money changes hands. You can opt out at any time: in the app, turn off Settings → Personalized ads; on the website, use the "Do Not Sell or Share My Personal Information" link in the footer; on iOS, decline the App Tracking Transparency prompt. See Section 7 for how the website cookie banner and opt-out work.
Categories of personal information we collect: Identifiers (name, email, phone number), geolocation data, internet or network activity (app usage, device info), and commercial information (subscription status).
Categories of personal information we disclose for a business purpose: We share limited data with the service providers listed in Third-Party Services below, solely to operate the Services. This is separate from, and does not include, the disclosure described in the next paragraph, which is made for cross-context behavioral advertising rather than a business purpose.
Categories of personal information shared for cross-context behavioral advertising: identifiers (hashed email address, hashed phone number, advertising and app-installation identifiers, account ID, IP address, browser and cookie identifiers); internet and app activity; commercial information (subscription purchases). Category of third party: Meta Platforms, Inc.
To exercise your privacy rights, contact legal@milebit.io. We will verify your identity before processing your request and respond within the timeframe required by your state's law (typically 45 days).
If you access the Services from the European Economic Area,
the United Kingdom, or Switzerland, you have rights under the
General Data Protection Regulation (GDPR), including:
Right of access to your personal data
Right to rectification of inaccurate data
Right to erasure ("right to be forgotten")
Right to restrict processing
Right to data portability
Right to object to processing
Right to withdraw consent at any time
Right to lodge a complaint with your local supervisory authority
Legal bases for processing under GDPR:
Performance of a contract (providing the Services)
Legitimate interests (security, fraud prevention, service
improvement)
Consent (location, microphone, marketing communications)
Legal obligations (tax, accounting, compliance)
Note: Milebit Services are designed for U.S. truck drivers.
Personal data is processed and stored in the United States.
By using the Services from outside the U.S., you consent to
the transfer of your data to the U.S.
To exercise GDPR rights, contact legal@milebit.io.
Milebit, Inc. is intended for users aged 18 and older.
If a user is identified as under 18, the account will be blocked and removed.
We use third-party service providers to operate the Services. Each receives only the data needed for its function.
Hosting and databases: Railway (application servers and databases).
File storage: Tigris (profile photos, covers, uploaded documents). Encrypted backups are stored with Google Cloud Storage.
Routing and maps: HERE and Trimble (PC*Miler) receive the addresses and coordinates of the stops on a route in order to calculate it. Turn-by-turn navigation is provided by Mapbox, which receives the calculated route and your device location while navigation is active. Mapbox may also use anonymized location telemetry to improve its maps, as described in its privacy policy. Map and point-of-interest data also comes from OpenStreetMap and public U.S. government datasets.
Traffic and weather: TomTom (traffic incidents) and Weatherbit (weather along a route) receive the map area or route being viewed.
Text message verification: Telnyx receives your phone number to deliver sign-in codes.
Email delivery: Resend receives your email address to deliver sign-in codes, invitations and notices.
Push notifications: Firebase Cloud Messaging (Google).
Artificial intelligence: Anthropic (United States), DeepSeek (operated from China) and Google Gemini, as described in Section 3.
Error and crash reporting: Sentry receives technical details of errors, which may include your account identifier and the request that failed. Firebase Analytics receives app usage events.
App analytics: Google Firebase Analytics and AppMetrica (operated by Yandex) receive app usage events and device identifiers to help us understand how the app is used.
Advertising and analytics: With your consent, Google Analytics (GA4) receives website usage events. Meta (Facebook/Instagram) receives identifiers (hashed email address, hashed phone number, advertising and app-installation identifiers, account ID, IP address, browser and cookie identifiers), internet and app activity, and commercial information (subscription purchases), used to measure and target advertising. See Section 7 and Section 10.
Messaging bots: Telegram (operation of our bots for the Services Directory and support; message content, Telegram IDs and usernames).
Payments: Apple App Store and Google Play for in-app subscriptions; Stripe for fleet accounts billed directly. Milebit, Inc. never receives your full card number.
Telematics (only if your carrier connects it): Samsara or Motive. Your carrier controls whether the integration is enabled. Milebit, Inc. does not expand a Fleet Customer's access beyond what it is already authorized to access from that provider.
If you give us a mobile number to sign in, to confirm a Services Directory listing, or to confirm ownership of a USDOT number, we send a one-time verification code to it by text message. We do not send marketing or promotional text messages.
Your number is disclosed to Telnyx, the communications provider that delivers these messages for us, and only for that purpose. We do not sell or rent mobile numbers, and we do not share your consent to receive text messages, or the content of those messages, with anyone for marketing.
Separately, as described in Sections 7 and 10, a hashed form of the phone number on your account may be shared with Meta to measure and target our advertising, and you can opt out of that sharing as described there.
You can stop text messages at any time by replying STOP, and get help by replying HELP or writing to support@milebit.io. The full terms of the program are in the SMS and Text Messages section of our Terms of Service.
If Milebit, Inc. is involved in a future merger, acquisition, or investment, user data may be transferred as part of that transaction, subject to this Privacy Policy.
We may update this Privacy Policy from time to time. If material changes are made, we will notify users through the Service or by other reasonable means.
If you have any questions about this Privacy Policy or wish to exercise your privacy rights:
General inquiries: info@milebit.io
Privacy and legal requests: legal@milebit.io
Technical support: support@milebit.io
Questions about this document?
Write to us — we answer within a few business days.