SMS opt-in evidence
This page shows every surface on which a person enters a mobile number into Haulyn and consents to receive text messages. It exists so that a carrier or messaging reviewer can see the opt-in exactly as a user sees it, without installing an app.
For the terms of the messaging program itself, see SMS Terms. For what Haulyn does with the number, see the Privacy Policy.
1. The consent language
Every sign-in surface below presents the same three pieces of text, in the same order, as static visible text — not a tooltip, not a link, not revealed on tap: a notice about the one-time code, an unchecked, optional consent checkbox with the label below, and the consent disclosure beside that checkbox. All of it sits directly above the control that submits the number.
The checkbox is the only thing that enrolls a number for Haulyn's ongoing automated messages — trip, delivery, account and review. It is never pre-ticked. Leaving it unticked does not prevent signing in, booking, or using any part of Haulyn.
1a. The one-time-code notice. The passcode that signs a person in is deliberately not governed by the checkbox — it is a response to an action the person just took, not traffic Haulyn originates. The page says so rather than leaving it to be inferred:
Signing in with a phone number sends a one-time code to that number.
1b. The checkbox label, shown beside an unchecked box:
Text me account, trip and delivery updates.
1c. The consent disclosure, as static text beside the checkbox:
Consent is not a condition of purchase or of using Haulyn. Message frequency varies. Message and data rates may apply. Reply HELP for help or STOP to cancel.
Followed by working links to the Privacy Policy and SMS Terms.
Consent to messaging is not a condition of purchase or of using Haulyn, is not pre-checked, and is not bundled with acceptance of any other agreement. A person can sign in, book and complete a trip with the box left unticked. The web sign-in screen in section 4 also carries a Use email instead control — a mode switch on the same form, not a separate page — so a mobile number is not required to use Haulyn at all. The wording is held as identical copies on the Haulyn site and in the platform codebase, each checked automatically on every change — on this site at merge and build time, in the platform on every deploy and daily — so those copies cannot diverge from one another unnoticed.
2. Consumer app — sign-in
A customer enters their own mobile number to sign in. Submitting the number signs them in and sends a one-time passcode to that number, and does nothing else. Enrollment for ongoing account, trip and delivery messages happens only if the consent checkbox is ticked, which it is not by default. A customer who leaves it unticked signs in and books normally.
3. Driver app — sign-in
A driver enters their own mobile number on the same pattern, with the same unchecked checkbox, the same label and the same disclosure. Submitting the number signs the driver in and sends a one-time passcode. The driver's answer at the checkbox is recorded the same way a customer's is.
4. Web sign-in
The same form on the web, for customers who book from a browser rather than the app. It can be opened directly at app.gethaulyn.com/login — no app install and no account are needed to see the number field, the unchecked consent checkbox, and the consent language beside it above the submit control. The same screen carries a Use email instead button directly below the submit control, which switches the same form to email sign-in without leaving the page — so a mobile number is not required to use Haulyn.
5. Business-partner path
Haulyn also fulfills deliveries and rides requested by business partners on behalf of their customers. In that case the customer enters their mobile number on the partner's own checkout or booking screen, not on a Haulyn screen, and Haulyn receives it through the Partner API.
Those customers are not enrolled for SMS, and Haulyn's automated messaging does not reach them. A partner's customer has never seen a Haulyn sign-in screen, so no consent is ever recorded against their number — and Haulyn's automated senders check the recipient's consent before sending, failing closed when there is none. The exclusion follows from the absent consent record rather than from any flag the partner sets. The delivery still runs and the partner tracks it through its own surface. Every number that receives Haulyn's automated trip, delivery, account or review messages is one the person entered themselves on a Haulyn screen and ticked the section 1 consent box on. Entering a number alone is not enough and never results in an automated message beyond the sign-in passcode.
Haulyn will begin messaging a partner's customers only once that partner meets the same bar Haulyn holds itself to in section 1 — not a lesser one. The partner must present an unchecked, optional consent checkbox carrying the section 1 label, with the section 1 disclosure displayed verbatim as static text beside it, naming Haulyn as the sender and linking to Haulyn's Privacy Policy and SMS Terms. The partner must not gate its own checkout or booking flow on that box, and must pass the answer back to Haulyn, which stores it against that person and honors it on every send. And the campaign must be amended to carry that partner's own opt-in form as evidence. No partner meets that today.
Campaign CKH6JR8 covers driver-to-customer messages carried over a masked number for the duration of a single job, so that neither party sees the other's real number. Its consent basis is the same as every other path on this page: a customer reaches it only by entering their own number on a Haulyn sign-in screen above and ticking the section 1 checkbox, and the driver side is a background-checked Haulyn driver. Haulyn authors no content on that campaign. End-to-end delivery on this path has not yet been demonstrated. Carrying it requires a 10DLC-registered number, numbers cannot be assigned to a campaign until that campaign is approved, and a send attempt from an unassigned number is refused by the carrier. Haulyn will verify delivery on this path as soon as numbers can be assigned.
6. Stopping messages
Replying STOP opts that number out. HELP returns support information. START re-subscribes. These replies are handled automatically, and the reply wording is held in constants frozen by an automated test that runs on every change. Telnyx maintains the opt-out list for Haulyn's account and enforces it at the platform: a message addressed to a number that has replied STOP is rejected by Telnyx rather than delivered. Full detail in SMS Terms.
The answer given at the checkbox is stored against the person, not merely against the screen, and it is checked at send time before Haulyn sends its automated trip, delivery, account and review messages. A number that never ticked the box does not receive those, and a withdrawal takes effect at the point of sending rather than at the point of display. Consent is captured at sign-in and withdrawn by replying STOP; Haulyn does not currently offer a separate settings control for it. Sign-in passcodes are unaffected either way: they answer a sign-in the person just attempted and are never sent unprompted.
7. Contact
Messaging compliance questions: support@gethaulyn.com. Haulyn messages are sent from (770) 746-7445.