Privacy Policy
Effective and last updated: 10 October 2026
This policy explains how MealBoss, operated by Firthouse, India, handles information through its restaurant-management app and related registration and support services. It applies to restaurant owners, managers, staff and people whose information they enter into MealBoss.
Privacy contact: firthouse.softwareengineer@gmail.com.
Current testing release. MealBoss 1.0.0 is distributed for internal QA testing, connects to the QA service and has in-app billing disabled. Use synthetic restaurant/customer records, not real restaurant operations or payments. Testers' actual account and device information is still personal data covered by this policy. Deletion-request intake is available; complete live deletion fulfillment is still being validated. Publishing this policy does not claim that validation is finished.
1. Information we handle
- Account and access information: name, email address, username, password verification data, account identifiers, requested job role, restaurant/branch memberships, permissions, invitation and verification records. Phone numbers are collected where you or an authorized administrator provide them. Passwords are processed for authentication and stored as password hashes, not as readable passwords.
- Restaurant and operational records: restaurant/branch names and identifiers, business contact details and addresses, menus, tables, orders, items, notes, prices, adjustments, payment-method/status records and staff actions. Customer names and phone numbers may be entered with orders. These records can contain personal information even when entered for a business.
- Notification and technical information: account-linked messaging tokens, an app-generated installation identifier and its server-side hash, notification preferences, app/platform information, request timestamps, security/audit events and service diagnostic information. Our hosting providers receive connection information such as IP addresses when handling network requests.
- Firebase notification information: Firebase Cloud Messaging and its Firebase Installations dependency process installation identifiers and SDK/app/device metadata to operate notifications. A Firebase installation identifier is distinct from MealBoss's app-generated identifier. Notification payloads can contain order numbers, order/branch/event identifiers and navigation information.
- Support and privacy correspondence: your email address, messages and any information you choose to send, plus request verification, case references and records of actions taken. Do not send passwords, one-time codes, payment-card details, identity documents or restaurant exports to support.
- Subscription records, where enabled: Google Play purchase identifiers/tokens, product and subscription status, billing events and verification/reconciliation records. Google handles the purchase interface and its payment information. MealBoss does not request full payment-card numbers or CVVs. This internal QA build has purchasing disabled.
The reviewed Android release does not include advertising, Firebase Analytics or Crashlytics SDKs. It does not request access to your contacts, microphone, camera or GPS location. A business address manually entered into MealBoss is not a reading of your device's GPS location.
2. Why we use information
We use information to create and authenticate accounts, verify access requests, apply restaurant and branch permissions, operate orders and restaurant records, deliver service notifications, provide business reports, respond to support/privacy requests, prevent unauthorized access and abuse, diagnose service problems, and maintain necessary audit and billing records.
Core account information is needed to use authenticated restaurant features. Other information depends on the fields and features you use. You can manage notification permission in Android settings; denying visible notifications does not necessarily stop all Firebase installation processing. Do not enter unnecessary personal or sensitive information into names, notes or business records.
MealBoss does not sell personal information or use it for targeted advertising in the current service.
3. Who can receive information
- Your restaurant team: authorized owners, managers and staff can access relevant records according to their roles and restaurant/branch membership. Restaurant administrators decide who should have business access. Information is not made public merely because it is stored in MealBoss.
- Service providers: Render hosts the API and public support pages; Neon hosts the configured PostgreSQL service; Google Firebase provides Android push notifications; Google/Gmail and configured email delivery services handle service and support correspondence. Providers process information needed to deliver their services. Google Play distributes the app and handles Play subscription services where enabled.
- Your chosen recipients: if you export, print or send restaurant documents, the destination you choose can receive the contents. Protect exported files and printed copies; MealBoss cannot remotely erase copies held by independent recipients.
- Necessary disclosures: information may be disclosed when required by applicable law or reasonably necessary to investigate abuse, protect security or resolve a dispute, limited to the relevant purpose.
Cloud and email providers may process data outside your country, including through international infrastructure. Their handling also depends on the service and contractual terms. See Render privacy, Neon privacy, Firebase privacy and security and Google privacy.
4. Security and local storage
The configured app-to-API connection uses HTTPS. The service uses authenticated access and server-side restaurant/branch authorization. The app uses platform-backed secure storage for sign-in tokens. Device-local settings and notification state may remain until removed through the app, operating system or uninstallation. These measures reduce risk but do not guarantee absolute security.
Keep your account credentials private, control access to shared restaurant devices, and contact support if you suspect unauthorized access. Uninstalling the app alone does not delete server-side account or restaurant records.
5. Retention and limits
Account and restaurant records are kept while needed to provide the service, maintain business records, handle support/disputes or meet applicable obligations. When deletion is requested, we review the account's personal data separately from other people's data and records that have a justified continuing business, security or legal purpose.
- Approved evidence policy: necessary security evidence has a 12-calendar-month retention period from the event; minimal deletion-case evidence has a 12-calendar-month period after actual case closure, subject to applicable legal holds. The current QA deployment does not yet establish end-to-end enforcement of these expiry periods.
- Financial and shared business records: automatic financial purging is disabled. The detailed financial retention schedule remains under review with an accountant; no fixed seven-year deletion deadline is promised. Personal information embedded in shared records requires a scoped review, not deletion of all records created by a departing staff member.
- Support messages, logs and exports: complete email threads and provider/log/export copies are not automatically covered by the minimal case-evidence period. Their minimization and applicable retention must be reviewed for the request. A final completion message must identify any justified retained categories and relevant time limits or criteria.
- Backups: restricted backup copies can persist until their applicable storage retention expires. Deletion records must be reconciled and reapplied before a restored system returns to service. A fixed expiry for all backup copies has not yet been verified for the current test service.
- Notification providers: removing our account-token link is not proof that every Firebase-held identifier has been erased. MealBoss does not store historical Firebase installation IDs. Provider retention and any required additional action must be considered before claiming completion.
Identifiers retained for access protection, restoration or financial integrity can remain pseudonymous personal information; we do not describe them as anonymous simply because a name or email was removed.
6. Access, correction and deletion requests
For questions, access/correction requests or deletion of your MealBoss account and associated personal data, email firthouse.softwareengineer@gmail.com. Available rights and exceptions depend on applicable law. We verify the requester's authority before disclosing information or changing an account.
Use the in-app account-deletion/support route or our public account-deletion page. The website does not require signing in or reinstalling the app. Send the email yourself; opening an email draft does not submit it or delete anything. Support supplies a case reference and a case-specific completion estimate and should explain unresolved work and any revised date.
A global account-deletion request can affect access to multiple restaurants. A sole owner must resolve ongoing ownership or separately authorize permanent restaurant closure; a general deletion email is not closure consent. Co-owned restaurants and other team members' information need separate protection.
Disabling an account is not the same as deleting its associated personal data. The current QA service has request intake but complete live fulfillment has not been verified. Requests must not be described as completed while required identity, copied-data, provider, backup or retention work remains unresolved.
Account deletion does not itself cancel or refund a Google Play subscription. Where applicable, manage your own subscription through Google Play's Payments & subscriptions settings and contact support for assistance.
7. Intended audience
MealBoss is a business tool intended for restaurant owners, managers and staff aged 18 and over. It is not directed to children. Do not enter children's personal information unnecessarily. If you believe a child has provided personal information through MealBoss, contact the privacy address so it can be reviewed and handled appropriately.
8. This website and policy updates
The MealBoss support and privacy pages contain no advertising, analytics scripts, tracking cookies or web submission form. Render still receives normal network-request information to serve and protect the pages. Selecting an email link opens your own email service; its provider handles the message under its own terms.
We may update this policy when the service or its data practices change. The effective date appears above. Material changes that require additional notice or permission will be handled before the affected processing begins.