Valorem Driver App Privacy

Separate reviewer and beta environment

Valorem Driver Review connects to a separate test service and shows a Reviewer environment notice. Its assigned accounts and work records are fictional, including W-2 and independent-contractor examples. A shift test still collects the test phone's real location, and information a tester types or uploads is sent to the test service. Use fictional information only; do not enter genuine identity documents, tax identifiers, banking details, signed agreements or operational deliveries.

Reviewer shifts can use the tester's actual location away from a warehouse; this does not record a warehouse attendance check. The reviewer service does not send provider push notifications, SMS or live signature requests. In-app assignment notices remain available. Longer route and battery behavior and iPhone background behavior remain under evaluation; this beta does not establish full-shift reliability.

In the reviewer environment, ordinary messages, subjects, attachments, announcements and proposed edits require authorized Valorem Admin approval before delivery. Admin reviewers can inspect these submissions even when they are not conversation participants. Submission times, decisions, reasons and report/block actions are recorded. Previously approved text remains visible while an edit is pending; messages may be delayed while an Admin is unavailable. Individual blocking and reporting are available. System assignment, shift and earnings notices remain available without message review. No external message-screening provider is connected.

Information we handle

• Account and contact details, account identifiers, application answers, availability and onboarding status.
• Identity and vehicle evidence supplied for onboarding, including identity documents, Social Security numbers where requested, vehicle information and insurance evidence.
• Training activity, assessment results, assigned documents, signatures and signing audit information.
• Schedules, shift and attendance information, work messages and attachments, performance information and estimated driver payouts.
• Workplace incident reports and supporting evidence, including incident time and location, people involved, injuries, affected body areas, and first aid or medical help requested or received when supplied in a report. This can include health information about the reporter or another person.
• Assignment versions, accepted First Shipment and Subsequent Shipment rates, acceptance time, and authorized rate-override reasons and history. These records support assignment terms and the corresponding earnings statements.
• If you choose direct deposit enrollment: account-holder name, optional middle initial, payee nickname, primary email, bank routing and account numbers, account type, consent and review history, and the payment method selected for a statement.
• Personal contractor records you choose to enter, such as receipts, expenses, mileage, odometer evidence and home-office planning information.
• On-duty location information, device notification identifiers and technical information needed to operate and secure the service.

Estimated payouts are informational. They are not official payroll records, filed tax returns or a guarantee of payment. Personal expense tools organize your records and provide planning information; they do not file tax returns. Detected GPS stops do not by themselves confirm deliveries, determine payable units or establish tax deductions.

Location and device permissions

An eligible driver can request a location check for a warehouse. During a shift the driver starts, the app uses background location to record route points and detected stops and display the on-duty position to authorized dispatch personnel. Background collection can continue while the screen is locked or another app is open. Ending a shift stops local tracking and, when offline, queues the shift end for synchronization. Device permissions, connectivity and operating-system restrictions can affect updates.

Location collection is limited to authorized driving duties. Applicants, off-duty users and staff without driving duties are not intended to be tracked. Camera and file access support evidence or attachments you choose to provide. You can manage device permissions in your device settings; removing a permission can prevent the related feature from working.

How information is used and accessed

We use information to administer accounts, review applications, provide onboarding and training, manage authorized work, support dispatch and communication, display estimated payouts, provide personal recordkeeping tools, respond to requests and protect the service.

Incident information supports authorized safety and incident follow-up. Access follows the app's incident permissions and assigned-team or explicitly granted operational scope. The app does not diagnose or treat injuries, monitor health, or dispatch emergency services. In the reviewer environment, use fictional incident and injury information only.

Access depends on account status, work arrangement and specific permissions. Applicants have limited application and onboarding access. Team operations are restricted to authorized roles and scopes. Personal contractor records are private; an administrator role alone does not grant access to those records.

