|
| 1 | +--- |
| 2 | +title: Privacy Statement |
| 3 | +parent: API Keys |
| 4 | +--- |
| 5 | + |
| 6 | +# Delphi Privacy Statement |
| 7 | + |
| 8 | +Anyone may access the Epidata API anonymously without providing any personal |
| 9 | +data. |
| 10 | + |
| 11 | +Some features of the API are only available by registering for an API key. We |
| 12 | +require an email address for all registrations so that we can contact you to |
| 13 | +resolve problems with excessive or abnormal usage patterns. Any additional |
| 14 | +personal information you provide to us at registration will be much appreciated, |
| 15 | +because it will help us understand what our data is used for and inform our |
| 16 | +plans and priorities, but is voluntary. |
| 17 | + |
| 18 | +You may also choose to share personal information with us to participate in user |
| 19 | +surveys. |
| 20 | + |
| 21 | +We log information about API traffic including the query parameters, API key, |
| 22 | +and source IP address for each request. We retain these logs for a period of not |
| 23 | +longer than five years. We use this information for the following |
| 24 | +purposes: |
| 25 | + |
| 26 | +* to monitor the responsiveness of the API service |
| 27 | +* to monitor the relative popularity of different data and features, alone and |
| 28 | + in concert with user survey results |
| 29 | +* to identify excessive or abnormal usage patterns which may harm our system |
| 30 | + |
| 31 | +The logs are only available to members of our operations team, and are expunged |
| 32 | +at or before they reach five years in age. |
| 33 | + |
| 34 | +If you provide us with your email address, we will only use it to contact you in |
| 35 | +the following scenarios: |
| 36 | + |
| 37 | +* you asked a question in a user survey and we have an answer for you |
| 38 | +* we make improvements or other changes to the Epidata API service |
| 39 | +* the API service experiences an outage |
| 40 | +* your API key is about to expire |
| 41 | +* your API usage becomes excessive or abnormal |
| 42 | +* a voluntary survey of our users, but no more than once every 6 months |
| 43 | + |
| 44 | +We store the mapping from tokens to email addresses in a location separate from |
| 45 | +server logs, using security measures consistent with our internal information |
| 46 | +security practices to help us keep your information secure. We only retrieve |
| 47 | +this mapping to resolve cases of excessive or abnormal usage. We automatically |
| 48 | +disassociate an email address from its API key when the API key has not been |
| 49 | +used for six months, or upon user request. You can request that your |
| 50 | +email address be removed from our records by filling out a |
| 51 | +[deletion request](https://forms.gle/GucFmZHTMgEFjH197). |
| 52 | + |
| 53 | +For more information, see |
| 54 | +[Carnegie Mellon’s privacy notice](https://www.cmu.edu/legal/privacy-notice.html). |
| 55 | +Further questions can be directed to [email protected]. |
0 commit comments