wizzledocs

Privacy

Messages and files are encrypted end to end between the app and the bridge. There are no accounts, and the app includes no analytics or tracking libraries.

On your phone

• The keys stay in the phone's secure storage and never leave it.
• On iPhone, the chats and files the app keeps are unreadable while the phone is locked and are left out of backups. On Android, backups are off for the app.
• Dictation from the app's microphone button runs on the phone, so the audio never leaves it. If the phone can't recognize your language on the device, dictation stays off.

The relay

• Sees, for each connection: the IP address, the pairing id, whether it is the app or the bridge, and the size and timing of each frame.
• Stores, per pairing: a hash of the pairing secret and, for iPhone, the push token. Removing the pairing deletes both.
• Logs when each side connects and leaves, with its IP address and the first 8 characters of the pairing id.
• Holds encrypted frames for a side that is offline, in memory only.

wizzle.app

Each time the app connects to a bridge it fetches the newest bridge version from wizzle.app, to tell you when an update is out. That request carries your IP address and whether the bridge is NanoClaw or OpenClaw, nothing else.

Apple

A push to an iPhone carries the title "Wizzle", the text "New message" and the pairing id. Nothing about the message or the agent goes to Apple.

Your NanoClaw or OpenClaw

The bridge decrypts on your NanoClaw or OpenClaw machine, so everything you send is readable there, as it is for any other channel: by NanoClaw or OpenClaw, by your agents, and by the model providers they use. Keys you save go to that machine. Wizzle has no control over it.