Legal · Privacy

Privacy Policy

Last updated: 16 November 2026 · Applies to EnvoyHome 0.2.0 (desktop Settings shell and mobile thin client), and to any self-hosted daemon you run. Mobile bundle id: com.envoymesh.envoyhome.

EnvoyHome is self-hosted. Chat, memory, documents, and smart-home control run on your home daemon — not on an EnvoyHome cloud brain. This page explains what the software processes, where it goes, and what the publisher does not collect.

1. The model in one paragraph

You run the agent on a computer you control. The desktop and phone are thin clients: they connect to that daemon over the home.* channel and display what it returns. There is no EnvoyHome registration and no mandatory vendor cloud that receives your household chats, Home Assistant tokens, or model API keys.

Who is responsible? When you self-host, the person or household operating the home machine decides what data is stored and which optional providers are configured. The publisher supplies software; it does not operate your daemon.

2. Data that stays on your machine

  • Chats and sessions. Transcripts, tool calls, and turn artifacts live in the daemon’s state directory on the home computer.
  • Memory. Profile facts, standing notes, daily logs, episodic indexes, and accepted learn proposals are stored locally, keyed by household account.
  • Documents. Files you place under knowledge/ and their per-account SQLite index stay on the home machine. They are not uploaded to an EnvoyHome service.
  • Secrets. Model provider keys, channel bot tokens, smart-home credentials, and device private keys are kept by the daemon. The phone and desktop receive results, not the stored keys.
  • Approvals and grants. Pending approval records and grants are durable files per account so a restart cannot silently forget a question.

3. Data the phone may process

CategoryExamplesWhere it goes
Pairing & session Pair URI, device credential, WebSocket endpoint To your daemon / EnvoyMesh hosting peer only
Account id The household profile you select Same
Chat & media Messages, attachments you pick, speech dictation audio Chat/media to your daemon. On-device speech-to-text stays on the phone unless you use the operating system’s cloud dictation
Optional location Latitude / longitude when “Share location with Home” is on and the OS permission is granted Ephemeral injection into that turn only — not standing memory by default
Push tokens APNs / FCM device tokens Registered on your daemon via home.registerPushToken
Local network LAN discovery, ws:// connection to the house Local network only

4. Push notifications

If you enable notifications, the daemon can send approval-needed and schedule notify-only wakes through Apple Push Notification service (APNs) on iOS or Firebase Cloud Messaging (FCM) on Android. Those platforms receive the push payload and device token needed to deliver the notification. On Android, Firebase is used only when the build includes a google-services.json; FCM is the messaging service in that case.

5. Pairing and network access

A phone pairs by scanning a QR code minted in desktop Settings, or by entering the daemon endpoint. iOS requires Local Network permission to reach a LAN address. Pairing binds the device to specific household accounts; a device cannot act for an account it is not bound to, and the daemon denies the request if that binding cannot be resolved.

6. Optional model and tool providers

EnvoyHome can run local models (llama.cpp or Ollama) or call a provider you configure, such as an OpenAI-compatible or Anthropic-compatible endpoint. When you use a cloud provider, the prompt and the context needed for that turn leave the home machine and are handled under that provider’s terms. This may include excerpts from documents or memory retrieved for the turn. Chat sessions and memory may be sent to the provider you chose; the publisher is not that provider.

Privacy Mode is a hard switch: it forces local turns and refuses cloud tools — web search, web research, browser, HTTP fetch, page extraction, remote MCP, image generation, and messaging. When smart-home egress blocking is enabled, it also refuses Home Assistant / MQTT actuation and event-source notifications.

Tools that browse or fetch the web contact third-party sites from the home machine. Those sites receive the request as any browser request would, and their own privacy policies apply.

7. Smart-home data

Hub credentials and broker passwords stay on the daemon. Device state, camera, lock, and presence data are treated as sensitive: a sensitive result forces the turn to local inference rather than sending it to a cloud provider. Device state does not enter standing memory automatically. EnvoyHome integrates with your hub; it does not operate a smart-home cloud of its own.

8. What the publisher does not collect

  • No mandatory account registration, email address, or phone number for the self-hosted product.
  • No vendor-operated store of your household chats, memory, documents, or smart-home tokens.

9. Retention and deletion

  • Revoke a device from Owner Settings on the desktop or phone; the credential can no longer open a session.
  • Delete local history from the app or by removing the relevant sessions and memory files in the daemon’s state directory.
  • Uninstall the phone app to remove its local data; uninstalling does not delete the daemon’s data on the home computer.
  • Clear the daemon state directory on the home machine to remove local memory and stored tokens. Back up anything you want to keep first.

10. Children’s privacy

EnvoyHome is not directed at children under 13, or under the minimum age required in your jurisdiction. Do not create household profiles for children without appropriate supervision.

11. Your choices

  • Choose local-only inference, or enable Privacy Mode to block cloud tools and optionally block smart-home egress.
  • Decide which documents enter the knowledge base and which optional providers, channels, and MCP servers are configured.
  • Accept or reject proposed memory and skill changes through PendingLearn before they become durable.
  • Withdraw a device’s access by revoking its pairing.

12. Changes to this policy

This policy may be updated as the preview evolves. The date at the top of this page is the effective date of the current version. Material changes will be reflected here before a public store listing is submitted.

13. Contact

Questions about this policy or the preview build:

This page is a product privacy summary, not legal advice. A publisher submitting to an app store must supply the legal entity and contact required by that store.

← Back to EnvoyHome