This policy covers the DeepTruck Verify website, workspace, carrier verification pages, and Chrome extension. It also applies when you receive a verification request without creating an account.
1. Who this policy covers
DeepTruck Verify (“DeepTruck,” “we,” “us”) provides tools for shippers to confirm carrier contacts, request documents, and keep a verification record. This policy explains our handling of information about account holders, carrier contacts, drivers, and people who contact us.
A shipper decides which carrier to check and which documents to request. If a shipper sent you a request, contact that shipper for questions about why it requested your information or how it uses its own copies. For information handled by DeepTruck, contact verify@deeptruck.io.
2. Information we handle
- Account details: your name, company name, email address, authentication information, and account identifiers.
- Carrier information: carrier name, USDOT and MC numbers, business contact details, and public registration, authority, and insurance information obtained from carrier profiles and public FMCSA/MOTUS sources.
- Verification records: the requesting account, email and phone confirmation results, document receipt status, request links, and timestamps.
- Uploaded documents: driver licenses, W-9 forms, insurance certificates, file names, and information contained in those files. These documents can contain sensitive personal information, including identification and tax information.
- Technical information: session tokens, browser and extension settings, cached carrier records, and request or error information handled by our hosting and service providers.
- Support messages: information you send when you contact us.
Passwords are submitted to our authentication provider to sign you in. The extension stores session tokens rather than saving your password.
3. How we use information
We use information to create and authenticate accounts, look up carriers, send requested verification emails and SMS codes, receive documents, display verification progress, and provide the requesting shipper with a record. We also use information to respond to support requests, investigate abuse, troubleshoot the service, and meet applicable obligations.
We do not sell personal information or use carrier contacts, uploaded documents, or extension data for advertising or data brokerage.
4. Chrome extension & local storage
On Central Dispatch carrier pages, the extension reads page content to identify the USDOT number and relevant carrier contact information. It uses that information to display a carrier profile and let you start a verification. Carrier lookups can contact public FMCSA/MOTUS endpoints; verification requests are sent to the configured backend.
The extension uses Chrome storage for account sessions, settings, carrier information, and cached verification results. Settings saved through Chrome’s sync storage may be synchronized by Chrome according to your browser settings. The workspace also uses browser storage to maintain your signed-in session.
The extension does not collect unrelated browsing history. Its use and transfer of user data are limited to the disclosed carrier verification features, related security needs, and applicable legal requirements, consistent with the Chrome Web Store User Data Policy, including its Limited Use requirements.
You can sign out, remove the extension, or clear browser storage. These actions do not automatically delete verification records or documents already sent to the service. If you configure a different backend, information you send to that backend is also subject to its operator’s policies.
6. Storage & security
The production service sends information over HTTPS. Uploaded documents are stored in a private storage bucket, and authenticated document access uses temporary signed links. Authentication and access checks help restrict workspace records to the requesting account.
No system can guarantee complete security. Protect your account, verification links, and downloaded files. Do not send passwords, SMS codes, or sensitive documents to our support email unless we have specifically arranged a suitable way to receive them.
Our providers may process information in countries other than your own, including the United States. Their infrastructure and legal requirements affect where information is handled.
7. How long information is kept
Account information, verification records, and documents remain in the service to support account access and verification history. We do not currently apply an automatic expiry period to every verification record or upload.
You can request deletion by contacting us. We may need to retain some information to meet legal obligations, resolve disputes, or investigate abuse, and provider backups may persist for a period after deletion. Copies retained by a requesting shipper are managed by that shipper.
8. Your choices & requests
Contact verify@deeptruck.io to request access to, correction of, or deletion of information handled by DeepTruck. Depending on your location, applicable law may provide additional rights, including objection, restriction, or portability. We will evaluate requests under applicable law and may ask you to verify your identity or authority before acting.
If you received a verification request, you can choose not to submit documents and contact the requesting shipper to discuss an alternative. A shipper may need certain information to continue its business process. Uninstalling the extension stops its access to carrier pages on your device.
9. Business use & children
DeepTruck Verify is intended for business users aged 18 or older. It is not directed to children. If you believe a child has provided personal information through the service, contact us so we can investigate and address it.
10. Updates & contact
We may update this policy as the service or our practices change. The date at the top identifies the current version. We will provide appropriate notice of material changes when required.
For privacy questions or requests, email verify@deeptruck.io. The rules for using the service are set out in our Terms of Service.