Privacy
Boons is a temporary, browser-based way to help someone you care about. This page explains what the service processes and what it does not keep.
Last updated July 20, 2026
Calls connect directly whenever possible. When a relay is needed for reliability, the encrypted stream passes through temporarily and is never saved.
When you start a session, your browser checks the temporary link, asks for the camera or microphone you choose to share, and connects the two participants. The helper can point, draw, freeze a frame, and download a screenshot on their own device.
Boons does not save video, audio, drawings, freeze frames, screenshots, recordings, accounts, profiles, or session history. Screenshots download directly to the helper's browser. Freeze frames stay in that browser and are released when they are no longer needed.
Media connects directly between the two browsers whenever the network allows it. If a direct connection is not possible, Boons can temporarily relay encrypted media through its TURN server so the call can continue. Relay traffic is not intentionally recorded or stored.
A frozen frame is a browser-local canvas copy of the current video frame. It is not sent to Boons. A screenshot is assembled in the helper's browser and downloaded locally; Boons has no screenshot upload endpoint.
A random session link identifies a temporary in-memory session. It lets the two browsers find each other through the signaling service and expires automatically. Ending a session removes it from the signaling service's memory.
Boons keeps daily aggregate counts—such as sessions created, successful connections, direct or relayed connection categories, reconnects, microphone fallback, fixed startup-failure categories, helpful or not-helpful responses, participant joins, abandoned sessions, capacity limits, and coarse timing ranges—to understand growth and reliability. The active report keeps at most 400 days of daily totals. It does not keep raw connection statistics, device details, free-form errors, session IDs, IP addresses, user-agent strings, referrers, cookies, persistent visitor IDs, media, drawings, or screenshots. Boons does not use these totals to identify or measure unique or returning users.
Networks and servers necessarily process connection information such as IP addresses, timing, and byte counts while delivering a session. Boons minimizes application logs and does not log media, drawing payloads, SDP offers or answers, or ICE candidates. Temporary TURN operational logs are kept outside Docker's host log stream.
Boons currently uses DigitalOcean to host the service, Cloudflare's public STUN service for connection discovery, Caddy and Let's Encrypt for HTTPS certificates, and GitHub Actions to deploy source code. Those providers may process the network and operational data needed to provide their services under their own policies.
Media is encrypted in transit, but no internet service can eliminate every risk. Device malware, a compromised participant device, browser bugs, unsafe links shared with others, or a participant recording their screen can affect privacy. Do not share a help link publicly.
There are no AI or contextual-analysis features in the current MVP. Any future feature of that kind must be explicitly activated by the user, process only the minimum frame or data needed for the immediate request, discard input after processing according to the selected provider and configuration, and be described here before launch.
If Boons changes how it processes or retains session information, this page will be updated before that change is released.
Questions about privacy? Contact privacy@boons.ai.