Privacy at WeeTransfer.uk
Anonymous by design.
You do not need an account, and WeeTransfer.uk does not fingerprint your browser.
How this browser remembers
A private, secure cookie identifies files uploaded from this browser. It is never included in public links. If you clear it or change device, management access cannot be recovered.
Cookie policy
We use only essential cookies that make WeeTransfer.uk work. We do not use advertising, social-media, or cross-site tracking cookies, and we do not ask third parties to place cookies through this site.
| Cookie | Purpose | Duration |
|---|---|---|
__Host-WeeTransfer.Owner |
Lets this browser view and manage files it uploaded. Its random value is stored securely and is not used in public sharing links. | Up to 270 days |
__Host-WeeTransfer.Antiforgery |
Helps protect forms and upload actions from forged requests. | Browser session |
Both cookies are first-party, secure, and HTTP-only, so browser scripts cannot read them. You can remove them in your browser settings; doing so removes access to the My files list for uploads made from this browser.
Anonymous usage statistics
We record limited operational statistics so we can understand site usage and keep the service reliable: the page or action category, request method, response status, duration, upload size where applicable, and the anonymous upload-owner record when one is already available. We do not use cookies for analytics, and these records are deleted after 90 days.
How your file travels
WeeTransfer offers two ways to send a file. The important difference is whether we temporarily store a copy.
Server Share
Best when the other person will download later.
Quick Share
Best when both people are online together.
Quick Share, in plain English
Quick Share is like handing a file directly to someone. Both people keep the page open, and the file moves from one browser to the other through an encrypted connection. WeeTransfer helps the browsers meet, but the file itself is not uploaded to or kept by us.
If the two browsers cannot connect directly, Cloudflare acts like a delivery route for the encrypted file. Cloudflare can see the network addresses involved and how much data passes through, but not the contents of the file. The four-digit PIN stops working after 10 minutes if nobody uses it.
For the technically curious
Quick Share technical details
File bytes travel over an encrypted WebRTC DataChannel. WeeTransfer temporarily handles signalling messages so the browsers can negotiate the connection, while Cloudflare provides STUN discovery and short-lived TURN relay credentials. If TURN is needed, Cloudflare relays encrypted traffic and necessarily processes both browsers' IP addresses and the relay byte count.
Unused four-digit PINs expire after 10 minutes. Connection details are removed after the transfer, when the session expires, when either browser disconnects, or when the service restarts.
To control relay costs, WeeTransfer keeps a random session ID, the declared file size, a conservative reserved data allowance, completion status, and the successfully reported byte count. We do not record the filename or file contents. Monthly usage records are retained for up to 13 months.