Privacy
This website is a reading surface. It has no accounts, sets no cookies and runs no analytics, so there is little to describe. This notice describes it exactly.
What this notice covers
This notice covers the OpenDeco public website, meaning the pages you can read at this address. It describes the website as its code stands, and every statement below is one the published source can be checked against.
It does not describe a product that has not been built. Where a capability does not exist, this notice says so.
What this website collects
Nothing about you. Reading these pages creates no record that identifies you, and the mechanisms that would normally create one are absent, not merely switched off.
- Cookies
- No response from this website carries a Set-Cookie header. No middleware exists that could add one, and no page script writes to document.cookie.
- Analytics and error monitoring
- No analytics, tag manager, session recorder or error-monitoring package is installed anywhere in this project.
- Third-party requests
- Reading a page contacts no other origin. Typefaces are served from the site's own build output, and the Content Security Policy permits no external origin at all.
- The contact form
- The form on the contact page has no action, no method and no submit handler, and its fields sit inside a disabled fieldset. Nothing typed into it is transmitted anywhere.
- Accounts and sign-in
- The website implements no account, session or authentication mechanism. The portal states that access is not open, and the sign-in and registration pages offer an identity provider only where a deployment supplies one.
- The data these pages show
- Datasets, model records, benchmark results and articles are built into the site in advance. No page calls an API or a database while you read it.
- Links to other websites
- Some pages credit an image or a source with a link elsewhere. Following one is a request you make to that website, under its own privacy notice. OpenDeco sends it nothing on your behalf.
What reaching this website involves
A page has to travel to your browser. The request that fetches it carries the metadata every web request carries: a network address, the address requested, a user-agent string and a timestamp. That metadata reaches whatever infrastructure serves the response, because without it the response cannot be returned.
This website's own code neither reads that metadata nor stores it. What the serving infrastructure does with it is decided by that infrastructure's configuration, which is a separate layer from the source of these pages.
| Question | The website code | The infrastructure serving it |
|---|---|---|
| What it does with a visit | Returns pages that were built in advance. It sets no cookie, reports to nowhere and contacts no third party. | Receives and answers the request your browser sends, which carries network and request metadata by design. |
| What it holds about you | Nothing. No account, no session, no API or database call on a public page, and no stored submission. | Whatever its operator configures it to record. That configuration is not set by this website's source. |
| How a claim about it can be checked | From the source, its dependency list and its Content Security Policy, which are the evidence for every statement on this page. | Not from the website source. It is a separate operational record. |
The research material published here
OpenDeco publishes datasets, model implementations, benchmark runs and written research. Those are records about exposures, models and results. Opening, filtering, comparing or downloading one creates no record about the person who did it, because the site holds no account and stores no submission.
Features this website does not have
Account sign-in, dive import and synchronisation, device pairing, voluntary research contribution, and outcome or health data collection are not implemented here. No data of those kinds is processed, because nothing exists to process it.
If any of them is built, this notice will describe it in full before it is switched on.
Your rights
Data-protection law gives a person rights over personal data held about them, including access to it, correction of it, erasure of it and objection to its use.
On this website those rights have almost nothing to act on. No account exists to disclose, no cookie or analytics profile to erase and no stored message to correct. A request will normally concern one of two other things: the request metadata described above, which is held by the infrastructure serving the site, or a published research record you believe describes you.
How to make a request
Decide what the request is about
A request about this website itself has no stored data to reach. A request about the metadata carried by a server request, or about a published research record, is the one worth raising.
Choose the route
The contact page lists the routes that are open and says when a route is not configured. Use the correction route for a published record and the general route for anything else.
Say what you are asking for
Name the page, record or dataset, give the dates if they matter, and state the outcome you want. Because there is no account, there is no stored identifier to match a request against, so the description is what makes it actionable.
Send security matters through the disclosure route instead
A vulnerability report reaches the process built for it through the vulnerability disclosure page, not through a data-rights request.
Changes to this notice
The revision date at the top of this page changes whenever the text changes. A material change is described here, and the notice in force is always the one on this page.