Obleevo

Terms of Use

Also available in Français · Español · Deutsch · Português · Română · 日本語

The agreement between you and the Operator

Version 2.0 · Last updated 20 September 2026 · Effective on first use after that date

These Terms govern your use of this deployment. They are written to be read: the sections that take something away from you — the disclaimer, the limitation of liability, and what a takedown cannot achieve — are in plain language rather than buried, because a clause nobody can understand is one a Quebec court may treat as abusive and strike out.

The short version. Obleevo introduces two browsers to each other and then gets out of the way. Files, messages, drawings, voice and screens travel directly between participants, or through an encrypted relay when no direct path exists; they are not stored or inspected by this service, and the operator has no technical means of reading them. Nothing survives a closed room. You are responsible for what you send and who you send it to. The service is provided as-is, with no warranty and no promise that it will be available.

The short version is a summary and nothing more. Where it and the full terms below disagree, the full terms govern.

1. The agreement

1.1 These Terms of Use (the Terms) are a binding agreement between you and [OPERATOR LEGAL NAME], [COMPANY NUMBER / REGISTERED ADDRESS] (the Operator, we, us), who runs the instance of Obleevo available at [SERVICE URL] (the Service).

1.2 You accept these Terms by ticking the box on the join screen. That tick is recorded in your browser’s session storage for the lifetime of the tab and nowhere else; it is not transmitted to us, and we hold no record that you accepted. Acceptance is nonetheless effective as between you and us, and continued use of the Service is independently an acceptance of these Terms.

1.3 If you do not agree, do not use the Service. There is no partial acceptance: the disclaimers in section 17 and the limitation of liability in section 18 are an inseparable part of the bargain under which the Service is offered at no charge.

1.4 If you use the Service on behalf of an organisation, you confirm that you have authority to bind that organisation, and you in these Terms means both you personally and that organisation.

1.5 These Terms are available in French and in English. In accordance with the Charter of the French Language, the French version prevails unless the parties have expressly agreed otherwise after having had the opportunity to read the French version.

2. Definitions

Content means anything you send through the Service: files, folders, messages, drawings, annotations, voice, and shared screens.

Room means a session identified by a code, existing only in the memory of a running process.

Participant means any person connected to a Room. Host means the Participant who created it.

Relay means a TURN server, where one is configured, which forwards encrypted traffic between Participants who cannot reach each other directly.

3. What the Service is, technically

3.1 The Service is a signalling service. It issues Room codes, applies the entry conditions the Host chose, and passes opaque connection blobs between browsers in the same Room. Once a direct connection exists, Content travels between Participants over an encrypted WebRTC data channel or media stream and does not pass through the Service.

3.2 The Operator does not receive, store, host, reproduce, index, transmit or moderate Content, and has no technical means of doing so. Room passwords are never sent to the Service; nor are invite-link secrets, nicknames, chat, file names or file bytes. This is a property of the architecture, not a policy we could choose to relax.

3.3 Two consequences follow, and you should hold both of them in mind. The Operator cannot read what you send — which is the point. The Operator also cannot retrieve it for you, prove what was sent, recover it after the fact, or take it down from a recipient’s disk — which is the cost.

3.4 Where a Relay is configured, encrypted media may pass through it. The Relay forwards ciphertext and does not hold the keys. It does, necessarily, observe the network addresses of the Participants it is forwarding between.

4. What the Service is not

The Service is not, and must not be relied on as: a backup service; an archive; a records-management or compliance system; a courier with proof of delivery; a guarantee of anonymity; or a substitute for professional advice about how to handle sensitive material.

If losing something would matter, keep your own copy. Nothing here is stored anywhere once a Room ends.

5. Eligibility and age

5.1 The Service is not directed to children. You must be at least [MINIMUM AGE] years old, or the age of digital consent where you live if that is higher, to use it.

5.2 We hold no accounts and collect no age information, so we cannot verify this and do not attempt to. The obligation is yours.

