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
- Your email address and its domain (the part after the @).
- What you write in the form: the organization (optional), the type of organization, the country, the intended use and the optional text about it (up to 300 characters).
- The two optional consents, each with the date you gave it, if you ticked them, and the date you withdrew it, if you did. Both boxes are unticked unless you tick them.
- A keyed hash of your API key. The key itself is shown to you once and is not kept: it cannot be recovered, only replaced.
- The day the key was created, the day it was last used (the day, not the time), and the day of the notice before deletion, if one was sent.
- The number of requests made with your key on each UTC day.
- Two internal markers: whether the key is active or suspended, and the last month in which it was counted as active in the monthly totals.
- If your key replaced earlier keys of the same address: the random internal identifiers of the last 12 of them, the day each was replaced, and the days consent (a) was given and withdrawn with each, so that the monthly export can record the change.
- While an email link is pending: the address, a keyed hash of the link, the fields of the form and when the link expires.
- If a key is suspended for abuse, for example to get round the limits: the day of the suspension and, once the key is deleted or by the next daily clean-up, a keyed hash of its email address (not the address itself) with that day, so that the address cannot get a new key. Nothing else.
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
- To give you a key, confirm that the address is yours, apply the limits of the key and stop abuse. Basis: providing the service you ask for (Article 6(1)(b) GDPR) and our legitimate interest in keeping the API available (Article 6(1)(f)).
- To know, in aggregate, how the API is used, so that it can be sized, maintained and reported on. Only monthly totals are made for this: active keys, new keys, and requests by type of organization and by country. They contain no address, name or domain, values below 5 are not shown in the copies made from them, and they are kept. Basis: legitimate interest (Article 6(1)(f)).
- The hash of the address of a key suspended for abuse is only used to refuse a new key to that address. Basis: legitimate interest in preventing abuse of the API (Article 6(1)(f)).
- Consent (a), "You may list my organization as a user of Open Well Data": we may name your organization, never you, as a user of Open Well Data, for example in a list of users or in reports about the project. If you left the organization empty, we may take its name from the domain of your address, but never from a personal mail provider such as gmail.com. Basis: your consent (Article 6(1)(a)).
- Consent (b), "I would be willing to give a short statement about how I use Open Well Data": we may write to you once, at the address you gave, to ask for a short statement. Nothing is published without your agreement to the text. Basis: your consent (Article 6(1)(a)).
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
- Email links stop working 24 hours after they are sent, or once used. They are deleted at that moment when another link is asked for or used, and at the latest at the next daily clean-up. The deletion link of a notice works until the day of the deletion.
- Requests per key and UTC day: 90 days.
- Your address, the form fields, the consents and the hash of your key: until you delete them, or until the day after the key has gone 18 months without use, when they are deleted. We try to send a notice to your address 30 days before that day; using the key once keeps it. The deletion does not wait for the notice if it cannot be delivered.
- The hash of the address of a key suspended for abuse: 24 months from the suspension. It is not removed when the data of that key is deleted.
- A withdrawn consent is no longer used from the day you withdraw it; that day and the day you gave it are kept, as the record of your choice, until the key is deleted.
- Monthly totals: kept; they contain no personal data.
Your choices and rights
- See everything kept about you:
GET /v1/keys/mewith your key in theX-API-Keyheader. - Delete your key and everything linked to it, at once:
DELETE /v1/keys/mewith your key. Without the key, use https://api.openwelldata.org/key/delete and follow the link sent to your address. Every message we send has a link to delete it all. - Requesting a key again replaces the old one, which stops working.
- You can also write to contact@openwelldata.org to see, correct or delete your data, or to object to its use. You may complain to a data protection authority, for example the one of your country in the European Union.
Changes
Any change to this notice is published here with its date before it applies.