SMS opt-in policy

Last updated: April 28, 2026

This page documents how Squash the Beef collects consent before sending SMS messages. It is published as evidence for our Twilio toll-free verification and as a reference for end users. The full privacy policy is at /privacy.

1. What Squash the Beef does with SMS

Squash the Beef is a peer-to-peer iOS app for friends to settle small grievances by paying small voluntary "make-it-right" amounts via Stripe. It is not a marketing app. SMS is used in three narrow, transactional situations only:

Friend invites — when a logged-in user invites a friend who isn't on Squash yet.
Beef notices — when a logged-in user files a beef against a non-user friend they previously consented to invite.
Verification codes — sent only when the user actively requests one on their own device.

No marketing. No drip campaigns. No purchased lists. No recurring sequences.

2. How consent is collected (in-app)

Before any SMS is sent to a recipient, the inviting user must affirmatively confirm consent inside the iOS app. The consent gate appears when a user is filing a beef and chooses to add a new friend by phone number ("File a beef" → friend picker → "Enter phone number"). The modal that opens is titled "Add Friend" and contains a Toggle with this verbatim text:

"This person agreed to receive a one-time invite SMS from Squash the Beef."

Below the toggle, a footer reminds the user:

"Required by SMS regulations. We send a single invite with a STOP-to-opt-out link."

Without affirmative toggle confirmation, the request is blocked client-side and no SMS is sent to the recipient. (For the alternate path where the user picks from their device's native contact picker, the affirmative selection of a contact is treated as the consent attestation — Apple's contact-picker UI requires explicit permission and the user must tap a specific contact to proceed.)

Screenshot of the Add Friend modal in Squash the Beef showing the consent toggle — The Add Friend modal with the consent toggle (in-app screenshot)

Source: ManualAddFriendSheet in FriendsView.swift (presented from CreateBeefView.swift) in the open repository at github.com/mraab-202/squash-the-beef.

3. Sample message bodies

These are the verbatim production templates, taken directly from smsService.js on our backend.

Friend invite (one-time, sent only after consent)

[Sender name] added you on Squash — the app for making things right between friends. Install: https://squashthebeef.net. Reply STOP to opt out.

Beef notice (one-time, when an existing user files a beef against a non-user friend)

[Sender name] wants to squash a beef with you ($X.XX): "[reason]". Install Squash to respond: https://squashthebeef.net. Reply STOP to opt out.

One-time verification code (user-initiated only)

Your Squash the Beef code is [123456]. Don't share it.

4. STOP and HELP keyword handling

Recipients can reply STOP (or UNSUBSCRIBE / END / QUIT / CANCEL) at any time to permanently opt out. Replies are routed through Twilio to our /webhooks/twilio endpoint, which:

Validates Twilio's X-Twilio-Signature header against the request.
Records the opt-out in our database, blocking all future messaging to that number across every sender on our platform.
Sends an automated confirmation that the recipient is opted out.

Replies of HELP receive an automated reply with our support email:

Squash the Beef: invites and beef notifications from friends. Reply STOP to opt out. Support: support@squashthebeef.net

5. Volume

Under 100 messages per day during the beta period. The app is in private TestFlight as of this writing and has not yet launched to the App Store.

6. Privacy and security

Phone numbers are stored only for users who create an account or are explicitly invited via the consent flow above.
We never share or sell phone numbers.
We do not upload the inviting user's address book — only the single contact they explicitly select is read by the client.
Full details: /privacy · /terms.

Contact: SMS / compliance inquiries — support@squashthebeef.net