5.3 You may not use the Service if you are barred from doing so under the laws of your country of residence or of the country from which you access it, or if you appear on any sanctions list described in section 15.

6. Acceptable use

You agree not to use the Service to: send material that is unlawful where you are or where your recipient is; send material that infringes another person’s rights; harass, threaten, defraud or impersonate anyone; distribute malware or anything designed to damage a device; circumvent the entry conditions of a Room you were not invited to; interfere with, overload or attempt to bypass the technical measures that protect the Service; or attempt to identify or deanonymise another Participant.

The prohibition on tampering with technical measures does not extend to good-faith security research conducted under section 16.

7. Your Content and your recipients

7.1 You keep every right you have in your Content. You grant the Operator no licence of any kind, because the Operator never receives it. Nothing in these Terms gives us permission to use, display, copy or analyse anything you send.

7.2 You warrant that you have the right to send what you send, and the right to send it to each recipient.

7.3 Sending is final. Once bytes leave your browser they are on someone else’s machine. Burning a Room disconnects everyone and erases Obleevo from their browser’s memory and offline cache; it cannot reach into a file that has already been written to their disk, a screenshot they took, or a recording they made. Treat every transfer as unrecallable.

7.4 You are responsible for who is in the Room. A Room code is short, and anyone holding the code or the invite link can attempt to join. If who is present matters, use a password room or an approval room, turn on Strict mode, and compare the safety words with each person before you send anything.

7.5 Content you receive is not vetted by anyone. Files arriving from another Participant are exactly as dangerous as files arriving by any other means. Scan them. The Service verifies that the bytes you received are the bytes the sender sent — it makes no statement whatsoever about whether they are safe.

8. Child sexual abuse material

8.1 Use of the Service in connection with child sexual abuse material is absolutely prohibited and is the gravest possible misuse of it.

8.2 We must be plain about our position: because Content never reaches us and is end-to-end encrypted between browsers, we cannot scan for such material, cannot hash-match it, and will not become aware of it through any technical means of our own.

8.3 Where we do become aware of it — through a report under section 9, or otherwise — we will destroy the Room concerned immediately, and we will report what we know to [NCMEC / IWF / LOCAL AUTHORITY] and co-operate with any lawful request. What we know will, in practice, be very little: a Room code, the times it existed, and whatever the reporter told us.

9. Reports, complaints and takedown

9.1 Reports of misuse may be sent to [ABUSE CONTACT]. Include the Room code, the approximate time, and enough detail to identify the problem. We aim to respond within [ABUSE RESPONSE TIME].

9.2 Copyright complaints under 17 U.S.C. §512 should be addressed to our designated agent, [DMCA AGENT], and must contain the elements §512(c)(3) requires. Counter-notices are handled under §512(g). In Canada, the notice-and-notice regime under sections 41.25 and 41.26 of the Copyright Act applies; we will forward a compliant notice where we are able to identify a recipient, which in the ordinary case we are not.

9.3 You should understand what a takedown can and cannot achieve here. We can destroy a live Room, and we can block a code. We cannot remove material, because we do not hold any: there is no copy on our systems to take down, and no copy anywhere except on the devices of the people who received it. A notice that asks us to remove a file is asking for something that does not exist.

9.4 Knowingly making a material misrepresentation in a notice may make you liable for damages under §512(f) and equivalent provisions elsewhere.

10. Intermediary status

10.1 In providing signalling, the Operator acts as a mere conduit within the meaning of Article 4 of Regulation (EU) 2022/2065 (the Digital Services Act) and, where applicable, the corresponding provisions of national law implementing the former e-Commerce Directive. We do not initiate transmissions, do not select the receiver, and do not select or modify what is transmitted.

10.2 Where a Relay is configured, its forwarding of encrypted media is automatic, intermediate and transient, and is performed for the sole purpose of carrying the transmission.

10.3 In Quebec, the Operator acts as a service provider offering technology-based documentary services within the meaning of sections 22 and 36 of the Act to establish a legal framework for information technology, and is not responsible for the activities of users where it does not take part in the transmission and has no knowledge of the content.

