Consent, opt-outs, approved templates, token usage and the limits of what FoodHubbie can guarantee on WhatsApp.
WhatsApp ordering and promotional campaigns run on the official Meta WhatsApp Cloud API, with templates approved by Meta. On an unofficial connection (a linked WhatsApp session) promotional sending is switched off by the software — those numbers are limited to transactional messages about an order in progress. This is deliberate: bulk promotional sending on unofficial connections is the fastest way to get a number restricted.
Marketing messages outside an open 24-hour conversation must use a Meta-approved template. The composer starts from approved shells (offer, discount, festive, win-back — in English and Hinglish) and fills in the offer details; the wording and structure that Meta approved is preserved. Meta may reject or later pause a template; when that happens the campaign cannot be sent until a replacement is approved.
Delivery, template approval and account standing are controlled by Meta. We cannot guarantee that a message is delivered, that a template is approved, or that Meta will not restrict a number for reasons outside our control. What we do control: consent-only audiences, approved templates, paced sending, an emergency stop, and keeping promotional sending off unofficial connections.
Message content, phone numbers and delivery status pass through Meta's Cloud API and are processed by Meta as a service provider. On this side, message history is stored with the outlet so staff can answer customers. See the privacy policy for the full picture.
Using FoodHubbie to message people who did not opt in, to send prohibited content, or to evade a Meta restriction ends the service for that outlet under the termination policy.