Privacy Policy

We collect information you and your carrier provide, information generated as you use the Service, and information we receive from your carrier or other authorized users in your carrier’s workspace.

• Account and contact information — email address, authentication credentials managed by our identity provider, session tokens, a user identifier, and your role (owner, administrator, dispatcher, or driver).
• Carrier and membership information — the carrier organization you belong to, your membership status, and operational settings for your role.
• Driver profile information — name, phone number, payment handle submitted by a driver (for example a Zelle or Cash App handle), emergency-contact details, and onboarding documents such as license or certification images that a driver uploads.
• Customer and shipment information — customer contacts, load and shipment details, pickup and delivery addresses, and related rates entered by carrier personnel.
• Job and operational records — assignments, job and shipment status updates, check-ins, detours, incidents, fuel stops, duty-session records, delivery and pickup records, invoices, and related timestamps.
• Precise or approximate location — when the feature is enabled and you grant permission, we collect device location during supported driver workflows. See Section 2.
• Device and push-notification information — device push token, platform (iOS or Android), app version, and a device identifier, used to deliver job assignments, status alerts, and operational notifications.
• Photos, audio, files, documents, and other user content — images captured or selected for pickup proof, Bills of Lading, chain of custody, cargo, and incident reporting; optional incident voice notes; signatures; documents you upload; and documents the Service generates (such as BOLs, delivery orders, and invoices).
• Communications and support requests — messages you send us for support, and, where your carrier has enabled these features, operational email and inbound SMS or voice load-intake content and metadata.
• Website inquiries and onboarding forms — business contact details you submit through forms on this site, including company information and the name, title, email address, and phone number of the people you designate. We use this information to respond to inquiries, prepare customer-specific agreements, provide onboarding communications, and administer the prospective or active customer relationship.
• Usage, security, diagnostic, and audit information — app version, device type, and diagnostic information needed to operate, secure, troubleshoot, and support the Service, and audit records of significant operational actions.

We do not use third-party advertising, cross-app tracking, attribution, or analytics SDKs in the Vigil mobile application, and we do not collect the contents of your address book, calendar, or web-browsing history.

Location is used to support carrier dispatch and operational workflows. It is not a public tracking feature, and Vigil is not an emergency-monitoring or personal-safety service.

• Location may be collected during supported driver workflows — for example, tagging a job status update or check-in, and, where enabled, sharing your location with your carrier’s dispatch team while you are clocked in to an active shift.
• Collection can occur in the foreground (while you are using the app) and, when the feature is enabled and you grant background permission, in the background while the app is not in the foreground. Background collection is tied to a supported, active duty session: it is available only when your carrier has enabled continuous location sharing, it runs only while you are clocked in, it is accompanied by a persistent on-device notification while active, and it stops automatically when you clock out.
• Before the system permission prompt, the app shows an in-app explanation of how location sharing works during your shift, and you choose whether to continue.
• Location may be precise or approximate, depending on the workflow, your device, and the permission you grant.
• Location is used to coordinate active work (assignments, check-ins, and document submissions), to support dispatch and job-progress visibility, to maintain operational and audit records, and for security and troubleshooting.
• Whether location sharing — and, in particular, background sharing — is available depends on your carrier’s configuration and on platform settings. The Service does not guarantee continuous availability or perfect accuracy of location.

You can control location permissions in your device settings. Denying or turning off location may limit the features that depend on it.

We use the information described above to:

• provide, operate, and maintain the Service;
• authenticate users and administer accounts and roles;
• provide carrier, administrator, dispatcher, and driver workflows;
• coordinate jobs and shipments;
• provide status, location, notification, and document features;
• communicate operational and service information to you;
• generate operational documents;
• provide support and respond to your requests;
• maintain security, auditability, reliability, and separation between carrier organizations;
• investigate incidents, misuse, and potential violations; and
• meet legal obligations that apply to us.

We use diagnostic and operational information to improve the reliability and security of the Service. We do not use your information for advertising or for building advertising or cross-context behavioral profiles.

We do not sell your personal information, and we do not share it for behavioral advertising or cross-context tracking. We disclose information only as needed to operate the Service:

• Your carrier organization and other authorized users in it — owners, administrators, and dispatchers in your carrier’s workspace can view operational records relevant to running the carrier’s operations, and drivers submit status, document, photo, audio, and (where enabled) location information into that workspace.
• Service providers and subprocessors — vendors that host or process information on our behalf to run the Service (see Section 5).
• Legal and safety disclosures — when required by law, regulation, or legal process, or to protect rights, safety, and security.
• Business transactions — in connection with a merger, acquisition, financing, or sale of assets, subject to this policy.
• At your or your carrier’s direction — including where you or your carrier generate a document link or a tracking-portal link that can be accessed by someone who has the link.

Vigil is designed so that one carrier’s data is not disclosed to another carrier through ordinary authorized use of the Service; our tenant-isolation controls are designed to restrict cross-carrier access. No security measure is perfect, and we do not guarantee that information can never be accessed by unauthorized parties.

We rely on the following categories of service providers. Each processes information only as needed to provide its part of the Service:

• Cloud application platform — authentication, database, file storage, and server functions (production infrastructure).
• Mobile application platform — app builds, over-the-air updates, and push-token infrastructure.
• Mobile push transport — Apple Push Notification service (iOS) and, for Android, Google’s Firebase Cloud Messaging as the delivery transport.
• Web hosting — hosting for the Vigil marketing site and the Vigil Command Center web surfaces.
• Transactional email — operational email such as document routing and invoices, where your carrier has enabled it.
• SMS and voice intake — inbound message and call handling for load intake, where your carrier has enabled it.
• Map imagery — a map-tile provider supplies the imagery for the dispatcher web map. This is used on the web dispatch surface only; that provider does not receive data from the mobile app.
• ETA and routing — where enabled, a mapping and routing provider is used on our servers to calculate estimated arrival times from job coordinates (for example, after an en-route check-in). This receives location coordinates, not other personal data.
• Optional voice-note transcription — where enabled, incident voice notes may be transcribed and structured by third-party AI providers.
• App distribution — Apple App Store and Google Play, and related platform services.

The current, named providers behind these categories are maintained in an internal data-provider and subprocessor register. We may add or change providers as the Service evolves and will update this policy where required.

We retain information for as long as needed to provide the Service and for legitimate operational, contractual, security, audit, dispute-resolution, and legal purposes. Retention varies by the type of record:

• Account, profile, and operational records are retained while your carrier’s account is active and as needed afterward for the purposes above.
• Your carrier may retain job, shipment, billing, compliance, and operational records (including historical BOL, proof-of-delivery, and invoice data) required for its legal, tax, insurance, and business purposes. Those records may still contain operational data from your activity after your account is removed.
• Location history is retained under a documented internal retention design. Some automated purge behavior is not yet active, so historical location data may be retained longer than a target schedule until purging is enabled.
• Legal holds and unresolved operational or contractual obligations may extend retention.
• Temporary exports and generated links (for example, document or tracking-portal links) may have their own expiration behavior.

Because some records must be preserved, a deletion request may not remove every record associated with you. See Section 7.

Vigil accounts are generally invitation-based and created by a carrier administrator; there is no public self-registration.

You may request deletion of your Vigil account and associated personal data by emailing privacy@seevigil.com with the subject line Vigil account deletion request. You can also start this request from within the Vigil app: Legal & Support → Delete account / data request, which opens a pre-filled message to that address. This is a request-and-review process, not an immediate self-service erase operation.

Full details of the process are on the account-deletion request page.

When we receive a request, we:

1. verify your identity and authority — your request should come from the email associated with your Vigil account, or a carrier administrator may authorize a request on behalf of a driver; and
2. review which records can be deleted or anonymized and which must be preserved.

Different categories of information may be treated differently. Your login and personal profile information can generally be deleted or anonymized, while carrier operational records, generated documents, audit records, information under a legal hold, and security evidence may be retained where legally, contractually, operationally, or technically required. Where records are retained, they may no longer be associated with an active login.

We will acknowledge and process verified requests, and we will tell you what was deleted or anonymized and what was retained.

We use reasonable administrative, technical, and organizational safeguards designed to protect information, including authentication, role-based authorization, tenant isolation between carrier organizations, encryption of data in transit, encryption at rest for certain data (including location data queued on a driver’s device), access controls, audit evidence, and operational monitoring. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. We review our practices over time.

• Device permissions — you can grant or deny location, camera, photo library, microphone, and notification permissions, and change them at any time in your device settings.
• Sign out — you can sign out of the app at any time.
• Deletion requests — see Section 7.
• Support — contact hello@seevigil.com for support, or privacy@seevigil.com for privacy requests.

Denying a permission may limit the feature that depends on it (for example, denying camera access prevents photographing documents).

The Vigil mobile application does not use advertising or analytics cookies or trackers. The Vigil web surfaces use only storage that is necessary to operate the Service — for example, keeping you signed in and maintaining your session. We do not use nonessential advertising or cross-site tracking cookies on our web surfaces.

Vigil is a business tool intended for authorized carrier personnel. It is not directed to children, and we do not knowingly collect personal information from children. If you believe a child has provided information to us, contact privacy@seevigil.com.

Depending on where you live and subject to applicable law, you may have rights regarding your personal information, such as rights to access, correct, delete, or obtain a copy of it. To make a request, contact privacy@seevigil.com. We may need to verify your identity and authority, and some records may be retained as described in Sections 6 and 7. Because Vigil accounts are provisioned by a carrier organization, we may coordinate your request with your carrier.

Vigil is offered for use in the United States. Vigil infrastructure and our service providers process information in the United States.

The Service is not currently offered to, or directed at, users outside the United States. If we extend the Service to other regions, we will update this policy before doing so.

We may update this policy from time to time. We will post the revised policy at this page and update the effective date. Where a change is material, we will take reasonable steps to make the update prominent. Your continued use of the Service after an update becomes effective indicates your acceptance of the updated policy.

Diamond Welmaker, provider of the Vigil service. 2881 Lithia Pl, Lithia Springs, GA 30122.