Direct deposit enrollment is optional. Submitted banking details are encrypted in application storage. Ordinary lists and statements display only account suffixes; an active administrator must verify their password and authenticator before opening full details for review. Notification alerts do not contain banking details. Enrollment and payment records do not themselves send a bank transfer. Stopping direct deposit blocks future payment records using that enrollment but does not recall an external transfer or erase historical records. Banking records are covered by the same preservation and deletion-request limitations described below.

An administrator may explicitly grant approved Partner accounts read-only access to current on-duty driver positions and retained on-duty route and stop history. Access is limited to the drivers covered by the grant, and can include retained history from before the grant. A location grant does not permit off-duty collection or access to private contractor records.

Service providers

Features use service providers for hosting and storage, notifications, training video, electronic signatures and mapping or address lookup. These include Render, Expo and the relevant Apple or Google notification services, Mux, SignWell, and Geoapify for authorized address lookups. Map displays also request tiles from the configured map service. Information sent depends on the feature used and may include contact or account details, device/network information, document and signing information, or coordinates needed for an authorized lookup.

Partner mobile route previews are drawn in the app without requesting street-map tiles. If an authorized viewer chooses Open Map for a current location, the selected coordinate is sent to OpenStreetMap in the browser. That link contains no driver name or account credential; the map service also receives normal browser/network information.

Company bookkeeping is maintained separately in Quicken Business & Personal. The app has no direct Quicken API connection. Any enabled business-file imports use sanitized business-only exports.

Retention targets and required records

The following periods are the company-selected targets for ordinary app data. They are not a claim that automated expiry already operates throughout the pilot.

Account information, estimated payout history and personal contractor files are kept while needed for their account or recordkeeping purpose. Their remaining routine-expiry rules are being finalized. A valid deletion request will be reviewed individually, including any specific retention obligation.

Written company schedules for applications, required work-history evidence and signed documents are being mapped to the applicable record types, governing events and legal requirements. Unresolved record classifications, missing trigger dates and specific preservation holds prevent automatic destruction. We will explain which records must remain and the applicable period or release criteria rather than treating all app data as subject to one blanket period. A hold remains until its required written release is verified.

When a required record must remain, access and use are limited to its justified purpose. A retained agreement does not automatically require keeping all messages or detailed GPS history. Signed originals and necessary signing evidence are preserved unaltered for their applicable retention period.

Privacy and account-deletion requests

Email [email protected] for access, correction or deletion requests, including if you cannot sign in or have uninstalled the app. For deletion, use the subject Valorem Driver account deletion and include the email address associated with your account. No reason for requesting deletion is required.

The company owner handles requests. We aim to acknowledge them within 7 calendar days. We may need to verify that the account or information is yours. Do not email your password, full tax identifiers or identity-document images; we will explain a suitable verification method if needed.

Our adopted target for the completed deletion program is ordinary deletion from active systems within 30 calendar days of receipt, following necessary verification and subject to specific retention obligations. During the current pilot, complete deletion tooling is still being implemented. We will tell you what can be completed, what remains pending, why particular records are retained, and the expected next step. Applicable legal request deadlines still apply.

The separate reviewer build offers an in-app request in Privacy & Account and a reviewer account-deletion request page. These tools apply only to reviewer accounts. The operational pilot continues to use the email route above. The reviewer workflow supports reviewed account removal and separately restricted retention of justified records, but full retained-record, external-copy and backup verification is not complete. Test account erasure is not proof that all copies have been removed. Uninstalling the app, signing out or submitting a request does not itself erase server records. Account deletion does not itself alter worker classification or settle a payment.

Our planned backup process will distinguish active-system removal from residual backup expiry and prevent removed data from reappearing during recovery. An offline device cannot be wiped immediately. Copies you independently exported to another destination may remain under your control.

Safeguards and updates

We use access controls and protected storage for sensitive information. Onboarding identity files use encrypted storage and restricted access. No security measure eliminates every risk. Contact us if you believe information has been accessed improperly or if your request needs further attention.

We will update this notice as the app, enabled services and retention/deletion processes change. The date at the top identifies the latest version.