EMWaver app

Privacy Policy

EMWaver is built to be local-first. Core hardware control, scripts, and device workflows run on your device and do not require an EMWaver account, cloud activation, hosted relay, or subscription.

Last updated: June 12, 2026

Who We Are

EMWaver is an open-source electronics app and website by Continual MI. This policy covers the EMWaver native apps and the public website at emwaver.ai.

Information EMWaver Handles Locally

The EMWaver apps may store scripts, script drafts, imported files, settings, console output, device labels, connection status, firmware-update status, and captured hardware signals on your device. This local information is used to run scripts, render app UI, connect to supported boards, and help you continue local hardware work.

If you provision Wi-Fi for a supported ESP32-class board, the app sends the SSID and password you enter to that board over the selected local transport. On platforms that offer secure local storage, EMWaver may use that storage for convenience, such as saving a Wi-Fi password locally on your device. EMWaver does not send Wi-Fi credentials to a Continual MI server.

Permissions

EMWaver requests device permissions only to support local hardware workflows. Bluetooth is used to discover and connect to nearby supported boards. Local network and Bonjour access are used to discover and connect to supported boards on your LAN. USB access is used to communicate with supported boards and firmware-update modes.

On Android, location permission may be requested because Android ties Bluetooth scanning to location-related permissions on some versions. EMWaver uses that permission for nearby-device discovery, not to collect or track your physical location. Storage or file permissions may be used to import, export, or manage local scripts and related files. Notification permission may be used for app or device-status notifications where the platform requires it.

Network Use

Core hardware control does not require an EMWaver account or cloud service. The apps may use the network when you open documentation, download app or firmware-related resources, check the macOS update feed, connect to a supported board on your local network, or open external community and source-code links.

Desktop EMWaver apps may expose an optional local MCP endpoint on your own machine when you enable it. That endpoint is intended for local clients and is controlled by your app settings.

What We Do Not Do

  • We do not require an EMWaver account for core local hardware control.
  • We do not sell personal information.
  • We do not use local hardware access for advertising profiles.
  • We do not use hosted device activation, ownership checks, or subscription gates for local control.
  • We do not store your local scripts in an EMWaver cloud service by default.

Third-Party Services

EMWaver may link to third-party services such as Discord and Continual MI web properties. Those services have their own privacy practices. The public website may also produce ordinary hosting and security logs, such as IP address, user agent, requested URL, and request time, as part of operating the site.

Retention and Deletion

Local scripts, settings, console output, signals, and device workflow data remain on your device until you delete them through the app, remove local files, clear app data, or uninstall the app. Operating-system backups may include app-local data depending on your device and backup settings.

Children

EMWaver is a technical electronics tool and is not directed to children under 13. We do not knowingly collect personal information from children through the EMWaver app.

Changes

We may update this policy as EMWaver changes. When we do, we will update the date at the top of this page.

Contact

For privacy questions, contact Continual MI through the EMWaver support page.