Proof SMS / Messaging Terms & Consent

Last Updated / Effective Date: July 11, 2026

These SMS / Messaging Terms & Consent (these "Messaging Terms") govern the text-message (SMS) and email notifications sent through Proof, the software-as-a-service platform operated by Proof Incorporated ("Proof Incorporated", "we", "us", or "our") at goproof.ca (the "Service"). These Messaging Terms are the messaging-program terms for the Proof messaging program (the "Program") and are the terms referenced in the Program's application-to-person (A2P) 10DLC registration and by the mobile carriers that carry the Program's messages. They are incorporated into, and form part of, the Proof Terms of Service (the "Terms"). Capitalized terms not defined here have the meanings given in the Terms.

The short version

This summary is for convenience only and does not replace the full Messaging Terms below.

Proof sends transactional, operational text messages and emails on behalf of the carriers that use it (each a "Customer") — things like arriving-soon alerts, hold-and-release wait-loop texts, badge and handoff links, work orders, and shipment or day-ticket updates. We never use the Program to send marketing. Message frequency varies by shipment activity. Message and data rates may apply. Reply STOP to any text to opt out and HELP for help. Opting out means you may stop receiving operational alerts about the shipment or asset you are working. Mobile carriers are not liable for delayed or undelivered messages. How we handle your information is described in our Privacy Policy.

1. About the Program

1.1. The Service lets carrier Customers keep the people involved in a shipment informed as an asset moves through its lifecycle. As part of that, Proof Incorporated sends SMS messages and emails on behalf of Customers to the drivers, field workers, and business contacts a Customer has associated with a shipment, relay, work order, or day-work ticket.

1.2. The Program is transactional and operational only. Messages relate to a specific shipment, asset, task, or account event. The Program does not send marketing, advertising, promotional, or solicitation messages of any kind.

1.3. Consistent with how the Service routes communications, SMS is used to reach field hands — drivers and mechanics — while office and business contacts (dispatch, shippers, receivers, brokers) generally receive email. This is an operational routing rule; the consent and compliance requirements in these Messaging Terms apply to every message the Program sends.

2. Who operates the Program

2.1. The Program is operated by Proof Incorporated using third-party communications providers, including Twilio for SMS and Resend for email. These providers act as our service providers (subprocessors) as described in the Privacy Policy. SMS is sent from the Program's messaging number(s); the specific sending number may change from time to time.

2.2. Each message is sent on behalf of a Customer in connection with that Customer's shipment or asset. The Customer is responsible for the recipients it enrolls and for the lawfulness of the messages sent under its account, as set out in Section 6.

3. Types of messages

The Program sends transactional and operational messages such as:

Arriving-soon alerts — an automated notice that a driver is approaching, generated from a tracking source before the driver's own arrival scan.
Wait-loop messages — "hold, we'll text you" notices when a receiver asks a driver to wait, the "ready for you" release when the receiver is ready, and periodic reminders while a hold is open.
Badge and handoff links — a driver's private link that identifies their phone to the Service, and relay/handoff links that add the next driver to a load.
Work-order messages — maintenance work orders and related PINs and instructions sent to a mechanic when a unit is delivered for repair.
Status and shipment updates — operational updates as an asset is dropped, loaded, emptied, made ready, stored, picked up, or otherwise changes state.
Day-work tickets — end-of-day summaries for per-load (day-work) operations.
Account and security notices — for example, alerts related to repeated failed PIN attempts or other operational-security events.

Sample messages (illustrative; actual wording varies):

Proof: BK-53173 arriving soon at Dufferin Aggregates — Milton. They're busy — hold and we'll text you when they're ready. Reply STOP to opt out.

Proof: You're clear to come in for BK-53173. Dock 7, check in at the office. Reply STOP to opt out.

4.1. Customer-obtained consent. By enrolling a recipient — for example, by entering a driver's or mechanic's cell number on an order, day-work ticket, work order, or handoff — the Customer represents and warrants to us that it has obtained that recipient's prior consent to receive the operational messages described in these Messaging Terms at the number provided, and that the number is accurate and belongs to that recipient. The Customer is responsible for obtaining, recording, and honouring that consent.

4.2. Recipient opt-in. A recipient may also consent directly — for example, by opting in through a scan flow (such as a "text me when it's ready" prompt), by tapping the private link a Customer sends them, or by otherwise electing to receive messages about a shipment. Providing a mobile number in one of these flows constitutes the recipient's agreement to receive the operational messages associated with that request.

