TechToony Meeting Room

Privacy Policy

Last updated: September 16, 2026

This page explains what data is collected when you use TechToony Meeting Room ("the service"), a peer-to-peer video call for up to seven people, how that data is used, and who it is shared with. By using the service you agree to this policy.

The short version. Your audio, video, and chat never reach the server — they go directly between participants and are encrypted end to end. But everyone you connect to learns your IP address, and the operator records connection metadata including your IP and approximate city. Sections 3 to 7 are the ones worth reading.

1. Who runs this service

This is a personal project operated by an individual, self-hosted on a home server rather than a commercial cloud. For questions or requests, contact privacy@techtoony.com.

2. No accounts, no profiles

You do not register, sign in, or provide any personal information to place a call. There is no user record to build a profile on. Rooms are identified by a random ID generated by the server when you start a call, and the display name you type is whatever you choose — it is not verified and is not retained after the call.

3. What the server records

The signaling server writes a technical log to its own local disk containing:

Room membership itself is held in memory only and is gone the moment the room empties. Nothing about the content of a call is logged, because the server never has access to it.

Be aware: this log is not rotated or automatically purged. It is kept on the operator's machine until manually deleted, and it is not shared with or sold to anyone.

4. Operator notifications

To watch for abuse and to know when the service is being used, the server sends a message to the operator's private Telegram channel when someone knocks at a room, is admitted or refused, joins, leaves, is handed the host role, or when a host ends a call.

Those messages can include:

These messages are visible only to the operator. They remain in that private channel until manually deleted.

5. Peer-to-peer media and chat

Once you are in a call, your camera, microphone, any shared screen, and anything you type in the chat panel flow directly between participants using WebRTC. The server does not see, store, or relay that content, and WebRTC's encryption (DTLS-SRTP for media, DTLS for the chat data channel) is on by default with no way to disable it.

Chat messages are held only in the browser tabs that were in the room to receive them. They are never written to disk by this service, they are not carried by the signaling server, and there is no history: someone admitted to the call late sees an empty conversation, and closing the call discards it on every device at once.

Everyone in the call learns your IP address. WebRTC cannot connect without exchanging network addresses, and because there is no central server mixing the call, you hold a direct connection to every other participant — so in a seven-person call, six other people's browsers see your address, not one. This is inherent to peer-to-peer calling. If you do not want to share your IP, use a VPN or do not join the call.

Nothing prevents another participant from recording their own screen, exactly as on any other video service. Encryption protects the data in transit; it cannot control what the person at the other end does with what they see.

6. STUN and TURN servers

To find a route between two networks, the service uses public STUN servers operated by Google. Your IP address is briefly shared with them as a normal part of WebRTC connectivity.

When a direct connection is impossible — strict firewalls, symmetric NAT, or both parties on the same VPN — the call falls back to a TURN relay operated by ExpressTURN (free.expressturn.com). Your encrypted media then passes through that third party's infrastructure. It cannot decrypt the contents, but it does handle the packets and sees the addresses at both ends. The tile badge in the call reads TURN whenever this is happening, so you can always tell.

7. IP geolocation lookup

For the operator notification described in section 4, your IP address is sent to ip-api.com to look up an approximate city and country. Results are cached briefly to avoid repeat lookups. See their privacy policy for what they do with it.

This lookup is made over plain, unencrypted HTTP, because the free tier of that service does not offer HTTPS. Your IP address is therefore visible to networks between this server and theirs while the lookup is in flight.

8. Cookies and tracking

The service sets no cookies, uses no analytics, and loads no third-party advertising or tracking scripts. The display name you type is remembered in your own browser's local storage so you do not have to retype it, and never leaves your device except as part of a call you join.

The room ID, the optional password, and the host key all live in the URL fragment — the part after #. Browsers do not send fragments to servers, so they never appear in the HTTP request or in the access log. The room ID does reach the server over the WebSocket when you join, since it has to.

9. Data retention

10. Children

This service is not directed at children under 13. If you are under 13, please do not use it.

11. Your rights

If you are in the EEA or UK, you have rights under the GDPR including access, correction, deletion, and objection. To exercise any of them, email privacy@techtoony.com.

In practice there is very little to act on: with no accounts, the only thing tied to you is an IP address in a log file and a handful of notification messages. Tell us roughly when you used the service and those can be found and deleted.

12. Changes

This policy may be updated from time to time. The "Last updated" date at the top reflects the most recent change.