Terms & acceptable use

Plain English, because there is not much to say. The service introduces two browsers to each other. What you then send is between you and the person you sent it to.

What the service is

xfrit helps two browsers establish a direct connection so a file can pass between them. We do not receive, store, host, scan or forward the file. By using the site you agree to these terms; if you do not, please do not use it.

This is worth stating in the terms rather than only in the marketing, because it defines what you are and are not being offered. There is no relay server. If the two browsers cannot establish a direct connection — which some restrictive networks prevent — the transfer fails. It does not quietly fall back to routing your file through our infrastructure. You are being offered a direct connection or nothing, and that is deliberate: it is what makes the privacy claims on this site architectural rather than a promise about our conduct.

Provided as-is

The service is free and provided without warranty of any kind, express or implied, including any implied warranty of fitness for a particular purpose. We do not guarantee that it will be available, that a transfer will succeed, or that it will succeed at any particular speed.

Transfers genuinely can fail. Some networks block direct connections between browsers outright. Closing a tab ends a transfer permanently, because there is no server-side copy to resume from. Do not use this as the only copy of anything you care about. It is a way to move a file, not a backup.

Acceptable use

You agree not to use the service to transmit, or attempt to transmit:

• anything unlawful where you are, or where the recipient is;
• material that infringes copyright or other rights you do not hold;
• malware, or anything designed to damage or gain unauthorised access to a system;
• material that sexually exploits or endangers children;
• content used to harass, threaten, defraud or impersonate;
• anything sent in order to evade a court order or other lawful restriction.

You are responsible for what you send and for holding the rights to send it. You are equally responsible for who you give a code to — anyone holding a live code can connect to that transfer.

You also agree not to attack the service itself: no attempts to overwhelm it, break the rate limits, hijack other people’s transfer codes, or probe it for vulnerabilities without asking us first. If you have found a genuine security issue, we would much rather you told us.

What we can and cannot do about misuse

We would rather be straightforward than imply powers we do not have. Because files pass directly between browsers and never reach our server — and because there is no relay in the path — we cannot inspect, scan, filter, retain or remove the content of any transfer. There is no stored file to take down, and no record afterwards of what moved. This is a consequence of the architecture described above, not a policy choice we could reverse on request.

What we can do is limit how many codes are created from one address, block abusive traffic, and respond to lawful requests to the extent of the very limited information we actually hold, which is set out on the privacy page. In most cases the honest answer to such a request is that nothing exists.

If someone is using the service to reach you with something unwanted, the practical remedies are the ordinary ones: stop accepting codes from them, keep whatever evidence you have, and report the conduct to the relevant platform or authority, who can act on evidence held by you rather than by us.

Reporting abuse

Email [email protected] with what happened and when, and include any evidence you hold. Please understand in advance that we will usually hold no corresponding records, for the reasons above. Reports concerning child safety are taken seriously and escalated to the appropriate authorities.

Availability and blocking

We may change, suspend or withdraw the service, and may block traffic that appears abusive or automated, at any time and without notice. Since there are no accounts, this is a matter of blocking traffic rather than terminating an account.

Limitation of liability

To the fullest extent the law allows, we are not liable for any loss arising from use of the service — including lost, corrupted or undelivered files, or anything that happens as a result of a file being sent to the wrong person. Nothing here limits liability that cannot lawfully be limited.

Copyright complaints

If you believe something sent using this service infringed your copyright, we want to be upfront about what we can do. We host nothing. There is no stored file to remove, no link to disable, and no record afterwards of what was transferred or by whom. A takedown notice therefore has nothing to act on — not because we decline to act, but because no copy exists on our systems at any point.

You are still welcome to contact us at [email protected], and we will respond honestly about what does and does not exist. Where infringement is happening, the effective route is against the person distributing the material, using evidence you hold.

Governing law

These terms are governed by the laws of the State of Iowa, United States, without regard to its conflict-of-laws rules. Any dispute arising from them or from use of the service will be brought in the state or federal courts located in Iowa, and by using the service you agree to that venue.

If you are using the service from outside the United States, note that it is operated from the United States and that your data is handled there.

Changes

These terms may change, with the date below updated. The architectural commitment — that files are not uploaded to or stored on our server — is not something we intend to change; if it ever did, it would be stated clearly on the home page rather than buried here.

Last updated 2 November 2026.