4.3. Scope of consent. Consent under this Section is limited to the transactional, operational messages described in Section 3. Consent to receive these messages is never a condition of any purchase, and the Program is not used for marketing.

5. Frequency, cost, opting out, and getting help

5.1. Message frequency. Message frequency varies by shipment activity — you will generally receive messages only when something happens on a shipment, asset, or task you are associated with, so volume depends on how active that work is.

5.2. Cost. Message and data rates may apply according to your mobile plan and carrier. Proof Incorporated does not charge recipients for messages, but your carrier may.

5.3. Opt out — STOP. You can opt out of SMS at any time by replying STOP (or another standard opt-out keyword, such as STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT) to any Program text. After you opt out we will send a single confirmation that you have been unsubscribed, and we will stop sending Program SMS to that number. Because these messages are operational, opting out may mean you stop receiving arriving-soon alerts, hold/release notices, handoff links, work orders, and other messages you may need to do the work in front of you. Opting out of SMS does not opt you out of email, and does not by itself remove you from a Customer's records.

5.4. Get help — HELP. Reply HELP to any Program text for help, or contact support@goproof.ca. You may also be directed to this page or to goproof.ca for assistance.

5.5. Opt back in. If you have opted out and want to resume messages, reply START (or UNSTOP) to the Program number, opt in again through a scan flow, ask the Customer to re-enroll you, or contact support@goproof.ca. Because active shipments re-send a driver's link, you may also be re-enrolled when a Customer next assigns you to a load.

6. The Customer's compliance responsibilities

6.1. Each Customer is responsible for its own compliance, and for the compliance of its Authorized Users, with all laws and carrier requirements that apply to the messages it causes the Program to send, including CASL in Canada; the TCPA and the A2P 10DLC registration and content requirements in the United States; and the rules of the CRTC, the CTIA, and the mobile carriers. This includes obtaining and maintaining valid consent (Section 4), honouring opt-outs, sending only within the transactional scope of the Program, and keeping recipient numbers accurate.

6.2. Each Customer represents and warrants that it will not use the Program to send marketing, that it has a lawful basis and any required consent for each recipient it enrolls, and that free-text it inserts into a message (for example, a note that rides a driver's text) complies with the Acceptable Use Policy. Free-text that is inserted into a message passes through the Program's messaging number; unlawful, abusive, or prohibited content can be blocked by downstream carriers, can damage the number's messaging reputation, and is a violation of the Acceptable Use Policy — the Service applies automated screening to certain free-text fields as a safeguard, but the Customer remains responsible for the content it sends.

6.3. The Customer will indemnify Proof Incorporated for claims arising from its messaging, including any claim that a message was sent without required consent or in violation of CASL, the TCPA, A2P 10DLC rules, or carrier requirements, as further set out in the Terms.

7. Delivery, carriers, and reliability

7.1. Carriers are not liable. Mobile carriers and other communications providers are not liable for delayed or undelivered messages. Message delivery depends on factors outside our control — carrier networks, device settings, coverage, roaming, filtering, and number portability — and we do not guarantee that any message will be delivered, delivered on time, or delivered to the intended recipient. Do not rely on a single message for any safety-critical or time-critical decision.

7.2. Filtering. Carriers independently filter message content and traffic. A message may be blocked or delayed by a carrier for reasons we do not control, including message content and sending-number reputation.

8. Privacy

8.1. To operate the Program we process the recipient's mobile number, the message content (including any operational note a Customer adds), delivery status, and related metadata. Our handling of this information — including the use of Twilio and Resend as subprocessors, retention, and your rights — is described in the Privacy Policy at goproof.ca. Questions about privacy may be sent to support@goproof.ca.

8.2. We do not sell recipients' mobile numbers or message content, and we do not share them with third parties for those third parties' own marketing. Mobile information is used only to operate the Program and is shared only with the service providers needed to deliver the messages and as otherwise described in the Privacy Policy.

9. Changes to these Messaging Terms

We may update these Messaging Terms from time to time. When we make material changes we will update the "Last Updated / Effective Date" above and, where required, provide notice through the Service. Your continued participation in the Program after an update takes effect constitutes acceptance of the updated Messaging Terms.

10. Contact

Questions about the Program or these Messaging Terms may be sent to support@goproof.ca, or by mail to Proof Incorporated, Ontario, Canada (mailing address on request via support@goproof.ca). For a description of how the messaging program works, this page is published at goproof.ca and may be cited in the Program's carrier and A2P 10DLC registration.