1. Operator and scope
Carrierintel is a carrier intelligence service operated by [PRE-PROD TODO: legal entity name], with a mailing address at [PRE-PROD TODO: business address]. This policy will apply to the Carrierintel website, API, accounts, reports, and related support communications when the production service launches.
The current build is a development environment. This draft is not an effective production privacy notice.
2. Information we process
Public carrier and regulatory data
Carrierintel collects and organizes records about commercial motor carriers from FMCSA and U.S. Department of Transportation sources, including Data.Transportation.Gov/Socrata and Motus. These records may include USDOT and docket numbers, names, business addresses, registration and authority status, fleet size, inspections, violations, crashes, insurance information, and other regulatory history.
Motus records may include carrier and company-officer names, titles, business phone numbers, and email addresses. Some business records can identify sole proprietors or other individuals even when published as carrier information.
Inferred ethnicity data
The development build can use an external name-classification model to infer an owner ethnicity category from an officer name. The result is probabilistic, may be inaccurate, and is not an official FMCSA fact or a verified statement about a person. Carrierintel may store the model label, normalized category, confidence, and classifier version.
During development, carrier contacts, inferred ethnicity, and the origin filter are visible to all users. The production audience and permitted use of these fields remain a release-blocking business and legal decision.
Account and authentication data
When you create an account, we process your display name, email address, password credential in hashed form, email-verification status, account role and plan, sessions, and security records used for two-factor or email one-time-password flows. We may also process messages you send to support.
Technical and security data
The API and website create structured request and error logs that may contain timestamps, request identifiers, IP addresses, route and response information, and technical error context. If configured, application errors from both the server and your browser may be sent to Sentry for error reporting; these reports are scrubbed of known contact and inferred-ethnicity fields and do not record your screen or session. The website uses authentication cookies and local storage as described in the Cookie Policy.
Payment data
Payments are not active in the current build. Before Stripe or another payment provider is enabled, this policy must identify the provider, the billing data exchanged, and the applicable retention and disclosure practices.
3. Why we process information
- Provide carrier search, profiles, reports, risk indicators, and data synchronization.
- Create and secure accounts, sessions, verification, and access controls.
- Operate, debug, protect, and improve the website and API.
- Prevent abuse, credential attacks, excessive automated access, and security incidents.
- Respond to support, correction, privacy, and legal requests.
- Meet legal obligations and enforce the Terms of Use.
[PRE-PROD TODO: confirm applicable legal bases and state-specific disclosures with counsel]
4. Sources
Carrier data comes primarily from FMCSA and DOT public systems, including Socrata datasets and Motus. Account and communication data comes from the user. Technical data is generated when the Service is requested or operated. Inferred ethnicity is generated by the external classifier identified in Carrierintel's internal data provenance records.
5. Sharing and service providers
Information may be disclosed only as needed to:
- hosting, database, backup, and network providers used to run the production service;
- Sentry for error reporting, when configured;
- Resend for transactional email, when configured;
- Stripe for subscription billing, once payments are enabled;
- professional advisers or authorities when required by law or necessary to protect rights and security.
[PRE-PROD TODO: list the final hosting location, every subprocessor, transfer mechanism, and provider policy]
6. Retention
Public regulatory data is refreshed and retained to provide current and historical carrier analysis. Account, session, verification, support, security-log, backup, and billing retention periods have not yet been approved.
[PRE-PROD TODO: approve and publish category-specific retention and deletion periods]
7. Access, correction, and deletion requests
Users may request access to, correction of, or deletion of account data through the production privacy contact, subject to legal and security exceptions. Requests concerning an official FMCSA inspection, crash, violation, or registration record should also be submitted through the authoritative FMCSA process, including the DataQs system.
Disputes about Carrierintel's inferred ethnicity, confidence, officer selection, or locally derived analytics must be handled by Carrierintel rather than DataQs. [PRE-PROD TODO: define the correction, suppression, appeal, and identity-verification workflow]
8. Security
The application uses access controls, hashed authentication credentials, session protections, structured log redaction, and production HTTPS requirements. No security measure is absolute. Final infrastructure, backup, incident-response, and breach-notification procedures must be documented before launch.
9. International use and regional rights
Carrierintel is intended to operate from the United States. Regional privacy rights and international transfer obligations depend on the final operator, hosting location, user markets, and subprocessors.
[PRE-PROD TODO: confirm launch jurisdictions and add required U.S. state, EEA, UK, and other notices]
10. Children
The Service is designed for business and professional use and is not directed to children. [PRE-PROD TODO: confirm the minimum user age and required handling procedure]
11. Contact and effective date
Privacy requests will be sent to [PRE-PROD TODO: privacy contact email and postal address]. This policy will become effective only after the operator, contact details, production data flows, retention schedule, PII visibility, subprocessors, jurisdictions, and legal review are complete.