CarrierWire Privacy Policy

Preview, Subscriber and Billing Data

We store preview and checkout drafts, subscriber email addresses, selected feed filters, existing-customer exclusion lists, Watchlist USDOT lists, Stripe customer and subscription identifiers, delivery records, management-link sessions, and support correspondence. Preview drafts include masked sample rows and their source date.

Payment card details are handled by Stripe and are not stored in CarrierWire.

Public Source Data

Carrier facts in feeds and public pilot pages come from the public FMCSA Company Census File. CarrierWire retains dated source snapshots so exported rows can be audited against the source file used.

Uploaded Watchlist USDOTs are customer account data. We use them to match and deliver alerts, not to publish a customer's book of business.

How We Use Data

We use customer information to create checkout sessions, provision subscriptions, deliver CSV feeds and heartbeat emails, maintain subscriber filters, answer support requests, prevent misuse, and keep operational records.

We may use aggregated operational metrics to understand service health, such as active subscriber counts, delivery counts, and failed delivery reasons.

For the free monthly report, we store your email, optional state preference, consent and confirmation dates, unsubscribe status, and delivery history. Report emails require confirmation and include an unsubscribe link.

Service Providers

We share the minimum information needed with service providers that run CarrierWire, including Stripe for subscription checkout and billing, email delivery providers for subscriber emails, hosting and database providers, and support tooling.

We may also disclose information when required by law, to protect the service, or as part of a business transfer.

Cookies and Logs

CarrierWire uses essential cookies and session storage for security, CSRF protection, checkout and management workflows, and signed subscriber-management sessions.

We retain coarse acquisition details, such as an approved campaign or referral source, in your session and with preview drafts, subscriptions and free-report signups. We use these details to aggregate events such as preview, checkout and first delivery. Analytics counters do not contain IP addresses, email addresses, full referral URLs or cross-site advertising identifiers. Do Not Track and Global Privacy Control requests suppress this acquisition tracking. Short-lived hashed abuse-limit keys help protect signup forms.

Application, security, and delivery logs may include IP addresses, request metadata, email delivery status, and error details needed to operate and debug the service.

Retention

We keep subscriber, billing, delivery, and support records while needed to operate the subscription, resolve disputes, meet accounting obligations, and preserve audit trails for delivered feeds.

Public FMCSA source snapshots may be retained separately from subscriber records so dated feed rows remain auditable.

Preview and checkout drafts retain selected filters, submitted exclusion or Watchlist USDOT lists, preview samples and coarse acquisition details after expiry, including when no purchase is completed. Expiry disables the checkout link; it does not delete the draft. There is currently no automatic draft-deletion schedule. Checkout records may also be needed to resolve delayed payment events. Suppression lists and Watchlist uploads are not published on public carrier pages.

Your Choices

Subscribers can cancel billing through Stripe's billing portal and can request a management link to update feed filters or Watchlist USDOTs. Transactional service emails may continue when needed to administer an active subscription.

Depending on where you live, you may ask to access, correct, delete, or export customer account information.

Security and Changes

We use reasonable technical and operational safeguards, but no internet service can guarantee perfect security.

We may update this policy by posting a revised version on this page. Material changes will be reflected by the last-updated date above.