10.4 No general obligation to monitor is imposed on the Operator, and none could be discharged: there is nothing to monitor.

11. Privacy between Participants

11.1 A direct peer-to-peer connection reveals each Participant’s network address to the others. This is inherent to WebRTC and not something the Operator adds or could prevent.

11.2 Where a Relay is configured, the Hide my IP option routes your traffic through it, so other Participants see the Relay’s address instead of yours. The Relay operator then sees your address in their place. This is a choice about who sees it, not a way for nobody to see it.

11.3 Other Participants can keep anything you send. Nothing in the Service prevents a recipient from saving a file, screenshotting a message, recording a shared screen, or photographing the display. The erasure guarantees in these Terms are about our systems and about the browser’s own memory, not about the intentions of the people you invited.

12. Availability and changes to the Service

12.1 The Service is offered without any service level and without any commitment to availability. It may be slow, unreachable, restarted, or withdrawn entirely, with or without notice.

12.2 Rooms exist only in the memory of a running process. A restart, a crash, a deployment, or a hosting platform idling the process to sleep destroys every live Room and every transfer in flight. This is by design and will not be treated as a fault.

12.3 Some capabilities depend on your browser. Streaming very large files to disk, receiving folders, and resuming an interrupted transfer require the File System Access API, which at the time of writing is available on desktop Chromium browsers only. Elsewhere the Service refuses large transfers rather than exhausting your device’s memory.

13. Suspension and termination

13.1 We may destroy any Room, refuse any connection, or block any Room code at any time, at our discretion, including where we believe on reasonable grounds that these Terms are being breached.

13.2 There is no account to suspend and no ban we can meaningfully apply to a person, because we do not know who anybody is. Enforcement is therefore blunt: it operates on Rooms and on connections, not on users.

13.3 You may stop using the Service at any time by closing the tab. Sections 7.3, 14, 17, 18, 19, 20 and 21 survive.

14. Third parties

14.1 The Service runs on infrastructure provided by [HOSTING PROVIDER] and, where configured, uses STUN and TURN servers identified in the Privacy Notice. Their terms apply to their own conduct and we are not responsible for it.

14.2 The Service loads no third-party code. Its Content-Security-Policy forbids every foreign origin, and its fonts and libraries are served from the same origin as the application. This is deliberate: code loaded from elsewhere could change the way safety numbers are computed, and you would have no way of noticing.

15. Export control and sanctions

The Service incorporates cryptography and may be subject to export control law. You confirm that you are not located in, and are not ordinarily resident in, a country subject to comprehensive sanctions by [RELEVANT AUTHORITIES], that you are not named on any applicable restricted-party list, and that you will not use the Service in breach of any export control or sanctions law that applies to you.

16. Security research

16.1 Good-faith security research is welcome. Report findings to [SECURITY CONTACT]. We will not pursue civil or criminal action against research that stays within 16.2.

16.2 Work only against Rooms you created; do not access, alter or retain another person’s Content or connection; do not degrade the Service for others; do not run sustained automated load; and give us [DISCLOSURE WINDOW] before publishing.

17. Disclaimer of warranties

THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE”, WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR STATUTORY. TO THE FULLEST EXTENT PERMITTED BY LAW WE DISCLAIM THE IMPLIED WARRANTIES OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, ACCURACY AND NON-INFRINGEMENT.

In particular, and without limiting the foregoing, we do not warrant that the Service will be available, that a connection will be established between any two Participants, that a transfer will complete or complete correctly, that data will not be lost, that the cryptography will be free of defects, or that the Service is fit for any purpose for which failure would be consequential.

This section does not apply to the extent that the law where you live does not permit it. See section 20.

18. Limitation of liability

18.1 TO THE FULLEST EXTENT PERMITTED BY LAW, NEITHER THE OPERATOR NOR ITS OFFICERS, EMPLOYEES OR SUPPLIERS SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFIT, REVENUE, DATA, GOODWILL OR ANTICIPATED SAVINGS, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY.

