Privacy Policy

In Plain Language

AI phone ordering

Calls are answered by an automated AI assistant. Calls may be recorded and transcribed.

What we keep

Call transcripts (and recordings if enabled), the phone number you called from, your name, delivery address, order details and payment status.

Why we keep them

To take and fulfil your order, to resolve disputes and refunds, to prevent fraud and abuse, to maintain and improve our service including training and evaluating our AI systems, and where the law requires.

Payments

Card details are entered only on Stripe's secure payment page. We never receive or store card numbers. Please do not read card numbers out loud on a call.

Text messages

We text you a payment link for your order. Reply STOP to opt out. Message and data rates may apply.

Service providers who process data for us

Telephone and SMS provider, speech and AI processing providers, payment processor, database hosting.

Your choices

You can request access to or deletion of your personal information by contacting us from the Help page. California residents have the rights described under the CCPA.

Retention

We keep call data for as long as needed for the purposes above.

Contact

Reach us through the Help page.

1. Who We Are

Mobile Bites AI ("Mobile Bites AI", "we", "us") operates an AI-powered phone and text ordering assistant for restaurants, available at mobilebitesai.com. This policy describes what we collect from restaurant owners and from the customers who call or text them, how we use it, who we share it with, and the choices you have.

2. AI Voice, Recording and Transcription

• Calls are answered by an automated voice assistant. Texts are handled by an automated messaging flow.
• Speech is converted to text by an automatic speech-recognition service. The resulting transcript, together with the order items, quantities, modifiers and prices, is what we process and store.
• Calls may be recorded and transcribed. We keep the transcript and the order record, and the recording where recording is enabled.
• California and several other states require consent from all parties before a call may be recorded. For that reason the assistant plays a spoken disclosure at the start of every call, before the conversation continues. Continuing with the call after that disclosure is treated as consent to the automated handling described here.
• If you would rather not speak with an automated assistant, say "representative" or "person" and the assistant will hand the call to the restaurant's own staff, or you may call the restaurant's own line directly.

3. Information We Collect

From restaurant owners

• Account details: business email, name and password or Google sign-in identity.
• Restaurant details: restaurant name, website, manager or owner name, business email, phone number.
• Setup details: your menu file, your allergy and substitution rules, fulfillment settings (pickup, delivery, last delivery order time), your customer dial-in number, an optional POS API key, and an optional SMS ticket phone number.
• Usage and billing data: minutes and messages used, invoice history and a Stripe customer ID once paid billing is enabled.

From customers who call or text a restaurant

• Phone number, name and any delivery or pickup details they give the assistant.
• Order contents, including allergen and substitution requests the customer volunteers.
• Order history with that restaurant, and the status messages we send back.

4. How We Use Information

• To answer calls and texts, take the order, and read it back for confirmation.
• To send the order to the restaurant's POS system or to an SMS ticket number.
• To send transactional messages: order confirmations, payment links, pickup and delivery updates, receipts.
• To apply the restaurant's own allergy and substitution rules while the order is being taken.
• To bill the restaurant for subscription, setup and usage.
• To prevent fraud, abuse and carrier-policy violations, and to debug and improve the assistant.

5. Sub-processors

We share only what each provider needs to do its job, under written confidentiality obligations. We do not sell your information.

We will notify restaurant owners before adding a sub-processor that handles customer data in a new way.

6. Payments

• Card details are entered on Stripe-hosted pages and never reach Mobile Bites AI servers.
• We do not collect or store card numbers, expiration dates or security codes in this app.
• Only a Stripe customer ID is stored on our side, so saved payment methods can be used for future invoices.
• Reaching the free-minute allowance does not charge anyone automatically; payment happens through the Stripe-hosted checkout the restaurant starts.

7. SMS and Mobile Messaging

• Messages we send are transactional: payment links, order tickets, confirmations and status updates.
• Customers can opt out of messages at any time by replying STOP. Reply HELP for help.
• Message and data rates may apply; frequency varies with order activity.
• No marketing messages are sent without separate, explicit consent from the recipient.

8. What We Keep and For How Long

For each customer who orders from a restaurant on Mobile Bites AI we keep:

• Phone number and name
• Saved delivery or pickup address
• Allergy and substitution notes the customer gave us
• Order history and the transcripts of those orders

These records are kept so the restaurant can re-serve the customer and so we can support the order. We keep them while the restaurant's account is active, then delete or anonymise them within 30 days of account closure, except where we must retain something longer for legal, tax or carrier-compliance reasons.

To request access, correction or deletion of your data, email privacy@mobilebitesai.com from the address on the account, or reply to any message you received. We will act on verified requests within 30 days and will tell the restaurant when the deletion affects an open order.

9. Legal Bases and International Transfers

We process data to perform the contract with the restaurant, for the legitimate purpose of operating and securing the service, and where required by law. Providers may process data outside your country; we rely on their standard contractual terms and safeguards.

10. Security

Data is encrypted in transit and at rest, access is limited to staff who need it, and each restaurant owner can see and edit only their own restaurant's records. POS API keys are stored as written by the owner and should be revoked in the POS dashboard at the end of the engagement.

11. Children

The service is for businesses. We do not knowingly collect information from children under 13.

12. Changes to This Policy

If this policy changes materially we will update the date at the top and, for restaurant owners, send an email before the change takes effect.

13. Contact

Privacy questions, deletion and access requests: privacy@mobilebitesai.com. Postal and formal legal notices: Mobile Bites AI, mobilebitesai.com.