Privacy Policy

Our privacy policy and how we use your data

Last updated: October 27, 2026

VETTA VERIFY LLC ("VettaVerify," "we," "us," or "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard information when you use our platform and related services (the "Service").

1. Information We Collect

Information You Provide

  • Account Data: Name, email address, company name, and role/profile details
  • Authentication Data: Password (if password auth is enabled), email OTP verification data, SMS OTP verification data, and related security metadata
  • Business Data: DOT/MC identifiers, carrier and broker notes, vetting records, and operational profile data entered into the Service
  • Billing Data: Billing contact and subscription details; payment card processing is handled by Stripe
  • Support and Communications: Messages and correspondence when you contact support or legal/privacy contacts

Information Collected Automatically

  • Usage Data: Pages viewed, feature interactions, search actions, and account activity logs
  • Device and Network Data: Browser type, OS, device details, IP address, and request metadata
  • Security and Login Data: Login activity and approximate geolocation inferred from IP and edge headers for fraud prevention and account security
  • Cookies and Similar Technologies: See our Cookie Policy for details

Carrier and Verification-Related Data

  • FMCSA and Public Source Data: Carrier profile, authority, inspection/safety records, and related lookup history
  • Phone Intelligence Data: Phone number validation and line-type intelligence (e.g., mobile/landline/VoIP) used for fraud controls
  • ELD and Location Data: Vehicle, driver, and location-sharing data where the carrier has authorized access
  • Driver Verification Data: Driver identity and history-sharing consent records for supported workflows

2. How We Use Information

We use collected information for the following business and commercial purposes:

  • Provide, maintain, and improve the Service
  • Authenticate users, protect accounts, and detect/prevent fraud or abuse
  • Support carrier verification workflows using email OTP, SMS OTP, phone intelligence, and related controls
  • Process subscriptions, billing operations, and account management
  • Power data products such as carrier risk indicators and analysis features
  • Send transactional communications, security notices, and service updates
  • Comply with legal obligations and enforce our agreements

3. AI Features Disclosure

Some Service features use AI providers (including Anthropic) to generate summaries, extraction results, and analysis outputs. When these features are used:

  • Relevant context may be sent to the provider to return feature output
  • We limit data shared to what is reasonably necessary for the feature
  • AI outputs may contain errors and are informational only

4. How We Share Information

We do not sell personal information. We share information only as needed to provide the Service, comply with law, or protect rights and safety.

Subprocessors and Service Providers

  • Supabase: database, authentication, and storage
  • Vercel: application hosting and edge infrastructure
  • Stripe: billing and payment processing
  • Resend: transactional email delivery
  • Twilio: SMS delivery and phone intelligence/lookup
  • Terminal.com: ELD integration and connected vehicle data
  • Trigger.dev: background job orchestration
  • Sentry: error monitoring and diagnostics
  • Expo: push notification delivery for the Vetta Driver app
  • Anthropic: AI processing for supported features

Other Disclosure Circumstances

  • Legal Compliance: To satisfy legal process or regulatory obligations
  • Business Transactions: In connection with merger, acquisition, financing, or asset sale
  • Rights Protection: To protect the rights, property, security, and safety of VettaVerify, users, and the public

5. Data Sharing Between Broker and Carrier Users

  • Carrier verification and profile information may be visible to authorized broker accounts for vetting purposes
  • Broker private notes and internal vetting commentary are not shared with carrier users by default
  • ELD/location data access depends on carrier authorization and can be revoked

6. SMS / Text Messages

We send transactional text messages to truck drivers when a broker asks them to check in for a load or to verify their identity for a carrier, then how to get the Vetta Driver app after a load check-in, short setup answers if the driver asks, and updates on that load (a new message from the broker, a reminder when location sharing stops, a prompt to confirm delivery). The carrier gives the driver's mobile number to the broker, and the broker confirms the driver's consent before any text is sent. We do not send marketing texts.

  • No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the categories of sharing described in this policy, including Section 4 (How We Share Information), exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
  • Reply STOP to any text to opt out, or HELP for help. You can also email support@vettaverify.com.
  • Message and data rates may apply.

See our SMS Terms for the full program terms, sample messages, and message frequency.

7. Vetta Driver App and Driver Check-in

Drivers can check in for a load through the Vetta Driver phone app or a check-in link sent by text. When they do, we collect:

  • Location: GPS location from the driver's device while the driver is sharing their location for a load, and only then. We do not collect location when the driver is not sharing for a load.
  • VIN photos: Photos the driver takes of the vehicle's VIN, when they were uploaded, and the location the driver shared with the check-in
  • Phone number: The driver's mobile number
  • Device identifiers: Identifiers for the driver's device and app installation, used to run the app and keep it secure
  • Push notification tokens: Used to notify the driver of new messages about a load and, while they share, to wake the app for a location update. Message and wake-up notifications go through Expo, which delivers them through Apple's and Google's push services. Expo receives the push token and, for message alerts, the broker name, the load number, a generic alert, and load and device identifiers; wake notifications carry only the token and a load identifier. On iPhone, location update requests go straight to Apple's push service. Apple receives only the device's location-push token; the notification itself is empty. Push notifications contain no message text
  • Messages: Messages the driver and the broker send each other about a load. The broker's authorized users can read the messages on their loads, and the driver reads them in the app or through the load's message link. Messages are kept with the load record
  • Crash reports: When the app hits an error, a report of what went wrong is sent to our error-monitoring provider (Sentry). Before it leaves the phone, we strip known location data, phone numbers, email addresses, VINs, access tokens and the private parts of links, no user account is attached, and screenshots and recordings are never sent
  • Usage and performance: In app versions that record it, which screens and steps of the app a driver reaches, such as opening a check-in link, taking a photo, answering a permission prompt or starting to share; whether location sharing is running and uploading; and which requests to our servers were slow or failed. Each record holds the app version, phone platform and OS version, the app language and the device identifier, and may name the load it belongs to by our internal identifier. It never holds location, the phone number, VINs, photos, message text, links or load numbers. We use it to find where drivers get stuck and to fix problems in the app. It is not shared with brokers, advertisers or analytics companies. We also record sign-in attempts: the outcome (such as a code sent, a wrong code or a successful sign-in) and, for a failure, which kind it was, the time, the app version and build, and, where supplied, the phone platform. These records hold no phone number and no lasting device identifier. When the app sends its installation identifier, the record keeps a code made from that identifier and the date, which changes every day. When a driver asks us to delete their data, we remove the sign-in records we can match to their phones; the rest are deleted after 90 days

For an identity check, the driver can also share a photo of their driver's licence and their location through a web link.

The broker who asked for the check-in or identity check can see its status, the location and photos the driver shared, and, while the driver shares their location for a load, the driver's position on that load. If the broker shares the load's tracking link, the people they share it with can see the load's status and position. Check-in data is kept with the load record; identity-check data is kept with the broker's record for that carrier.

8. Data Retention

We retain data for as long as needed for service delivery, security, legal compliance, dispute handling, and legitimate business purposes. Retention periods vary by category, including account records, transactional records, security logs, and regulatory records.

When retention is no longer required, we delete or de-identify data according to our internal controls.

Vetta Driver usage and performance records (Section 7) are deleted once they are more than 90 days old, at the next daily cleanup.

9. Security Measures

  • Encryption in transit and platform-level encrypted storage
  • Access controls, authentication controls, and audit logging
  • Row-level database access controls where applicable
  • Security monitoring and incident response practices

No system can guarantee absolute security. You are responsible for maintaining the confidentiality of your account credentials.

10. U.S. State Privacy Rights

Depending on your state, you may have rights to request access, correction, deletion, portability, and to opt out of certain data uses where applicable.

How to Submit a Rights Request

Submit requests to privacy@vettaverify.com with enough information for us to verify identity and locate records. We may request additional verification before completing a request.

Authorized agents may submit requests on your behalf where allowed by law. We aim to respond within timelines required by applicable law.

Sale/Sharing Statement

We do not sell personal information for monetary consideration. We do not knowingly share personal information for cross-context behavioral advertising.

11. Children's Privacy

The Service is intended for business users and not directed to children under 13. We do not knowingly collect personal information from children under 13.

12. Cross-Border and Third-Party Services

Service providers may process data in the United States and other jurisdictions where they operate. Third-party sites or services linked from the Service are governed by their own privacy terms.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date on this page.

14. Contact Us

For privacy questions or requests, contact:

VETTA VERIFY LLC
Tennessee, United States
Mailing address available upon request
Email: privacy@vettaverify.com