18.2 OUR TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THE SERVICE SHALL NOT EXCEED THE GREATER OF (a) THE AMOUNT YOU PAID US FOR THE SERVICE IN THE TWELVE MONTHS PRECEDING THE CLAIM, WHICH FOR A FREE SERVICE IS ZERO, AND (b) [LIABILITY CAP].

18.3 Nothing in these Terms excludes or limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot lawfully be excluded.

18.4 Quebec. Under article 1474 of the Civil Code of Québec, a person may not exclude or limit liability for bodily or moral injury caused to another. Sections 18.1 and 18.2 therefore do not apply to bodily or moral injury, and do not apply to gross or intentional fault. Under section 10 of the Consumer Protection Act, a stipulation excluding the Operator’s liability for its own act is prohibited in a consumer contract and is without effect.

19. Indemnity

You agree to indemnify and hold harmless the Operator against any claim, demand, loss, liability, damage, cost or expense (including reasonable legal fees) arising out of your Content, your use of the Service, or your breach of these Terms or of any law.

This section does not apply to consumers to the extent the law where you live prohibits it, and in Quebec does not apply to a consumer contract governed by the Consumer Protection Act.

20. Quebec consumers

20.1 Language. These Terms are available in French. By using the Service in English you do not waive your right to the French version, which remains available at all times and which prevails under section 1.5.

20.2 Abusive clauses. This is a contract of adhesion. Under article 1437 of the Civil Code of Québec, an abusive clause in such a contract is null, and under article 1435 an external clause is null if the consumer was not aware of it. Nothing is incorporated into these Terms by reference except the Privacy Notice, which is linked from every page and from the join screen.

20.3 Your forum. Under section 19 of the Consumer Protection Act, a Quebec consumer may bring proceedings in the district of their domicile, and any clause to the contrary is without effect. Section 21.1 does not deprive you of that right, nor of the protection of any mandatory rule of Quebec law.

20.4 Prohibited stipulations. Any stipulation in these Terms that the Consumer Protection Act prohibits is deemed not written as regards a Quebec consumer, and the remainder continues in force.

21. Governing law and disputes

21.1 These Terms are governed by the law of [JURISDICTION], without regard to its conflict-of-laws rules, and the courts of [VENUE] have jurisdiction, subject to section 20.3.

21.2 If you are a consumer resident in Quebec, the European Union, the United Kingdom or another jurisdiction whose law gives you the right to bring proceedings in your own courts and to the protection of your own mandatory consumer law, 21.1 does not take that away from you.

21.3 Before starting proceedings, please write to [CONTACT]. Most things are faster to fix than to litigate.

22. General

22.1 Changes. We may amend these Terms. The version number and date at the top will change, and the join screen will ask you to accept again when the version does. Continued use after a change is acceptance of it.

22.2 Severability. If a provision is held unenforceable, it is severed and the rest continues in force.

22.3 No waiver. A failure to enforce a provision is not a waiver of it.

22.4 Assignment. You may not assign these Terms. We may assign them to a successor in connection with a transfer of the Service.

22.5 Entire agreement. These Terms and the Privacy Notice are the whole agreement between us about the Service and replace anything said before.

22.6 Software licence. The software behind the Service is licensed separately under [LICENCE]. These Terms govern your use of this deployment, not your rights in the source code.

23. Contact

[OPERATOR LEGAL NAME], [POSTAL ADDRESS].

General: [CONTACT EMAIL] · Abuse: [ABUSE CONTACT] · Security: [SECURITY CONTACT] · Accessibility: [ACCESSIBILITY CONTACT] · Copyright agent: [DMCA AGENT]

See also the Privacy Notice, which describes the small amount of data the signalling service necessarily handles and how long it exists for.

Last reviewed:

About · Why this · FAQ · Privacy · Accessibility · Cookies · What’s new

Obleevo is developed by The House of Brendrof. Proprietary software, free to use.

Back to Obleevo