Account and authentication
Name, email, password-derived hash, verification and enabled state, email-verification time and method, account timestamps, last-login timestamps, authentication timestamps, and hashed server-side refresh-token records.
Public information
This page applies to haulveeo.com and app.haulveeo.com.
01 / Information
The information involved depends on how you interact with Haulveeo and what your organization chooses to enter in the application.
Name, email, password-derived hash, verification and enabled state, email-verification time and method, account timestamps, last-login timestamps, authentication timestamps, and hashed server-side refresh-token records.
When applicants and invitees confirm their email address: the address entered, a keyed hash of the one-time code, attempt counts, and timestamps, plus a hash of the single-use verification token. To limit repeated or automated requests, we use a keyed hash of your IP address for rate limiting; no raw IP address is stored for this purpose. These records are kept for at most 24 hours.
Organization name and slug, access-request and review status, internal review information, memberships, roles, active state, driver association, and invitation information.
When you ask for a demo: your name, business email, company, role, optional phone number, fleet-size range, time zone, three proposed meeting times, an optional note, the policy versions you acknowledged and when, and a one-way hash of the request key used to prevent duplicates. We email you to confirm a time, and staff who review requests see these details. The form stores nothing in your browser.
Information you include when you email us at [email protected] about access, support, billing, privacy, accessibility, partnership, or legal matters.
Load references, customer names, statuses, schedules, revenue, mileage, addresses, appointment windows, instructions, assignments, and timeline notes.
Driver name, email, phone, status, organization and account associations, plus unit number, equipment type, VIN when supplied, and equipment status.
PDF or image file bytes and metadata such as organization, load and uploader associations, document type, original filename, content type, size, checksum, storage key, status, and timestamps.
Expenses, descriptions, amounts and currency, invoice numbers, customer names, invoice amounts, statuses, dates, and notes.
For Haulveeo's own subscription: plan and subscription status, trial and renewal dates, Stripe customer and subscription identifiers, checkout and consent records with the accepted policy versions, and billing history. Card numbers and payment-method details are entered on Stripe-hosted pages; Haulveeo does not receive or store them.
Requested URLs, timestamps, action and object identifiers, before-and-after audit snapshots, and technical request information such as IP address and browser or user-agent data when received by the service or infrastructure.
02 / Sources
We receive information directly from account holders and people who contact us; from organizations, administrators, and authorized members using the application; from records and files those users submit; and from the service and hosting infrastructure as it handles requests and records activity.
03 / Use
04 / Access
Operational records are associated with an organization. Depending on assigned roles and workflow permissions, administrators and other authorized members of that organization may see, update, or act on those records. Users should submit only information their organization is authorized to manage in Haulveeo.
06 / Retention
There is no fixed retention period established for every category. We retain information while reasonably needed to operate the service, provide requested functionality, maintain security and business records, resolve disputes, and meet applicable legal obligations. Documents can enter a soft-deleted state, and backups may preserve copies; that does not establish a universal physical-erasure deadline.
Email-verification codes, attempt counts, single-use verification tokens, and rate-limit records are deleted within 24 hours. The time and method of a completed verification are kept with the account, together with an audit record of the verification.
Subscription, billing, and consent records are kept as business and tax records for as long as reasonably needed and as applicable law requires, including after a subscription ends. Stripe keeps its own records of payments and payment methods under its own policies.
07 / Safeguards
Current practices include password hashing, hashed server-side refresh-token records, authenticated requests, organization-aware authorization, and restricted production service boundaries. No transmission, storage, or operational measure eliminates every risk, so we cannot guarantee absolute security.
08 / Requests
Depending on where you live and applicable law, you may be able to request access to, correction of, or deletion of certain personal information. Email [email protected]. We may need to verify your identity and authority, coordinate with your organization, and retain information where legitimate operational, security, recordkeeping, dispute, or legal needs apply.
09 / Eligibility
Haulveeo is intended for business users who are at least 18 years old. The sites and service are not directed to children, and we do not intend for children to create accounts or submit information.
10 / Updates
We may revise this policy as the service and our practices develop. The centralized effective and last-updated dates identify the version presented here.
11 / Contact
Email [email protected] for privacy questions or requests. Please identify the relevant host and organization, but do not send passwords or authentication secrets.