Privacy Policy

Last updated: 2026-05-27

Bedcoder is an open-source remote control for AI coding agents. It is privacy-first by design: end-to-end encrypted, no signup, no user accounts. This page explains what little data is handled and how.

1. Summary

• No accounts, no email, no profile.
• Your messages, files, terminal output and screen frames between phone and desktop are end-to-end encrypted; keys are never shared with us.
• Our relay sees only encrypted bytes — it cannot decrypt your content.
• We do not sell, share, or monetize your data.

2. Data we don't collect

We do not collect or store:

• Names, email addresses, phone numbers, or any personal identifiers.
• The contents of your conversations with the AI agent.
• Your source code, files, or terminal output.
• Encryption keys (generated on your devices, delivered out-of-band via QR code).
• Conversation history — the relay drops messages once they are delivered.

3. Data the public relay handles

To route messages between your phone and your desktop, our public relay at relay.bedcoder.org stores the minimum needed to deliver traffic:

• Anonymous session record: a randomly generated session id, creation time, and last-active time. No identifying information is attached.
• Push notification token (optional): if you enable push notifications, the relay stores the platform token (Apple Push Notification service / Firebase Cloud Messaging) so it can wake the app when your agent needs attention. You can disable push notifications in the app at any time; the token is deleted when its session is removed.
• Connection metadata: IP address and timestamps are observed at the network level for abuse prevention and basic operational logs. They are not linked to your identity and are rotated within a short window.

Session records are deleted automatically when the session is removed in the app or when it expires due to inactivity.

4. Data stored on your devices

The Bedcoder app stores the following locally, on your phone only:

• The list of sessions you've paired: session id, nickname, relay URL, the symmetric encryption key, and the last-active time.
• An optional transcript cache so you can review conversations offline.
• App preferences (e.g., a custom relay URL).

You can remove this data at any time by deleting a session in the app, or by uninstalling the app.

5. Self-hosting

You can run your own relay (open source, MIT license). In that case, the data above lives entirely on your own server, not ours.

6. Third-party services

• Apple Push Notification service / Firebase Cloud Messaging: used solely to deliver push notifications. Subject to Apple's and Google's privacy policies, respectively.
• AI providers (e.g., Anthropic): your prompts and the agent's responses flow through the bedcoder process on your own machine to the AI provider you configure (typically Anthropic Claude). Bedcoder is not the AI provider; that provider's privacy policy applies to the prompts they receive. We do not see this content.

7. Children's privacy

Bedcoder is a developer tool and is not directed to children under 13. We do not knowingly collect personal information from children.

8. International users (GDPR / CCPA)

Because the relay only stores anonymous session metadata, data-access, portability, and deletion requests are satisfied by deleting the session in the app. If you need additional confirmation, contact us at the address below.

9. Security

• End-to-end encryption with XSalsa20-Poly1305 (TweetNaCl secretbox).
• Pairing verifies a commitment and a 6-digit Short Authentication String (SAS) to prevent man-in-the-middle attacks.
• The protocol, the relay, the agent, and the apps are all open source and auditable on GitHub.

10. Changes to this policy

If our practices change, we'll update this page and the "Last updated" date. Material changes will also be noted in the project's GitHub release notes.

11. Contact

Questions or requests: open an issue at github.com/shipunyc/bedcoder/issues.