Open Well Data

Privacy: Open Well Data API keys

Version of 17 November 2026. It applies from the day API keys are available at https://api.openwelldata.org/key.

Who is responsible

Open Well Data is run by Daniel Delgado-Uriarte, who decides how this data is used (data controller). Contact: contact@openwelldata.org.

This notice covers the optional keys of the Open Well Data API. The API works without a key, and without a key nothing described here is kept. Downloading files from the site or from Zenodo needs no key and no registration; the site has its own notice at https://openwelldata.org/privacy/.

What is kept with a key

The API does not keep IP addresses, the content or parameters of your queries, browser details or cookies, with or without a key. Its request limits per client use Cloudflare's rate limiting, which keeps short-lived counters at Cloudflare and nothing in our database.

Why, and on what basis

Without the consents you get the same key and the same limits. You can withdraw either consent at any time, without affecting what was done before: PATCH /v1/keys/me with your key, or write to contact@openwelldata.org.

Who receives it

Nobody. This data is not shared with, sold or rented to any company or other third party, and it is not used for marketing. The only messages sent to your address are the links you ask for, a notice before an unused key is deleted, and, only if you ticked consent (b), one request for a statement.

Cloudflare runs the API for us as a processor, under its data processing terms, and does not receive the data for any purpose of its own: the API runs on Cloudflare Workers; the database is Cloudflare D1, created to store the data in the European Union; the messages are sent with Cloudflare Email Service from contact@openwelldata.org.

Cloudflare, Inc. is based in the United States, and Workers run in Cloudflare's data centres around the world, so a request or a message may be processed outside the European Union. Cloudflare's Data Processing Addendum (version 6.4, https://www.cloudflare.com/cloudflare-customer-dpa/) covers these transfers with the EU Standard Contractual Clauses and states that Cloudflare complies with the EU-US Data Privacy Framework.

The two forms (to request a key and to delete one without it) use Cloudflare Turnstile to check that they are sent by a person. Turnstile runs in your browser from challenges.cloudflare.com and Cloudflare processes the signals it needs for that check; the API only receives whether the check passed. Turnstile is not used on any other page or request of the API.

Copies outside the database

Once a month the controller exports from the database, to his own computer and nowhere else: the monthly totals; the names of the organizations whose users gave consent (a), never their addresses or names; and, only for consent (b), the address, organization and intended use, to write to you once. A withdrawal or a deletion reaches these copies at the next monthly export, that is, at the latest about a month later: the record of a named organization is then kept without its name, as an organization that was registered and whose permission was withdrawn, with the day; the address of consent (b) is removed. That computer has encrypted backups, which are deleted on a rolling basis within about 13 months.

How long

Your choices and rights

Changes

Any change to this notice is published here with its date before it applies.