#security#transparency
How Parsely uses SMS—and what we don’t do
SMS is core to logging in v1: you text meals, we log them, we reply with macros. Here’s how that fits with account messages, Twilio, and your controls.
Jalen Stephens · Founder3 min read
Parsely uses SMS for two reasons: logging should meet you where you already are, and some account messages still need a reliable channel. We’re deliberate about what we send—and what we never send.
What we send
- Meal logging replies: when you text what you ate, we parse, log to your account, and text back a compact summary (foods, macros, and optional day context).
- Account and subscription notices you explicitly need (e.g. billing or access changes), described in product and legal docs.
- Security messages where required to protect your account (e.g. alerts or verification, depending on what we ship).
What we won’t do
- We don’t sell phone numbers.
- We don’t send marketing texts you didn’t ask for.
- We don’t share your number beyond our SMS subprocessor (e.g. Twilio) as described in the Privacy Policy.
Your controls
Reply STOP to opt out of non-essential SMS where applicable, and HELP for help. Some security messages may be limited where required for account safety—see the policy for details.
For retention, subprocessors, and rights, our Privacy Policy is the source of truth alongside what engineering actually implements.