How device pairing works
On the receiving browser, create a pairing QR or manual code. The monitoring browser scans or enters it, then both browsers compare and confirm the same code before pairing. No account is required.
What is end-to-end encrypted
Motion, test, monitoring, and heartbeat messages are encrypted in the monitoring browser and decrypted only in the paired receiving browser. Rapid Cactus relays ciphertext and cannot read alert contents. Hosting and network infrastructure can still observe ordinary connection metadata such as IP addresses, timing, duration, message frequency, approximate ciphertext size, and opaque endpoints communicating through the service.
What stays on the monitoring device
Camera video, frames, clips, thumbnails, audio, zone geometry, settings, and Event History never leave the monitoring browser through Remote alerts. Each alert is small text only.
What happens when the heartbeat stops
Encrypted heartbeats let the receiver show a delayed warning and alert once after 45 seconds without a valid monitoring heartbeat. A receiver connection failure is shown separately, and a restored heartbeat produces one restoration notice.
Why the receiving browser must remain open
The receiving browser must remain open and connected. Alerts do not arrive after the receiving browser is closed or suspended. Version 1 does not use background Web Push, email, SMS, or a third-party notification provider.
Remote-alert limitations
Delivery is not guaranteed. It depends on both browsers, both networks, and the receiving page remaining active. Remote alerts do not provide live camera viewing or make Rapid Cactus a certified security service.