Last updated: May 9, 2026

Overview


Mise is a Wear OS client that connects to your self-hosted Mealie server, with an optional companion phone app for easy setup. This app is an unofficial, third-party client and is not affiliated with or endorsed by the Mealie project.

Data Collection


Mise does not collect, store, or transmit any personal data to the developer or any third party. Specifically:
  • No analytics are collected
  • No crash reports are sent externally
  • No advertising SDKs or trackers are included
  • No personal information is shared with third parties

    • Data Storage


    All data displayed in the app (recipes, shopping lists, meal plans) is fetched from and stored on your own self-hosted Mealie server. The developer has no access to your server or its data.
    The app stores the following locally on your watch:
  • Server URL and API token — used to authenticate with your Mealie server
  • Cached shopping lists — for offline access
  • Recent recipe history — a list of recently viewed recipe IDs
  • Pending edits — shopping list changes made while offline, synced when connectivity is restored

    • The companion phone app does not store any data. Credentials entered in the phone app are sent directly to the watch via the Wearable Data Layer and are not persisted on the phone.
    This local data is stored in Android DataStore on the watch and is not transmitted anywhere other than to your configured Mealie server.

    Network Communication


    The Wear OS app communicates exclusively with the Mealie server URL that you configure. No other network requests are made. The security of this connection (HTTP vs. HTTPS) depends on your server configuration.
    During the QR code setup flow, the watch app temporarily runs a local HTTP server on your watch (accessible only on your local network) to receive credentials from your phone. This server is shut down immediately after setup.
    The companion phone app uses the Android Wearable Data Layer API to send configuration data (server URL and API token) to a paired watch. This communication happens locally between phone and watch — it does not pass through any external server.

    Children's Privacy


    This app is not directed at children under the age of 13 and does not knowingly collect any information from children.

    Changes to This Policy


    If this privacy policy is updated, the changes will be included in the app's release notes and the updated policy will be published alongside the new release.

    Contact


    If you have questions about this privacy policy, contact:
    Email: [email protected]