The short version
Docelora sets no cookies. Not for analytics, not for advertising, not for preferences, and not for sessions. There is nothing to accept, reject or manage, which is why you have not been shown a consent banner.
Nor does Docelora store anything else in your browser. No localStorage, no sessionStorage, no IndexedDB, no cache of your documents. Close the tab and nothing about your visit remains on your device.
What a cookie is, and why sites use them
A cookie is a small piece of text a website asks your browser to keep and send back on your next visit. They are how sites remember that you are signed in, which language you chose, or which items are in a basket. They are also how advertising networks recognise the same person across different sites, which is the use that consent rules exist to govern.
Docelora needs none of these. There is no sign-in, because the tools do not require an account. There is no basket. There is no advertising network. Every setting you choose on a tool page lives only in that page while it is open.
What Docelora uses instead
| What you might expect a cookie for | What actually happens |
|---|---|
| Remembering you between visits | Nothing is remembered. Each visit starts fresh. |
| Keeping you signed in | There is no sign-in and no account. |
| Remembering your tool options | They live in the page while it is open, and are gone when you close it. |
| Knowing which files you chose | Your browser holds them in memory to upload. Nothing is written to your device. |
| Finding your finished file again | A job reference is held by the open page only. Closing it loses the reference, and the file is cleared shortly after. |
| Measuring how many people visit | No analytics of any kind are installed. |
| Advertising | No advertising network is present. |
Third-party scripts
There are none. No page on this site loads JavaScript, a stylesheet, a font or an image from another company’s servers. Everything a page needs is in the page itself.
This matters more than it sounds. A single third-party script can set cookies, read the address of the page you are on and report it elsewhere, entirely outside the control of the site including it. Not having any is the most reliable way to be able to say so.
The one external address any page contacts is Docelora’s own processing service, and only when you actively use a tool. Nothing is sent there simply because you read a page.
Server logs
Serving a web page inevitably involves a server receiving a request, and web servers ordinarily keep a short record of requests they handle. That is a function of the hosting, not of a cookie, and it happens whether or not a site uses cookies at all.
Docelora’s own processing service deliberately does not log the contents of your documents or the names of the files you upload. What the underlying hosting platform records about network requests is governed by that provider, named in the Privacy Policy.
If this changes
Docelora intends to carry advertising in future, and advertising networks generally do set cookies. Measurement tools generally do too.
If either is added, this page will be rewritten to name what is set, what it is for and how long it lasts, and the appropriate consent mechanism will be in place before anything is set rather than after. A policy that describes a state of affairs that has already stopped being true is worse than no policy at all.
You do not have to take this on trust. Open your browser’s developer tools, look under Storage or Application, and use Docelora normally. The cookie list for this site stays empty.
That is a claim anyone can falsify in about thirty seconds, which is the kind of claim worth making.
Questions about this policy
Docelora is operated under the name Docelora.com, from the United Kingdom. Questions about this policy can be sent to info@docelora.com.
See also the Privacy Policy, which covers what happens to the documents you upload, and the Terms.