Legal / Plain language
Terms of use
The rules for using NulBridge, in plain language. It is a free tool provided as-is: use it lawfully and respect the people you talk to.
Last updated:
The short version
Free, as-is.
NulBridge costs nothing and comes with no warranty or uptime promise.
Use it lawfully.
No illegal content, harassment, malware or scams.
Don’t attack it.
No brute-forcing codes, overloading servers or dodging rate limits.
We can’t see your content.
So we can’t moderate it. You are responsible for what you share.
Know who you’re talking to.
Anyone with your link or code can join. Compare safety codes.
Keep your own copies.
Nothing is stored, so nothing can be recovered after a session ends.
On this page11 sections
Agreement
These terms apply when you use NulBridge at nulbridge.pages.dev: the website and the web app that runs in your browser. It is run by the operator of this deployment (“we”, “us”). We have kept them short and in plain language.
By using NulBridge, you agree to these terms and to the privacy policy. If you don’t agree, please don’t use it. You must be at least 13 years old, or older if the law where you live requires it.
The service
- NulBridge connects two browsers directly for end-to-end encrypted chat, file transfers of up to 500 MB per file, and voice and video calls.
- It is free. There are no accounts, and conversations aren’t stored anywhere.
- We may change, add or remove features at any time.
- You can stop using NulBridge whenever you like. There is no account to close.
Acceptable use
Don’t use NulBridge to:
- break the law, or help anyone else break it;
- share content that is illegal where you or the recipient are, including any material that sexually exploits children;
- harass, threaten, stalk, blackmail or impersonate anyone;
- send malware, phishing links or anything designed to damage devices or data;
- scam or defraud people;
- infringe other people’s rights, including copyright and privacy;
- gather information about people without their knowledge, such as tracking their location from their IP address.
And don’t attack or abuse the service itself:
- don’t try to guess, brute-force or collect 6-digit codes or private links;
- don’t overload, disrupt or probe the website, the signaling server, the code service or anyone’s connection, including with denial-of-service attacks;
- don’t get around rate limits or other protections;
- don’t use bots or scripts to create sessions or codes in bulk.
We may limit or block access to protect the service, for example from a network that attacks it. Found a security problem? Please report it instead of exploiting it: see the security page.
Your responsibilities
- Know who you’re talking to. Anyone with your private link or 6-digit code can join until someone does. Send them only to the person you mean, through a channel you trust.
- Compare safety codes for anything sensitive. If the codes on your two screens differ, end the session: someone may be in the middle.
- Own what you send. You are responsible for what you share and receive, and for following the laws that apply to you.
- Keep your device secure. Encryption can’t protect a compromised device or a malicious browser extension.
- Keep your own copies. Nothing is stored, so nothing can be recovered after a session ends.
We can’t see your content
Messages, files and calls are end-to-end encrypted and travel directly between the two browsers. We never receive them. That means we can’t read, monitor, filter, moderate or recover them, and we can’t act on reports about what was said in a conversation.
If someone misuses NulBridge against you, end the session (closing the tab ends it for both of you) and don’t share a new link or code with them. If you are in danger or a crime has been committed, contact your local authorities.
We can act on abuse of the service itself, such as attacks on its servers. To report one, contact the operator of this deployment.
Third-party services
NulBridge relies on services run by others: hosting by Cloudflare Pages, the public PeerJS cloud server for signaling, STUN servers from Google and Cloudflare, and Supabase for 6-digit codes. Their own terms and policies cover their part, and we aren’t responsible for their availability or for how they operate.
The privacy policy explains what each one can see.
Availability
- NulBridge comes with no guarantee that it will be available, fast, or work on every network or device.
- Sessions can fail or drop, for example when a network blocks peer-to-peer connections, a phone pauses a background tab, or one of the services above is down.
- We may change, suspend or discontinue NulBridge, or any part of it such as 6-digit codes, at any time and without notice.
- Don’t rely on NulBridge as your only way to reach someone, and never use it for emergencies.
No warranty
NulBridge is provided “as is” and “as available”. To the fullest extent the law allows, we make no promises or warranties of any kind, express or implied. That includes any promise that it will be secure, error-free or uninterrupted, that it fits a particular purpose, or that it doesn’t infringe anyone’s rights.
We build NulBridge carefully, but no software is completely secure, and its encryption has not been independently audited yet. You use it at your own risk.
Limitation of liability
In plain terms: NulBridge is free, so we can’t take responsibility for losses that come from using it.
To the fullest extent the law allows, we are not liable for any indirect, incidental, special, consequential or punitive damages, or for any loss of data, messages, files, profits or goodwill, that results from using NulBridge or from being unable to use it. We are also not responsible for what other people do with NulBridge, including the person you connect with.
Some places don’t allow these limits. Where that is the case, they apply only as far as the law permits, and nothing in these terms limits liability that can’t legally be limited.
Changes to these terms
We may update these terms. When we do, we will change the “Last updated” date at the top. If you keep using NulBridge after a change, you accept the updated terms.
Contact
This deployment doesn’t list a contact address. For questions about these terms, contact the operator of this deployment.
To report a security problem, see the security page.
End of document
Read next
Last updated: