Obleevo

Cookie policy

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

There are no cookies

This page exists because "we use no cookies" is a claim that deserves to be checked rather than believed, and because a few things are kept in your browser that are not cookies and would be dishonest to leave out.

1. No cookies, and no banner

This service sets no cookies. Not analytics cookies, not advertising cookies, not preference cookies, and not the "strictly necessary" ones either — there is no session to keep, because there are no accounts.

That is why there is no consent banner. Under Quebec’s Act respecting the protection of personal information in the private sector as amended by Law 25, and under the EU ePrivacy Directive, consent is required before storing or reading information on your device except where it is strictly necessary to provide a service you asked for. Nothing here reaches even that threshold, so there is nothing to consent to. A banner asking permission for nothing would be theatre, and it would train you to click through the ones that matter.

The real-time connection library this application uses is configured not to set its own cookie, which it would otherwise do by default.

2. What is kept in your browser, and why

Cookies are not the only way to keep something on a device, and a page that says "no cookies" while filling your local storage is telling a technically true lie. Here is everything:

Session storage — one key. gd-agreed holds the version of the Terms you accepted. It dies when the tab closes and is never sent to the server. Strictly necessary: without it you would be asked to accept the Terms on every interaction.

Local storage — nothing. Deliberately. Even your light or dark theme preference is held in memory only, because a remembered preference is itself a record that this browser opened this service.

Service worker cache — the application’s own files. HTML, stylesheet, scripts and fonts, so the application opens offline and can be installed. No content from any room is ever cached. Burning a room clears this cache and unregisters the worker.

IndexedDB — only if you ask, per transfer. Ticking “resume this if the tab closes” writes a database named ghostdrop-resume holding a file’s name, size, which blocks were verified, the hashes needed to verify the rest, and your browser’s own handle to the file you chose. It does not hold the file’s contents. It is deleted when the transfer finishes, when you cancel, when you leave or burn the room, and in any case after seven days. Leaving deletes the whole database rather than emptying it, so the name stops appearing in your browser’s own storage listing.

That is the complete list. If you find anything else, section 6 of the privacy notice tells you how to say so.

3. Nothing loads from anywhere else

A cookie policy is usually long because the page loads a dozen third parties, each of which sets its own. This one loads none. Fonts, the stylesheet, every script and the real-time library are served from this origin, and the content security policy forbids loading executable code from anywhere else.

That is not only a privacy choice. A third party that serves you a font can see that you are here, when, and from which address, without setting anything at all.

Two network connections do happen, and neither involves storage on your device: the connection to this server itself, and the peer-to-peer connections to the people in your room. Section 3 of the privacy notice describes exactly what each can see.

4. Clearing it yourself

Everything above is under your control and can be removed without asking us. Burn or Leave clears the session key, empties and unregisters the service worker cache, and deletes the resume database. Closing the tab clears the session key on its own.

Your browser’s own “clear site data” for this origin removes all of it at once, and nothing here will recreate it until you use the service again.

Because none of it is sent to us, there is nothing on our side to delete, and no request you need to make in order for it to be gone.

Last reviewed:

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

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

Back to Obleevo