Spheric Labs

SMS / Text Messaging Program

This page documents the SMS (text message) program operated by Spheric Labs (“Spheric Labs,” “we,” “us,” or “our”). It describes who sends messages, how we obtain consent, what messages look like, and how recipients opt out. Messages are transactional and operational — we do not send marketing or promotional texts through this program.

Who sends messages

Spheric Labs builds and operates its own web applications, and those applications send transactional/operational SMS to their end users. The primary application enrolled in this messaging program is DirtBoss, a dispatch and ticketing app for dirt-hauling companies. Typical messages include dispatch notifications, bill-of-lading (BOL) upload links tied to a specific ticket, and account or task updates. These are operational messages sent to people who use the app or whose account holder has added them (for example, a dispatcher adding a driver).

Our applications and their domains

So that message content can be verified against the business sending it, here are the applications in this program and the domains that appear in their messages:

DirtBoss operates at dirtbossapp.com. Links contained in our SMS messages use the dirtbossapp.com domain. Tokenized paths such as /t/… (for example https://dirtbossapp.com/t/abc123xyz) are DirtBoss’s own first-party upload links — for instance, a secure BOL upload link scoped to a single ticket. They are not a third-party URL shortener.

Where we collect phone numbers

Phone numbers are collected inside our applications through in-app forms — for example during account creation, work-order intake, or when an account holder adds a team member (such as a dispatcher adding a driver). At the point of collection, the following consent disclosure is shown directly beneath the phone field:

By adding a mobile number, you confirm this person has agreed to receive a one-time text from DirtBoss to confirm SMS enrollment. After they reply YES, DirtBoss will send them operational texts (dispatch, ticket uploads). Msg & data rates may apply. Msg frequency varies. Reply STOP to opt out, HELP for help. Terms · Privacy Policy
Representative rendering of the DirtBoss “Add driver” form. The SMS consent notice (shown in muted text beneath the phone field) appears at the point of collection in every DirtBoss form that captures a mobile number.

How opt-in works (double opt-in)

After a mobile number is entered, our system sends a single confirmation text asking the recipient to opt in. Only numbers that reply YES receive operational messages. If there is no YES reply, no further messages are sent. The confirmation message reads:

Opt-in confirmation text

[App Name] (a Spheric Labs product) would like to send you SMS updates about your account, work orders, and tasks. Reply YES to confirm. Reply STOP to opt out. Msg & data rates may apply. Msg frequency varies. Terms: https://www.sphericlabs.dev/terms Privacy: https://www.sphericlabs.dev/privacy

“[App Name]” is replaced with the specific product sending the message — for example, “DirtBoss.”

Sample messages you may receive

Once opted in, recipients receive operational messages. Every message identifies the sending application and includes opt-out instructions. For example:

Sample operational text

DirtBoss: upload your BOL for ticket 1042. Link expires in 7 days. https://dirtbossapp.com/t/abc123xyz Reply STOP to opt out, HELP for help.

Opting out and getting help

You can opt out at any time by replying STOP (we also honor END, CANCEL, UNSUBSCRIBE, and QUIT). You will receive a single final confirmation that you have been unsubscribed, and we will not send further messages unless you opt in again. Reply HELP for help, or contact us any time at hello@sphericlabs.dev. Message frequency varies. Message and data rates may apply.

Your data and privacy

We do not share mobile opt-in data — including phone numbers and SMS consent — with third parties or affiliates for their marketing or promotional purposes. Phone numbers are used only to operate the application the recipient is associated with. See our Privacy Policy for full details on how we handle personal information.

More information

Privacy Policy · Terms of Service