Privacy Policy

1. No account, no profile

Pling has no sign-up, login, or user profile. We do not collect your name, email address, phone number, or any identifier when you open a room.

2. What we process to connect you

To coordinate presence and WebRTC signaling, our server briefly handles:

• The room name and the display name you choose;
• Ephemeral signaling messages needed to establish peer connections;
• In-room chat messages, agenda, shared notes, and live-caption transcript text, which are relayed to participants only and not persisted.

This data lives only in memory for the duration of the room and is discarded when the room becomes empty. We do not store, archive, or index it.

3. What we never collect

• Pling servers do not record, capture, or store your audio or video;
• We do not log the contents of your chat messages after the room closes;
• We do not sell or share personal data with advertisers;
• We do not build behavioral profiles of users.

4. Peer-to-peer media

Audio, video, and screen-sharing streams travel directly between participants' browsers using encrypted WebRTC connections whenever the network allows. Your media does not pass through or get stored on Pling servers. On restrictive networks, a TURN relay may forward encrypted media transit; the relay cannot read the encrypted content.

5. Local storage

Pling stores your chosen display name in your browser's localStorage so you don't have to retype it. We also store your cookie consent choice ("accepted" or "rejected"). These values stay on your device; you can clear them anytime from your browser settings.

Live speech recognition runs in your browser. The resulting caption text is relayed through the meeting server so participants can share a transcript, then discarded when the room becomes empty. After you leave, your browser keeps your meeting record in memory only while the room page remains open so you can review, copy, or download it.

If a participant starts local recording, their browser combines the call's media and saves it on their own device. Pling shows everyone in the room who is recording, but the recording is not uploaded to or stored by Pling. Participants are responsible for obtaining any consent required by law.

Meeting summaries are optional. At the end of a call, Pling may keep an encrypted-in-transit, short-lived copy of the existing transcript in server memory and issue your browser a single-use authorization. Only if you select “Send transcript and summarize” does Pling send that transcript to OpenRouter, which routes it to an available third-party AI model. Pling requests providers that do not use prompts for data collection by default. Availability and provider practices can vary. Pling does not persist the transcript or generated summary to a database or localStorage. A record persists on your device only if you copy or download it.

6. Measurement and analytics

Pling uses the following measurement tools to understand which pages and features are used. None of them are used for advertising or cross-site behavioral tracking. Where required by law, these scripts load only after you accept cookies via the consent banner.

• Cloudflare Web Analytics — privacy-preserving, aggregate page-view metrics and bot detection. Cloudflare may also retain short-lived edge logs (IP, request timing) for security and performance.
• Google Tag Manager (GTM) — loads and manages our analytics tags on the Pling domain.
• Google Analytics 4 (GA4) — counts page views and feature usage. We have configured GA4 to anonymize IP addresses at collection. GA4 may set cookies such as _ga and _ga_<container-id>.
• PostHog — records the limited product events we explicitly send, such as room creation or joining and in-call feature actions, to help us improve Pling. We disable PostHog's automatic click and page-view capture. PostHog may process a pseudonymous browser identifier, device and browser information, IP address, and the event data described above. Our PostHog endpoint is hosted in the EU.

See our Cookie Policy for the full list of cookies these services set and how to disable them.

7. Third parties

Pling interacts with a few third parties to function:

• Cloudflare, which provides our edge, TLS, Web Analytics, and DDoS protection;
• Google (via Tag Manager and Analytics 4) for aggregate usage metrics, as described above;
• PostHog for consented product-usage analytics, as described above;
• OpenRouter and the selected AI model provider, which receive transcript text only after you explicitly request a meeting summary;
• Public STUN/TURN providers (such as Cloudflare) that help browsers locate each other for WebRTC;
• Google Fonts, which may set its own cookies or logs when fonts load;
• Your browser vendor, whose WebRTC implementation governs encryption and local device access.

These parties have their own privacy policies that apply when you use their services. We do not sell or share personal data with advertisers.

8. Server logs

Cloudflare and our hosting provider may retain short-lived, automated server logs (such as request timing and IP addresses) for operational and security purposes. These are not associated with your meeting content and are rotated according to the provider's policies.

9. Children

Pling is not directed at children under 13 (or the minimum age in your jurisdiction). If you believe a child has used the Service in a way that requires action, please reach out.

10. Your choices

• Use any display name you like — it doesn't have to identify you;
• Grant or deny camera and microphone permissions in your browser;
• Decline measurement cookies in the consent banner, or clear them later;
• Leave a room at any time, which ends relay of your media and messages;
• Clear your browser's localStorage to remove your saved display name and consent choice.

11. Changes to this policy

We may update this Privacy Policy. The "Last updated" date above indicates the latest revision; continued use after changes constitutes acceptance.

12. Contact

Privacy questions? Reach out through our Contact page.