SMS and Messaging Policy
Last updated June 2026.
CustodyLinx messaging is operational. It exists to keep custody, safety, and compliance obligations met while controlled product is in motion.
Operational messaging only
CustodyLinx sends SMS and push messages to operator users and authorized drivers for operational and compliance purposes only: dispatch assignments, custody-handoff confirmations, dead-man check-in prompts, diversion and incident alerts, and regulator-deadline reminders. These are service messages tied to the movement of controlled product. We do not send marketing or promotional text messages.
Consent
Messaging is enabled by the operator for the users and drivers it authorizes, as part of using the service. A user provides a mobile number through their operator administrator and consents to receive the operational messages above. Consent for service messaging is a condition of the operational role, not a marketing opt-in.
Message frequency
Frequency varies with operational activity: a driver on an active run may receive several messages during a trip, while an administrator may receive only occasional alerts. Message and data rates may apply from your mobile carrier.
Opt-out and help
Reply STOP to any message to unsubscribe from non-critical operational texts, and HELP for assistance. Because some messages are safety and compliance critical (for example a diversion alert or a dead-man check-in on a controlled load), opting out of SMS may require the operator to move that user to another notification channel to keep the chain of custody and safety obligations intact.
Carriers
Carriers are not liable for delayed or undelivered messages. Delivery depends on your carrier and device.
Privacy
Mobile numbers and message metadata are handled under our Privacy Policy. We do not sell mobile information, and we do not share it for cross-context behavioral advertising.
The registered sending entity, the messaging sender ID, and program-specific terms are finalized with counsel before any production messaging is enabled. Until then, messaging runs only in the operator's configured environment.