Skip to content
MilEats
—Loading launch countdown
SMS

SMS Disclosure

Effective: 2026-05-21 (v2) Prior version effective: 2026-05-03 (v1, initial publication)

This page explains exactly what SMS messages MilEats sends, how you opt in, how to opt out, and the legal disclosures required by the Telephone Consumer Protection Act (TCPA), state analogs, and CTIA / mobile-carrier guidelines.

This page is the canonical SMS disclosure. Consent is captured outside our Privacy Policy and outside our Terms of Service, as a separate explicit action you take in the MilEats app.

1. Who is sending the messages

MilEats LLC, a Delaware limited liability company. SMS is delivered through Twilio Inc. as our messaging service provider. You can reach us at:

2. What messages you will receive

By providing your phone number and explicitly opting in inside the MilEats app, you agree to receive SMS text messages from MilEats for the following purposes only:

  • Order confirmations. Receipt and pickup or delivery time.
  • Delivery status updates. Driver assigned, en route, arrived, delivered.
  • Customer support replies. Responses to support tickets you initiated.
  • Account and security alerts. One-time login codes (only if you opt into SMS login), password reset confirmations, suspicious-activity notices.

We do not send promotional or marketing SMS without separate, additional opt-in. Marketing SMS, if we ever offer it, is captured through a distinct consent flow with its own checkbox and disclosure language.

3. How you opt in

We do not collect SMS consent through our Privacy Policy, our Terms of Service, or as a side effect of creating an account. SMS consent is captured separately at the point of use, through one of the following four surfaces. Each surface is independent. Opting in on one surface does not opt you in on another.

  1. Customer app, Profile -> Edit Phone screen (order-update SMS). You enter your phone number and explicitly check a box labeled "Yes, send me SMS updates about my orders. MilEats will text order confirmations, delivery status, and support replies." The checkbox is unchecked by default. The screen lists the message categories, frequency, cost disclosure, STOP / HELP instructions, and links back to this disclosure and the Privacy Policy. Opting in here is never required to use the Platform.
  2. Customer app, Checkout (first order, order-update SMS). If you have not already opted into order-update SMS, the checkout flow asks you to opt in alongside delivery instructions, with the same explicit unchecked-by-default checkbox and disclosure links.
  3. Customer app, SMS sign-in (verification code only). When you choose phone-number sign-in on the login screen, the phone-input step displays a disclosure block above the Continue button explaining that tapping Continue requests a one-time 6-digit verification code by SMS from MilEats to confirm your number, with frequency ("up to one code per sign-in attempt"), cost ("message and data rates may apply"), STOP / HELP instructions, and links to this disclosure and the Privacy Policy. Email sign-in is offered as an equivalent alternative on the same screen. Submitting the phone number is an explicit consent capture for the single verification-code message, narrowly scoped under TCPA's transactional carve-out for account-verification messages. Verification-code consent is single-use and naturally re-captured at each sign-in attempt.
  4. Partner app, SMS sign-in (verification code only). Restaurant operators sign in to the partner app via Auth0 passwordless SMS. The phone-input step displays a disclosure block above the Continue button equivalent to surface 3. Submitting the phone number is an explicit consent capture for the one-time login code. Email, Apple, and Google sign-in are offered as equivalent alternatives on the same screen. Broader SMS to partners (new-order alerts, payout alerts, etc.) requires a separate future opt-in flow not yet implemented.

Consent for the order-update surfaces (1 and 2) is recorded against your account with a timestamp and the version of this disclosure you agreed to. You can review or revoke that consent anytime from Profile -> Edit Phone. Consent for the verification-code surfaces (3 and 4) is single-use, captured fresh per sign-in attempt, and does not persist between attempts.

Screenshots of the in-app opt-in screens are published for transparency and for review by mobile carriers and messaging providers. Three published screenshots cover all four surfaces above; surfaces 1 and 2 share the same checkbox component, so edit-phone.png is the canonical evidence for both:

Reviewers verifying compliance can also request a TestFlight build by emailing support@mileatsdelivery.com.

4. Frequency

Up to approximately 10 messages per order across the order lifecycle. Frequency may exceed this for orders with multiple status changes (delivery exceptions, support escalations, address corrections). MilEats does not send unsolicited SMS outside of an active order or an active support thread.

5. Cost

Message and data rates may apply, depending on your wireless carrier and plan. Contact your wireless carrier for details. MilEats does not charge you for SMS.

6. How to get help

Reply HELP to any MilEats SMS to get a customer-support contact link. You can also email support@mileatsdelivery.com or visit https://mileatsdelivery.com/contact at any time.

The HELP auto-reply we send is:

"MilEats support: support@mileatsdelivery.com or https://mileatsdelivery.com/contact. Mon-Sun, 9am-9pm Pacific Time. Reply STOP to unsubscribe."

7. How to opt out

Reply STOP to any MilEats SMS at any time to immediately unsubscribe. You will receive one final confirmation message and no further SMS from MilEats. After you reply STOP:

  • We mark your account as having revoked SMS consent.
  • We log the timestamp of the revocation.
  • Twilio honors the opt-out at the messaging provider level.
  • You can opt back in at any time by replying START or by re-checking the consent box in the MilEats app.

The STOP confirmation we send is:

"You're unsubscribed from MilEats SMS. No further messages. Reply START to re-subscribe or visit https://mileatsdelivery.com/legal/sms."

8. Privacy and data handling

Phone numbers and SMS interaction logs are processed only for the purposes described above. Specifically:

  • We do not sell your phone number.
  • We do not share your phone number with third parties for their own marketing.
  • We share your phone number with Twilio (our messaging service provider) and, during an active order, with the assigned rider via Twilio's proxy-masking so the rider never sees your real number.
  • We retain SMS metadata (delivery status, opt-in or opt-out events, timestamps) for 13 months for delivery quality and legal-compliance purposes, then delete it.

For the full data-handling picture, including your rights and how to exercise them, see our Privacy Policy and our Do-Not-Sell page.

9. Carrier disclosures

  • Wireless carriers (T-Mobile, AT&T, Verizon, and others) are not liable for delayed or undelivered messages.
  • MilEats is registered with The Campaign Registry (TCR) and uses A2P 10DLC and toll-free messaging routes that are verified and approved for the message types described above.
  • If your carrier blocks our SMS for any reason, contact us via email or the contact form so we can investigate.

10. Changes to this disclosure

We will update this page when we change SMS message types, opt-in language, frequency, or our messaging provider. Material changes are recorded with a new "Effective" date at the top of this page. We will not retroactively use SMS consent collected under an older disclosure version for new message types not described in that version; we will re-prompt you for fresh consent.

11. Contact

For SMS-specific questions or to verify how your number is used:

For privacy rights generally, see our Privacy Policy and Data Subject Request form.