Last Updated: October 2026

This Privacy Policy describes how Pondchat ("we", "us") collects, uses, and discloses information when you use pondchat.com.

1. No Accounts

We do not require registration. We do not collect names, email addresses, or phone numbers as part of normal use. If you contact us for support, we will only use the information you voluntarily provide to respond.

2. Data We Collect

Usage analytics

We use Cloudflare Web Analytics on marketing pages to count page views and measure page-load performance. It is cookieless, aggregated, and does not track you across sites. The Telegram Mini App and in-call rooms do not load analytics. We do not use Google Analytics, and we never use analytics to identify individual users or to record conversation content.

Local storage on your device

Your browser may store preferences locally, including:

Theme (dark/light mode)
Media UI state (microphone, camera, and chat panel preferences)
Chat history in IndexedDB (up to 50 messages per room; cleared when you leave the room)

This data stays on your device unless you clear site data in your browser.

Server connection metadata

When you connect to a room, our infrastructure (Cloudflare Workers and Durable Objects) processes connection metadata such as room identifiers, WebSocket signaling messages, and client IP addresses for rate limiting and abuse prevention. We do not build user profiles from this data.

The public agent mint endpoint POST /api/agent/pond is anonymous (no account or API key). We use the client IP to enforce a short rate limit. Optional request fields source and label (≤64 characters) may appear in operational logs for debugging — do not send secrets or personal data in those fields. Mint outcomes and reads of agent discovery files (llms.txt, skills, MCP/A2A cards) are logged structurally (status, User-Agent, truncated IP hint) for abuse monitoring — not for advertising profiles. Minted rooms follow the same media and chat rules as other web ponds.

3. Communication Data

Media (video, audio, screen share)

Media streams are established directly between participants using WebRTC (DTLS-SRTP). We do not record or permanently store video, audio, or screen content on our servers. Pondchat does not provide recording or download of calls.

If direct peer-to-peer connectivity fails, encrypted media may pass through Cloudflare TURN relays. Relayed packets are not retained by us after the session.

Text chat

Chat messages are encrypted on your device with AES-GCM using a key derived from the room name (PBKDF2). The server stores ciphertext only—it cannot read message content without the room key.

Up to 50 recent messages per room may sit in Durable Object storage while someone is connected (hibernation and a late joiner in that same call). When the last person leaves, that copy is wiped. Anyone with the room link can derive the decryption key — including automated agents, who can read recent chat through our public MCP get_messages tool without appearing as a visible participant.

File sharing

Files are sent directly between participants over an encrypted WebRTC data channel — the same DTLS-protected connection as calls. They are never uploaded to, relayed by, or stored on Pondchat servers; our server does not even see file names or metadata. Each recipient must accept a transfer before any bytes flow. When a direct peer path is impossible, already-encrypted packets may transit Cloudflare TURN relays, which cannot decrypt them and do not retain them. Transfers are limited to 100 MB per file and exist only in your browser's memory until you choose to download.

Signaling

WebRTC offers, answers, and ICE candidates are relayed in real time over WebSocket during an active session. This signaling data is not archived as a permanent communication log (unlike encrypted chat history described above).

Noise cancellation

When you enable noise cancellation, microphone audio is processed locally in your browser (Web Audio API and RNNoise WASM). Processing happens on your device; we do not send raw audio to a separate noise-cancellation service.

4. Cookies and Similar Technologies

We do not set analytics or advertising cookies. Cloudflare may set strictly necessary security cookies (for example, for bot protection). Our progressive web app (PWA) may cache static assets via a service worker to improve load times; this does not store your conversations.

5. AI Agents and Public Documentation

We publish machine-readable documentation for developers and AI agents (for example, llms.txt, /.well-known/api-catalog, agent skills, MCP/A2A cards, and /docs/api/agent-pond.md). These resources describe the service and do not contain personal user conversation data.

Our robots.txt includes Content Signals declaring preferences for AI training and indexing (ai-train=no, search=yes, ai-input=yes).

Browsers that support WebMCP may expose optional tools (such as creating or joining a room URL) to on-page AI assistants. These tools call the same mint/join paths in your browser and do not upload conversation content to us.

Automated agents can also participate inside rooms: they may post and read chat through the MCP tools (announced as AI participants when they post, silent when they only read), or join as ordinary WebRTC media peers like any participant. No room content is sent to us beyond what the room protocol already handles.

6. Third-Party Services

Cloudflare: Hosting, DNS, Workers, Durable Objects, static assets, TURN relay when needed, and cookieless Web Analytics.
Google STUN: Public STUN servers used by WebRTC for NAT traversal (no media content is sent to Google).

7. Your Choices

Leave a room at any time; local chat history for that room is cleared on exit.
Deny camera, microphone, or screen-share permissions in your browser.
Clear site data in your browser to remove local preferences and IndexedDB chat history.

8. Children's Privacy

Pondchat is not directed at children under 13. We do not knowingly collect personal information from children.

9. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last Updated" date at the top will reflect the latest revision.

10. Contact Us

If you have questions about this Privacy Policy, contact us at hello@pondchat.com.