Privacy Policy

MealDispatch ("we", "us") provides operations software for meal-delivery kitchens in India — a marketing website at mealdispatch.com, a mobile app (iOS and Android), and the backend services that connect the two. This policy explains what we collect, why, and the choices you have.

Who the policy covers

• Operators — staff of a meal-delivery kitchen who sign in to the mobile app or the web dashboard to manage menus, orders, customers, and invoices.
• Subscribers — end customers who use the subscriber-side of the mobile app to pick meals, schedule skips, and view invoices.
• Website visitors — anyone browsing mealdispatch.com or submitting the contact form.

What we collect

From operators and subscribers using the app:

• Account credentials — email and/or phone number, authenticated through Amazon Cognito. We store only what Cognito keeps; passwords are never visible to us.
• Organization profile — the kitchen's name, slug, and city, provided during onboarding.
• Operational records entered by operators about their own business: menus, meal photos, plan definitions, customer names, phone numbers, delivery addresses, orders, invoices, and ledger entries.
• Subscriber selections — meal picks, skip schedules, payment status. These belong to the kitchen the subscriber is signed up with.
• Photos chosen via the mobile photo picker — used only to attach an image to a meal you create. Uploaded to our Amazon S3 storage and served back via the kitchen's menu views.
• Device-level diagnostics — error logs and crash reports for the mobile app and Lambda backend, with no third-party advertising SDKs.

From website visitors:

• Contact form submissions — name, email, kitchen name, and message, used only to reply to your enquiry.
• Server access logs — IP address, user-agent, request path, kept by our hosting provider for security and debugging purposes.

What we do not collect

• No advertising identifiers (IDFA, AAID).
• No third-party analytics that fingerprint users across apps.
• No payment card details — when payments run through UPI or other flows, the kitchen's payment provider handles them directly.
• No microphone, camera, contacts, calendar, or location access.

How we use the data

• To authenticate operators and subscribers and load only their own organisation's data.
• To deliver the core product functions: menus, orders, deliveries, invoices, skips, reminders.
• To send transactional notifications (e.g. WhatsApp reminders, order cutoff warnings) initiated by the operator's settings.
• To investigate bugs, prevent abuse, and keep the service up.

We do not sell personal information. We do not share it with advertisers. We do not use it to train AI models outside of the kitchen's own scoped data.

Where the data lives

All application data is stored in our Amazon Web Services account in the ap-southeast-2 (Sydney) region. Photos are stored in Amazon S3 in the same region. Auth identities are managed by Amazon Cognito. We may move data to other AWS regions in the future and will update this policy if we do.

Subprocessors

The services we rely on to run MealDispatch:

• Amazon Web Services — hosting, storage, auth, queues.
• Twilio / WhatsApp Business — operator-initiated reminders, when enabled.
• Expo Application Services — mobile app build pipeline.

How long we keep it

Data is retained for as long as the kitchen's account is active. On account deletion, application data is purged within 60 days; backups may persist for up to 90 days. Anonymised aggregate metrics (e.g. order counts) may be kept indefinitely for product analytics.

Your rights

You can request access to, correction of, or deletion of any personal data we hold about you. Operators can edit or delete most data directly inside the app. For deletion requests beyond that, email [email protected] and we will respond within 30 days.

Children

MealDispatch is built for kitchen operators and adult subscribers. We do not knowingly collect information from anyone under 13. If you believe a child has signed up, email us and we will remove the account.

Changes to this policy

We update this page when our practices change. The "last updated" date at the top is the effective date. Material changes will be announced to active operators by email.

Contact

Questions or requests: [email protected]. For general support, use the contact form.