Privacy Policy
This policy explains how VinTelligent, Inc. ("Vintelligent", "we", "us") handles information in our mobile application and the related account, inspection-report, and account-deletion services (together, the "Service"). The information processed depends on the features and account you use.
Key points
- Personal accounts can save inspections, damage photos, and recorded routes on Vintelligent's servers, without affiliation with a customer company.
- Route location collection starts only when you start a route. It can continue while the app is in the background or the screen is locked. Use Stop on the route screen to end collection.
- An inspection report link can be opened by anyone who has the link, including someone to whom a recipient forwards it.
- Stopping a route, signing out, or uninstalling the app does not by itself delete records already uploaded to a server.
- You can request account or data deletion using the options in Account and data deletion.
1. Accounts and scope
Personal registered accounts. You can register directly with Vintelligent. Your account is used to associate your inspections, photos, and routes with you and to retrieve uploaded records later.
Organization accounts. If an employer, customer, carrier, or other organization gives you access, its systems and instructions may determine the available workflows, recipients, access rights, and retention of business records. The organization may have its own privacy notice.
Guest access. Guest access is more limited than a registered personal account and does not provide personal Route Tracking. Guest use does not mean that no information is processed: for example, a VIN lookup sends the requested VIN to the Service, and network requests can generate technical logs.
2. Information we process
- Account and authentication information
- Username, email address, internal account identifier, password-based authentication information, session tokens, and email-verification or password-recovery information. We also process messages you send to support.
- Vehicle, inspection, and business records
- VINs you scan or enter, decoded vehicle information, inspection dates, the inspecting account's username, no-damage results, and damage areas, types, and severities. Organization workflows may also process truck, load, unit, terminal, parking, delivery, signature, and other operational records that you enter or submit.
- Camera images and photos
- The camera supports code scanning and vehicle or damage photography. Submitted inspection photos are uploaded with the inspection. A photo can contain information visible in the image and metadata embedded in the file. Avoid unnecessarily photographing people, personal documents, or unrelated information.
- Location and route information
- During an active route, device latitude and longitude, point timestamps, route identifier, truck number, account identifier, route start and stop times, and the selected recording interval. Certain organization workflows also capture a vehicle's yard or terminal position when you use that feature.
- Technical and support information
- Information needed to operate and troubleshoot the Service, such as IP address, request times, account/login events, app and operating-system versions, device details, and diagnostic records. Map services can also process their own SDK identifiers and diagnostics, as explained below.
- Information stored on your device
- Preferences, saved route sessions and points, inspection records, temporary photos, and pending uploads. These support offline use, recovery after a normal restart, and later synchronization.
3. How we use information
- Create and authenticate accounts, verify email addresses, and support password recovery.
- Decode VINs and provide vehicle, inspection, and customer-specific logistics features.
- Save and synchronize inspections, damage photos, and routes; provide My Inspections, My Routes, and report links.
- Record the progress of a truck during a route you explicitly start.
- Support authorized organization workflows and integrations where enabled.
- Respond to support and privacy requests, protect access, investigate abuse, and diagnose service failures.
We do not sell personal information. Route recording is a logistics feature, not a requirement to give us access to your activity in unrelated apps or websites.
4. Route tracking and location
You start a route by entering a truck number and selecting Start. We request the location permissions needed for this feature and explain background use before the relevant permission request.
While a route is active, the app listens for device-location updates. It saves the first available location fix after Start, then records points at your selected interval: 1, 2, 3, 5, 10, or 15 minutes (5 minutes by default). The operating system may provide location updates more frequently than the interval at which the app saves points. Accuracy, battery settings, permissions, connectivity, and operating-system behavior can affect collection and delivery; a selected interval is not a guarantee of uninterrupted real-time reporting.
For personal accounts, saved route information is associated with your account and uploaded to Vintelligent's route service for later retrieval. If connectivity is unavailable, points and route events can remain on the device and upload later when the same account reconnects.
Location updates may continue while the app is in the background or the screen is locked, subject to permissions and platform restrictions. We do not promise tracking after an iOS force-quit. A saved active route can be restored after a normal app restart.
To stop collection, press Stop on the route screen. Signing out also ends collection on that device. You can withdraw location permission in device settings. A Stop event may need to synchronize later if the device is offline, and points recorded before Stop may still upload. Stopping does not erase existing route history.
Opening saved route history or its map does not start a route or request new location collection. Business yard or terminal location capture is a separate workflow and is not permission for an ongoing route session.
6. Third-party services
Google Maps. Map screens use Google Maps SDKs. When used, these services can process IP addresses, device and SDK information, SDK-specific identifiers, crash or performance data, and map requests or interactions, depending on the platform and SDK configuration. Displaying a saved route on a map is distinct from requesting a new device-location fix. Google's handling is described in its Privacy Policy.
VIN decoding. Vintelligent's generic VIN-decoding service sends the requested VIN to the U.S. National Highway Traffic Safety Administration's vPIC service to obtain vehicle details. That decoding request does not include your Vintelligent password or authentication token. See NHTSA's privacy information. Customer-specific services may use different vehicle-data sources.
Servers and providers may operate outside your country. Contact us for information about the processing locations and protections relevant to your account. Your organization can explain any separate providers it selects for its own workflows.
App-related account pages may use session and security cookies, for example to protect a deletion confirmation. Device permissions and local app storage are separate from those browser cookies.
7. Storage and retention
Records may exist both on your device and on the backend serving your account. Retention depends on the record and its purpose:
- Personal account information
- Kept while needed to maintain your account, provide the Service, and handle account or privacy requests, subject to deletion and any applicable, explained retention exception.
- Personal inspections, photos, and routes
- Kept to provide your saved history until the relevant data or account is deleted. Ending a route does not automatically delete its points; this version does not apply an automatic two-day route-history expiry.
- Local records and pending uploads
- Can remain on the device after signing out so that the same account can resume synchronization. Clearing the app's storage or removing the app generally removes its local copies, subject to device backup or restore settings. It does not remove server records.
- Organization records
- Subject to the organization's operational requirements, applicable contracts, and legal obligations. Ask the organization about its retention schedule and any independent copies it holds.
- Logs, backups, and cleanup records
- Can remain separately from live account records. Deletion of a live account does not instantly rewrite backups or previously generated exports. We can explain the applicable retention and deletion handling when you submit a privacy request. Storage-cleanup records are kept while required file removal remains unresolved.
Where information must be retained for a specific legal or security reason, we will explain the relevant exception in response to your request, as applicable. We do not promise that every historical record, backup, log, or third-party copy disappears immediately.
8. Account and data deletion
Personal accounts: you can initiate a request through our account-deletion page. Verify the account using your username or email and current password, review the confirmation, and confirm only if you intend to delete the account permanently. You do not need to reinstall the mobile app to use this page. Contact support@vintelligent.com if you cannot access it or want to request deletion of particular records.
Successful account deletion removes the personal account and its linked inspections, damage records, photos, recorded routes and points, and associated account-authentication records from the active service. Original inspection links cease to work. If photo-storage removal fails, access can be revoked and the account deleted before remaining files finish cleanup; cleanup is retried rather than described as immediately complete.
Records that cannot safely be attributed to your account, separately retained logs or backups, organization-controlled records, and copies saved by other people require separate consideration. Include relevant details in your request so we can investigate rather than delete another person's records by mistake. These limits do not remove any rights you have under applicable law.
Before browser-based deletion, stop any active route and sign out on your devices. A browser request cannot reliably erase offline device storage or remotely operate every running app instance. Clear the app's local storage if you also want to remove device-side copies. Signing out or uninstalling alone is not an account-deletion request.
Organization accounts: contact the organization that manages access, or contact us for help identifying the appropriate administrator. Deleting a personal Vintelligent account does not delete records independently controlled by an organization.
9. Your choices and privacy requests
- Choose whether to register, use the more limited guest experience, submit an inspection, or start a route.
- Manage camera, location, background-location, Bluetooth/nearby-device, and notification permissions, where requested, in device settings. Denying a permission can prevent the related feature from working. Bluetooth is used in supported printer workflows.
- Use Stop to withdraw from an active route's collection. Previously recorded data is handled separately under the retention and deletion sections.
- Choose whether and with whom to share an inspection link.
- Contact us to request access, correction, a copy, or deletion of your personal information. Depending on where you live, you may also have rights to restrict or object to processing, withdraw consent where it is the basis for processing, or complain to a privacy regulator.
We may need to verify your identity and account ownership before handling a request. Do not email us your password, authentication token, or verification code. For organization-controlled information, we may need to coordinate with the organization.
10. Security
We use measures intended to protect information, including account-based access controls. Personal-account authentication, inspection uploads, and route-history services use HTTPS endpoints. We do not claim that all customer-managed systems have the same configuration. No online service or device can be guaranteed completely secure.
Protect your device, credentials, and report links. Let us know promptly if you believe your account or a report link has been exposed.
11. Children
The Service is intended for vehicle and logistics use, not for children under 13 or the higher minimum age required in their location. If you believe a child has provided personal information, contact us so that we can investigate and address it.
12. Changes to this policy
We will post revised versions on this page and update the policy date. Where required, material changes will be communicated separately and any additional permission obtained before the new processing begins.
13. Contact us
VinTelligent, Inc.Email: support@vintelligent.com
8230 Grizzly Peak Drive
Las Vegas, NV 89113
United States
Please identify the app, your account email or username, and the nature of your request. Do not include your password or verification codes.