LEGAL
Privacy
How OpenDeco handles account data, imported dive data, research contributions, logs and deletion.
On this page
This site holds nothing about you. It sets no cookie, writes nothing to your browser and loads no script, font or image from another origin. No account system, import path or contribution workflow is deployed, so the sections below describe what is designed and not yet what is running.
What OpenDeco collects
From a visitor to this site, nothing. The content security policy the site sends allows scripts, styles, fonts, images and network connections from its own origin only. No analytics service, no tag manager and no embedded third party can observe you here.
One thing still reaches a server. An HTTP request carries a network address and a user-agent string because the protocol works that way. Where those requests are recorded, and for how long, depends on the hosting provider, and OpenDeco has not chosen one.
Account information
OpenDeco operates no account system. Sign-in, passkey enrolment and account recovery are specified and none of them is deployed, so no account record exists to describe.
Pending legal review
Private dive data
No import path exists and OpenDeco holds no dive log belonging to anyone. The design separates a reader's own dive data from the research corpus. An imported dive stays private to its owner, and it enters a dataset only through an explicit contribution step.
Pending legal review
Research contributions
The contribution workflow is specified and not deployed. A contributed record carries its own consent context and its own review state by design. A reviewer can therefore trace any contribution back to the terms its owner agreed to.
Pending legal review
Anonymization and research releases
This section describes machinery that already exists in the repository. An aggregate computed from restricted records inherits the restriction, and it becomes publishable only when a recorded rights assessment on that dataset version names the aggregation permitted.
The bundle builder enforces that. It resolves a disposition for every dataset version from its classification, access type, embargo, licence and rights review, and it refuses to write a bundle that carries record-level data a disposition withholds. The check runs against the artifact contents, not against a flag on the release. A benchmark stratified finely enough can identify a single exposure, so small-count disclosure is treated as a real risk.
Logs and security data
No OpenDeco service is deployed, so no application log, audit record or session store exists yet. The audit log is specified as append-only and the admin control plane sits behind a separate trust boundary from this site.
Pending legal review
Retention
Pending legal review
Export and portability
Pending legal review
Withdrawal and deletion
Pending legal review
Processors and service providers
One provider is in the picture today. GitHub hosts the repository, its issue and advisory workflows and its released artifacts. No database, object store, queue or email service is running.
The infrastructure decision is recorded as deferred, with binding selection criteria. Published data-processing terms, a published subprocessor list and a clear international transfer position are mandatory criteria: a candidate that fails one is disqualified.
Pending legal review
International transfers
A United Kingdom or European Economic Area region for data at rest is a mandatory criterion in the infrastructure decision. It is a criterion, not a preference, because it interacts with health-data handling. No region is in use today, because no service is running.
Pending legal review
Your rights
Pending legal review
Changes to this notice
A revision line sits directly under the heading of this notice. No version has been issued, so the line records that instead of a date. When a version is issued, the wording it replaces stays reachable.
Contact
OpenDeco publishes no privacy address yet. The one published security route is security@opendeco.net, and it is for vulnerability reports.
A factual error on this page is a correction, and the correction route records it against the page and version affected.
Pending legal review