Privacy Policy
1. Who we are
The HaulMesh driver app (“the app”) is operated by Kotenko Roman Mykolaiovych, trading as HaulMesh (“we”, “us”), 47 vul. Shevchenka, apt. 82, Kaniv, 19003, Ukraine.
This policy explains what the driver mobile app collects, why, who it is shared with, and what control you have over it. The dispatcher dashboard at app.haulmesh.com is covered by the same policy; where the two differ, the difference is noted.
Contact for any privacy question or request: [email protected]
2. Short version
| Do we sell your data? | No. We do not sell or rent personal information, and we do not share it for cross-context behavioural advertising. |
|---|---|
| Do we show ads? | No. The app contains no advertising SDKs. |
| Do we track your location in the background? | No. The app does not request location permission and cannot read your device’s GPS. See §4.7. |
| Do we use analytics or tracking SDKs? | No. Only crash diagnostics (§4.8). |
| Who else sees your data? | The dispatcher you choose to link with, and the service providers listed in §6. |
| Can you delete your account? | Yes — in the app under Profile → Delete account, or at haulmesh.com/delete-account.html without installing anything. See §10. |
3. Accounts and roles
The app is for drivers. Creating an account requires an email address you can verify. A driver account is free.
A driver may link to a dispatcher. Linking always follows an explicit action — you accept an invitation, or you send a link request. Once linked, the dispatcher can see the data described in §5. You can unlink at any time (subject to having no active load in progress), which stops future sharing.
4. What we collect
4.1 Account data
Email address, password (stored only as a salted hash — we never see it), first and last name, phone number, country, and your display preferences (language, currency, metric/imperial units, time zone). We record whether your email and phone are verified, when you last signed in, and your account roles.
Why: to create and secure your account, verify it is you, and render the app in your language and units.
4.2 Driver profile
Insurance provider, policy number and expiry; home base city, state, country and its approximate coordinates; the maximum distance you are willing to run; availability status and notes; preferred equipment types.
Why: dispatchers use this to decide which loads to offer you, and insurance details are a legal prerequisite for hauling freight.
4.3 Truck data
Unit number, VIN, year, make, model, equipment type, dimensions and weight, axle count, hours-of-service ruleset, and capability flags (hazmat, TWIC, bonded, team driver). You choose per truck whether it is visible to dispatchers or private.
Why: truck dimensions determine which routes are legal for you, and equipment type determines which loads you can take.
4.4 Regulatory identifiers
Where you choose to provide them: carrier and operator numbers (such as MC, DOT or CVOR) and cross-border trusted-traveller details (such as a FAST card number and expiry). These fields are optional — leave them blank if you do not run cross-border.
4.5 Work records
Loads assigned to you, their status history and timestamps, cancellations and who initiated them, and aggregate counters such as loads completed and cancellation count.
4.6 Documents you upload
Photographs and files you attach to a load — typically bills of lading and proofs of delivery — with their file type and upload time. The app asks for camera and photo-library access only when you tap to attach a document; you can decline and the rest of the app keeps working.
4.7 Route planning data
When you plan a route, the app sends the start and destination points you select on the map, together with the dimensions of your selected truck, so a truck-legal route with bridge-clearance, restriction and incident warnings can be calculated. We count how many routes you plan each month to enforce the free-tier limit.
These are points you tap on a map. The app does not request location permission and does not read your device’s GPS, in the foreground or the background. If a future version adds device positioning, it will ask for permission first and this policy will be updated before it ships.
Map tiles are loaded directly from the OpenStreetMap tile servers by your device; those servers therefore see your IP address and which map areas you view.
4.8 Device and diagnostic data
A Firebase Cloud Messaging registration token and your platform (Android/iOS), so we can deliver push notifications about your assignments.
If the app crashes or hits an error, we send a diagnostic report containing the error and its stack trace, the app version, and the device model and OS version. We have not enabled the crash reporter’s personal-data collection option.
4.9 Support messages
If you contact support through the app, we store your message, our replies, and the email thread they travel over.
4.10 Data stored only on your device
Access and refresh tokens are held in the operating system’s encrypted keystore (Android Keystore / iOS Keychain). A local database caches your assignments and reference data so the app works offline, and queues actions taken offline until the connection returns. Uninstalling the app removes all of it.
5. What your dispatcher can see
Once you are linked to a dispatcher, that dispatcher can see: your name and contact details, your driver profile, the trucks you have marked public, your regulatory identifiers, your assignments and their status history, and the documents you upload against their loads.
Trucks marked private are not shown to dispatchers. Before you are linked to anyone, drivers appear in a “free drivers” pool visible to dispatchers, showing profile basics and public truck equipment so a dispatcher can invite you.
6. Who we share data with
We do not sell personal information. We share it only with the dispatcher you link to and with the service providers below, each acting on our instructions for the stated purpose.
Documents you upload are not sent to a third party: they are stored on our own servers in Toronto (§7).
| Provider | Purpose | Data involved |
|---|---|---|
| Google (Firebase Cloud Messaging) | Delivering push notifications | Push token, notification content |
| Sentry (servers in Germany) | Crash and error diagnostics | Error reports, app version, device model and OS |
| road511 | Truck-legal route calculation and road-condition warnings | Route start/end points, truck dimensions |
| HERE Technologies | Underlying routing engine, reached through road511 | The same route request |
| OpenStreetMap Foundation | Map tiles, fetched directly by your device | IP address, map area requested |
| Zoho Mail | Transactional and support email | Email address, message content |
We may also disclose data where legally required, or where necessary to establish or defend a legal claim.
7. Where your data is processed
The app is offered to drivers in Canada and the United States.
Our servers, including the storage holding your uploaded documents, are located in Toronto, Canada. HaulMesh is operated from Ukraine, so our personnel access those systems remotely from there.
Two of the providers in §6 process data outside Canada: Sentry stores crash diagnostics on servers in Germany, and Google (Firebase Cloud Messaging) delivers push notifications through its global infrastructure, including the United States. Route requests go to road511 and HERE; map tiles are fetched by your device from OpenStreetMap servers.
By using the app you acknowledge this processing, carried out under the safeguards described in §9.
8. How long we keep it
| Data | Retention |
|---|---|
| Account and profile | While your account is active |
| Assignments and documents | 7 years — freight and tax records must be retained by law |
| Route-planning counters | Reset monthly |
| Crash diagnostics | 90 days |
| Support messages | 3 years |
When you delete your account we remove or anonymise your personal data, except records we are legally required to keep, and except data that has become your dispatcher’s own business record — for example a completed delivery and its proof of delivery.
9. How we protect it
All traffic between the app and our servers is encrypted with TLS. Passwords are stored only as salted hashes. Tokens are held in the device’s hardware-backed keystore. Access to production systems is restricted to personnel who need it.
No system is perfectly secure; we cannot guarantee absolute security, but we will notify you and the relevant regulator where the law requires it after a breach affecting your data.
10. Your rights
Regardless of where you live, you can:
- See the data we hold about you;
- Correct it — most fields are editable directly in the app’s Profile tab;
- Delete your account and the data attached to it;
- Export a copy in a machine-readable format;
- Withdraw consent for push notifications, or for camera access, in your device settings.
Deleting your account
Two routes, both free and neither requiring you to contact us:
- In the app: Profile → Delete account.
- On the web, without installing the app: haulmesh.com/delete-account.html.
Deletion removes your account, profile, trucks and identifiers. Assignments and the documents attached to them are retained for the period in §8 because freight and tax law requires it, and because a completed delivery is also your dispatcher’s business record; they are unlinked from your identity where that is possible.
Regional rights
If you are in Canada, PIPEDA applies. You may ask for access to your personal information and challenge its accuracy, and you may complain to the Office of the Privacy Commissioner of Canada.
If you are in California, we do not sell or share personal information as those terms are defined by the CCPA/CPRA, we do not use it for cross-context behavioural advertising, and we will not discriminate against you for exercising your rights.
To exercise any of these, email [email protected] from the address on your account. We respond within 30 days.
11. Children
The app is a commercial tool for licensed commercial drivers and is not directed to children. We do not knowingly collect data from anyone under 18. If you believe a minor has created an account, contact us and we will remove it.
12. Changes to this policy
We will post any change on this page and update the “last updated” date. If a change materially affects how we use your data, we will notify you in the app or by email before it takes effect.
13. Contact
Kotenko Roman Mykolaiovych, trading as HaulMesh
47 vul. Shevchenka, apt. 82, Kaniv, 19003, Ukraine
Email: [email protected]