API Use Policy
Thank you for using the Mailchimp application program interfaces (“APIs”). By accessing the APIs, you agree to this API Use Policy (the “Policy”) and our Terms. Mailchimp has open APIs that you can access at https://mailchimp.com/developer/ and https://mandrillapp.com/api/docs/. We provide these APIs to allow people to build on and benefit from our Service by creating software, services, or modules that connect to our platform or have access to the data within our platform via our APIs (an “Integration”). This Policy is and will be treated as part of our Terms. Capitalized terms used and not otherwise defined in this Policy have the meanings given to them in our Terms.
You’ll only access the API using OAuth or an API key. If you have an Integration, then users must have the option to log in via OAuth or their API key. You won’t prompt users to provide their Mailchimp username, password, or security questions.
2. Permitted Use
You will implement and maintain appropriate technical and organizational security measures to protect and to preserve the security, integrity and confidentiality of the data of your users. These security measures shall prevent the unauthorized access or disclosure of personal or confidential data that you process. You must promptly report any security deficiencies or security incidents that may impact or compromise our users, APIs, or Service in writing to email@example.com. And, if there is a security incident, you will work with us to immediately correct the incident or deficiency.
We reserve the right to review or audit your books, records, agreements, access logs, third-party audit and examination reports, systems, networks, facilities (including physical and remote access to data centers and cloud facilities), controls, policies and procedures related to your Integration to ensure compliance with this Policy. You will promptly correct any security flaws or deficiencies. Upon remediation, you will certify in writing that you are now in compliance.
We grant you a non-exclusive, non-transferable, non-sublicensable, revocable, limited right to access and use the APIs to develop, test and support your Integration and to distribute or allow access to your Integration to users of your service, provided that you comply with this Policy and all applicable laws. You have no right to distribute or allow access to our stand-alone APIs. We may terminate your access to our APIs at any time for any reason.
We own all rights, titles, and interest in the Service and the APIs, including all intellectual property rights, marks, code, and features. You won’t infringe, reverse engineer, or copy our code, design, or content. You will not access our APIs in order to compete with our Service. Any rights not expressly granted by this Policy are withheld, so if you don’t see it here, then it’s not a right we’re giving you. You own all rights, titles, and interest in the Integration, except for the APIs, our marks, and the Service. If you provide feedback about the APIs or the Service, we may copy, modify, create derivative works, display, disclose, distribute, or use that feedback without any obligation to you.
7. Use of Marks
You may only use our name and marks (meaning our logos, mascots, and copyrighted images) according to our Brand Guidelines. You may not alter or remove any proprietary notices in our marks. You won’t use our name or marks in your Integration name or logo, or in any way that implies an endorsement by us (that includes putting your logo on Freddie). If you use our marks to create your logo or name, you’ll immediately assign those rights to us at no expense.
To the maximum extent permitted by law, we provide the APIs as-is. That means we don’t provide warranties of any kind, either express or implied, including but not limited to merchantability and fitness for a particular purpose.
We may update or modify the APIs and this Policy from time to time by posting the changes on this site or notifying you via email. These changes may affect your use of the APIs or the way your Integration interacts with the API. If we make a change that’s unacceptable to you, you should stop using the APIs.
You may have access to confidential, proprietary, and non-public information specific to the APIs (“Confidential Information”). You may use this information only to build with the APIs. You won’t disclose the Confidential Information to anyone without our written consent, and you’ll protect the Confidential Information from unauthorized use and disclosure in the same way you’d protect your own confidential information.
You’ll indemnify and hold us and our Team harmless from any losses (including attorney fees) that result from third-party claims that relate to your use of the API.
12. The Rest
Updated May 27, 2020