Privacy Policy
Last updated 2026-09-24
Audio flows directly between the Monitor and Parent phones, encrypted end-to-end by WebRTC's own DTLS-SRTP. This site's signaling relay only ever helps the two phones find each other — it forwards small JSON call-setup messages, never audio, and keeps no record of who paired with whom beyond a few minutes. There is no account, no cloud storage, and no analytics anywhere in the app.
What the signaling relay sees
When you pair two phones, each connects to the signaling relay
(wss://wewe-api.hub13.xyz by default) and joins a "room" named
after the six-digit pairing code. The relay's only job is forwarding
WebRTC session-setup messages (SDP offers/answers, ICE candidates)
between the two phones in that room so they can establish a direct
connection. Once that connection is up, audio flows peer-to-peer — the
relay is no longer involved and never sees or stores it.
The relay keeps no database and no long-term logs of pairings. A room that never gets a second peer is discarded after five minutes, and connection attempts from a single address are rate-limited — both purely to stop someone from squatting on or guessing pairing codes, not to retain data. See the signal-server source for the exact wire protocol.
Using your own relay instead
The default relay is a convenience, not a requirement. The Settings screen in the app lets you point at your own self-hosted instance (see the source repository for how) or one someone else you trust runs — both phones just need to agree on the same relay to pair.
What stays on your device
Paired monitors and the activity log (when a cry/noise alert fired, when a connection dropped) are stored in a local database on your phone and never transmitted anywhere. Uninstalling the app deletes them.
Permissions
| Permission | What it's for |
|---|---|
| Camera | Scanning a monitor's QR code to pair. Never used for anything else, and no image is ever stored or transmitted. |
| Microphone | The Monitor's live audio capture, and the Parent's push-to-talk. Streamed live over the encrypted peer connection only — never written to disk. |
| Foreground service, wake lock, notifications | Keeping the microphone and connection alive while the screen is off, and showing that persistent "Wewe is monitoring" notification — not for anything in the background you can't see. |
Changes to this policy
If what the app or relay does ever changes, this page changes with it. The source for the app, the relay, and this site is public — see the repository for the exact code.