1. Scope and contact
This policy describes how Nomadic Express LLC handles information in Load Settle Pro and the related company website at drivenomadic.com. The service supports authorized company accounts, driver settlements, transportation records, fuel and expenses, documents, reports and business communications.
For privacy questions, corrections or deletion follow-up, contact exnomadic@gmail.com. You can also submit a privacy request without signing in, including after company access ends.
This policy concerns the service. It does not replace a separate employment, independent-contractor, carrier, equipment, dispatch or payment agreement.
2. Information we handle
Information comes from you, authorized company users, imported business documents and the operation of the service. It can include:
- Accounts and profiles: names, email addresses, account and company identifiers, assigned roles, account status and sign-in/session information. Driver records can include contact details, profile photos, truck or trailer assignments, driver type, pay method and rate, and fuel-card references.
- Business and financial records: driver/payee references, settlement periods, load references and locations, shipper/receiver details, mileage, revenue, fuel purchases, additions, deductions, expenses, payment dates and record status. Historical records can include relevant driver and company snapshots.
- Documents: receipts, driver documents, images and PDFs; filenames, types, sizes and record associations; and extracted text or proposed fields used for review.
- Communications and service activity: messages, sender and recipient identifiers, read timestamps, support requests and privacy correspondence. Configured email delivery processes selected recipients, subjects, message content, attachments, delivery status and provider references. Sign-in and service operation can also produce security, error and delivery information.
A location recorded on a receipt or load document is different from continuous device-location tracking. Provide only the information needed for the task. Do not include passwords, recovery codes, full payment-card details, government identifiers, medical records or unrelated sensitive information in ordinary messages.
3. Why information is used
- Provide authorized account access and the records needed for an assigned role.
- Import, organize, review and correct settlements, fuel, expenses and supporting documents.
- Generate reports and PDFs and support authorized business communications.
- Investigate reported calculation, import, access and recordkeeping problems.
- Maintain necessary transaction evidence, resolve disputes and meet applicable obligations.
- Protect access and handle support or privacy requests.
Access to company information does not authorize unrelated uses. Software terms are not blanket consent to every possible use of personal information. A materially different purpose requires appropriate notice and any permission required by law.
4. Documents, imports and OCR
The standard document-reading workflow uses browser-based OCR and extraction to help populate fields for human review. OCR can misread dates, amounts, names and rows. Compare proposed values with the original, resolve flagged items and check totals before confirming a record.
Saving a business record or uploading an original receipt can send information to the application server and storage. Browser-based OCR does not mean every document or extracted value stays only on your device. Upload only records you are authorized to provide.
5. Who may receive or access information
Authorized company users. Drivers, dispatchers, accounting users and administrators access information within their assigned roles and permissions. Business access is for authorized work, not unrestricted use of another person's information.
Service providers. Cloudflare supports website/server infrastructure. Supabase supports authentication, the database and file storage. Configured transactional email uses Resend and can include a selected recipient, message content and attached business PDF. Each provider receives information needed for the relevant service; this does not mean every provider receives every category.
Exports and disclosures. Authorized downloads and email exports create recipient-controlled copies. Check the destination and included records before sharing. Specific records may also be disclosed to authorized professional advisers or authorities when necessary for a legitimate business purpose or applicable obligation.
Provider systems and recipients can handle information in locations different from yours. For questions about a particular record, recipient or processing location, contact exnomadic@gmail.com. Account deletion does not automatically erase downloaded, emailed or independently controlled copies.
6. Cookies and browser storage
The service uses sign-in, refresh and password-recovery cookies to support account access and security. Cookie expiry is separate from retention of company records or provider logs. Blocking or clearing sign-in cookies can require you to sign in again.
Browser storage remembers preferences such as the light/dark theme. Session storage supports tutorial state and temporary workflow notices. If you use the offline-draft feature, an encrypted settlement draft is saved in that browser with your chosen passcode. Clearing browser data can remove a local draft and preferences; it does not delete company records stored by the service.
The privacy request form sends its submitted fields to the request service. It does not use the contact address to publicly confirm whether an account exists.
7. Retention and financial history
Ending an account and keeping a necessary company record are separate matters. A settlement can need enough historical identity to show whose work and payment it records. That does not justify retaining every profile field, photograph, message or temporary copy indefinitely.
Financial-record baseline: seven years
Our company baseline is seven years from filing the related tax return. Keep affected records longer when needed for unfiled returns, audits, disputes, contracts, legal holds or other applicable obligations. If the related return has not been filed, this filing-based clock has not started.
This is a company baseline, not a claim that every record has the same statutory retention period. It does not apply seven years to all personal information and does not authorize an automatic financial purge.
For other information, retention depends on its purpose and the circumstances below rather than a single fixed period:
- Login, sessions and profileProvide authorized access, maintain necessary contact details and protect accountsKeep operational details while needed for authorized access. After access ends, review login and profile information for deletion, separating any limited security evidence or information needed for a specific obligation.
- Settlements and financial evidenceAccounting, tax, transportation, contractual and dispute-related recordkeepingUse seven years from filing the related tax return as the company baseline. Keep affected records longer where required by an unfiled return, audit, dispute, contract, legal hold or other applicable obligation.
- Drafts, imports and temporary extraction dataComplete, check or correct the relevant workflowReview temporary copies for deletion when they no longer support a current task or correction. If a source document is needed as financial or dispute evidence, keep it under the corresponding record rule rather than as an indefinite temporary copy.
- Messages and operational recordsNecessary business communication and supporting evidenceKeep information while needed for the business matter, a documented obligation or an active dispute. Review older material for deletion or minimization when that need ends. Supporting financial evidence follows the applicable financial rule.
- Privacy requests and verification evidenceHandle a request and document its outcomeUse only proportionate verification information. Keep a limited record of the request, decision and actions for accountability and legal needs; review additional identity evidence for earlier deletion once verification and any related dispute are resolved.
- Security and delivery logsSecurity, troubleshooting, abuse prevention and delivery trackingKeep logs for the time reasonably needed for those purposes, considering incident severity and applicable obligations. Preserve relevant evidence for an active incident or hold; review remaining logs for deletion or minimization when no longer needed.
- Backups and provider-held copiesRecovery and service operationBackup and provider copies may expire through their applicable recovery or retention cycles rather than immediately with an account request. Restrict retained copies to their recovery, security or legal purpose, and account for them when explaining what has and has not been deleted.
Relevant evidence may need to remain available under a specific dispute, investigation or legal hold. When the applicable purpose, obligations and holds end, review the information for deletion or appropriate de-identification. Information that remains linked to an identifiable driver is still personal information.
8. Removing access and requesting deletion
Remove Access is not account deletion. It stops access but does not by itself erase personal information or company financial history. Requesting deletion does not immediately delete an account.
A deletion request requires identity and authority verification, review of the relevant information, and consideration of applicable retention needs. We distinguish unnecessary account/profile information from records that must be kept for a documented reason. Necessary historical identity can remain without keeping an active login.
Messages, source documents, audit records, backups and provider copies require separate consideration. A receipt or approval is not confirmation that every deletion step is complete. Incomplete or unverified steps must remain identified as such. There is no guarantee of instant erasure or deletion of copies independently controlled by other recipients.
A request does not cancel amounts owed, waive a payment or settlement dispute, or authorize destruction of another person's records. Submit a privacy request or contact exnomadic@gmail.com for follow-up.
9. Requests, corrections and choices
Depending on the law that applies to you, you may have rights to request access or a copy, correction, deletion, restriction, objection or other choices concerning your information. Contact exnomadic@gmail.com to ask about a right, an authorized representative or review of a decision. Nothing in this policy limits rights you already have under applicable law.
Start with a contact address, the type of request and only enough context to identify the issue. Before disclosing or changing information, we need proportionate verification of identity and authority. A contact address alone is not proof of identity. Do not send identity documents or access credentials through the ordinary form or email; ask for an appropriate verification method first.
The public acknowledgement does not reveal whether an account exists. We assess requests under applicable requirements and explain relevant scope, retained information and reasons, and the outcome. You can ask for status or clarification through the privacy contact. Applicable legal response requirements still apply; this policy does not replace them with a different deadline.
A financial correction may require a traceable revision or adjustment rather than destruction of the original evidence. For a settlement concern, identify the settlement and disputed items through the company review channel. If you no longer have access, the privacy contact can direct your inquiry.
10. Security and updates
Sign-in controls, assigned permissions and authenticated document access help protect information. No internet service can guarantee absolute security. Report suspected unauthorized access through an established company channel; do not include passwords or recovery codes.
We may update this policy as practices or requirements change. The version and effective date appear above. Material changes require appropriate notice and any permission required by law; an update does not silently remove non-waivable rights. See also the Terms of Use.