Room access and data privacy
This is a technical explanation of Telepaste's current data flow. No account is required, but that does not mean every transfer is anonymous, end-to-end encrypted or stored only on your devices.
Your room code is an access key
Anyone who knows a room code or has its invitation link can join that room and access its shared items while they are available. There is no account-based membership approval. Generate a hard-to-guess code, avoid public or reused codes, and check the connected-device list before sharing.
Invitations include the room code in their URL. They can remain in browser history or in messages where you share them. Keep them private. Search-engine exclusion is not authentication and cannot prevent someone with a link from visiting it.
Text and room metadata use the service
Room messages, display names, file metadata and connection-signaling messages pass through the Telepaste service. The hosted version runs on Cloudflare. Connection IP addresses are processed for rate limiting and session handling.
HTTPS protects the hosted browser connection in transit, but the application does not end-to-end encrypt text messages against the server. Image previews may also be included in room metadata even when you later transfer the original file using Direct.
File storage depends on the transfer path
- Direct: file bytes travel on a browser-to-browser WebRTC data channel. Choosing Direct does not upload the original file to the Cloud cache. Signaling and file metadata still use the service.
- Cloud: the service receives the upload, streams it to the receiver and caches successful uploads in Cloudflare R2. Cached files are temporary, with a 24-hour retention limit subject to the item's expiry.
- LAN: your local Telepaste server handles the file and can retain a temporary copy. Stopping that local server clears its temporary files. Local HTTP is not the same protection as the hosted HTTPS connection.
Expired items are removed by the service's cleanup process. These limits are not a promise of immediate physical erasure from all infrastructure. A recipient's downloaded copy is outside Telepaste's control.
What is saved in your browser
The application remembers the last room code and display name in local storage and caches server information briefly in session storage. Original selected files and active transfers depend on the open page. Reloading or closing it can interrupt transfers or remove access to an uncached original file.
Leaving a room is not a delete-everywhere operation. On a shared device, clear the site's browser data when you are finished. Do not treat short-lived download URLs as permanent or as a substitute for keeping invitations private.
Website performance measurements
The hosted site uses Cloudflare Web Analytics to measure page visits and loading performance. This is separate from the file-transfer service and does not require an analytics account from you. Read Cloudflare's description of Web Analytics for how its browser beacon works. Telepaste does not add custom analytics events containing room codes, shared text or filenames.
For the practical choices, read the file transfer guide. For room codes and copying, see the online clipboard guide.