- What Notelocal collects
- The studio collects nothing: there is no backend, no account, no login, no telemetry and no online crash reporting. On your own computer, in the app's data folder, Notelocal keeps the thread (text, links, file items and their details), the files themselves, the device's own key and certificate, the list of devices you paired, their last local addresses, and the helper's settings. Paired devices hold copies of the same thread.
- Where processing happens
- Everything happens on your own devices, and items travel directly between paired devices over pinned, mutually authenticated TLS 1.3. Two named exceptions, both visible to other devices on the same local network and neither carrying content: while running, the helper announces a Notelocal service on the local network, so any device there can see that a Notelocal device is present; and while a pairing code is showing, that announcement says so. Unpaired devices receive nothing.
- What leaves your machine
- Measured on both computers in October 2026, from test builds rather than a store release. On Windows, from an installed test package, the only outbound connection seen was to the paired device on the home network, and its local-network announcements went only to the standard local multicast addresses. On a Mac, from a test build, a three-minute watch saw one remote end, the paired device on the home network, and its announcements went only to the local multicast address. A store release and the phones have not been measured, so this page makes no claim about them. By design its code refuses any address outside the local network, and there is no server or account for it to reach.
- Effective date
- 2026-10-08(provisional while the product is in development; confirmed at its Store release)
Read the Notelocal licence agreement