Control over your data.

No required account, Firebase, cloud AI or analytics SDK. Data is held in the device’s encrypted database.

1Steps

  1. Notification content is not written to durable history.
  2. Only data for your configured action goes to the Home Assistant/HTTP service you choose; Drive is optional.
  3. You manage passwords and backups.
  4. This page describes current data flows; the company’s final legal privacy policy must be completed before store release.

2Limits

  • Automations, history, connections, keys, and preferences are stored in an encrypted database. The password vault protects the key to these data. If you forget your password, we cannot recover it.
  • Contains only feature counts, statuses and error codes. Flow names, addresses, notifications, variable values and credentials are excluded. The file is saved where you choose and is not sent automatically.
  • Sender names match separately from message text. If the app does not provide sender details, the filter does not match. A display name is not verified contact identity.

Privacy · Web

This site uses no analytics or advertising SDK. Appearance and language stay in your browser; search and examples run locally.

Next

Search the guide